Dunning email best practices for B2B AR teams

‍

Sending a customer a statement with five overdue invoices seems efficient, but it's actually the fastest way to delay payment because AP departments work from queues and a multi-invoice statement creates a research task, not a payment prompt. Each invoice needs to be located, matched against internal POs, and approved separately before any payment moves forward.

B2B dunning emails that get paid rely on clarity, single-issue framing, and technical deliverability standards that most AR teams overlook entirely. But knowing the best practices is only half the problem. Executing them consistently across hundreds of accounts without missing the long-tail customers nobody has time for requires moving beyond manual workflow tools and into autonomous execution.

Crafting effective B2B dunning emails

Subject lines that drive invoice action

Subject lines that include the invoice number and specific amount due consistently outperform generic alternatives. Your AP contact receives dozens of vendor emails per day, and a subject line reading "Action required: Invoice #4821 for $12,450 due today" gives them exactly what they need to prioritize without even opening the message.

Best practices for B2B dunning subject lines:

• Include invoice number and dollar amount: Give AP contacts what they need to act without opening a second system
• Use direct language: "Action required" or "Payment due" outperforms "Friendly reminder" for overdue invoices
• Match urgency to aging bucket: A 3-day-late email sounds completely different from a 45-day-late one

Avoid using symbols like $, !, or * in subject lines and never write in ALL CAPS. These formatting choices trigger spam filters before the recipient's mail server evaluates any content.

Send one overdue item at a time

AP departments process invoices from a queue. When you send a five-invoice statement, you're not asking the AP analyst to pay five invoices. You're asking them to create a project. Each item needs to be matched against a PO, reviewed against goods receipt, and approved by a different person depending on dollar thresholds.

Send one invoice per email. Each email becomes a single, completable action: The AP analyst opens it, clicks the payment link, and it's done. Treating each invoice separately rather than batching them is one of the highest-impact changes a collections team can make to its daily output.

Prevent delays: Include invoice PDF

The most common payment delay isn't a dispute. It's a missing document. "We never received the invoice" is a real problem in B2B, where invoices arrive through email, customer portals like Ariba and Coupa, and sometimes EDI. Attaching the original invoice PDF to every dunning email eliminates that excuse and removes the customer's need to go looking for it in another system.

Include in every email:

• The original invoice PDF as an attachment
• Invoice number, due date, and amount in the email body
• The PO number if one was provided at order time (many ERPs require this for payment approval)

Image-only email formats trigger spam filters and prevent the email body from being searched by the recipient's AP team when they try to locate the message later.

Position payment link early for action

The payment link needs to appear in the first paragraph, not at the bottom after three paragraphs of account history. If the AP analyst has to scroll to find the payment method, many won't, because pay-or-skip decisions happen fast in a busy AP inbox.

Stuut's digital payment integration generates a payment link via Stripe and places it in the communication automatically. When a customer clicks through, they can complete payment directly, replacing the manual processes many industrial companies still use, including AR teams writing down credit card numbers and keying them into SAP.

When and how to increase dunning urgency

Dunning should escalate in both tone and contact level as invoices age, progressing from informational touchpoints to formal notices and escalation.

Early dunning email: Build trust

Send a pre-due reminder at Day -3 as a service touchpoint: Confirm the invoice details, provide the amount and due date, and offer the AP team a chance to flag potential issues. Day +1 should be courteous, acknowledging that payments can cross in transit while confirming you haven't received payment yet. Include the invoice PDF, a payment link, and your direct contact information.

For manufacturing and distribution businesses running Net 60 terms, extend your cadence by 15 to 20 days to match standard industry payment cycles. Pressing too hard on a Net 60 invoice that's only 45 days old damages the relationship without accelerating cash, because payment isn't due for another 15 days.

Day +7 and Day +14: Clear and urgent language

