Skip to main content

Concepts

The Dunning glossary on a single page. Terms appear exactly as they do in the interface.

Portfolio

  • Customer — the person (individual or company) who owes. Carries a document (CPF/CNPJ), emails, phone numbers, addresses, tags, notes, and custom data. It is the central record: charges, agreements, and notifications always point to a customer.
  • Classification — the customer's payer-profile label (for example: New, Good, Regular, or Bad payer). It can be assigned manually or automatically, based on payment history. Collection rules can be associated with classifications.
  • Tags — free-form labels to organize and filter customers and charges.
  • External ID (external_id) — the record's identifier in your system (ERP, spreadsheet, CRM). It is the deduplication key for imports and integrations: if Dunning finds the same external_id, it updates instead of duplicating.

Charge

  • Charge — a receivable: amount, due date, customer, and status. It is born Pending, becomes Overdue once the due date passes, and ends up Paid, Cancelled, Written off, or in one of the legal states. See the full lifecycle.
  • Original Amount / Current Amount — the amount at issuance and the amount owed today (original + interest + fine − discount).
  • Days Overdue — how many days have passed since the due date of an unpaid charge. Recalculated daily.
  • Source — where the charge came from: manual, spreadsheet, API, ERP, or Kobana. See Sources.

Rule

  • Collection Rule — the automatic sequence of steps that runs for each charge: a reminder before the due date, a notice on the day, collection messages afterwards. A rule can be marked as Default: charges created without an explicit rule enroll in it.
  • Step — one stage of the rule, with a trigger (for example, 3 days after the due date), a channel (email, SMS, WhatsApp), and an action (notification, agreement offer, manual task, among others).
  • Rule version — when a charge enrolls in a rule, it is pinned to a snapshot of the steps at that moment. Editing the rule later does not change charges already enrolled in it.
  • Execution (of the engine) — the record of each step evaluated for a charge: scheduled, sent, delivered, suppressed, and why. It appears in the charge detail view, under Engine executions.
  • Template — the message template used by a step, with interpolated variables (customer name, current amount, due date).
  • Suppression — a recorded contact block (opt-out, "that's not me", dispute, among others). Suppression overrides any rule step: the message does not go out and the reason is recorded.

Negotiation and exceptions

  • Agreement — an installment plan for the debt with a discount, accepted by the operator or by the debtor on the portal. An accepted agreement pauses the rule.
  • Dispute — a challenge raised by the debtor ("I already paid", "I don't recognize this", "wrong amount"...). Opening a dispute pauses the rule immediately; the decision (upheld or dismissed) resumes or closes the charge.
  • Credit bureau registration / Protest — legal actions that always go through human review before taking any effect.
  • Legal hold — a block on the charge that prevents steps incompatible with its legal situation.

Communication and access

  • Notification — each message sent (or suppressed) to a debtor, with channel, recipient, delivery status, and cost.
  • Debtor Portal — the secure page where the debtor views their debts, simulates and accepts agreements. The operator generates the link via the Portal Link button on the customer record; the debtor confirms the last 4 digits of their document before seeing any amounts.
  • Task — an item in the operators' work queue: proof-of-payment verification, credit bureau registration approval, manual follow-up.