Dunning
Collect overdue receivables, on cadence.
The right reminder, to the right customer, at the right time.
Donnerstag keeps every overdue invoice moving through an approved dunning cadence, sending reminders, escalating levels, logging promises to pay and surfacing only the accounts that need a call.
Part of Accounts Receivable · from overdue balance to collected cash
Accounts grouped by level, with promises tracked.
Every overdue account shows its dunning stage, next contact date and any logged promise to pay.
Running
Account
Level
Overdue
Status
Paid
Promise logged
Escalated
Reminder sent
Paid
What Dunning runs before anyone picks up the phone.
Overdue balances are grouped by risk, matched to the right cadence, and reminders are issued on schedule without a person.
Track aging
Keep every open invoice bucketed by days overdue, so the worklist is always prioritized by risk and value.
Run the cadence
Advance each account through your dunning levels automatically, pre-due, reminders, final notice, on the timing you set.
Send on channel
Issue reminders by email or portal in the customer’s language, using approved templates and tone per level.
Log promises to pay
Capture promised amounts and dates, pause the cadence accordingly and resume automatically if a promise is missed.
Escalate on rule
Route accounts that cross a threshold to a call, a credit hold or a collections owner, within your policy.
Exclude disputes
Automatically hold dunning on invoices under dispute so customers are never chased for contested amounts.
Define your path, from pre-due to escalation.
The ladder below is illustrative. Timing, channel and tone at each level follow your collections policy.
−5 days
Pre-due notice
A courtesy reminder before the due date to prompt on-time payment.
+7 days
Reminder 1
A friendly first reminder once the invoice passes due.
+21 days
Reminder 2
A firmer follow-up referencing the growing balance and terms.
Email · Letter
+45 days
Final notice
A formal notice signalling escalation if unpaid.
Letter
+60 days
Escalation
Credit hold, a collections call or handover per your policy.
Call · Hold
Each level has its own timing, channel and tone. The account advances automatically, until a payment, promise or dispute changes the path.
Three things change the cadence.
The account advances automatically until one of these interrupts it.
Branch · Payment
Cash applied
Cash applied closes the account and stops the cadence automatically.
Branch · Promise to pay
Cadence paused
A logged promise pauses reminders until the promised date, then resumes if unmet.
Branch · Dispute
Dunning held
An invoice under dispute is held out of dunning so the customer is never chased for a contested amount.
Segment and define the strategy.
Not every customer should be chased the same way. Segments carry their own cadence, tone and escalation threshold.
Soft
Strategic accounts
Relationship-first cadence with a manager touch before any hold.
Standard
Standard customers
The default level path on standard timing and templates.
Firm
High-risk / chronic
Accelerated cadence, earlier escalation and tighter credit control.
What reaches a collector.
The cadence handles the routine. What surfaces is the account where judgment changes the outcome.
Broken promise
Commitment missed
A logged promise to pay passed its date without payment arriving.
Resolution:
Escalate a level and route to the account owner with the history attached.
Disputed
Invoice under dispute
The customer is withholding payment pending a dispute or deduction.
Resolution:
Hold the cadence and link the case so collections and dispute stay aligned.
High value
Material exposure
The overdue balance exceeds the threshold where automated reminders are appropriate.
Resolution:
Route to a named owner for a call, with the full position prepared.
No response
Cadence exhausted
The account has moved through every reminder level without a reply.
Resolution:
Escalate to collections or legal per your policy, with the trail preserved.
From overdue balance to collected cash.
Select an action to see what it does, and the authority it runs under.
01
Segment
Group accounts by risk, value and aging.
02
Sequence
Set the reminder levels and their timing.
03
Send
Issue reminders inside the approved boundary.
04
Track
Log responses, promises and payments.
05
Escalate
Raise level, call, or route to collections.
Act on an account
See the whole ledger. Drill to any account.
An overview of collections at operation level, then open to the account, invoices and outreach history behind every figure.
Running
Account
Level
Overdue
Status
Paid
Promise logged
Escalated
Reminder sent
Paid
Keep every account answerable.
Know who owes, how overdue, and what happens next.
Who owes?
The customer and open invoices in dunning.
How overdue?
The aging bucket and days past due.
What level?
The current dunning stage and next action.
What’s been done?
The reminders sent and contact history.
Any promise?
The promised amount and date, if logged.
What’s next?
The scheduled action or escalation.
What Dunning gains
Collections work when the cadence never lapses. These are the outcomes the operation is built to produce.
Collect earlier
A consistent cadence starts before due date and never lapses because the team was busy.
Fewer manual reminders
Routine chasing runs on approved rules, so collectors spend time on accounts that need them.
Promises actually tracked
Commitments are logged with dates and followed up automatically when they slip.
Right tone, right level
Escalation follows your policy rather than whoever happened to send the last email.
Aligned with disputes
Accounts under dispute pause instead of receiving reminders that damage the relationship.
Traceable contact history
Every reminder, response and promise stays attached to the account and the balance.
Disputed balances stay linked.
Where a customer withholds payment over a claim, the deduction case and the collections cadence stay connected.