The dunning platform that never forgets — and never collects wrong
Track every charge from due date to payment. Contact at the right time, through the right channel, with the payment method right in the message. Paid? The workflow stops instantly. Disputed? It pauses and logs it. Everything explainable and auditable.
Good collections is a process, not a reminder
Kobana Dunning automates your company's collections end to end: it notifies before, on and after the due date, offers agreements, logs responses and promises, pauses for exceptions, and closes itself out the moment the money comes in.
- Steps by trigger: D-N, day-of, D+N, post-issuance
- Templates with variables by channel, category and tone
- Versioned workflows: changing a workflow never affects charges already enrolled
- Serious actions (credit bureau reporting, protest) always require human review
- Payment confirmed → workflow completed, pending sends suppressed
- “I already paid” → immediate pause + proof request + verification
- Dispute opened or opt-out → corresponding transition happens instantly
- Revalidation milliseconds before every send
- Allowed hours by state, with holidays calculated automatically
- Maximum contacts per day and per week, per person
- Opt-out, dispute, legal hold, death and 7 more suppression types
- Outside the legal window = reschedule, never discard
Everything a collections operation needs
A promise you can verify
No charge forgotten, wrongly repeated, kept alive after payment, or made outside the law — and every action (or non-action) is explainable and auditable. It's not a slogan: it's architecture.
Never collects after payment
Before handing any message to the provider, the system rechecks payment, cancellation, disputes and holds against fresh data straight from the database. If it fails the check, the send is suppressed — and the reason is logged.
Never sends duplicates
Deterministic keys per charge, step and channel. Webhooks deduplicated by idempotency. Single-job queue. A provider retry never turns into a duplicate message.
Never contacts outside the law
State-level contact-hour policies (like Law 15.426/2014 in São Paulo), per-person limits and suppressions are evaluated at send time. Outside the window, the message is rescheduled.
Nothing disappears silently
A failed job goes to the retry queue with the error logged. Every 10 minutes, a reconciliation job compares expected state against the queue — and fixes any drift.
Works with the Kobana gateway — or without it
With the Kobana rail, payment is confirmed in real time via webhook and the workflow stops instantly. In standalone mode, you record payment signals from a PSP, CNAB file or manual entry, each with its own confidence level.
Frequently asked questions
See Dunning in action
A demo with a full portfolio scenario: workflows running, agreements, disputes with SLA and the debtor portal in practice.