Day +7 and Day +14 emails shift tone from informational to professional urgency. State clearly that the invoice is overdue, how many days past due, and what the next steps are if payment isn't received. If your contracts include late fees, reference the applicable clause and the exact fee amount. Do not apologize for following up. Collecting on a valid, delivered invoice is a normal business activity.

The final dunning email ultimatum

Day +30 introduces the formal notice stage. This email should come from your AR Manager or Controller, and it needs to clearly state three things:

1. The total amount outstanding and exact number of days overdue
2. The specific date by which payment must be received
3. The consequence if payment is not received (credit hold, late fees, referral to external collections)

Day +45 is the final warning before escalation. Name the consequence and follow through on it.

The right moment for a collection call

Email isn't always enough. For invoices over 30 days past due or accounts that have gone silent, a phone call carries urgency that text cannot replicate. Stuut's AI-powered voice calling contacts customers with full account context, including open invoices, payment history, and prior communications, and handles real conversations, confirming payment timing, answering balance questions, and escalating to a human when the situation requires judgment.

This matters specifically for industrial buyers in manufacturing and distribution, where phone-based collections remain standard. Most AR platforms have zero calling capability. Stuut's AI-powered call agent contacts customers with full account context and handles real conversations without a human initiating each call. Stuut chooses the right channel based on customer history and urgency, so your team doesn't have to manually triage which accounts need a call today.

Dunning email templates for each overdue phase

The contact you email determines whether a dunning email gets actioned or ignored. Early-stage emails typically target the AP team, while later-stage communications escalate to management and finance leadership.

Primary contact: Accounts payable (early stage)

Subject: Action required: Invoice #[XXXX] for $[AMOUNT] due [DATE]

Key elements for this stage:

• Open with the payment link in the first sentence
• Attach the invoice PDF and reference the PO number
• Keep the body between 75 and 100 words, because Drip research shows emails in this range achieve the highest response rates at 51%
• Close with your direct phone number and AR email address

When to loop in the AP manager (later stage)

Example subject: Invoice #[XXXX] - [XX] days overdue: $[AMOUNT]

Key elements for this stage:

• Address the AP Manager by name and cc the original AP contact
• Summarize prior contact attempts (number of emails sent, dates)
• State the number of days past due explicitly in the first sentence
• Repeat the payment link and attach the invoice again

For accounts with no response after multiple emails, adding a direct phone number and requesting a specific callback date can improve reply rates.

CFO/VP Finance for escalated payments (extended overdue)

Example subject: Outstanding balance of $[TOTAL] - [YOUR COMPANY NAME]

Key elements for this stage:

• Address the CFO or Finance Director directly, keeping the message under 100 words
• Lead with the total outstanding balance and days overdue
• State the specific payment deadline and consequence (credit hold, collections referral)
• Offer a direct phone call to discuss resolution

When to involve sales in dunning

Loop in your Account Manager when the invoice is tied to a renewal at risk, the customer has raised unresolved service concerns, or your team has made multiple contact attempts with no response. When sales gets involved to address underlying relationship issues or disputes, pause the formal dunning cadence on that specific invoice until resolution. Resume dunning only after the underlying issue is cleared.

Ensure dunning emails reach their inbox

Technical deliverability directly determines your cash collection rate. Dunning emails that land in spam are invisible to your AP contact, and the invoice ages regardless.

Is your email reputation hurting collections?

Your domain's sender reputation determines whether your emails reach inboxes or spam queues. ISPs score your domain based on bounce rates, spam complaints, and engagement history. If your AR team sends dunning emails from a shared marketing domain or a domain without authentication, emails get filtered before anyone reads them. A deteriorating sender reputation produces collection failures that look like customer non-response but are actually a deliverability problem your team can fix.

SPF, DKIM, DMARC for email deliverability

Configure all three authentication protocols for any domain sending dunning emails:

• SPF (Sender Policy Framework): Lists which servers are authorized to send email from your domain
• DKIM (DomainKeys Identified Mail): Adds a cryptographic signature proving the email content hasn't been altered since it left your server
• DMARC: Tells receiving mail servers what to do if SPF or DKIM checks fail, and generates reports so you can see authentication failures

