A Comprehensive Guide to the Dunning Letter: What It Is and Why You Should Automate It With NetSuite

Payment reminders help resolve outstanding balances, but they can take time and resources to send. NetSuite automation makes it easy to send notices that spur revenue.


We all have clients or customers who don’t pay their bills. Some forget and need gentle reminders. Others need a lot more encouragement. 


Either way, you have your own accounts to settle and need cash to keep flowing so you can maintain your business. Clients can't pay whenever they want. 


We know how exhausting it can feel to hound people for payment. It’s not fun, and it wastes staff resources. The NetSuite Dunning Letters SuiteApp automates the process so you can save time and energy on a task no one likes. The application identifies overdue invoices and sends payment reminders using sample templates or custom letters you design for your clients.


Schedule a free consultation with SuiteDynamics and get expert advice about establishing a dunning system that gets results. We can implement and configure the SuiteApp to free your team up for making sales and increasing profits. 


Schedule a FREE Consultation
A graphic explaining that dunning letters decrease the chances of delinquency by 33%.


What Is a Dunning Letter?


A dunning letter is a notice or letter your company sends a customer about an unpaid bill or debt. It's like a friendly (or not-so-friendly) reminder to pay the money they owe. The word "dunning" comes from an old term for demanding payment.


Here's how it typically works:


  1. The customer receives a product or service from your company, and you send a bill or invoice.
  2. If the customer forgets to pay the bill or doesn’t pay on time, you might send a dunning letter.
  3. This letter usually includes information about the unpaid amount, bill details, and a clear request for payment. It may also mention any late fees or penalties your company could add if the customer continues to delay payment.
  4. If the customer still doesn’t pay, you may send multiple dunning letters, each one potentially more urgent or strongly worded than the last. 


Dunning Levels

 

The term “dunning levels” refers to the sequence of increasingly severe reminders you may send customers about overdue bills or unpaid debts. These reminders are like steps in a staircase, each level becoming more assertive or urgent. The goal is to remind customers to settle their debt by escalating communication tone and content.


Sending Dunning Letters in NetSuite


We know it’s frustrating to manually track outstanding balances and send notices to clients and customers—especially when automated options exist. The NetSuite Dunning Letters SuiteApp identifies overdue invoices and automatically issues payment reminders so you can focus your workforce on more strategic tasks. 


The application also allows you to set up procedures, including dunning levels, that guide the automated process. You can determine the intervals at which to send letters and how urgent the notices should read at your chosen escalation points, such as 30, 60, or 90 days.


The NetSuite Dunning Letters SuiteApp also allows you to:


1.     Customize dunning letter templates.

2.     Create dunning letter templates in various languages. 

3.     Establish evaluation workflows, determining which customers will be dunned.

4.     Choose whether to send notices manually or automatically.

5.     Choose whether to email notices, print them, or both.

6.     Pause dunning to handle customer billing inquiries or extend a customer’s payment time. 


The SuiteApp also features a dashboard that consolidates your dunning data into a single view. It features the following charts and lists. 


1.     Dunning Overdue Receivables

2.     Recently Sent/Printed Dunning Letters

3.     Dunning Average Time to Pay

4.     Dunning Overdue Receivables by Customer

5.     Dunning Overdue Receivables by Age

6.     Total A/R Overdue

7.     Customers with Paused Dunning

8.     Invoices with Paused Dunning


SuiteDynamics experts can help customize a dunning procedure for your company in the NetSuite Dunning Letters SuiteApp. We’ll ensure you have a solid system that collects as much outstanding revenue as possible. Schedule your free consultation today.


Graphic advertising SuiteDynamics consulting services.


4 Tips for Writing Custom Dunning Letters

 

You can use NetSuite’s dunning letter samples with minimal changes. Or you can write your own templates to better reflect your company culture and voice. It’s your choice, but if you choose the latter option, keep these tips in mind. 


  1. Keep the first letter light and polite. Your customer or client may have simply forgotten to schedule payment, so it’s best to start with a gentle reminder to settle the account. You don’t want to harm the relationship. State that the bill is overdue and politely request they pay by a set date. 
  2. Make the second letter firm. Keep your tone calm, even after your customer ignores the first dunning letter. Remain factual. State the amount the customer owes and how overdue that payment has become. Then, explain the legal steps you plan to take if the customer doesn’t settle their bill by a specific date. 
  3. Prepare for legal action after the third letter. You may choose to skip the third letter and start legal action after the second notice’s due date expires. Still, if you send a third letter, keep it short and direct. Tell the customer what legal actions you plan to take if they don’t pay within a set timeframe.
  4. Follow up with a phone call. We recommend calling your customer or client the day after sending each dunning letter. This practice lets you clear up any misunderstandings or billing issues and answer questions about your invoice. 
  5. Hire a lawyer. Having an attorney review your dunning letters is a good idea, especially if you deal with large transactions or plan to take legal action. These notices must be written correctly.

 

