Chasing overdue invoices is a repeating job that slips because nobody enjoys it. The improved process checks the overdue list every day, looks at each customer's history, drafts the right reminder in your tone and holds back anything disputed or sensitive.
The owner or office manager approves every reminder before it is sent. The system never sends on its own, and it never changes anything in the accounts.
The job today
Once a week, if there's time, the owner or office manager runs an aged debtors report, scrolls down the list and decides who to chase. Some customers get a polite email, some get a call, and some get forgotten. Promises to pay are remembered, or not. Reminders are written from scratch each time, so the tone varies with the mood of the week.
Where it breaks
- Chasing happens in bursts, so invoices drift from 30 days to 60 before anyone notices.
- Nobody can see at a glance who was chased, when, and what they said.
- Disputed invoices get the same reminder as forgotten ones, which annoys good customers.
- It depends on one person, and stops when they are busy or away.
The improved process, step by step
- Read the overdue listEach morning the system reads overdue invoices from your accounting software, read-only.
- Check the customer historyIt looks at previous reminders, notes of promises or disputes, and any "do not chase" flag you have set.
- Draft the right reminder AI preparesAn assistant drafts a reminder at the right stage (friendly, firm, final) in your tone, with the invoice details filled in.
- Hold back sensitive accountsDisputed invoices, key customers and anything over a limit you set go to a separate list for a phone call instead.
- A person approves each send A person approvesThe owner or office manager reads the drafts, edits any that need it and approves them. Unapproved drafts are never sent.
- Log it and set the next dateThe sent reminder is logged against the customer and the next check date is set, so nothing quietly drops.
Where a person must approve
Every reminder is approved by a person before it is sent.
Any account that is disputed, sensitive or over your agreed limit is passed to a person to handle directly, not drafted at all.
The data boundary
- The system has read-only access to invoices and customer contact details. It cannot raise credit notes, change balances or take payments.
- Only the details needed for the reminder are used: customer name, contact, invoice number, amount and dates.
- Drafts and sending go through your own email account, so replies come back to you.
- Every draft, edit and send is logged.
Checklist before you start
- We can export or read overdue invoices from our accounting software.
- We have agreed reminder stages and roughly what each one should say.
- We know which customers should never get an automatic draft.
- We have a limit above which a person always calls instead.
- One person owns approving reminders, with a named cover.
- We know where promises to pay and disputes are recorded.
This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.