Dunning Process for Accounts Receivable Teams

The dunning process is the structured way an accounts receivable team follows up on overdue invoices, payment failures, unresolved disputes, and customers who go quiet after a due date. It is not just reminder emails. For finance, it is a cash control workflow that decides when to remind, investigate, escalate, and stop treating the issue as routine.

That distinction matters because accounts receivable is tied to working capital, customer experience, and reporting accuracy. The Association for Financial Professionals describes accounts receivable as amounts owed for goods or services already delivered, while J.P. Morgan connects receivables management to collections, cash visibility, and liquidity planning. If dunning is informal, finance may not know whether cash is late because the customer forgot, the invoice is wrong, a purchase order is missing, or payment was made but not matched.

What Is in This Article?

• What the dunning process should include
• How to design a practical overdue invoice workflow
• How to separate reminders, disputes, escalations, and payment application
• Which controls and metrics finance teams should track
• Where automation helps without damaging customer relationships

Why the Dunning Process Matters

Late payments rarely have one cause. A customer may be waiting for internal approval, missing remittance details, disputing a line item, changing billing contacts, experiencing cash pressure, or simply ignoring low-priority invoices. A single generic reminder sequence treats all of those cases the same, which is why many collections workflows become noisy but ineffective.

A strong dunning process gives finance teams three things: consistency, visibility, and an audit trail. Every overdue invoice receives the right action, managers can distinguish routine lateness from high-risk accounts, and the record shows what was sent, who responded, what was promised, and why an invoice was escalated or paused.

This is especially important for businesses with project billing, marketplaces, agencies, staffing operations, subscription contracts, or large customer accounts. The more people involved, the easier it is for follow-up to split across inboxes, spreadsheets, and accounting notes.

Dunning Process for Accounts Receivable Teams

The best dunning process starts before an invoice is overdue. Finance should define the due date, customer contact, payment method, purchase order requirement, dispute route, and escalation owner when the invoice is issued.

Use this operating model:

1. Confirm invoice readiness. Check that the invoice has the correct customer entity, billing contact, payment terms, tax details, purchase order, service period, attachments, and payment instructions.
2. Send a pre-due reminder for higher-risk invoices. This is useful for large invoices, new customers, customers with approval-heavy procurement teams, or accounts with prior late payments.
3. Start the first overdue reminder. Keep the tone factual and helpful. Include invoice number, amount, due date, payment link or instructions, and a clear path for disputes.
4. Check for blockers. If the customer replies with a dispute, missing document request, PO issue, or approval delay, route the case instead of continuing automated reminders.
5. Escalate by age and value. A $500 invoice that is two days late should not follow the same path as a $75,000 invoice that is 30 days late.
6. Record promises to pay. Capture the promised payment date, owner, customer contact, and next action if payment does not arrive.
7. Match payment and close the case. Once cash arrives, reconcile it against the invoice, remittance advice, bank deposit, and accounting record. Stripe’s payment reconciliation guidance is a useful reminder that matching payment records to accounting records confirms the transaction is complete.

A Practical Dunning Workflow

The workflow should be simple enough for the team to follow, but specific enough to prevent every exception from becoming a manual judgment call.

Segment Customers Before You Automate

Dunning automation works best when the rules reflect customer context. Segment by invoice amount, account tier, days overdue, payment history, dispute status, contract terms, risk, and relationship owner. A strategic customer may need an account-management touch before formal escalation. A small routine invoice may only need a clean reminder sequence and self-service payment path.

Subscription businesses should also distinguish failed-card recovery from B2B invoice collections. Failed-card dunning focuses on retry timing and payment method updates. B2B invoice dunning usually involves procurement contacts, approval chains, remittance details, purchase orders, and dispute documentation.

Common Dunning Mistakes

• Sending reminders before checking invoice quality. If the invoice is wrong, dunning just accelerates frustration.
• Continuing automated reminders after a dispute is raised. Disputes need routing, evidence, and ownership.
• Using the same tone for every account. Payment pressure should reflect risk, relationship, and agreed terms.
• Leaving sales or account owners out too long. Customer-facing teams often know whether the delay is administrative or strategic.
• Failing to close the loop after payment. Cash that is received but not applied still leaves the invoice looking overdue.

Controls, Compliance, and Metrics

For B2B teams, dunning should stay professional, factual, and documented. If collections involve consumers or regulated debt collection activity, legal requirements may apply. The Consumer Financial Protection Bureau’s debt collection resources show why collection communications need care, though businesses should get legal advice for their specific situation.

Track metrics that show cash impact and workflow quality: days sales outstanding, percentage of invoices overdue, average days past due, promise-to-pay kept rate, dispute rate, response rate, escalation volume, cash application lag, and write-off rate. These metrics show whether collections are improving or reminders are only creating activity.

Where Workhint Fits

Workhint helps teams turn the dunning process into a live operating workflow instead of a spreadsheet checklist. A finance team can use workflow automation software to route overdue invoices, assign follow-ups, capture dispute reasons, notify account owners, escalate high-value invoices, track promises to pay, and keep a record before cash is applied.

The value is not that every customer receives more messages. The value is that finance, operations, and customer-facing teams share the same source of truth about why an invoice is overdue and what should happen next.

FAQ

What is the dunning process?

The dunning process is the structured follow-up workflow used to collect overdue invoices or failed payments. It usually includes reminders, blocker checks, escalation rules, dispute routing, and payment closeout.

Is dunning the same as collections?

Dunning is part of collections. Collections is the broader function of managing overdue receivables, while dunning usually refers to the reminder and escalation process used to recover payment.

When should a dunning process start?

For high-risk or high-value invoices, it should start before the due date with a readiness check. For routine invoices, the first reminder often starts shortly after the due date.

Should dunning be automated?

Routine reminders, routing, owner assignment, and status tracking can be automated. Disputes, strategic accounts, unusual payment delays, and sensitive escalations should still involve human judgment.

Conclusion

A useful dunning process is controlled, contextual, and easy to audit. It helps finance teams collect cash faster, but it also protects customer relationships by separating simple reminders from real blockers. The goal is not to chase every invoice harder. The goal is to know which overdue invoices need a reminder, which need a fix, which need escalation, and which are already paid but waiting for reconciliation.