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 Invoice Factoring and 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

You have 340 overdue invoices in your AR system. Your team has the capacity to personally contact 15 customers per day. Without automation, 325 of those invoices get no outreach this week. Dunning is the automated process that closes that gap — and the difference between a well-designed dunning sequence and a generic one is measured in days of DSO. Dunning is the automated process of sending sequential payment reminders to customers with overdue invoices. The term comes from 17th-century English financial practice, but the concept is fundamental to modern AR: when a payment is past due, the company sends a series of notices — starting with a polite reminder and escalating in urgency — designed to prompt payment without damaging the customer relationship. Dunning sequences are time-based: they trigger at defined intervals after the invoice due date (day 3, day 10, day 20, day 30) and typically combine multiple channels — email primarily, sometimes SMS or automated phone calls. The sequence ends when the invoice is paid, when the customer disputes the invoice and the dunning pauses for resolution, or when the balance escalates beyond the dunning sequence to manual collections. Dunning is the automation layer that ensures every overdue invoice gets systematic outreach regardless of team capacity. Without it, collections is limited by headcount. With it, headcount focuses on the exceptions — high-balance accounts, complex disputes, customers who don't respond to automated outreach — while the automated sequence handles the volume.

How dunning sequences work — and what makes an automated sequence effective vs ignored

A dunning sequence is defined by its timing, channels, message content, and escalation logic. Timing determines when each notice goes out relative to the invoice due date. A typical B2B sequence might send a gentle reminder at day 3, a more direct follow-up at day 10, a firm notice with payment link at day 20, and a final notice at day 30 before escalating to manual collections. Spacing between notices should reflect realistic customer AP cycles — in B2B, customers typically have weekly or biweekly AP runs, so notices timed only a day apart may not align with when the customer is actually processing payments. Channel selection affects response rates. Email is the default, but for high-balance accounts or customers who have ignored email reminders, adding a direct call or a portal notification increases contact rate. Some AR platforms support multi-channel sequences — email for the first two reminders, automated phone call for the third. Message content matters as much as timing. Generic dunning messages — 'Your invoice is overdue. Please remit payment.' — get lower response rates than messages that include the specific invoice number, amount, due date, and a direct payment link. The easier you make it for the customer to pay in the moment they read the reminder, the higher the payment rate. Message tone should escalate: friendly reminder, then direct request, then formal notice with consequence language. Content that escalates in urgency at the same pace as the timing escalation reinforces the seriousness of the outstanding balance.

How dunning interacts with dispute resolution, customer segments, and payment plan negotiations

Dunning sequences need to pause when a customer enters a dispute. An automated reminder sequence that continues sending payment demands while a customer has an open dispute frustrates customers, signals that the company isn't listening, and can escalate a resolvable billing disagreement into a relationship problem. Well-configured dunning systems have a dispute flag that pauses the sequence for the specific invoice until the dispute is resolved. The challenge is ensuring that dispute flags are actually applied — that when a customer calls to dispute an invoice, the AR team logs it in the system rather than handling it outside the dunning workflow. Customer segmentation also matters for dunning effectiveness. A single dunning sequence applied to all customers doesn't account for the fact that a Fortune 500 customer with complex AP processes behaves differently than a small business customer. Enterprise customers may legitimately need longer to process invoices through internal approvals; sending aggressive dunning at day 5 creates friction without accelerating payment. Segmented sequences — by customer size, by payment terms, by historical payment behavior — produce better outcomes than one-size-fits-all automation. Payment plan negotiations represent a specific dunning edge case. When a customer can't pay in full, a structured payment plan with defined installments may be better than continued dunning against the full balance. AR platforms that support payment plan creation — installment schedules tied to the original invoice, with dunning adjusting to the installment due dates rather than the original invoice due date — give collections teams a structured option that pure dunning sequences don't provide.

How AR platforms implement dunning sequences — what customization vs out-of-the-box templates actually looks like

Virtually every AR platform includes some form of dunning. The meaningful differences are in the depth of customization and the logic sophistication. Out-of-the-box templates provide a starting point — pre-written email templates, default timing intervals, standard escalation paths. For companies with straightforward AR and homogeneous customer bases, standard templates may be adequate. For companies with diverse customer segments, complex payment terms, or high dispute rates, customization is essential. What to probe in a platform evaluation: Can you build multiple dunning sequences and assign them to customer segments, or is there one global sequence? Can the sequence be paused at the invoice level when a dispute is flagged, and does that pause require manual action or happen automatically? Can message content be personalized beyond invoice number and amount — pulling in account manager name, preferred payment method, or customer-specific payment portal links? Does the platform track dunning effectiveness — open rates, payment rates by sequence step, average days-to-pay by sequence type — so you can optimize the sequence based on what actually works? Can the sequence branch based on customer behavior — sending a follow-up call task if an email went unopened for three days? These customization layers separate AR platforms that do dunning from those that have thought through what makes dunning actually work.

Questions to ask when designing or evaluating a dunning process

• Are dunning sequences segmented by customer type, payment terms, or balance size — or is there one sequence for all customers?
• Does the dunning sequence automatically pause when an invoice is flagged as disputed, or does it require manual intervention?
• What channels does the dunning sequence support beyond email, and can multi-channel steps be configured based on prior response?
• Does each dunning notice include a direct payment link tied to the specific invoice — or does it only reference the invoice number?
• How does the sequence handle partial payments — does it update to dun for the remaining balance, or continue with the original amount?
• What reporting exists to measure dunning effectiveness — payment rates by sequence step, average days-to-collect by segment?

How dunning sequences fail when they're configured once and never revisited

The most common dunning mistake is applying the same sequence to all customers regardless of account size or relationship. A $300K enterprise customer receiving the same automated email as a $2,000 small business customer is a relationship misstep — enterprise customers expect and deserve human engagement, not automated notices. The sequence logic should route large-balance accounts to manual collections outreach faster, not run them through the full automated sequence. The second mistake is continuing dunning on disputed invoices. When the AR system doesn't have a mechanism to flag invoices as disputed and pause the sequence, customers receive increasingly urgent automated payment demands while simultaneously communicating a dispute to the AR team via phone or email. This contradiction signals internal disorganization and escalates disputes that could be resolved with a single coordinated outreach.