Finance teams use Sage to manage accounts receivable, providing accurate invoice data, customer balances, and visibility into ageing. Within these teams, AR specialists, credit controllers, and finance managers rely on Sage to track invoices, monitor overdue accounts, and enforce collections policies.
For AR teams running structured collections processes, dunning messages are a critical tool to encourage timely payment and reduce overdue exposure. In Sage, these messages can be automated to ensure customers receive consistent, policy-aligned communications as invoices progress through ageing stages. This includes defining escalation timing, standardising message content, managing customer responses, and maintaining records to support reporting and oversight.
This guide provides a practical framework for automating dunning messages in Sage, enabling AR teams to improve efficiency, enforce credit policy, and maintain professional customer interactions—without requiring changes to the underlying finance system.
What do dunning messages mean in accounts receivable?
In B2B accounts receivable, dunning messages are structured escalation communications sent when invoices become overdue. They reflect a defined collection policy and progress based on invoice ageing and customer behaviour.
As escalation progresses, three things typically change:
Tone — from informational to directive
Authority — from AR operations to finance leadership
Outcome — from reminder to enforcement
The objective of dunning messages is to get customers to pay on time, provide a clear payment commitment, or raise a dispute early enough to resolve it.
How dunning messages run in Sage environments
Sage is commonly used by scaling finance teams, including multi-entity organisations, where accounts receivable operations need a reliable system of record for invoices, customers, balances, and ageing.
In most Sage-led AR teams, dunning messages are executed across a hybrid workflow:
Sage holds the invoice and customer balance truth
Email is the communication channel
Shared inboxes support customer responses
Spreadsheets or notes are used for tracking commitments and disputes
What Sage enables for dunning automation
Sage provides the essential information AR teams need to manage overdue invoices, including:
Customer and invoice records – a complete view of who owes what
Open receivables visibility – seeing which invoices are unpaid
Ageing reporting – tracking how long invoices have been overdue
Payment and allocation tracking – knowing which payments have been made and applied
Customer contact information – ensuring messages reach the right person
Reporting for oversight – monitoring collections performance
Sage stays the main system of record while dunning automation works on top of Sage to make sure messages are sent consistently according to company policy, and that results like payments or disputes are tracked in an organised way.
The 3 components of a Sage dunning workflow
The dunning process works best when three areas are clearly defined:
Which invoices to follow up on (Eligibility and Timing)
Decide which overdue invoices should receive dunning messages and when.
Consider factors like due date plus any grace period, minimum invoice amounts, or accounts with active disputes.
Segment customers if needed, so communications are appropriate for each group.
How messages escalate (Escalation Policy)
Define what happens as invoices stay unpaid longer.
This includes the stages of escalation, how often messages are sent, the tone used, and who sends them (AR staff or senior finance).
Escalation should follow company policy and gradually move from reminders to more formal action if needed.
How responses are handled (Execution and Response Handling)
Plan what happens after a message is sent.
Capture customer replies, track promises to pay, and route disputes or questions to the right team.
Apply rules consistently, such as pausing follow-up if a valid dispute exists or resuming if a payment commitment is missed.
When these three components work together, dunning in Sage becomes a structured, repeatable process rather than a series of manual reminders.
Example dunning message workflow in Sage (1–45 days overdue)
Below is a practical example of how dunning messages can be automated in a Sage environment. This is not a universal template — it’s a starting framework that most AR teams can adapt by customer segment, region, or entity.
Days 1–7 overdue: Friendly reminder
Objective: prompt payment or confirm payment status.
Message tone: helpful, low-friction.
Action: resend invoice and payment details if needed.
Days 8–14 overdue: Direct follow-up
Objective: get a payment commitment date.
Message tone: clear, firm, but still customer-friendly.
Action: request a confirmed payment date and escalation contact if needed.
Days 15–30 overdue: Escalation message
Objective: move the account into structured escalation.
Message tone: directive.
Authority: senior AR/finance operations.
Action: confirm escalation stage and policy expectation.
Days 31–45 overdue: Final notice
Objective: trigger payment, dispute submission, or credit action.
Message tone: formal and time-bound.
Authority: finance leadership/credit.
Action: clear consequence (e.g., credit hold review, service impact, formal credit escalation).
This timeline is useful because it forces consistency. The automation goal is not sending more messages — it is ensuring the right messages are sent at the right stage, and that replies lead to the correct next action.
Step-by-step: how to automate dunning messages in Sage
The most effective approach to dunning automation in Sage follows a simple sequence.
1) Define dunning message stages and escalation rules
Start by mapping your stages clearly. Most organisations already have these informally, but automation requires them to be explicit.
A typical structure includes:
Stage 1: friendly reminder
Stage 2: follow-up and commitment request
Stage 3: escalation
Stage 4: final notice/credit action
2) Set eligibility rules so only the right invoices enter dunning
Eligibility rules prevent “false chasing,” which is one of the fastest ways to damage customer trust.
Common eligibility logic includes:
Overdue invoices beyond a grace period
Invoices above a minimum threshold
Excluding invoices with active disputes
Excluding invoices pending billing correction
Excluding customers on special arrangements
3) Automate outbound dunning messages with consistent timing
Once eligibility is defined, automation ensures:
The right message is sent at the right stage
Timing is predictable
Coverage is complete across the volume
Tone and authority match the escalation stage
This is where most teams begin — and it creates immediate efficiency.
4) Standardise dunning message structure (without making it robotic)
Strong dunning messages are structured, but not generic.
High-performing dunning messages typically include:
Invoice reference(s), due date(s), outstanding amount(s)
A clear request (pay, confirm date, raise dispute)
Payment instructions or portal link
The next step and escalation expectation
The correct sender authority for the stage
5) Automate response handling and link replies to invoice context
Outbound messages are predictable. Customer replies are not.
Responses typically include:
Payment confirmations
Revised payment commitments
Dispute notifications
Operational/admin queries
“Sales is blocking payment” objections
Automation becomes truly effective when replies are:
interpreted consistently
Linked to the correct customer and invoice context
Recorded in a structured way
Routed to the right owner when needed
This is what turns dunning into a controlled workflow rather than a series of email threads.
6) Apply pause and resume rules consistently
Most AR policies already define conditions such as:
Pause escalation if a dispute is valid
Pause escalation if a commitment is confirmed
Resume escalation if the commitment date is breached
Escalate if exposure breaches a threshold
Automation allows these rules to be applied systematically so treatment remains consistent across collectors, teams, and entities.
7) Route exceptions without breaking the workflow
Not all cases should be handled end-to-end through automation.
A strong Sage dunning automation model:
Automates the standard cases
Identifies exceptions early
Routes them to the correct owners
Reserves full context, so manual work is efficient
Typical exception owners include:
AR operations
Disputes/billing
Credit
Sales (only when needed)
8) Feed dunning outcomes back into reporting and oversight
Dunning messages generate behavioural signals. Automation makes it possible to capture them consistently, including:
Promise-to-pay reliability by customer
Dispute frequency by escalation stage
Response behaviour by segment
Escalation effectiveness over time
Time-to-resolution for customer queries
These signals support:
Improved forecasting
Earlier credit intervention
Better customer segmentation
Stronger controllership and governance
Dunning message templates (by escalation stage)
Below are enterprise-grade templates designed to be automated. They are intentionally short, structured, and policy-aligned.
Note: These templates assume B2B customers and should be adapted for entity, region, and legal requirements.
Template 1: Friendly reminder (early overdue)
Subject: Reminder: Invoice [INV-XXXX] now overdue
Hi [Name],
I’m reaching out regarding invoice [INV-XXXX] for [Amount], due on [Due Date], which is now overdue.
Could you confirm payment status and expected payment date? If you need the invoice resent or payment details, I’m happy to provide them.
Thank you,
[Sender Name]
Accounts Receivable | [Company]
Template 2: Follow-up + payment commitment request (8–14 days)
Subject: Action required: Payment date confirmation for invoice [INV-XXXX]
Hi [Name],
Invoice [INV-XXXX] for [Amount] remains outstanding and is now [X] days overdue.
Please confirm the expected payment date. If there is a dispute or issue preventing payment, please share the details so we can resolve it promptly.
Kind regards,
[Sender Name]
Accounts Receivable | [Company]
Template 3: Escalation message (15–30 days)
Subject: Escalation: Overdue balance for [Customer Name]
Hi [Name],
We are following up as invoice [INV-XXXX] for [Amount] remains unpaid and is now [X] days overdue.
In line with our payment policy, this account is now in escalation. Please confirm payment by [Date] or provide dispute details immediately so the correct action can be taken.
Regards,
[Sender Name]
Finance Operations | [Company]
Template 4: Final notice / credit action (31–45 days)
Subject: Final notice: Overdue invoice [INV-XXXX] – immediate action required
Hi [Name],
Invoice [INV-XXXX] for [Amount] remains outstanding and is now [X] days overdue.
Unless payment is received or a formal dispute is submitted by [Date], the account may be reviewed for credit action in line with our policy.
Please confirm your next steps today.
Sincerely,
[Sender Name]
[Title] | Finance / Credit | [Company]
Benefits of automating dunning messages with Sage
When Sage is used to automate dunning messages, accounts receivable teams typically see measurable improvements across three areas:
1. Operational Efficiency
Reduces manual chasing of overdue invoices
Minimises time spent managing inboxes and tracking customer replies
Limits repeated follow-ups by standardising messaging
Frees collectors to focus on high-risk accounts and more complex cases
2. Cash Flow
Speeds up customer payments
Makes Days Sales Outstanding (DSO) more predictable
Decreases the number of disputes that reach late stages
Improves enforcement of payment commitments
3. Governance and Customer Experience
Ensures consistent escalation treatment across accounts
Provides clear records of commitments, disputes, and customer interactions
Reduces the risk of sending conflicting messages to customers
Improves coordination between AR, credit, disputes, and sales teams
Where AI agents can extend Sage dunning message automation
Beyond traditional ERP automation, finance teams are using AI agents to make dunning smarter, faster, and more consistent. Unlike fixed workflows, AI agents act as an agentic execution layer, ensuring that dunning messages are sent reliably, customer responses are interpreted correctly, and follow-up is aligned with company policies.
One example is Paraglide, which sits on top of tools like Sagee without r redefining your dunning policies. Its AI agents work directly in the finance inbox to reply to billing queries, manage routine follow-ups, track promises-to-pay, identify bottlenecks, and prioritise high-value accounts. This ensures overdue invoices receive timely attention while maintaining professional, policy-aligned communication with customers.
In practice, AI agents can:
Automate routine replies and resolve billing queries that would otherwise slow collections.
Log and track promises-to-pay, ensuring commitments are followed up automatically.
Escalate accounts according to internal policies when deadlines are missed or risk increases.
Maintain a full, auditable history of communications without altering ERP data or accounting logic.
Final thought
Automating dunning messages in Sage is not about sending more reminders. It is about building a structured, policy-aligned workflow that ensures consistent follow-up, disciplined exception handling, and reliable execution across invoice volume.
Sage provides the AR foundation. Dunning message automation turns that foundation into scalable outcomes — and AI agents can extend execution further when teams need higher coverage and faster response handling.