Confirm what is actually still outstanding before anything is sent. An overdue line needs context, and the state of the account should decide the next step.
Aren’t automated reminders enough?
Not if they go to the wrong person about the wrong balance.
1. Check before contact.
Balance. Check current open items, receipts, credits and unapplied payments.
Context. Look for disputes, a promise to pay, agreed terms or an existing conversation.
Recipient. Confirm the right contact, invoice copy and account details.
Practical check: A stale export is not enough evidence to send a fresh demand.
2. One queue, different next steps.
A fictional queue:
- Paid, not applied
- Investigate and reconcile the receipt.
- Disputed
- Route the issue to its owner and pause routine reminders.
- Promise recorded
- Follow the agreed date and review the outcome.
- Information missing
- Obtain the correct invoice or contact details.
- Genuinely overdue
- Prepare the approved reminder or personal follow-up.
Practical check: A rule-based queue may be enough. AI could help interpret replies.
3. Draft first. Verify the send.
Assistance. Summarize the account and prepare a message from approved facts.
Review. Confirm the current status, recipient and wording immediately before release.
Follow-through. Record the contact and any reply. Keep terms, discounts and write-offs with authorized people.
Practical check: Measure incorrect contacts and dispute resolution, not just emails sent.
Read more: Cash Flow Forecasting With AI: Keep the Assumptions Visible · AI Invoice Processing: A Captured Invoice Isn’t Ready to Pay
The example is fictional. This is general guidance, not accounting or legal advice. Customer messages need to follow company policy and the rules that apply.