NetSuite Dunning Letters: How to Automate Collections

Key Takeaways

• Customer-level dunning is the default starting point. Oracle documents customer-level dunning as the recommended standard use case because it evaluates the customer account as a whole instead of treating every invoice as a separate project.
• The setup order matters. NetSuite requires you to create templates, then level rules, then procedures, then assignment and scheduling. If you skip that order, the automation logic will feel inconsistent even when the records are saved correctly.
• The Dunning Setup Assistant can shorten initial rollout. Oracle provides a guided assistant with predefined levels, schedule pages, template assignment, and bulk assignment controls for multi-subsidiary setup.
• Recipients need their own audit pass. If the customer email is suppressed, NetSuite requires at least one dunning contact with an email address before the record can be saved for email delivery.
• Automation depends on workflow scheduling, not just templates. A procedure with email templates still will not send notices automatically until the dunning evaluation workflow is copied, scheduled, and released.
• Saved-search segmentation is where collections get smarter. Procedures can be scoped by subsidiary, class, location, department, and saved search so your notices match real account policies instead of one generic reminder sequence.

NetSuite Dunning Letters Prerequisites

Before you configure the Dunning Letters SuiteApp, make sure your account and team are ready for the feature operationally, not just technically.

• The Dunning Letters SuiteApp must be installed.
• Someone with Administrator, Accountant, or Dunning Director access should own the initial setup.
• Your team should decide whether reminders should be evaluated at the customer, invoice, or invoice group level.
• You need at least one test customer and overdue invoice for validation.
• Your email, PDF, and contact strategy should be settled before you release the live workflow.

Oracle’s Dunning tab documentation shows that the installed SuiteApp exposes setup pages for configurations, level rules, templates, and procedures. It also includes bulk assignment, queues, and manual send or print actions. Oracle notes in its subsidiary configuration guide that each active subsidiary gets a dunning configuration record automatically after installation, and those records default to auto-assign procedures to new customers, invoices, and invoice groups. That default is useful, though it also means you should review subsidiary behavior before you assume production accounts are segmented correctly.

If your account spans multiple business units, this is also the right point to confirm whether your internal admin team owns ongoing rule changes. Dunning gets messy when nobody owns it after go-live, especially once additional modules start influencing billing and collections workflows.

NetSuite Dunning Letters Setup at a Glance

Use this rollout sequence to configure the Dunning Letters SuiteApp:

Oracle’s Dunning Setup Assistant follows a similar flow: roles, levels, messages, schedule, and bulk assignment. It also ships with three predefined levels by default, which you can customize or replace based on your collections policy.

For many teams, it functions like a lightweight accelerator for first-time rollout. One useful detail many teams miss is that Oracle allows negative days overdue values if you want to send a reminder before the due date rather than after it.

NetSuite Dunning Letters Setup Steps

If you want the short version, set up NetSuite dunning letters in this order:

1. Review subsidiary defaults and auto-assignment behavior.
2. Choose customer-level, invoice-level, or invoice-group dunning.
3. Create email and PDF templates for each reminder stage.
4. Build dunning level rules for days overdue and balance thresholds.
5. Create the dunning procedure and assign a default manager.
6. Add saved-search criteria, recipients, and delivery settings.
7. Copy, schedule, test, and release the workflow that sends notices.

Step 1: Review subsidiary-level defaults

Start at Dunning > Setup > Dunning Configuration and inspect each active subsidiary. Oracle states that new and active subsidiaries automatically receive a dunning configuration record, and the default settings check auto-assignment for new customers, new invoices, and new invoice groups.

If you want broad automation, those defaults may be fine. If your business has one subsidiary that should follow a stricter collections cadence than another, clear the auto-assignment boxes and control assignment through saved-search criteria instead. This is often the better choice for companies with different payment cultures across product lines or entities.

Step 2: Decide which dunning model fits your process

Choose the model before you build anything else:

Oracle explicitly recommends customer-level dunning as the standard approach in its guide to customer, invoice, and invoice-group dunning. It sends one letter based on the customer’s overdue position and can include all overdue invoices. Use invoice-level dunning only when a specific invoice needs different treatment, such as a large-value exception, a separate template, or a special payment term. Use invoice-group-level dunning if your billing process depends on invoice groups rather than individual invoice communication.

That decision will drive which procedures you create and which workflow scheduler you release later.

Step 3: Build your templates first

NetSuite requires templates before procedures can use them. Oracle’s setup order is clear: create dunning email templates or PDF templates, create a dunning template record, then assign those records to dunning levels.

For email templates, Oracle documents two main paths in its email template instructions:

1. Create the record at Documents > Templates > Email Templates > New.
2. Either write the content directly, upload a file, or copy the sample template content from the SuiteApp’s File Cabinet bundle.

For PDF templates, Oracle notes that FreeMarker/XML is required and the SuiteApp stores sample files under SuiteBundles > Bundle 392827 > Templates. It also recommends a naming convention that includes the level and locale, such as dunningbody_level1_en_US_pdf.xml.

Keep the early templates plain. Collections notices usually fail because they are unclear, not because they are under-designed. Each level should answer four questions fast:

• Which invoice or account is overdue?
• How many days past due is it?
• What amount remains open?
• What should the customer do next?

Step 4: Create dunning level rules

Next, create the threshold logic at Dunning > Setup > Dunning Level Rule > New. Oracle’s level-rule documentation explains that a level rule defines both days overdue and outstanding amount thresholds. It also confirms that the overdue calculation is based on the transaction’s Due Date field, not some alternate custom date.

Teams also decide how strict the trigger should be at this stage. Oracle’s guide to determining the dunning level offers two bases:

• Minimum transaction amount AND total overdue balance
• Minimum transaction amount OR total overdue balance

Use the AND option when you want tighter control and fewer notices for small balances. Use OR when collections should escalate aggressively as soon as either the invoice amount or the total account exposure crosses your threshold.

If you transact in more than one currency, Oracle recommends defining amounts for all currencies used by your customers. Otherwise, NetSuite converts the rule amount using the prior month’s exchange rate. That can work operationally, but it is not the cleanest model for teams that want clear local-currency thresholds inside NetSuite Accounting Software.

Step 5: Create the dunning procedure

With templates and level rules in place, build the actual procedure at Dunning > Setup > Dunning Procedures. Oracle’s procedure setup guide describes the procedure as the record that ties together escalation points, templates, intervals, and applicability.

At minimum, your procedure should define:

• Applies To: Customer, Invoice, or Invoice Group
• Dunning levels: At least one level is required
• Sending schedule: Automatic or manual
• Default dunning manager
• Selection criteria: Subsidiary, class, location, department, or saved search when relevant

Oracle also notes that a procedure must have a default dunning manager. That matters because the dunning manager appears in operational handoffs and controls who sees letters in the queues after the workflow runs.

Step 6: Segment notices with saved searches

Saved-search segmentation turns simple reminders into real collections automation. Oracle’s selection-criteria documentation shows that dunning procedures can be filtered by subsidiary and saved search. Additional class, department, and location filters are available when those features are enabled.

In practice, that means you can create separate procedures for:

• strategic accounts with white-glove terms
• smaller customers with standard escalation
• high-risk accounts requiring earlier reminders
• invoice groups tied to consolidated billing

If your account uses classes, departments, or locations, Oracle warns that the classification must exist on the main invoice record to affect assignment. Line-level classifications alone do not drive dunning eligibility.

Saved searches also do serious work here. A finance team might create one search for customers over a specific overdue threshold, another for accounts tied to a certain subsidiary, and a third for customers whose notice path should exclude standard customer-email delivery. That segmentation approach pairs well with broader process optimization because it reduces one-size-fits-all automation.

