Invoice collections in NetSuite: How to build a dunning process that actually moves cash

If your accounts receivable (AR) team’s Monday morning starts with exporting an aging report, you know that by the time your report is complete, it’s already outdated. By then, new invoices have aged into the overdue bucket and the ones from last week still haven’t been paid.

As a result, the process is naturally reactive and starts after the invoice is already late, and it depends entirely on someone remembering to follow up. Since everyone is busy, you get a chaotic to-do list with no enforcement mechanism, which doesn’t make for a solid collections strategy. 

Here’s how to build a dunning process in NetSuite that runs before invoices go past due, escalates systematically when they do and makes it easy for customers to pay without friction.

Key highlights:

• Dunning is the structured process of reminding customers about overdue invoices and escalating the urgency as invoices age.
• NetSuite supports dunning natively through dunning letters with escalation levels, but the feature has limitations at scale.
• The most effective collections strategy reduces the need for collections in the first place.

What is dunning and why does it matter for NetSuite teams?

Dunning is the systematic process of sending payment reminders and escalation notices for overdue invoices. It follows a structured sequence – friendly reminder, firmer follow-up, formal notice, final warning – with each step triggered by how long the invoice has been past due.

It’s easy to see why dunning management matters. Inconsistent collections directly impact days sales outstanding (DSO), cash flow and working capital. Without a structured dunning process, follow-ups happen once someone remembers. 

That means the AR manager chases the invoices they notice, which aren’t necessarily the ones that matter most. And invoices that slip past 60 days become significantly harder to collect, so the longer accounts receivable sits unpaid, the less likely you are to see the cash.

For NetSuite teams, dunning works best when it runs inside the enterprise resource planning (ERP) system, where your invoice data, customer records and payment history already live. When collections happen outside the system of record, you’re reconciling two versions of the truth, which complicates an already complex process. 

How to design a dunning policy before configuring automation

Before you even think about touching a dunning procedure in NetSuite, write the policy. Automation without a clear escalation framework just sends the wrong emails faster. Here’s how to create a policy that works for your processes.

1. Define when communication starts

Most teams default to reaching out after an invoice is overdue, but by then you’ve already lost time. Best practice is to send a courtesy reminder three to five days before the invoice is due. This single step reduces the volume of invoices that ever reach Level 1 dunning, because sometimes customers just need the nudge.

2. Set escalation levels and timing

Most teams use a four-level structure.

• Level 1 (seven days past due): This is a friendly reminder to your customers. The wording is straightforward, like “Your invoice is past due. Here’s a link to pay.”
• Level 2 (21 days past due): Use a firmer tone, such as “This is your second notice. Please remit payment or contact us to discuss payment options.”
• Level 3 (45 days past due): This is a formal notice to accounts, with wording like “Your account is significantly overdue. Please contact [named person] immediately.”
• Level 4 (60+ days past due): This is where you give a final warning with consequences. “If payment is not received by [date], [consequence].”

3. Decide what triggers a pause

Active disputes, pending credit memos and payment plan agreements need to pause the dunning sequence instead of override it. If a customer disputes a $50,000 invoice and gets a collections letter the next day, you’ve damaged the relationship for no reason.

4. Assign ownership at each level

Levels 1 and 2 can be fully automated, while levels 3 to 4 need a named person. The customer at 45+ days overdue wants to talk to a human, so your escalation letter needs a direct phone number and email instead of a generic AR inbox.

5. Document consequences

Late fees, service suspension and referral to collections are all realistic and fair consequences for overdue payments, but you need to define them in your policy before they appear in a demand letter. 

If your Level 4 letter threatens suspension but the operations team has no process for it, the threat is empty and your credibility erodes.

6. Set the reporting cadence

Weekly AR aging reviews with dunning status covering how many invoices sit at each level, total overdue balance and DSO trend. Without a weekly review, collections become reactive and  problems surface after invoices have already aged past the point of easy recovery.

How NetSuite dunning works natively

NetSuite includes a built-in dunning feature that handles basic payment reminders and escalation. It’s functional for straightforward AR environments, but it has significant limits at scale that you don’t want to overlook.

Setting up dunning procedures

NetSuite’s dunning starts with creating a dunning procedure that defines your escalation levels. Each level sets a days-past-due threshold, an email template and weighting rules that determine how NetSuite prioritizes which invoices to evaluate first. 

NetSuite’s dunning starts with creating a dunning procedure that defines your escalation levels. Each level sets a days-past-due threshold, an outstanding amount threshold and an email template. NetSuite offers three dunning modes:

• Customer level dunning is the recommended standard, as it evaluates all of a customer’s overdue invoices together and sends one consolidated letter listing everything outstanding. 
• Invoice level dunning lets you treat specific invoices differently, with separate procedures and templates per invoice. It’s useful when certain contracts or billing arrangements need distinct follow-up rules. 
• Invoice group level dunning sends letters for grouped invoices, which works for teams that batch invoices by project or PO.

Once the procedure is built, you assign it to customers, invoices or invoice groups. NetSuite can also assign procedures automatically based on subsidiary, saved search or department when new customer or invoice records are created. 

An administrator schedules the dunning evaluation workflow, and NetSuite will evaluate which invoices qualify, assigning the correct dunning level and sending or queuing the appropriate letter.

Dunning letter templates and delivery

The tone of your dunning letter matters as much as the timing. 

In Netsuite, each escalation level gets its own email template, and those templates should match the tone your policy defines. This means being friendly at Level 1 and much more formal by the time you hit Level 4. 