Missing even one creates a gap that spam filters use to downgrade your deliverability score regardless of how well-written your email content is.

Strategies to bypass spam filters

Remove these from every dunning email template before sending at scale:

• Symbols like $, !, or * in subject lines
• ALL CAPS phrases in subject or body text
• URL shorteners (bit.ly and similar) for payment links, which spam filters associate with phishing attempts, so use full branded URLs instead
• Image-only email bodies with no plain text content
• Phrases like "act now," "free," or "limited time offer"

Always test email templates in a spam checker before deploying across your full portfolio.

Confirm emails reach the inbox

Track bounce rate, open rate, and hard bounces alongside collection rate. A bounce rate above 2% begins damaging sender reputation, and hard bounces should stay below 0.5% for any well-managed outbound campaign since each one signals an invalid address in your ERP. Low open rates on dunning emails typically indicate spam placement rather than genuine disinterest from the customer.

Review and act on all customer feedback

Dunning emails generate replies that contain critical AR intelligence: Dispute signals, contact changes, PO mismatches, and promise-to-pay dates. An AR team that can't capture and act on these replies the same day loses both the data and the payment.

Configure your dunning reply address

Never send dunning emails from a no-reply address. A customer replying to confirm payment or flag an invoice error needs that reply to reach someone who can act on it immediately. Use a monitored AR inbox that routes to your collections team or your AR platform's triage queue.

Assigning dunning email responses

Every inbound reply needs to be triaged and actioned promptly. Common reply types and the correct response:

• Promise to pay: Log the date, set a follow-up if payment doesn't arrive by the committed date
• Invoice not received: Resend immediately with PDF attachment
• Dispute: Pause dunning on that invoice, open a dispute case, and route to the correct internal team
• Wrong contact: Update your ERP with the correct AP contact and resend to the corrected address

Stuut autonomously triages inbound replies across email, SMS, and voice. It logs promise-to-pay dates, resends invoices on request, answers balance questions, and routes disputes to a human analyst, which is the work that prevents your team from spending entire afternoons on email detective work instead of strategic collections.

Dealing with bounced dunning emails

Hard bounces indicate invalid addresses and require immediate action:

1. Check your ERP for typos and search for alternative AP contacts
2. Contact your sales team for the current correct contact information
3. Update your ERP, resend to the corrected address, and document the change in your audit trail so future communications route correctly. If a customer consistently uses a non-standard AP routing, log the preferred submission method in your ERP so the entire team benefits from the discovery.

Your toughest dunning email questions answered

Optimal dunning email cadence

For most B2B businesses on Net 30 terms, a seven-touch cadence from Day -3 through Day +60 produces the best results: Day -3 (pre-due courtesy notice), Day +1 (first reminder), Day +7 (second reminder), Day +14 (firm follow-up), Day +30 (formal notice from AR Manager), Day +45 (final warning), and Day +60 (escalation or collections referral). For manufacturing and distribution businesses on Net 60 terms, see the cadence adjustment guidance in the Early dunning email section above. Research consistently points to Tuesday through Thursday, 9:00 to 10:30 AM in the recipient's local time zone, as the highest-engagement window [source].

Target dunning emails by customer

Not every customer should receive the same cadence. Segment your portfolio into at least four groups:

1. On-time payers: Light-touch cadence with a Day -3 pre-due notice as the primary touchpoint
2. Habitual late payers: Compressed cadence starting at Day +1, with a voice call added by Day +14
3. High-risk accounts: Escalate to AP Manager earlier in the cycle and involve senior AR leadership at extended aging
4. Strategic VIP accounts: Manual review before each outreach, because these accounts need white-glove treatment and the collections approach should reflect that relationship value

Handling 'invoice not received'

The three steps that prevent this delay (attaching the PDF, including the PO number in the body, and logging portal submissions in your ERP) are covered in the Prevent delays: Include invoice PDF section above.

