What is dunning in simple terms?

Dunning is the systematic process of communicating with customers to recover overdue or failed payments. In a subscription business, when a recurring card charge is declined, dunning kicks in: the system retries the charge on a smart schedule and sends a sequence of reminders asking the customer to fix or update their payment method. The goal is to recover revenue that would otherwise be lost silently and to keep the customer subscribed. Lightbridge ERP treats dunning as a core part of the recurring-revenue billing process, not an afterthought bolted on at the end.

What is dunning management and why does it matter?

Dunning management is the discipline of designing, running, and tuning the dunning process: the retry schedule, the communication sequence, the grace periods, and the escalation rules. It matters because failed card payments are a leading cause of involuntary churn, the unintended loss of customers who never meant to cancel. A meaningful share of recurring-revenue cancellations trace back to a card that simply expired or temporarily declined. Strong dunning management recovers a large portion of those payments, so it protects revenue the business already earned. Lightbridge ERP designs dunning management around both recovery rate and customer experience, so the process recovers money without alienating good customers.

How does the dunning process reduce involuntary churn?

Involuntary churn is churn caused by payment failure rather than a deliberate cancellation, and the dunning process exists to recover those accounts before they lapse. The process works in layers: pre-dunning prevents failures by flagging expiring cards early, smart retry logic re-attempts soft declines at the moments most likely to succeed, and a timed communication sequence prompts the customer to update a failed payment method. Because a recovered payment keeps an existing customer, the revenue impact compounds across the customer lifetime. Lightbridge ERP frames dunning as churn prevention first and collections second, because keeping a paying customer is worth far more than a single recovered invoice.

What is the difference between dunning and pre-dunning?

Dunning reacts to a payment that has already failed: it retries the charge and chases the customer to resolve it. Pre-dunning acts before the failure happens, reminding customers that a card is expiring, an invoice is about to bill, or a payment method needs attention. Pre-dunning is the most efficient part of failed payment recovery because preventing a decline takes less effort and causes less disruption than recovering from one. A complete dunning process runs both: pre-dunning to shrink the failure rate, then dunning to recover the failures that still occur. Lightbridge ERP builds both stages into the billing design rather than treating pre-dunning as optional.

How does failed payment recovery fit into the billing system?

Failed payment recovery is one stage of a larger recurring-revenue flow that runs from quote to cash. Subscriptions are priced and contracted, invoices are generated on a billing schedule, charges are attempted against a stored payment method, and dunning handles the charges that fail. Recovered payments then flow back into revenue recognition and reporting. Because dunning sits between billing and the books, its design affects collections, deferred revenue timing, and churn metrics at once. See the subscription billing models guide for how recurring invoices are structured and the quote-to-cash guide for the end-to-end flow that dunning lives inside.

How does NetSuite handle dunning and recurring billing?

NetSuite supports dunning and recurring billing through its billing and subscription capabilities, including configurable retry and reminder behavior for failed charges. As a neutral example of how a platform implements the concept, NetSuite SuiteBilling manages subscription billing schedules and renewals, while advanced revenue management governs how recovered and recognized revenue posts under the applicable standard. Lightbridge ERP delivers NetSuite in-house, so it can configure dunning, billing, and revenue recognition together. See how NetSuite does this in the SuiteBilling guide and the advanced revenue management guide. The dunning concept itself is platform-neutral, and Lightbridge advises on it across systems.

Does dunning change how revenue is recognized?

Dunning affects when cash is collected, not the underlying rules for when revenue is earned. Under ASC 606, revenue is recognized as performance obligations are satisfied, following a five-step model, and amounts billed but not yet earned sit as a contract liability, commonly shown as deferred revenue, until the obligation is satisfied. A failed-then-recovered payment changes the timing and certainty of collection and may affect reserves for uncollectible amounts, but it does not by itself change the period in which a subscription is earned. This is general information, not accounting, tax, or legal advice. Lightbridge ERP, whose team includes CPAs and controllers, helps organizations connect dunning, billing, and revenue recognition correctly for their own facts.

How do you configure dunning in NetSuite?

