Get a personalized demo of Stuut and see how it can help with AR automation.
Most teams managing overdue accounts can't contact every customer before invoices age further. Volume outpaces capacity, and accounts in your 31-60 day bucket drift into 61-90 days without a single outreach attempt. Early contact on overdue invoices significantly improves collection rates, yet most businesses don't make first contact until the account has aged well past the optimal window. The problem isn't willingness, it's volume. A structured dunning process paired with multi-channel execution closes that gap without adding headcount.
This guide covers the dunning cadence, tone progression, legal requirements, channel selection, and six copy-paste templates for every stage. It also explains the compliance constraints that apply to B2B dunning across email, SMS, and voice. And it shows how autonomous collections can execute this entire workflow for you, covering every account in your aging report instead of only the ones you have time to reach.
A dunning letter formally requests payment on an overdue invoice. The goal isn't just to collect money but to preserve the business relationship while documenting your outreach history in case the account escalates to legal action. Each letter creates a record that demonstrates good-faith effort and establishes a timeline courts or collections agencies can use if the account doesn't resolve. Most overdue invoices aren't genuine disputes. They're the result of clerical errors: an invoice sent to the wrong contact, a missing purchase order number, or a payment routed to the wrong account. A timely, structured dunning letter resolves these issues before they age further.
The probability of collecting an account drops to roughly 73% after 90 days and below 50% after six months, according to data from Atradius cited by ledgerup.ai's AR aging report guide. Starting your cadence early isn't aggressive, it's protective. A reminder sent at day +1 costs one email. A balance written off at day 180 costs the full invoice amount.
Escalate based on aging buckets. Assume a clerical error at 1-30 days and send a gentle reminder. Add phone contact and copy the customer's account manager at 31-60 days. Escalate to your AR manager with explicit consequences at 61-90 days. Move to a formal final demand at 90+ days, referencing all prior contact attempts and stating specific next steps.
Each letter creates a paper trail that protects you legally, signals seriousness to the customer, and removes the ambiguity that allows overdue accounts to drift into the next aging bucket without resolution. Without that structure, customers who receive inconsistent or delayed reminders can push back on late fees or dispute the contact timeline. You can pair your dunning cadence with broader cash flow tactics by reviewing the DSO improvement checklist.
Your timing determines whether customers respond to your dunning efforts or let them sit unread. A practical cadence for most B2B AR teams follows this four-stage structure:
Avoid sending dunning communications on Fridays or weekends because AP teams process payments Monday through Thursday, and an email sent Friday afternoon sits unread for 48 hours while losing momentum. Tuesday and Wednesday mornings typically produce higher open rates and faster payment responses for B2B dunning communications. Match your send time to the customer's local business hours to avoid automated filtering that routes external communications to a lower-priority queue.
Assume positive intent in the 1-30 day window. The customer likely missed the invoice or has an internal approval delay, and your tone should make responding easy. Reattach the invoice, include the payment link in the first two lines, and keep the message under 100 words.
By 31-60 days, the account has ignored at least one reminder. Shift from helpful to expectant by requesting a specific payment date and copying the customer's account manager to signal that the relationship is now involved. Reference your prior contact attempt by date so the customer understands this isn't the first outreach.
At 61-90 days, be direct. Mention the account is under review and that continued non-payment may result in an account hold. Reference prior contact attempts by date to establish a clear paper trail.
At 90+ days, state the invoice number, total balance, all prior contact dates, and a specific payment deadline. This letter should come from a senior AR team member. Cite next steps clearly: referral to a collections agency, credit reporting, or legal action.
A practical B2B cadence sends 4-6 communications before escalating to external action. One research-backed timeline runs: pre-due reminder at day -3, first reminder at day +1, firm follow-up at day +21, formal notice at day +30, final warning at day +45, and escalation at day +60 if payment or a response has not been received.
This maps to the four-stage table above, with Stage 1 covering days -7 to +3, Stage 2 at days 21-30, Stage 3 at days 31-45, and Stage 4 from day 60 onward. Your specific timing depends on your payment terms, industry norms, and customer mix, but the principle remains consistent: start early, escalate steadily, and document every touchpoint.
The same invoice can generate a payment or a dispute depending entirely on how you ask for it. Effective dunning communication is professional, helpful, and empathetic at every stage, even when the message is firm. Customers who feel respected in the process pay faster and continue the relationship. Customers who feel pressured or accused dispute more and pay slower.
First reminders work best when they assume the customer missed the invoice. Lead with that assumption, attach the invoice again, and make payment as easy as possible. Avoid phrases like "as per our records" or "kindly be advised" because they signal bureaucratic detachment rather than a business partnership.
Stage 2 and 3 letters shift from service to collections without becoming adversarial. Use "requesting confirmation" instead of "demanding payment" because you're giving the customer a constructive way to respond, which improves resolution rates while making the urgency clear. Naming the prior contact date in your opening line signals persistence without aggression and gives the customer fewer grounds to claim they weren't notified.
Final demand letters must state consequences without emotional language. "Your account will be referred to our collections partner on [date] if payment is not received" is more effective than "We are extremely disappointed." Stick to facts: the amount, the date, and the consequence.
Not every customer responds to the same approach. VIP accounts with a history of paying slightly late need a different touch than long-tail accounts you've never called. A customer who always pays after a phone call doesn't need four emails first.
Stuut tracks each customer's response history across email, SMS, and voice, and uses that behavioral data to adjust channel selection and timing per account. If a customer consistently responds to SMS but ignores email, Stuut routes future contacts through SMS without you updating a rule or editing a spreadsheet.
Dunning letters carry legal weight, and the rules vary depending on whether you're collecting B2B or B2C debt, using first-party outreach or a third-party agency, and operating across multiple jurisdictions. Most AR teams focus on the message and forget that the channel, timing, and opt-out language are equally regulated. The sections below cover the federal rules that apply to most B2B collections programs and flag the state-level requirements that extend beyond them.
The Fair Debt Collection Practices Act covers third-party collectors pursuing consumer debt, not B2B first-party collections. However, some states extend protections to original creditors. The FDCPA prohibits contact before 8 a.m. or after 9 p.m. for third-party collectors, which is a useful B2B standard even when not legally required. If your AR process uses a third-party collections agency, FDCPA compliance becomes mandatory.
The Telephone Consumer Protection Act (TCPA) requires prior express written consent before you send marketing texts, make marketing robocalls, or send fax advertisements. Qualifying consent includes a signed credit application with SMS opt-in language, a checkbox acknowledgment on an onboarding form, or a written agreement that explicitly authorizes automated communications to a specific phone number. Verbal consent does not meet the written consent standard under TCPA. Violations carry statutory damages of $500 to $1,500 per violation per class member, which makes compliance non-negotiable. Since April 2025, FCC rules require you to honor opt-out requests through any reasonable method, not just STOP keyword replies. Document consent records in your CRM before launching any SMS dunning program.
California, New York, and Texas enforce state-level debt collection statutes that extend beyond FDCPA rules, and some apply to original B2B creditors. If your AR portfolio spans multiple states, align your templates with the strictest applicable jurisdiction rather than maintaining state-by-state variations. Review your templates with legal counsel when rolling out in new states, and document your compliance process as part of your AR policy.
Avoid language that implies legal action you haven't authorized, suggests credit reporting you won't pursue, or creates a record a court could construe as harassment. Specifically:
Relying solely on email fails because AP contacts change, inboxes fill, and automated reminders get filtered. Adding SMS and voice to your dunning program reaches customers that email alone misses. Each channel serves a different function: email creates a documented paper trail, SMS catches attention when inbox volume is high, and voice handles accounts that need a live conversation to resolve.
Email is the primary B2B dunning channel. Keep subject lines factual and include three elements sources consistently recommend: the word "Invoice," the invoice number, and the due date, for example, "Invoice #[INV-XXXX] - Payment due [DATE]". Attach the invoice PDF directly for first reminders, since many customers misplace the original, and include the payment amount, due date, and a payment link in the first three lines.
SMS works for Stage 2 and 3 reminders once you've made email contact. Aim for brevity, but required elements take priority over the 160-character single-segment limit. When company name, invoice number, amount, payment link, and opt-out instructions are included, most messages will span two SMS segments (up to 306 characters, because concatenated multi-part messages reserve 7 bytes per segment for the User Data Header, reducing each segment from 160 to 153 usable characters). That's acceptable provided every required element is present.
Voice calls reach AP contacts that written communications don't, and they move faster to resolution because they create two-way dialogue rather than a request waiting in an inbox. AI-powered voice calling now enables AR teams to run contextual calls at scale, with the AI agent carrying full knowledge of each customer's account, prior payment history, and conversation log. The call script below gives your team or AI agent a structure that covers the four most common responses: confirmed payment, no invoice on file, dispute, and no answer.
Opening: "Hi [Name], this is [Your Name] calling from [Company]'s AR team."
Core message: "I'm following up on invoice [INV-XXXX] for $[AMOUNT], which was due on [DATE]. I wanted to check if there's anything we can help process quickly."
If they confirm payment is coming: "Great. Can you give me an estimated payment date so I can update our records?"
If there's an issue: "Understood. What do we need to correct to get this resolved today?"
If no answer: Leave the invoice number, amount, your callback number, and a payment link.
A research-backed multi-channel sequence for a B2B invoice:
Every dunning letter needs the same core information to be actionable. Missing any of these elements forces the customer to reply with questions, which adds days to collection time. Review each template against this list before sending and confirm all fields are populated from your ERP data rather than left as placeholders.
Required elements for every dunning letter:
Always cite the invoice number and purchase order number if one was issued, because many AP departments process by PO number and a missing reference is one of the most common reasons invoices stall in approval queues. State the number of days explicitly: "Invoice #INV-2456 is now 47 days past due" cuts through faster than "your payment is overdue."
For payment options, include every method you accept: ACH bank details, credit card, check mailing address, and any online payment portal. When using payment links in dunning communications, ensure they meet PCI compliance requirements and use secure, tokenized checkout processes. Stuut generates and sends Stripe payment links during customer conversations so the customer receives a secure checkout link for immediate settlement.
Note: Replace bracketed fields [First Name], [INV-XXXX], [AMOUNT], and [DATE] with actual customer and invoice data. Stuut populates these fields automatically from your ERP data. Review all templates with legal counsel before use to ensure compliance with applicable federal and state debt collection laws in your jurisdictions.
Subject: Invoice #[INV-XXXX] - Payment reminder
Hi [First Name],
This is a quick note to flag that invoice #[INV-XXXX] for $[AMOUNT] was due on [DUE DATE]. We've attached a copy in case the original was misplaced or landed in the wrong inbox.
If you've already sent payment, thank you and please ignore this message. If not, you can pay directly at [PAYMENT LINK] or reply to this email with any questions.
[Your Name] | [Company] AR Team | [Phone]
Subject: Invoice #[INV-XXXX] - [X] days past due
Hi [First Name],
Invoice #[INV-XXXX] for $[AMOUNT] is now [X] days past due. We sent a reminder on [DATE] and haven't received a response or payment yet.
Please confirm the payment status or let us know if there's an issue we can address. You can pay via [PAYMENT LINK] or reach me directly at [PHONE/EMAIL].
[Your Name] | [Company] AR Team
Subject: Urgent: Invoice #[INV-XXXX] requires your immediate attention
Hi [First Name],
I'm following up on invoice #[INV-XXXX] for $[AMOUNT], which is now [X] days past due. We've reached out on [DATE 1] and [DATE 2] without receiving payment or a response.
We need to resolve this by [RESOLUTION DATE] to avoid placing your account on hold. Please reply to confirm a payment date or call me at [PHONE] today.
[Your Name], [Title] | [Company]
CC: [Account Manager Name]
Subject: Final notice - Invoice #[INV-XXXX] | Action required by [DATE]
Dear [First Name],
Invoice #[INV-XXXX] for $[AMOUNT] is now 90 days past due. Despite contact on [DATE 1], [DATE 2], and [DATE 3], we have not received payment or a response.
If we do not receive full payment or a confirmed payment arrangement by [DEADLINE DATE], we will refer this account to our collections partner and may report the balance to commercial credit bureaus.
To resolve this today, pay at [PAYMENT LINK] or call [PHONE] to discuss a payment arrangement. We want to resolve this before external action becomes necessary.
[AR Manager Name], [Title] | [Company]
[Company Name]: Hi [First Name], invoice #[INV-XXXX] for $[AMOUNT] is [X] days past due. Pay now: [LINK] or call [PHONE]. Reply STOP to opt out.
Opening: "Hi [Name], this is [Your Name] calling from [Company]'s accounts receivable team. I'm reaching out about invoice #[INV-XXXX] for $[AMOUNT], which was due on [DATE]."
If they confirm payment is coming: "Great. Can you give me an estimated payment date so I can update our records?"
If they haven't received the invoice: "No problem. I can resend it right now. What's the best email address? I can also send a payment link so you can process it as soon as you receive it."
If they raise a dispute: "I'll log that as a dispute and make sure the right person on our team follows up today. Can you send me the details in writing so I can route this accurately?"
Closing: "Thanks for your time. You'll hear from us by [DATE] with a resolution. My direct line is [PHONE] if anything comes up before then."
The templates above give you the structure. Adjusting tone, channel, and format for your specific customer base determines whether they convert. The two variables that matter most are the region your customer operates in and the currency and date formatting on the invoice itself.
International invoices need explicit formatting and country-level compliance checks. Spell out the month (June 15, 2026, not 06/15/26), include the currency code (USD, EUR, GBP), and specify bank account details in the format used in the customer's country. Regulations also vary significantly across jurisdictions: EU-based customers fall under GDPR, which governs how you store and process contact data used in dunning outreach, and UK collections are subject to FCA debt collection guidance that sets conduct standards for creditor communications.
If your AR portfolio includes customers in these regions, review your dunning templates and data practices with legal counsel before sending automated outreach across those accounts. Complete bank routing details in the invoice can help streamline the payment process.
California, New York, and Texas maintain debt collection statutes with requirements beyond the federal FDCPA, and some cover original B2B creditors. For teams managing multi-region AR complexity, the Versapay alternatives guide covers ERP integration considerations that affect cross-border collections.
The templates above take time to write, but that's the easy part. The hard part is sending them consistently across 500 accounts while tracking responses, logging promises to pay, routing disputes, and updating your ERP in real time. That's where AR teams lose hours every day.
Stuut is designed to monitor invoice due dates across your AR portfolio and contact customers before invoices go overdue, not just after. It sends reminders across email, SMS, and voice, choosing the right channel based on each customer's history.
When a customer replies with a question, Stuut handles the response: logging promise-to-pay dates, resending invoices, answering balance questions, and routing complex issues to your team. This approach helps AR teams cover their full account portfolio without adding headcount, because the AI covers the accounts you never had time to contact while you focus on the ones that need your judgment.
One of the most common concerns we hear from collections teams is that automated communications will damage relationships with key accounts. It's a legitimate concern. Stuut addresses it by giving your team visibility and configuration control: you can see all customer interactions in real time through the dashboard and configure which accounts receive AI-driven outreach based on your portfolio strategy.
AI in collections works best when it handles volume and humans handle judgment, not as a replacement but as a division of labor that matches skill to task. Your expertise becomes more valuable when the AI handles volume because your institutional knowledge about which disputes need sales involvement, which payment plans require AR Director approval, and which customers respond only to a phone call is what routes exceptions correctly and coaches the AI on tone and timing for your portfolio.
Stuut connects to SAP, Oracle, NetSuite, and Microsoft Dynamics via API without modifying your ERP configuration. The average onboarding completes in 3-4 days, with full go-live, including configuration, typically within 6-10 days. For context on how that compares to legacy platforms, see the HighRadius implementation timeline guide.
Bishop Lifting, an industrial equipment company with 45 branches and over 1,000 invoices processed daily, reduced overdue receivables by 35% and reportedly unlocked millions in working capital after going live with Stuut. Their AR team went from managing collections reactively to handling 50% more accounts per employee, with Stuut covering 91% of outbound communications autonomously. The team didn't shrink. They shifted from chasing routine payments to managing complex disputes and strategic accounts.
When your dunning cadence has been completed without payment or a resolution (typically 4-6 communications over 60-90 days with no response, broken promise-to-pay dates, or refused contact), the account moves to external action: referral to a commercial collections agency, credit bureau reporting, small claims court for smaller balances, or formal legal proceedings for larger ones.
Document every contact attempt and response before external escalation because that record supports your claim. Book a demo to see how Stuut handles dunning across your AR portfolio, covering every account in your aging report without adding headcount.
A dunning letter is a written communication sent to a customer requesting payment on an overdue invoice. The term covers everything from a first friendly reminder to a final formal demand before collections or legal action.
Most B2B AR teams send 4-6 communications over 60-90 days before escalating to a third-party agency or legal action, following a cadence that starts at day +1 and escalates at day +60.
No, the federal FDCPA applies specifically to consumer debt collected by third-party agencies, not to first-party B2B collections. However, some states extend broader protections that may apply to B2B original creditors.
The TCPA requires prior express written consent before sending marketing or automated text messages. You need to honor opt-outs through any reasonable method. Restricting contact to 8 a.m. to 9 p.m. local time is a FDCPA requirement for third-party collectors and a recommended best practice for first-party B2B outreach, but it is not a legal TCPA requirement for first-party collections. Document consent in your CRM regardless of message type.
The account moves to external action: referral to a commercial collections agency, credit bureau reporting, small claims court for smaller balances, or formal legal proceedings for larger ones. Document all prior contact attempts before taking external action.
Automation handles the routine, low-risk contacts: first reminders, invoice resends, and payment confirmations. Your AR team focuses on complex accounts, VIP relationships, and disputes that require judgment. Automation improves customer response times by covering accounts you never had time to reach manually.
Dunning letter: A formal payment reminder sent to a customer with an overdue invoice, progressing in urgency across multiple stages until payment is received or the account is escalated.
Aging buckets: Time segments used to categorize overdue invoices: 0-30, 31-60, 61-90, and 90+ days past due. Each bucket typically triggers a different dunning stage and tone.
DSO (Days Sales Outstanding): The average number of days it takes to collect payment after a sale. Lower DSO means faster cash conversion, and effective dunning directly reduces DSO.
FDCPA: The Fair Debt Collection Practices Act, a federal law regulating third-party debt collectors pursuing consumer debt. It does not cover first-party B2B collections federally, though some states extend similar protections to original creditors.
TCPA: The Telephone Consumer Protection Act, which governs automated calls, SMS marketing, and fax advertising. It requires prior express written consent for marketing texts and automated calls and applies to B2B outreach programs.
Cash application: The process of matching incoming payments to open invoices in your AR subledger. Manual cash application is a key bottleneck in month-end close.
Promise to pay: A customer's verbal or written commitment to pay by a specific date, logged during a collection call or email exchange. It forms the basis for the follow-up timeline.
Short-pay: When a customer pays less than the full invoice amount, often due to a deduction, disputed line item, or early-pay discount. Short-pays require investigation and often generate a separate dunning communication for the balance.
Dunning cadence: The sequence of communication touchpoints sent at defined intervals across a dunning campaign, typically covering email, SMS, and voice across 4-6 touches over 60-90 days.
%20STUUT%20_%20WSJ%20Banners.pdf%20(4).png)