Avoiding automated dunning mistakes

A common automated dunning mistake is cadence-blindness: The system keeps sending emails on schedule without recognizing that a customer has disputed an invoice, made a partial payment, or already committed to a payment date. This happens with rule-based automation because the rules can't adapt to new information without manual reconfiguration. If a customer who always pays on the 15th receives a third reminder on Day +10, you've created noise and damaged trust without accelerating payment.

Stuut's self-learning intelligence recognizes these patterns automatically. It pauses outreach when a dispute is detected and adapts cadence based on individual payment patterns without requiring your team to update rules manually.

Dunning email checklist

Before every dunning campaign goes out, verify:

• Subject line includes invoice number and dollar amount
• Invoice PDF attached
• Payment link placed in the first paragraph
• PO number referenced if applicable
• Correct contact at the correct escalation level for the aging bucket
• SPF, DKIM, and DMARC configured on the sending domain
• No spam trigger words, symbols, or URL shorteners in the email
• No-reply address replaced with a monitored AR inbox
• Dispute flags checked before sending (never dunning an invoice in active dispute)
• Segmentation applied (VIP accounts manually reviewed before outreach)

Manual vs. autonomous dunning: What changes

‍

Bishop Lifting reduced overdue receivables by 35% and unlocked $3M in working capital by using Stuut's autonomous collections across 45 branches, with the AI handling 91% of outbound communications and the AR team shifting to complex disputes and white-glove service for top accounts. PerkinElmer reduced overdue invoices from 50% to 15% in one year while collecting $300M, managing 80% of tail customers through automation.

Book a demo with the team to see how Stuut handles the dunning volume your team doesn't have capacity for. Stuut covers every account in your portfolio while your collectors focus on the disputes and relationships that require real judgment.

FAQs

How many dunning emails should you send before escalating to a collections agency?

Most B2B AR teams work through 5 to 7 dunning touches over 45 to 60 days before referring an account to external collections. For strategic accounts, involve your Account Manager at Day +30 to explore resolution before escalating externally.

What is the best time and day to send a B2B dunning email?

Research consistently points to Tuesday through Thursday, 9:00 to 10:30 AM in the recipient's local time zone, as the highest-engagement window [source], and subject lines that include the invoice number and specific dollar amount consistently improve open and action rates.

How much does one day of DSO cost a mid-market company?

One day of DSO equals approximately $137,000 in tied-up working capital for a company with $50M in annual revenue (annual revenue divided by 365 days). Reducing DSO by 5 days frees roughly $685,000 in cash at that revenue level, so a 10-day reduction would free approximately $1.37M using the same formula, though this is an extrapolation rather than a figure drawn directly from published benchmarks.

What is the difference between a dunning email and a payment reminder?

A payment reminder goes out at or before the due date and is a courtesy touchpoint. A dunning email is sent after the due date and is a collections action with escalating urgency, named consequences, and a clear escalation path.

Key terms glossary

Dunning: The structured process of contacting customers with overdue invoices through a sequence of escalating communications, from courtesy reminders through formal notices and external collections referrals.

Days Sales Outstanding (DSO): A measure of how long it takes to collect payment after a sale, calculated as accounts receivable divided by total credit sales, multiplied by the number of days in the period. Lower DSO means faster cash conversion and more working capital available for operations.

Cash application: The process of matching incoming payments to specific open invoices in the ERP. Stuut's automated cash application achieves a 95%+ automated match rate with real-time ERP posting.

Aging buckets: Categories that group open invoices by how long they've been outstanding, typically 0 to 30, 31 to 60, 61 to 90, and 90+ days. Aging buckets determine dunning urgency level, escalation contact, and when to involve collections.

PO (Purchase Order): A commercial document issued by a buyer to a vendor authorizing a purchase transaction. Many B2B AP departments require the PO number to match invoices to authorized purchases before processing payment.