In NetSuite, the Dunning Letters SuiteApp automates dunning through three record types. A dunning procedure is the escalation path assigned to a customer. Dunning levels are the stages within it, each keyed to a Days Overdue threshold and a letter template. Dunning templates hold the message, with merge fields for personalization and a PDF layout for print or email. Per Oracle NetSuite documentation, a procedure can hold up to 15 levels, later levels must sit further past due than earlier ones, and the Days Overdue field accepts negative values from -1 to -99 so a level can send a reminder before the invoice is even due. A scheduled evaluation workflow then processes open, posting invoices that have aged into a level and generates the letters. Lightbridge ERP delivers NetSuite in-house and sets these thresholds to match the collections policy rather than a default.

JH Written by Jully Hayasaka with Robert LabardeeNetSuite Advanced Accounting Lead and Founder and CEO

What is dunning?

Lightbridge ERP defines dunning as the systematic process of communicating with customers to recover overdue or failed payments. In subscription businesses, dunning management retries declined card charges and sends a sequence of reminders, turning silent payment failures into recovered revenue and protecting recurring billing relationships from involuntary churn.

Recurring-revenue advisory The quote-to-cash flow

Dunning is the systematic recovery of overdue and failed payments.

Dunning is the structured process of communicating with customers to recover payments that are overdue or have failed. The word predates software billing: it once meant persistently asking a debtor to pay. In a modern subscription business, dunning is mostly automated, because the typical failure is not a customer refusing to pay but a recurring card charge that simply declined.

That distinction matters. Most recurring-revenue payment failures are accidental: an expired card, a temporary hold, a hit transaction limit. The customer still wants the service and does not even know the charge failed. Dunning closes that gap by retrying the charge and prompting the customer to act, recovering revenue the business already earned. For the broader picture, the subscription billing models guide explains how recurring invoices are generated in the first place.

Lightbridge ERP is an independent, vendor-neutral ERP advisory firm. It treats dunning as a designed part of the recurring-revenue billing process, not a default left untouched, because the rules that govern retries and reminders directly affect both recovered revenue and customer trust.

The dunning process runs in stages, from prevention to escalation.

A mature dunning process is not a single reminder email. It is a sequence of stages that starts before a payment can fail and ends with a deliberate decision about accounts that never recover. Each stage has a distinct job, and tuning them together is the work of dunning management.

Pre-dunning

Outreach before a charge fails: reminders that a card is expiring, an invoice is about to bill, or a payment method needs updating. Pre-dunning prevents a failure rather than reacting to one, which makes it the highest-return step in any dunning process.

Smart retry logic

Failed charges are retried on a schedule tuned to decline reasons and issuer behavior, not a fixed daily attempt. Retrying an insufficient-funds decline near payday, for example, recovers more than an immediate re-charge.

Dunning communications

A timed sequence of emails, in-app notices, and optional SMS that tell the customer a payment failed and how to fix it. Tone and cadence escalate as the overdue period lengthens, while keeping the relationship intact.

Account state and escalation

Rules that govern grace periods, soft suspension, and final cancellation when recovery fails. The dunning process decides when to keep retrying, when to pause service, and when to write the account off.

Dunning management depends on why a payment failed.

Effective failed payment recovery starts by classifying the decline. A charge that failed for a temporary reason should be retried, while a charge that failed permanently should route straight to a request for a new payment method. Treating every failure the same wastes retries and irritates customers, so the decline reason drives the response.

Soft declines

Temporary failures such as insufficient funds, a transaction limit, or a transient processor error. Soft declines are the core of dunning management because a later retry often succeeds without the customer doing anything.

Hard declines

Permanent failures such as a closed account, a reported-stolen card, or a card flagged as invalid. Hard declines will not recover on retry, so dunning routes them straight to a request to update the payment method.

Expired cards

A common, fully preventable cause of failed payments. Card-account updater services and expiry-aware pre-dunning catch most of these before the charge ever fails, which is why expiry handling sits at the front of a strong dunning process.

Smart dunning recovers more by tuning retries and reminders to behavior.

