What Is Dunning? Your 2026 Guide to Invoice Recovery
Discover exactly what is dunning and how a structured process helps you recover unpaid invoices faster in 2026. Get our guide on stages, legal rules, & best
You sent the invoice two weeks ago. The client said accounts payable would “process it soon.” Your project manager is asking whether the next phase should start, payroll is coming up, and now someone on your team is digging through old email threads to figure out whether the client is late, confused, or unhappy with the bill.
That's where most businesses realize they don't have a payment process. They have a memory problem, an inbox problem, and a follow-up problem.
Dunning is the fix. It's the structured process of following up on unpaid invoices or failed payments in a way that gets cash in, surfaces disputes early, and protects the relationship while there's still something worth saving. Done well, it replaces random nudges and awkward check-ins with a repeatable system.
Table of Contents
- The Hidden Cost of Chasing Late Payments
- Dunning Explained Beyond Simple Reminders
- The Four Stages of an Effective Dunning Cycle
- Adapting Your Dunning Strategy for Each Client
- How Automation Supercharges Your Dunning Process
- Staying Compliant and Measuring Success
The Hidden Cost of Chasing Late Payments
Late payment rarely looks dramatic at first. It looks like a bookkeeper sending “just checking in” emails, an account lead forwarding the same invoice twice, or an owner deciding whether to call a client personally because nobody else wants to push.
The direct cost is obvious. Cash comes in late. The hidden cost is worse. Your team spends time reconstructing context that should already be in the receivables process. They ask whether the invoice was sent to the right contact, whether the PO is missing, whether the client disputes hours, or whether nobody followed up at all.
Manual chasing also creates tone problems. One client gets three reminders in a week because two people followed up separately. Another hears nothing for a month because everyone assumes someone else handled it. That inconsistency makes you look disorganized, even when the work itself was strong.
A practical dunning process fixes that by turning collections into a sequence. You decide in advance what happens before due date, right after due date, and when the issue shifts from “probably overlooked” to “something is blocking payment.” If you don't have that structure yet, even a simple invoice tracker template for overdue payment follow-up is better than relying on scattered notes and inbox searches.
Practical rule: If your follow-up depends on who remembers to send it, you don't have a receivables process. You have a recurring fire drill.
For agencies, consultants, and service firms, that matters because payment issues aren't only about money. They're often about missing approvals, misunderstood scope, or invoices that landed with the wrong person. A proper dunning process doesn't just ask for payment. It identifies the blockage and resolves it before the account gets damaged.
Dunning Explained Beyond Simple Reminders
Dunning is often described too narrowly. People hear the term and think it means “send a reminder when an invoice is overdue.” That's incomplete.
It's a structured recovery process. It identifies non-payment, applies a sequence of communications, escalates when needed, and separates ordinary delay from a real exception. In modern finance operations, that sequence can be automated, timed, and adapted to account value or customer behavior.
Where the term comes from
The term comes from the 17th-century English verb “to dun,” which meant demanding repayment of a debt, as explained in TreviPay's guide to the history and meaning of dunning. That origin still matters because it distinguishes dunning from basic billing. Billing sends the invoice. Dunning manages what happens when payment doesn't arrive.
The old version was manual and blunt. The modern version is more disciplined. It can start with polite reminders, move into targeted follow-up, and end with formal escalation or legal action if needed. The purpose hasn't changed. Recover revenue while doing as little relationship damage as possible.
Two very different dunning problems
This is the distinction most articles miss.
In subscription and SaaS, dunning usually means failed payment recovery. A card expires. A charge is declined. A retry schedule starts. The system sends update-payment emails, retries the card, maybe uses account updater services, and tries to stop involuntary churn.
In professional services, the issue often isn't card failure at all. It's dispute, confusion, or internal client process. According to Stripe's resource on subscription-based dunning and payment recovery, 60-70% of AR failures in agencies and consultants stem from billing disputes rather than insufficient funds, and businesses that automate dispute routing within dunning see a 22% higher recovery rate.
That changes how you should work the account.
If a SaaS customer's card fails, the best next action is usually technical and transactional. Retry logic, card update, account notice.
If a consulting client doesn't pay, the best next action is often diagnostic. Ask whether they need revised backup, a corrected billing contact, milestone approval, or an explanation of charges. That's why a good process for following up on an unpaid invoice without escalating too early matters more in services than a generic past-due template.
The fastest way to damage a good client relationship is to treat a valid billing question like deliberate non-payment.
That's the answer to “what is dunning.” It's not one email. It's the operating system for recovering payment, and the workflow should look different depending on whether you're chasing a failed card or resolving a blocked invoice.
The Four Stages of an Effective Dunning Cycle
A strong dunning cycle works because it escalates in steps. It doesn't open with threats, and it doesn't wait too long to get serious. The timing matters.
ResolutAI outlines a structured timeline of pre-dunning at 7–10 days before due, initial dunning at 1–7 days after due, escalation at 15–30 days after, and final action at 30–60+ days. The same source notes that consistent automation can improve DSO by 10–15% in subscription models in the right setup, as described in its breakdown of the dunning timeline and performance impact.
Stage one before the invoice becomes a problem
This is the most underused stage. For service firms, pre-dunning means checking the basics before the due date becomes an overdue problem.
You confirm the invoice reached the right contact. You make sure supporting documents are attached. You verify that the client's AP process, PO requirement, or approval chain hasn't changed.
A simple message works:
Just confirming invoice 1847 was received and is queued for payment on the due date. Let me know if AP needs any backup or a resubmission to a different contact.
That note feels administrative, not confrontational. It prevents a lot of avoidable delay.
Stage two when payment first slips
The first overdue message should assume oversight, not bad intent. Teams often get this wrong by sounding irritated too early.
Keep it short. Restate the invoice number, amount due, original date, and payment options if relevant. For service businesses, add one line that makes it easy to raise a dispute without friction.
Here's the practical goal: get a response. A response gives you information. Silence is what slows collections.
Stage three when a reminder is no longer enough
At this point, email alone often stops working. You then switch channels and ask direct questions.
Call the billing contact. Copy the project sponsor if appropriate. Ask whether the issue is approval, budget timing, a disputed line item, or simple processing delay. If the client has been responsive historically, a firm but respectful note usually works better than sending the same reminder again with “second notice” in the subject line.
For agencies, this stage should also trigger an internal check. Make sure your own team didn't cause the hold with vague line items, unapproved change work, or a missing statement of work reference.
Stage four before collections or service action
This is the point where the account needs a formal decision, not one more casual email. Your next step might be a final demand, service suspension under contract terms, escalation to leadership, or handoff to counsel or collections.
Be precise. State what's outstanding, what prior attempts were made, and what happens next if the balance isn't resolved.
Here's a simple operating table teams can adapt:
| Stage | Timing | Tone | Sample Message Snippet |
|---|---|---|---|
| Pre-dunning | 7–10 days before due | Helpful, confirmatory | “Checking that invoice 1847 was received and scheduled for payment.” |
| Initial dunning | 1–7 days after due | Polite, matter-of-fact | “Invoice 1847 is now overdue. Please confirm payment status or let us know if anything needs review.” |
| Escalation | 15–30 days after due | Direct, solution-focused | “We haven't received payment or an update. Is there a dispute, approval issue, or processing delay we should resolve today?” |
| Final action | 30–60+ days | Formal, controlled | “Unless we receive payment or a resolution plan by [date], we'll move this balance to formal escalation under our agreement.” |
The sequence matters more than the wording. A good dunning cycle feels deliberate. A bad one feels emotional.
Adapting Your Dunning Strategy for Each Client
A flat process creates avoidable mistakes. The same reminder cadence shouldn't apply to a long-term enterprise client, a small new customer, and an account that's late every single month.
The reason is simple. Payment risk isn't only about the invoice. It's about relationship history, account value, dispute likelihood, and how much context the client already has.
High-value clients need a human approach
For high-value accounts, automation should support the process, not replace judgment. Baremetrics notes that industry standards treat accounts at $50,000 or more in annual recurring revenue as high-value enough to justify human intervention and personal outreach during dunning, not email-only recovery, in its guide to modern dunning management practices.
That principle applies beyond SaaS. If a major client owes a meaningful balance, don't hide behind templates. Have the account lead or finance owner call. Ask what's blocked. If the issue is a legitimate dispute, route it to the person who can solve it fast.
Smaller and newer clients fit automation better
For lower-value or newer accounts, consistent automation usually beats ad hoc personal follow-up. The point isn't to be cold. The point is to be reliable.
Use clean reminders, predictable timing, and clear payment instructions. If the client replies with a question, then you shift into a human conversation. Until then, there's no reason to spend senior team time composing custom emails for every routine overdue invoice.
A reminder process should earn the right to become personal. It shouldn't start there for every account.
Chronic late payers need tighter controls
Some clients don't need softer language. They need firmer boundaries.
That might mean shorter follow-up intervals, deposits before new work, milestone billing with approval gates, or pausing deliverables when balances age beyond your threshold. If you keep granting exceptions without changing terms, you train the client to pay on their schedule, not yours.
The practical trade-off is relationship versus predictability. Good clients with one-off issues deserve flexibility. Repeated offenders need a process that protects your cash first.
How Automation Supercharges Your Dunning Process
Teams typically don't struggle because they lack the words for a reminder. They struggle because execution breaks down. Someone forgets to follow up, uses the wrong template, misses a reply that signals a dispute, or sends the same tone to every client regardless of context.
Automation fixes the consistency problem first.
What good automation actually does
At a basic level, software triggers reminders before and after due dates. That's useful, but it's not enough.
A stronger setup does four things well:
- Times communication properly: It sends reminders based on due date, aging, and payment status instead of relying on manual calendar checks.
- Adjusts by account context: It doesn't treat a small first invoice the same way it treats a large long-running balance.
- Routes replies intelligently: If a client asks a billing question, the issue goes to a human who can resolve it instead of sitting inside a shared inbox.
- Creates visibility: Finance and account teams can see what's overdue, what was contacted, and where human action is needed.
That last point matters more than people think. Automation without visibility just sends more messages. Automation with visibility helps you manage risk.
For teams that still send invoices manually, it also helps to tighten the front end. A cleaner send process reduces downstream confusion. This guide on sending an invoice through email clearly and professionally is a good example of the upstream habits that make collections easier later.
Where accounting systems fit
The best dunning setups connect directly to the system of record. That's usually Xero, QuickBooks, Stripe, or an ERP.
In more complex finance environments, SAP S/4HANA handles dunning through Transaction Code F150 as a 3-step process of saving parameters, scheduling the run, and generating dunning notices. Gaurav Consulting's explanation of the SAP S/4HANA dunning procedure shows how rule-based filtering can screen accounts by overdue days, thresholds, and payment deadlines before notices go out.
That's the useful lesson even for smaller firms. Good automation is rule-based. You define who enters the cycle, when they enter, how messages change, and when a human takes over.
A short demo makes the difference easier to see in practice.
What doesn't work is spraying generic reminders at every overdue account and calling that automation. If the workflow can't distinguish between a processing delay, a dispute, and a high-risk account, your team still ends up doing the hard part by hand.
Staying Compliant and Measuring Success
A dunning process can be operationally sound and still create problems if it ignores local rules. This becomes more serious when you work across borders.
Compliance mistakes that slow payment
Compliance isn't just a legal footnote. It affects collections speed. A 2024 Global Payments Compliance Report found that 43% of cross-border B2B firms face delayed collections due to unintentional dunning violations, including cases like not following Germany's “Mahnung” format, as summarized on Wikipedia's overview of the dunning process and cross-border compliance issues).
For practitioners, the takeaway is practical:
- Match the jurisdiction: Consumer and business rules differ, and country-specific requirements can change what a valid notice looks like.
- Control tone and content: Aggressive language, premature legal threats, or sloppy privacy handling can create new problems instead of resolving the old one.
- Document every step: Keep a clear record of notices, replies, disputes, and account decisions.
Good dunning is firm. Compliant dunning is firm within the rules that apply to the customer, the contract, and the country.
The metrics worth watching
The two metrics finance teams usually watch most closely are DSO and CEI.
DSO tells you how long receivables are staying outstanding. CEI tells you how effectively the team collects what became due. Neither metric means much in isolation, so pair them with qualitative review. Look at which disputes repeat, which clients always need human outreach, and which invoice formats trigger questions.
If you only measure “was money eventually collected,” you'll miss the process flaws that keep creating slow pay.
If you're tired of manual chasing, Payment Reminder helps automate payment reminders, adapt follow-up by invoice context, route billing exceptions, and keep you updated with a clear weekly AR summary. It's built for teams that want invoices paid without turning collections into a full-time job.