Of course, you can create more than three dunning levels and corresponding dunning letter templates. The SuiteApp lets you add up to 15 levels to a dunning procedure. Just remember to keep your language calm and firm and to escalate the urgency appropriately. 


Learn more about the NetSuite Dunning Letters SuiteApp during a free consultation with SuiteDynamics experts. We’ll advise on how best to configure the application for your company’s needs, and we'll complete its implementation and setup so you can stay focused on company growth. 


Schedule a FREE Consultation


Settle Outstanding Bills with Little Headache


In a perfect world, everyone would pay bills on time and in full. Unfortunately, that’s not going to happen. People will forget, misunderstandings will happen, and, sadly, some will choose dishonesty. Meanwhile, your company needs revenue to keep employees paid and vendors happy. 


We know you would probably prefer never to send a payment reminder. But as a growing business, you must have a dunning procedure in place—preferably an automated one. The NetSuite Dunning Letters SuiteApp takes the burden of flagging overdue invoices and sending notices off your team so they can spend more time expanding your brand. 


Schedule a consultation with SuiteDynamics experts and discover how this application can make your office more efficient. We’ll help you establish the proper dunning procedures by implementing the NetSuite Dunning Letters SuiteApp with precision and care. Establish a better, smarter payment reminder system today. 


Schedule a FREE Consultation




We pull information from NetSuite material, SuiteDynamics experts, and other reliable sources to compose our blog posts and educational pieces. We ensure they are as accurate as possible at the time of writing. However, software evolves quickly, and although we work to maintain these posts, some details may fall out of date. Contact SuiteDynamics experts for the latest information on NetSuite ERP systems.




Part of this text was generated using GPT-3, OpenAI’s large-scale language-generation model. After generating the draft language, our team edited, revised, and fact-checked it to ensure readability and accuracy. SuiteDynamics is ultimately responsible for the content of this blog post.

Why Make-to-Order Manufacturing Breaks Down in Spreadsheets

March 27, 2026
Spreadsheets built modern business. For decades they served as the unofficial operating system of job shops and custom manufacturers everywhere. They are flexible, familiar, and just comfortable enough to feel like a real solution. In the early days of a growing shop, they genuinely work. But as make-to-order complexity increases, as custom BOMs multiply, lead times tighten, and engineering revisions pile up, spreadsheets strain under the pressure. Every job is different, but spreadsheets want everything to be the same. In make-to-order environments, no two jobs are identical. Unique BOMs, custom routings, variable material costs, different setup requirements, customer-specific specs. Spreadsheets, though, thrive on repetition and standardized rows. So the more variation you introduce, the more tabs you create. The more exceptions you add, the more manual overrides appear. The more formulas you patch together, the more fragile the whole thing becomes. Eventually, the file turns into something only one person truly understands. That’s a liability, not a system. Capacity becomes a guessing game. In make-to-order shops, capacity isn’t theoretical. It’s constrained by reality. Machines go down. Operators vary in skill. Setup time fluctuates from job to job. Rush orders blow up carefully planned weeks. Spreadsheets struggle here because they’re built on static inputs. You can build a beautiful planning sheet with machine-hour allocations, but unless it dynamically adjusts for real-time job status, operator availability, overlapping resource conflicts, and maintenance downtime, you’re not really planning. You’re forecasting best-case scenarios. And that’s exactly how shops overpromise delivery dates and end up paying for it later in overtime and expediting costs. Engineering changes don’t cascade cleanly. Change is a constant in make-to-order manufacturing. A customer tweaks a dimension, a material substitution becomes necessary, or a tolerance tightens halfway through production. In an integrated system, that change automatically updates BOMs, routings, cost projections, and scheduling impact all at once. In a spreadsheet environment, it depends entirely on who remembers to update which tab. A routing might change without adjusting the labor estimate. A material substitution might never feed into the margin calculation. A lead-time adjustment might not reach the production schedule until it’s too late. These small disconnects multiply quickly, and because spreadsheets have no enforced relationships between data sets, the errors don’t announce themselves. Institutional knowledge becomes a single point of failure. Ask most growing job shops who owns the master spreadsheet and you’ll get a name. One estimator, planner, or operations manager who has become the living interpreter of years’ worth of embedded formulas, assumptions, and logic that nobody else fully understands. This works fine until it doesn’t. When that person goes on vacation, gets sick, or leaves, the shop loses operational clarity. In an environment already defined by complexity, having critical knowledge live inside one person’s mental model of a file is an inefficient bottleneck. Visibility stops at the file boundary. Spreadsheets are static snapshots. Make-to-order manufacturing is anything but. Without real-time feedback loops, shops find themselves unable to answer questions that should be simple: Are we actually on track this week? Which jobs are consuming more labor than quoted? Where is the bottleneck right now? Which customers consistently drive margin compression? When performance data doesn’t flow automatically from the floor back into quoting and planning, improvement stalls. You can’t refine what you can’t see. Here’s the thing about spreadsheet failure in manufacturing… it’s not dramatic. It’s gradual. First the files get slow, then fragile, then opaque. By the time leadership feels the real pain through late shipments, squeezed margins, and rising overtime, the architectural issues are widespread. Make-to-order manufacturing demands systems that understand relationships: how a routing affects capacity, how a BOM revision affects cost, how a delayed job cascades through the rest of the schedule. The question most shops ask is whether they can make the spreadsheets work. The better question is what it’s actually costing to keep them. The most resilient make-to-order manufacturers are building systems that preserve flexibility without sacrificing the visibility needed to actually run the business. Adaptability is the advantage. 