Smart dunning, also called automated dunning, replaces a fixed retry schedule and a generic reminder with logic that responds to the situation. It retries soft declines at moments more likely to clear, such as near a typical payday for an insufficient-funds failure, and it stops retrying hard declines that will never recover. It varies the communication cadence by customer and by how overdue the payment is, and it hands off cleanly to a payment-update flow when the card itself is the problem.

The payoff is a higher recovery rate with fewer wasted attempts and less customer friction, which is why smart dunning is now standard in serious recurring-revenue operations. The configuration still has to match the business: retry timing, grace periods, and escalation rules differ for a consumer app and an enterprise contract. Lightbridge ERP tunes these rules to the operating model rather than accepting a platform default, so dunning recovers revenue without eroding the relationship.

Dunning sits between billing and the books in the recurring-revenue flow.

Dunning is one stage of a larger flow that runs from quote to cash. Subscriptions are priced and contracted, invoices are generated on a billing schedule, charges are attempted against a stored payment method, and dunning handles the charges that fail. Recovered payments then flow into revenue recognition and reporting. Because dunning sits between billing and the general ledger, its design touches collections, churn metrics, and the timing of recognized revenue at once. The quote-to-cash guide maps the full sequence dunning lives inside.

Commercial billing platforms implement dunning differently, and Lightbridge names them only as neutral examples. NetSuite, for instance, manages recurring billing and renewals through SuiteBilling and governs recognized revenue through advanced revenue management. See how NetSuite does this in the SuiteBilling guide, the advanced revenue management guide, and the CPQ guide for how quotes feed billing. The dunning concept itself is platform-neutral, and Lightbridge ERP advises on it across systems.

Dunning changes the timing of cash, not the rules for earning revenue.

It is worth separating two questions that dunning often blurs: when cash is collected and when revenue is earned. Dunning affects the first. Under ASC 606, the revenue standard the FASB issued with the IASB as IFRS 15 (ASU 2014-09, published at asc.fasb.org), revenue is recognized through a five-step model: identify the contract, identify the performance obligations, determine the transaction price, allocate it to the obligations, and recognize revenue as those obligations are satisfied. ASC 606 superseded most of the legacy ASC 605 guidance and most industry-specific revenue rules.

For a subscription, amounts billed but not yet earned sit as a contract liability, commonly presented as deferred revenue, and convert to revenue as the service is delivered. A payment that fails and is later recovered changes the timing and certainty of collection, and may affect reserves for uncollectible amounts, but it does not by itself move the period in which the subscription is earned. This is general information, not accounting, tax, or legal advice. Lightbridge ERP, whose team includes CPAs and controllers, helps organizations connect dunning, billing, and revenue recognition correctly for their own facts.

Lightbridge ERP configures dunning in NetSuite through procedures, levels, and templates.

The dunning concept is platform-neutral, but the configuration is concrete. In NetSuite, the Dunning Letters SuiteApp automates the accounts-receivable side of the process: it evaluates open, overdue invoices on a schedule and generates letters or emails against a defined escalation path. Per Oracle NetSuite documentation, three record types carry the design. A dunning procedure is the escalation path assigned to a customer. Dunning levels are the stages within it, each keyed to a days-overdue threshold and a letter template. Dunning templates hold the message itself, with merge fields for personalization and a PDF layout for print or attachment.

Each dunning level sets a Days Overdue value that governs when its letter can be sent, and later levels must sit further past due than earlier ones. NetSuite documents a maximum of 15 levels per procedure. A useful detail: the Days Overdue field accepts negative values, from -1 to -99, so a level set to -3 sends a reminder three days before the invoice is due. That is pre-dunning built into the same escalation, a way to shrink the failure rate before an invoice ever ages, which the subscription billing models guide connects to how the recurring invoices are generated in the first place.

Eligibility is scoped deliberately. NetSuite evaluates only open, posting invoices that have reached a level's days-overdue threshold, against customers whose records carry an assigned dunning procedure. Customers, invoices, and invoice groups can be excluded from a run, so disputed items and accounts under a payment arrangement stay out of the sequence rather than receiving an escalating letter by accident. Lightbridge ERP, which delivers NetSuite in-house with NetSuite-certified engineers on staff, sets these thresholds and exclusions to match the collections policy instead of an out-of-the-box default.