In these messages, include invoice details, outstanding balance and clear payment instructions so the customer has everything they need to act. 

NetSuite supports both email-based and PDF dunning letters. Email delivery can run automatically when the evaluation workflow fires, making it the more practical option for most teams. PDF letters go through a manual print queue, which can be slow at high volumes but works for customers who require physical correspondence.

Where native dunning falls short

NetSuite’s dunning handles the basics, but AR teams running high-volume collections hit the walls quickly.

• No prioritized worklists. The AR team can’t see which overdue invoices to chase first by risk or value. Every overdue invoice gets the same treatment based on level, regardless of amount or likelihood of collection.
• No built-in payment portal. The dunning letter tells the customer to pay but doesn’t give them a one-click way to do it natively. Customers receive instructions but still have to initiate payment separately.
• No dispute routing. If a customer disputes an invoice, dunning continues unless someone manually pauses it. There’s no automated workflow to route the dispute to the right person and hold the sequence.
• No predictive scoring. There’s no way to identify which overdue invoices are likely to pay late versus likely to default, so the team can’t prioritize where to focus their effort.
• 100-letter batch cap. Both the email sending queue and PDF print queue process a maximum of 100 letters at a time, forcing manual reruns for teams with large overdue portfolios.

Five ways to reduce overdue AR before it reaches dunning

Before optimizing your dunning workflow, look upstream. Plenty of overdue invoices may trace back to a billing error, a payment friction point or a communication gap that could have been caught before the due date passed.

Here are five ways to prevent overdue AR: 

1. Automate billing to eliminate invoice errors. A wrong amount, a missing line item or a misapplied discount gives the customer a reason to dispute the invoice instead of paying it. Then, that dispute pauses the entire order-to-cash cycle while your team investigates. Automated billing, meanwhile, generates invoices from contract terms, which means fewer errors, fewer disputes, and fewer invoices aging into dunning.
2. Send invoices immediately on the billing date. Every day between the billing event and invoice delivery is a day added to DSO. If your team generates invoices on the first of the month but does’'t email them until the fifth, you’ve already lost five days. Automated invoice delivery eliminates the lag and starts the payment clock the moment the billing event occurs.
3. Offer a self-service payment portal. Customers who can view their invoice, select a payment method and pay in one click pay faster than customers who receive a PDF and have to initiate a bank transfer. Payment portals – Stripe, NetSuite SuiteCommerce or third-party options – reduce steps between “I got the invoice” and “I paid it.”
4. Send proactive reminders before the due date. A courtesy reminder three to five days before the invoice is due is a nudge, not a dunning letter. And it works. A significant portion of late payments aren’t intentional; they’re the result of the invoice sitting in someone’s inbox. A pre-due-date reminder reduces the number of invoices that ever reach Level 1.
5. Make payment terms clear on the invoice. Include due date, accepted payment methods, late fee policy and a direct payment link all on the invoice. Ambiguity causes delay. If the customer has to ask how to pay, you’ve added days to your DSO before the invoice is even overdue.

How to measure whether your collections process is working

You can’t improve a collections process you're not measuring. These five metrics show whether your dunning is actually moving cash or just sending emails:

1. Days sales outstanding (DSO): Measures the average number of days between invoicing and payment. Track the trend monthly, as a single DSO number is less useful than the direction. If DSO is climbing quarter over quarter, something upstream is broken.
2. Aging bucket distribution: This assesses what percentage of AR is current versus 31–60 versus 61–90 versus. 90+. A healthy AR ledger has the majority in current. If the 61–90 bucket is growing, dunning isn’t escalating fast enough, or escalation letters aren’t compelling enough to drive action.
3. Collection effectiveness index (CEI): Measures how much of the receivables that were available to collect actually got collected in the period. It’s more nuanced than DSO because it accounts for new billing. 
4. Dispute rate: Tracks what percentage of invoices trigger a dispute. If the rate is above 5%, the billing process – not the collections process – needs attention first. You can’t collect your way out of bad invoices.
5. Dunning level distribution. Measures how many invoices are at each escalation level. If most overdue invoices never get past Level 1, the reminders are working. If they’re piling up at Level 3–4, the escalation path needs review – either the messaging isn’t driving urgency or the customers can't easily pay.

Signs you need a dedicated collections platform

Dunning procedures and upstream prevention handle most overdue AR. But some teams reach a point where the volume, complexity or risk profile of their receivables outgrows what native NetSuite dunning can manage.

Here are the signs to look for: 

• Overdue AR exceeds 20% of total receivables and the trend is rising. At this volume, manual follow-ups and basic dunning letters can’t keep pace. A dedicated platform with prioritized worklists and automated outreach adds capacity the AR team doesn't have.
• Dispute resolution takes weeks, not days. If customers dispute invoices and the dunning process doesn’t pause or route the dispute to the right person, the relationship suffers and cash stalls.
• The AR team needs predictive risk scoring. Knowing which overdue invoices are likely to pay late versus likely to default changes how the team allocates its time. AI-powered collections platforms score risk in ways native dunning can’t.
• Cash application is a separate reconciliation exercise. If the payment comes in but doesn’t auto-apply to the invoice, the collections “win” creates a new manual step. Platforms that combine collections with automated cash application close the loop.
• Multi-entity AR needs consolidated collections visibility. Running dunning across subsidiaries in NetSuite OneWorld requires coordination that a dedicated platform can centralize.

‍