Where Fabrication Shops Lose Margin (And Don’t Know It)

March 23, 2026
In custom manufacturing , when systems break down, profit rarely disappears all at once. It leaks. Quietly, repeatedly, and often in ways that never show up clearly on any report. Walk into almost any fabrication shop and you’ll hear some version of the same story: the backlog is strong, revenue looks good, we’re staying busy. And yet the margin feels thinner than it should. For job shops running custom work, profitability doesn’t usually collapse because of one bad decision. It erodes through small, daily inefficiencies buried inside quoting, scheduling, engineering changes, and the gap between what was planned and what actually happened on the floor. Here’s where shops most commonly lose efficiency, and how to get it back. The quote that was almost right. For custom orders, every quote is a prediction, and predictions are dangerous when they’re disconnected from real shop-floor data. Outdated labor standards, underestimated setup time, material prices that changed since the template was built, and capacity assumptions based on average weeks instead of current reality. These errors are each small on their own, but a 4% underestimate on labor here, a missed secondary operation there, add up across hundreds of jobs. Small errors compound into real margin loss. The best-performing shops treat quoting as a living system fed by actual job performance data, not static spreadsheets that nobody updates. Capacity that looks available but isn’t. On paper, there’s open space on the schedule. In practice, that open week includes a machine down for maintenance, a senior operator on vacation, two complex jobs already competing for the same bottleneck, and a rush order someone verbally committed to last Thursday. Without finite capacity planning, shops routinely overcommit based on theoretical machine hours rather than real-world constraints. The fallout is predictable: overtime spikes, expedited shipping costs, re-sequencing chaos, and exhausted operators. Margin shrinks not because the shop is incapable, but because it’s planning in averages. Engineering changes that never get repriced. Designs evolve. A hole moves, a weld spec changes, or a tolerance tightens. Each adjustment has a cost. But many shops hesitate to reprice midstream, worried about damaging the customer relationship, and end up absorbing the extra labor and rework time instead. Do this enough times and it becomes a cultural norm: “we’ll just take care of it.” That’s margin erosion disguised as good service. High-performing job shops track engineering change impact in real time and make repricing decisions based on data rather than discomfort. Setup time hiding in plain sight. In low-volume, high-mix environments, setup time is often the silent killer. When shops don’t track setup separately from run time, assume it’ll all come out in the wash, and never refine their routings based on what actually happened, they end up underpricing complexity. In job shops producing one to fifty unit runs, setup can represent a disproportionate share of total labor. If it isn’t measured accurately, it can’t be priced accurately. The spreadsheet layer nobody talks about. Most shops run a hybrid environment where the ERP handles transactions and spreadsheets handle reality. Capacity lives in one file, quoting assumptions in another, and actual job performance in someone’s head. This creates invisible disconnects. Quotes not aligned with current routing, schedules that don’t reflect real constraints, and historical performance that never feeds forward into better decisions. Each disconnect feels manageable in isolation. Collectively, they create margin leakage that leadership can feel but can’t quite locate. What makes all of this so frustrating isn’t that shop owners don’t care. It’s that they can’t see clearly enough to act decisively. Without integrated visibility across quoting, routing, capacity, and quality, operators run on instinct. And instinct works remarkably well until scale and complexity outpace it. The shops that consistently outperform aren’t necessarily the biggest or the busiest. They operate with clarity and consistency. Fewer assumptions and more decisions based on reality. In a manufacturing landscape where lead times keep shrinking and customers expect speed and precision at the same time, margin won’t be protected by effort alone.
Factory worker in hard hat using laptop, monitoring control panel with screens.