Running NetSuite dunning well is a matter of scheduling, exclusions, and audit trail.

NetSuite runs dunning two ways: a scheduled evaluation workflow that processes accounts automatically, or a manual generate-dunning-letters action for a chosen set of customers and dates. The evaluation reads each customer's last-sent date and current dunning level, then decides whether the account has aged into the next level. A minimum dunning interval on the procedure caps how often two consecutive letters reach the same customer, which prevents over-contacting an account but also means a same-day correction after a run has to be handled deliberately rather than by firing another letter immediately.

One scheduling detail matters for any organization operating outside the workflow's default time zone: an evaluation timed without accounting for that offset can run on the prior calendar day and skip invoices expected to be picked up. The practical fix is to align each subsidiary's scheduled evaluation to local business hours so reminders land at the start of the customer's day. For example, a company with two subsidiaries in different regions would schedule a separate evaluation per region rather than a single global run. Every generated letter is retained as a PDF record, which gives A/R a clean audit trail of what was sent and when.

The best-practice line is consistent with the concept above: dun by reason and by aging, not by brute force. Keep templates specific and courteous, exclude disputes and payment plans, and treat the schedule as a control point rather than a set-and-forget job. A faster, more accurate collections sequence pulls cash in sooner, which is the operational lever behind the days sales outstanding that measures how long receivables sit before they convert. Lightbridge ERP tunes the NetSuite configuration to the collections policy and, where advanced logic is required, builds it under change control so every manual intervention stays visible for governance.

What is dunning: frequently asked questions