Step 7: Configure recipients and delivery settings

Now move to the customer or invoice records and finish delivery logic. Oracle’s recipient rules are strict enough that they are worth testing in a sandbox first.

On the customer’s Dunning subtab, review these settings:

• Allow Letters to be Emailed
• Do Not Send Letters to Customer Email
• Add BCC Email to Sales Representative
• Dunning Recipient contacts

Oracle states that if Do Not Send Letters to Customer Email is checked, you must add at least one contact with an email address on the Dunning Recipient subtab. Oracle also allows escalation-level notifications per recipient, peer visibility in a single email, and BCC notices to the sales rep for overdue alerts.

Recipient routing is one of the most important governance decisions in the whole process. If your organization wants finance to lead collections while still keeping account owners informed, BCC to the sales rep is usually cleaner than giving everyone direct recipient status on every level.

Step 8: Schedule the workflow that runs the automation

Many teams mistake the final setup step as “already done.” Creating procedures and recipients is not enough. Oracle’s workflow scheduling documentation says an administrator must copy, schedule, and release the relevant workflow before NetSuite will evaluate and send letters automatically.

Go to Customization > Scripting > Workflows, then:

1. Open the correct scheduler workflow.
2. Make a copy.
3. Edit the workflow name and schedule.
4. Confirm the Repeat box is checked.
5. Select the frequency, start date, and run time.
6. Set Release Status to Release when ready.

Oracle recommends scheduling dunning workflows outside normal business hours and running them on weekdays only if you want to avoid weekend debt-chasing emails. Oracle also notes that schedules are stored in the user’s current time zone when created, so timezone drift can happen if the schedule owner later changes preferences without re-editing the workflow.

If your business operates across subsidiaries or formal approval chains, review how the workflow will interact with your reporting in SuiteAnalytics, your broader NetSuite Modules, and any cross-functional account ownership before you release it in production.

Common Mistakes to Avoid with NetSuite Dunning Letters

1. Using invoice-level dunning when customer-level would do

Invoice-level dunning exists for exceptions. If you make it your default model, setup and maintenance get heavier fast. Oracle’s own customer, invoice, and invoice-group dunning guidance points teams back to customer-level dunning as the recommended standard.

2. Validate recipient settings before releasing workflows

The workflow can be technically correct and still send notices to the wrong people. Validate customer email behavior, recipient-contact behavior, and sales-rep BCC logic before you release anything in production, because Oracle documents both the workflow release process and the recipient requirements clearly.

3. Treating templates as the only control point

Templates set tone, though they do not determine who qualifies, when notices fire, or which balances are included. Those controls live in level rules, procedure settings, and scheduling, as Oracle outlines in its dunning procedure setup guidance.

4. Forgetting the dunning manager requirement

Oracle requires a default dunning manager on the procedure. If ownership is unclear, the queue review process and operational troubleshooting slow down immediately.

5. Skipping saved-search segmentation

A single global procedure is tempting. It is rarely the best long-term choice. Saved-search criteria let you reflect real account policy, especially across subsidiaries or customer tiers.

Advanced Tips for Better Collections Automation

Use the Dunning Setup Assistant for first rollout

If you are implementing dunning for the first time, Oracle’s guided assistant is a practical way to stand up a workable baseline. Oracle’s Dunning Setup Assistant documentation shows that it walks through roles, levels, messages, schedules, and bulk assignment in sequence, which is useful for multi-subsidiary accounts.

Start with manual sending if your policy is still unsettled

Oracle supports Manual sending as well as automatic scheduling. If your message tone, thresholds, or account segmentation are still being debated internally, queue notices manually first, review them, and then switch the sending schedule to Automatic once the business process is stable. That gives your finance systems lead a chance to validate output before the workflow is released.

Put disputes on pause instead of hacking the rule set

