The short answer: a B2B dunning process is a scheduled series of payment reminders and account decisions after an invoice becomes due. A sound process increases clarity without relying on threats: verify the invoice, reach the right contact, identify disputes, record promises, and escalate by written rules.
“Dunning” can sound aggressive, but the useful version is operational. It answers four questions for every open invoice: what message goes out, when it goes out, who owns the reply, and what event changes the next step. California's State Administrative Manual emphasizes prompt follow-up and written procedures for state agencies. It does not set the schedule for private B2B creditors; the framework below adapts the general recordkeeping principle to a small-business workflow.
Before the first reminder
Do not automate a bad invoice. Confirm the legal customer name, invoice number, balance, agreed due date, purchase-order reference, delivery or acceptance evidence, payment instructions, and correct accounts-payable contact. Check for credits and payments that may not have been applied.
A practical 30-day dunning schedule
This is a hypothetical starting point, not a required legal timeline. Adapt it to your contract, customer segment, invoice size, and staffing.
| Timing | Purpose | Channel | Exit condition |
|---|---|---|---|
| 3–5 days before due | Confirm receipt and remove administrative blockers | Receipt confirmed or issue routed | |
| 1–3 days past due | Friendly reminder with invoice details | Payment date or blocker identified | |
| 7 days past due | Ask for a specific status and date | Email, then call | Documented promise or dispute |
| 14 days past due | Escalate internally and contact a decision-maker | Call plus written recap | Approved plan or management review |
| 21 days past due | State the unresolved balance and next internal step | Formal email or letter | Payment, plan, dispute, or final review |
| 30 days past due | Review whether the account stays internal or moves to another channel | Internal decision | Named owner and dated action |
Worked example: a reminder that should stop
Suppose a $4,800 invoice is due on June 1. A reminder is scheduled for June 8, but the customer replies on June 6 that one line item was billed twice. The account owner should record the disputed line, confirm the supporting purchase order and invoice, and route the correction to the person authorized to issue a credit. The June 8 generic reminder should be suppressed while that review is open.
If the duplicate $800 charge is confirmed, the owner sends a corrected $4,000 balance and an explanation of the credit. If the charge is supported, the owner responds with the relevant record and asks for a specific payment or review date. In either case, the next action comes from the documented facts, not from automatically advancing to the next dunning stage.
Put this into the account log: disputed amount, reason, evidence requested, decision owner, date promised to the customer, resolution, corrected balance, and next follow-up date. The private follow-up planner can help turn those fields into an internal sequence without uploading customer data.
What each message should contain
- The customer and invoice number.
- The original amount, any applied credits or payments, and current balance.
- The agreed due date.
- A copy of the invoice or a secure way to retrieve it.
- Clear payment instructions and the contact for questions.
- One requested action with a reasonable response date.
Keep the tone factual. Avoid claims about consequences you have not verified or actions you do not intend to take. Use the overdue invoice email templates for stage-specific wording and the call script when email does not resolve the account.
Build branches, not just reminders
If the customer says the invoice is wrong
Record the disputed amount and reason, pause automated escalation for that portion, route the evidence to the person who can decide it, and promise a response date. Correct a real error promptly; explain a supported balance with the relevant documents.
If the customer promises a payment date
Record the date, amount, payment method, and person making the promise. Schedule follow-up for the next business day after the promise date. A missed promise is a stronger escalation signal than a generic “past due” label.
If the customer asks for installments
Use a written plan stating the balance, installment amounts, dates, payment method, treatment of new purchases, and what happens after a missed installment. Our payment-plan guide provides a structured checklist.
If the customer is silent
Verify the contact, use more than one appropriate channel, and escalate to a known business contact rather than repeatedly sending the same email to an unattended inbox. Log every attempt.
Controls that prevent dunning mistakes
- Suppression rules: stop automation for verified disputes, payments in transit, credits awaiting approval, or legal holds.
- Contact hygiene: maintain a current billing contact and backup contact separately from the buyer or project lead.
- Single account record: keep reminders, calls, replies, promises, and decisions together.
- Approval thresholds: define who may offer a plan, adjust a balance, suspend service where contractually permitted, or select an outside provider.
- Quality review: sample messages for accurate amounts, respectful wording, functional payment links, and correct recipients.
Measure the process without gaming it
Track more than messages sent. Useful operating measures include invoices reaching each stage, percentage with confirmed receipt, disputes awaiting action, promises kept, unapplied cash, and balances resolved before the final stage. Pair these with aging and DSO, while remembering that a lower DSO can reflect sales mix or seasonality as well as collection performance.
When the sequence should end
Every dunning sequence needs a terminal decision. The account may be paid, corrected, credited, placed on a documented payment plan, written off under approved policy, referred for professional advice, or evaluated for an external provider. Repeating reminders indefinitely is not a decision. Use the escalation framework and the broader unpaid invoice recovery guide to choose the next step.
Editorial review
How this page was prepared
This guide answers a defined operational question, separates general process guidance from legal advice, and links to 2 relevant primary or authoritative sources for verification.
Examples are illustrative, not reported customer outcomes. Advertising does not control our conclusions. Read our editorial and correction standards.