What is dunning in simple terms?: Dunning is the systematic process of communicating with customers to recover overdue or failed payments. In a subscription business, when a recurring card charge is declined, dunning kicks in: the system retries the charge on a smart schedule and sends a sequence of reminders asking the customer to fix or update their payment method. The goal is to recover revenue that would otherwise be lost silently and to keep the customer subscribed. Lightbridge ERP treats dunning as a core part of the recurring-revenue billing process, not an afterthought bolted on at the end.
What is dunning management and why does it matter?: Dunning management is the discipline of designing, running, and tuning the dunning process: the retry schedule, the communication sequence, the grace periods, and the escalation rules. It matters because failed card payments are a leading cause of involuntary churn, the unintended loss of customers who never meant to cancel. A meaningful share of recurring-revenue cancellations trace back to a card that simply expired or temporarily declined. Strong dunning management recovers a large portion of those payments, so it protects revenue the business already earned. Lightbridge ERP designs dunning management around both recovery rate and customer experience, so the process recovers money without alienating good customers.
How does the dunning process reduce involuntary churn?: Involuntary churn is churn caused by payment failure rather than a deliberate cancellation, and the dunning process exists to recover those accounts before they lapse. The process works in layers: pre-dunning prevents failures by flagging expiring cards early, smart retry logic re-attempts soft declines at the moments most likely to succeed, and a timed communication sequence prompts the customer to update a failed payment method. Because a recovered payment keeps an existing customer, the revenue impact compounds across the customer lifetime. Lightbridge ERP frames dunning as churn prevention first and collections second, because keeping a paying customer is worth far more than a single recovered invoice.
What is the difference between dunning and pre-dunning?: Dunning reacts to a payment that has already failed: it retries the charge and chases the customer to resolve it. Pre-dunning acts before the failure happens, reminding customers that a card is expiring, an invoice is about to bill, or a payment method needs attention. Pre-dunning is the most efficient part of failed payment recovery because preventing a decline takes less effort and causes less disruption than recovering from one. A complete dunning process runs both: pre-dunning to shrink the failure rate, then dunning to recover the failures that still occur. Lightbridge ERP builds both stages into the billing design rather than treating pre-dunning as optional.
What is smart dunning or automated dunning?: Smart dunning, also called automated dunning, replaces fixed daily retries and generic reminders with logic tuned to why a payment failed and how the customer behaves. It distinguishes soft declines, which often recover on a later retry, from hard declines, which never will, and it schedules retries at moments more likely to succeed, such as near a typical payday for an insufficient-funds decline. It also personalizes the communication cadence and stops retrying once a charge clearly will not recover. The aim is a higher recovery rate with fewer wasted attempts and less customer friction. Lightbridge ERP configures smart dunning inside the billing platform so the rules match the business, not a vendor default.
How does failed payment recovery fit into the billing system?: Failed payment recovery is one stage of a larger recurring-revenue flow that runs from quote to cash. Subscriptions are priced and contracted, invoices are generated on a billing schedule, charges are attempted against a stored payment method, and dunning handles the charges that fail. Recovered payments then flow back into revenue recognition and reporting. Because dunning sits between billing and the books, its design affects collections, deferred revenue timing, and churn metrics at once. See the subscription billing models guide for how recurring invoices are structured and the quote-to-cash guide for the end-to-end flow that dunning lives inside.
How does NetSuite handle dunning and recurring billing?: NetSuite supports dunning and recurring billing through its billing and subscription capabilities, including configurable retry and reminder behavior for failed charges. As a neutral example of how a platform implements the concept, NetSuite SuiteBilling manages subscription billing schedules and renewals, while advanced revenue management governs how recovered and recognized revenue posts under the applicable standard. Lightbridge ERP delivers NetSuite in-house, so it can configure dunning, billing, and revenue recognition together. See how NetSuite does this in the SuiteBilling guide and the advanced revenue management guide. The dunning concept itself is platform-neutral, and Lightbridge advises on it across systems.
Does dunning change how revenue is recognized?: Dunning affects when cash is collected, not the underlying rules for when revenue is earned. Under ASC 606, revenue is recognized as performance obligations are satisfied, following a five-step model, and amounts billed but not yet earned sit as a contract liability, commonly shown as deferred revenue, until the obligation is satisfied. A failed-then-recovered payment changes the timing and certainty of collection and may affect reserves for uncollectible amounts, but it does not by itself change the period in which a subscription is earned. This is general information, not accounting, tax, or legal advice. Lightbridge ERP, whose team includes CPAs and controllers, helps organizations connect dunning, billing, and revenue recognition correctly for their own facts.
How do you configure dunning in NetSuite?: In NetSuite, the Dunning Letters SuiteApp automates dunning through three record types. A dunning procedure is the escalation path assigned to a customer. Dunning levels are the stages within it, each keyed to a Days Overdue threshold and a letter template. Dunning templates hold the message, with merge fields for personalization and a PDF layout for print or email. Per Oracle NetSuite documentation, a procedure can hold up to 15 levels, later levels must sit further past due than earlier ones, and the Days Overdue field accepts negative values from -1 to -99 so a level can send a reminder before the invoice is even due. A scheduled evaluation workflow then processes open, posting invoices that have aged into a level and generates the letters. Lightbridge ERP delivers NetSuite in-house and sets these thresholds to match the collections policy rather than a default.
Can you exclude customers or invoices from a NetSuite dunning run?: Yes. NetSuite dunning evaluates only open, posting invoices that have reached a level threshold, and only for customers whose records carry an assigned dunning procedure. Customers, invoices, and invoice groups can be excluded from a run, which keeps disputed items and accounts under a payment arrangement out of the escalating sequence rather than receiving a reminder by accident. A minimum dunning interval on the procedure also caps how often two consecutive letters reach the same customer. One operational detail matters for global teams: schedule each subsidiary evaluation to its own local business hours, because an evaluation timed without accounting for the workflow time zone can run on the prior calendar day and skip invoices. Every generated letter is retained as a PDF record, giving accounts receivable a clean audit trail. Lightbridge ERP configures these exclusions and schedules to the operating model.

From failed payments to recovered revenue.

When silent payment failures are draining recurring revenue, Lightbridge ERP designs dunning, billing, and revenue recognition to work together, vendor-neutral by design and in-house where NetSuite fits.

Talk to an ERP advisor Explore ERP consulting