Oracle supports pausing dunning on a customer, invoice, or invoice group record. That is cleaner than editing the rule structure every time a billing issue or service dispute needs temporary relief.

Extend templates with saved-search fields

Oracle documents that the SuiteApp includes a predefined transaction search named customsearch_base_dunning_invoice, and those fields can be used inside template output. If your finance team wants a letter to show invoice number, due date, remaining balance, or currency without manual editing, this is the reliable way to do it.

Review assignment logic after every major A/R policy change

When payment terms, subsidiary structure, or collections ownership changes, revisit dunning procedures and saved-search criteria together. Dunning automation ages badly when the business changes faster than the rule set.

Next Steps

If you need help turning this setup into a repeatable process, Anchor Group is a NetSuite implementation partner and development firm with certified NetSuite consultants supporting manufacturing, wholesale distribution, retail, and renewables teams. That is especially useful when dunning needs to connect to SuiteAnalytics reporting, custom workflows, or broader ERP optimization after go-live.

Frequently Asked Questions

What are NetSuite dunning letters?

NetSuite dunning letters are automated past-due notices that use templates, thresholds, and schedules to send consistent reminders inside NetSuite to customers. They standardize collections without requiring manual reminders for every account.

How do NetSuite dunning letters work?

NetSuite dunning letters work by checking overdue rules, selecting the right template, and sending or queueing the matching notice automatically. NetSuite then checks which customers, invoices, or invoice groups meet your rules and applies the correct notice procedure.

What is the difference between invoice-level and customer-level dunning?

Customer-level dunning fits standard collections, while invoice-level dunning works better for exceptions that need separate timing, messaging, or payment-term treatment. Oracle identifies customer-level dunning as the recommended default model. Invoice-level dunning is better when one invoice needs different handling from the rest of the customer’s account.

Can NetSuite send automatic payment reminders?

Yes, NetSuite can send automatic payment reminders when permissions, procedure settings, and the scheduled dunning workflow are configured correctly for delivery.

Oracle states in its guide to sending dunning letters automatically that automatic sending requires customer or invoice email permissions to be enabled. It also requires the procedure’s sending schedule to be set to Automatic and the relevant dunning workflow to be scheduled and released.

How do you automate collections in NetSuite?

You automate collections in NetSuite by combining templates, thresholds, recipient rules, segmentation, and a scheduled workflow for open A/R follow-up. Most teams start with customer-level dunning, then add exception handling, reporting, and reply ownership once the reminder cadence is stable.

How do you reduce DSO with NetSuite?

You reduce DSO with NetSuite by sending reminders on time, routing replies cleanly, and escalating accounts through one consistent collections process. DSO usually improves when notice timing, recipient routing, and escalation rules are governed in one workflow instead of left to ad hoc manual chasing.

Is the NetSuite dunning module worth it?

The NetSuite dunning module is worth it when your team needs governed escalation, shared visibility, and exception controls beyond simple reminder emails. If your overdue volume is low and your notice policy is simple, a lighter saved-search or workflow setup may be enough. The native module becomes more valuable when you need level-based escalation, better visibility, pause and resume controls, and cleaner governance across customers or subsidiaries.

Can I use saved searches with NetSuite dunning letters?

Yes, saved searches let NetSuite dunning procedures separate customers, invoices, and invoice groups into different notice paths without manual sorting. Oracle allows procedures to use saved-search criteria for customers, invoices, and invoice groups. That is how most teams create different notice paths for different account segments without building separate manual processes.

Related Articles:

• NetSuite Matrix Items: How to Manage Product Variants & Attributes
• NetSuite Customizations: What You Can Customize & Best Practices
• NetSuite WIP and Routing: How to Track Work-in-Progress for Manufacturing
• NetSuite Customer Portal: How to Set Up Self-Service for Buyers

Disclaimer: This content is for general informational purposes only and may not reflect current updates or your specific configuration—please confirm details with your Anchor Group consultant.