Skip to main content

Overview

Dunning is a collection rule system: it follows each charge from due date to payment, contacts the debtor at the right time through the right channel, records the responses, and closes out on its own when the money comes in. The product's promise boils down to this: no charge is forgotten, improperly repeated, kept alive after payment, or pursued outside the law — and every action (or non-action) is recorded and explainable.

In practice, your daily work comes down to three things: keeping the customer portfolio up to date, making sure charges get into the system (manually, by spreadsheet, or through an integration), and handling the exceptions the rule sets aside for human review. Everything else — reminders, pauses due to disputes, and settlement on payment — the engine does on its own.

Dunning dashboard

How the account is organized​

Your operation is structured in four levels:

  1. Organization — your Dunning account. Members, permissions, API keys, and general settings live here.
  2. Workspace — a grouping of companies. Useful for separating different operations or brands within the same account.
  3. Company (creditor) — the legal entity on whose behalf you collect. Portfolio customers belong to the company.
  4. Branch — subdivisions of the company. Every company has a headquarters; additional branches are optional. Charges, rules, classifications, and templates belong to the branch (or to the headquarters, when there are no branches).

You manage this hierarchy on the Structure page in the sidebar menu: create workspaces, companies, and branches, with a name and optional CNPJ. Changes are reflected in the context selector and in outgoing communications.

The context selector​

At the top of the screen sits the context selector: a menu showing the account's workspaces and, within each one, its companies and branches. When you switch context, every screen starts showing data for that slice — customers, charges, metrics. The Headquarters option appears so you can work at the company level, with no branch selected.

If your operation is simple (one company, no branches), you never need to touch this selector: the default context covers everything.

The basic flow​

  1. Register (or import) your customers — individuals or companies, with document, email, and phone number.
  2. Create the charges — amount, due date, and customer. One at a time, by spreadsheet, or through the API.
  3. The rule takes over — each charge automatically enrolls in an active collection rule (the default rule, unless you choose another) and receives the steps at the right time: a reminder before the due date, a notice on the day, progressively firmer messages afterwards. All within the legal contact windows of the debtor's state.
  4. You handle the exceptions — disputes, "I already paid" claims, credit bureau registration, and protest go through human review before taking any effect.

Where to start​