Why “Perfect” Production Planning is a Myth, and How Finite Capacity Planning Fixes It

January 5, 2026
Every manufacturing leader has lived this moment: The schedule looks perfect. Orders are slotted. Commitments are made. And then reality shows up. A machine goes down. A key operator calls out. Setup times balloon. One late job cascades into five. Suddenly the plan (built meticulously inside your ERP) falls apart. Not because your team failed, but because the plan was never grounded in reality to begin with.  The Hidden Lie Inside Most ERP Schedules
Woman Working in Modern Factory Setting

Connecting AI to NetSuite Using MCP

August 27, 2025
NetSuite’s Model Context Protocol (MCP), built in partnership with Anthropic, helps users leverage AI
job shop manufacturing

What is Job Shop Manufacturing? Complete 2025 Guide

June 20, 2025
Job shop manufacturing is a production method where small batches of 1-100 units of customized or unique products are made to meet specific customer requirements. Unlike mass production, each order typically requires unique setups, specialized processes, and custom routing through the facility. In this comprehensive guide, you'll learn: The complete definition of job shop manufacturing How job shops differ from other manufacturing types Industries that rely on job shop methods Technology solutions that optimize job shop operations When to consider implementing specialized ERP systems What is Job Shop Manufacturing? (Definition) Job shop manufacturing is a production strategy focused on customization over volume . Instead of producing thousands of identical items, job shops create small quantities of unique products tailored to specific customer specifications. Key defining characteristics: Small batch sizes - Typically 1-100 units per order High product variety - Hundreds or thousands of different products Custom specifications - Each order has unique requirements Project-based workflow - Work orders last days to weeks Skilled labor - Requires specialized expertise and flexibility Job Shop is a powerful, fully integrated solution built for custom manufacturers, combining quoting, configuration, production, and fabrication workflows inside NetSuite. Learn more about SuiteDynamics' NetSuite Job Shop for Manufacturing.
A man is holding a box and a woman is looking at a tablet in a warehouse.

When Non-Standard Data Skews Your DIO: Practical Solutions for Messy Inventory Records

By Grace Martin • May 27, 2025
Uncover the challenges of data quality affecting DIO accuracy, from ghost inventory to inconsistent formats. Find out how to tackle these issues effectively with a NetSuite ERP.

Why PE Firms Are Consolidating NetSuite Instances Across Portfolio Companies

May 8, 2025
In the world of private equity, creating operational value has become increasingly critical as the market evolves. With exit timelines extending and competition for deals intensifying, PE firms are looking beyond financial engineering to drive returns. One emerging strategy that's gaining traction is the consolidation of NetSuite instances across portfolio companies. The Hidden Challenge of System Fragmentation As PE portfolios grow through acquisition, a common pattern emerges: multiple portfolio companies operating on separate NetSuite instances. While each system may work effectively in isolation, the fragmentation creates significant operational inefficiencies at the portfolio level: Redundant Licensing Costs: Each separate instance requires its own licensing structure , creating unnecessary expenses that directly impact EBITDA. Manual Consolidation Effort: Finance teams spend countless hours extracting, transforming, and manually consolidating data from disparate systems. Inconsistent Processes: Basic business functions are handled differently across portfolio companies, limiting standardization efforts. Limited Portfolio-Wide Visibility: Gaining insight across the entire portfolio requires extensive manual effort, delaying strategic decision-making. Integration Challenges: Onboarding new acquisitions becomes increasingly complex when each company maintains its own environment.
Esusu logo

Case Study: Esusu's Journey to Financial Efficiency

April 30, 2025
Explore Esusu's partnership with SuiteDynamics to enhance financial processes. Schedule a consultation to see how your business can thrive with NetSuite solutions.
Image of an office worker and a laptop, illustrating the concept of case management setup.

NetSuite Case Management Set Up: How to Configure Case Statuses, Rules, Types, Priorities, and More

By Brittany Klecker • April 30, 2025
Discover how to effectively set up and configure case statuses, rules, types, priorities, and more in NetSuite's case management system. Streamline your workflow and improve customer support with this comprehensive guide.
A man is holding a stack of cardboard boxes in a warehouse.

Understanding Backorders: What They Are, Why They Happen, and How to Manage Them

By Grace Martin • April 26, 2025
Backorders disrupt revenue and frustrate customers. Learn what "backordered" means, how backorders happen, their impact on businesses, and how NetSuite ERP can minimize the issues.
More Posts