Dunning

Dunning matters because finance software evaluations usually slow down when teams use the term loosely. This page is designed to make the meaning practical, connect it to real buying work, and show how the concept influences category research, shortlist decisions, and day-two operations.

Definition

The practice of sending structured, escalating payment reminders to customers with overdue invoices — progressing from friendly nudges to formal demands based on how far past due the balance is.

Dunning is usually more useful as an operating concept than as a buzzword. In real evaluations, the term helps teams explain what a tool should actually improve, what kind of control or visibility it needs to provide, and what the organization expects to be easier after rollout. That is why strong glossary pages do more than define the phrase in one line. They explain what changes when the term is treated seriously inside a software decision.

Why Dunning is used

Teams use the term Dunning because they need a shared language for evaluating technology without drifting into vague product marketing. Inside ar automation software, the phrase usually appears when buyers are deciding what the platform should control, what information it should surface, and what kinds of operational burden it should remove. If the definition stays vague, the shortlist often becomes a list of tools that sound plausible without being mapped cleanly to the real workflow problem.

These terms matter when buyers need cleaner language around cash collection, payment matching, and customer-account follow-up.

How Dunning shows up in software evaluations

Dunning usually comes up when teams are asking the broader category questions behind ar automation software software. Teams usually compare AR automation platforms on collections workflow, cash application support, dispute visibility, customer portal quality, and the reporting needed to manage cash performance. Once the term is defined clearly, buyers can move from generic feature talk into more specific questions about fit, rollout effort, reporting quality, and ownership after implementation.

That is also why the term tends to reappear across product profiles. Tools like BILL, HighRadius, Upflow, and Versapay can all reference Dunning, but the operational meaning may differ depending on deployment model, workflow depth, and how much administrative effort each platform shifts back onto the internal team. Defining the term first makes those vendor differences much easier to compare.

Example in practice

A practical example helps. If a team is comparing BILL, HighRadius, and Upflow and then opens Airbase vs BILL and Upflow vs Versapay, the term Dunning stops being abstract. It becomes part of the actual shortlist conversation: which product makes the workflow easier to operate, which one introduces more administrative effort, and which tradeoff is easier to support after rollout. That is usually where glossary language becomes useful. It gives the team a shared definition before vendor messaging starts stretching the term in different directions.

What buyers should ask about Dunning

A useful glossary page should improve the questions your team asks next. Instead of just confirming that a vendor mentions Dunning, the better move is to ask how the concept is implemented, what tradeoffs it introduces, and what evidence shows it will hold up after launch. That is usually where the difference appears between a feature claim and a workflow the team can actually rely on.

• Is the biggest problem collections execution, cash application, disputes, or customer payment visibility?
• How well does the product fit the ERP and banking setup that drives receivables operations?
• Will the workflows help collectors prioritize effort more intelligently as volume grows?
• How much faster will leadership get usable visibility into overdue balances and collection trends?

Common misunderstandings

One common mistake is treating Dunning like a binary checkbox. In practice, the term usually sits on a spectrum. Two products can both claim support for it while creating very different rollout effort, administrative overhead, or reporting quality. Another mistake is assuming the phrase means the same thing across every category. Inside finance operations buying, terminology often carries category-specific assumptions that only become obvious when the team ties the definition back to the workflow it is trying to improve.

A second misunderstanding is assuming the term matters equally in every evaluation. Sometimes Dunning is central to the buying decision. Other times it is supporting context that should not outweigh more important issues like deployment fit, pricing logic, ownership, or implementation burden. The right move is to define the term clearly and then decide how much weight it should carry in the final shortlist.

Related terms and next steps

If your team is researching Dunning, it will usually benefit from opening related terms such as Accounts Receivable, AR Aging Report, Bad Debt Write-Off, and Cash Application as well. That creates a fuller vocabulary around the workflow instead of isolating one phrase from the rest of the operating model.

From there, move into buyer guides like What Is AR Automation? and then back into category pages, product profiles, and comparisons. That sequence keeps the glossary term connected to actual buying work instead of leaving it as isolated reference material.

Additional editorial notes

What is dunning?

Dunning is the systematic process of communicating with customers about overdue payments through a series of increasingly firm reminders. The term originates from the word 'dun' — to make persistent demands for payment. A dunning sequence typically starts with a polite reminder shortly after the due date and escalates through progressively more urgent notices over 30, 60, and 90 days. In modern AR automation, dunning sequences are automated: the system sends the right message at the right time based on how long the invoice has been overdue, the customer's payment history, and the balance amount.

Why dunning automation matters for software buyers

Without automated dunning, payment reminders either do not get sent (the AR team is too busy) or they get sent inconsistently (some customers get follow-ups, others do not). Both outcomes directly increase DSO and bad debt. Automated dunning ensures every overdue invoice gets the appropriate follow-up without requiring manual effort. The AR team's time shifts from writing and sending reminder emails to handling the responses — disputes, payment plans, and escalations.

The evaluation differentiator is customization depth. Basic dunning sends the same email to every customer at the same intervals. Sophisticated dunning lets you create different sequences by customer segment (enterprise clients get white-glove treatment, small accounts get automated sequences), by invoice size (a $500 invoice gets emails only, a $50,000 invoice triggers a phone call task at 15 days), and by payment history (chronically late payers get shorter intervals between contacts).

How dunning works in practice

A typical automated dunning sequence: Day 1 past due — friendly email reminder ('Just a heads up, Invoice #1234 was due yesterday'). Day 7 — second reminder with invoice attached and payment link. Day 15 — more direct email requesting payment status and offering to discuss any issues. Day 30 — formal notice that the account is 30 days past due with a statement of all open invoices. Day 45 — notice that the account is under review and may be placed on credit hold. Day 60 — final demand before escalation. Each email includes the invoice details, outstanding amount, and a direct link to pay online. The system logs every communication and tracks open rates and response rates to optimize timing and messaging.

Example: Automated dunning recovering $380K in overdue receivables

A professional services firm with 650 active clients had $1.9M in receivables over 30 days past due. The controller was the only person sending payment reminders — inconsistently, maybe 20 emails per week out of 180 that needed attention. After implementing automated dunning with a 6-touch sequence over 60 days, 68% of overdue invoices were paid after the first or second automated reminder alone. Within 90 days, past-due receivables dropped from $1.9M to $780K. The controller estimated that recovering even half of that $1.1M reduction through manual follow-up would have required a dedicated AR specialist costing $65K per year.

What to check during software evaluation

• Can you create multiple dunning sequences for different customer segments or invoice types?
• Does the system support multi-channel dunning (email, SMS, in-app notifications)?
• Can dunning be paused automatically when a customer has an open dispute or payment plan?
• Does the platform track dunning effectiveness — which messages drive the most payments?
• Can the system escalate from automated dunning to a manual collections task when thresholds are reached?