How to chase overdue customer invoices with an AI agent

Check before you chase. The agent first confirms each overdue invoice is really owed: no open dispute, no unapplied payment, no credit note waiting. Then it sends the early reminders on approved templates at depth 3 and records any promise to pay. Final notices, late payment interest, putting an account on stop and referral to collections stay with credit control.

What is the process, and who owns it?

Chasing overdue invoices, or dunning, is the sequence of contacts that follows a missed due date: a reminder, a firmer reminder, a final notice, then escalation. Each step costs goodwill as well as time. A reminder sent for an invoice the customer has paid, or is disputing, does more damage than no reminder at all.

The credit control lead owns the process, the stage schedule and the templates. Account managers own relationships with key customers and should approve any contact with them. The financial controller owns escalation beyond the final notice. Whether an agent should be doing this at all is weighed in can an AI agent chase overdue customer invoices. The wider finance position is in AI agents for finance: books you can audit.

How does the agent chase, step by step?

1. Agent, depth 1: reads the aged receivables. Every invoice past due, by customer, with days overdue. Evidence: the ageing snapshot used.
2. Agent, depth 1: runs the pre-chase checks. Open dispute or query on the invoice. Unapplied cash from that customer. Credit note pending. Payment plan agreed. Customer flagged as key account or in a special arrangement. Evidence: each check and its result, per invoice.
3. Agent, depth 1: confirms the invoice was delivered. Sent to the right billing contact, with the right purchase order reference. Many "overdue" invoices were never received or were rejected by the customer's system. Evidence: the delivery record.
4. Agent, depth 3: sends stage 1 and stage 2 reminders on approved templates to the billing contact: invoice, amount, due date, how to pay, who to contact with a query. Evidence: message, template and stage.
5. Agent, depth 3: records replies. A promise to pay with a date, a query, a dispute, a request for a copy. Promises pause the schedule until the date; queries and disputes go to the owner. Evidence: the reply and the action taken.
6. Agent, depth 2: drafts the final notice and any escalation, with the full contact history.
7. Person, credit control lead: decides escalation. Final notice, late payment interest or charges, account on stop, referral to a collection agency or solicitor. Evidence: the decision and its reason.

Why do early reminders sit at depth 3 and final notices with a person?

An early reminder states a fact and asks a question. If it was wrong, an apology fixes it. A final notice carries a consequence: interest, a stopped account, a third party. Those affect the customer relationship and sometimes the customer's own business, and they are hard to walk back once a supplier relationship sours.

Key accounts are the exception at the early stages too. A reminder from an automated sender to a customer your sales director spent a year winning can feel like an insult. For those accounts the agent drafts and the account manager sends or approves. The same split between routine reminders and personal judgement applies inside the business when chasing missing expense receipts from colleagues.

What stays with a person?

Every consequence, every dispute and every key account contact. Disputes need someone who can look at what was delivered against what was invoiced and decide whether a credit is due. The billing side of that is upstream: invoices raised correctly from the contract in the first place generate fewer disputes, as described in raising customer invoices from signed contracts. Whether the agent may raise invoices at all is a separate grant, covered in can an AI agent issue customer invoices.

Which controls matter, and what evidence do they leave?

Pre-chase checks before every reminder. No reminder without a clean check. Evidence: the check results filed with each reminder verdict.

Stage schedule enforced. The agent cannot skip a stage or shorten a gap. Evidence: stage and timing on each reminder.

Promises recorded and honoured. A promise pauses chasing until its date. Evidence: the promise, the pause and what happened on the date.

Key account flag. Evidence: held verdicts on any key account contact.

Escalation by a person. Evidence: the credit control lead named on every final notice and escalation.

What should you measure?

• Overdue balance by age band, and how it moves.
• Reminders sent for invoices that were disputed or paid. The number that tells you whether the checks work. Should be near zero.
• Payments received after each stage.
• Promises to pay kept.
• Disputes surfaced by reminders, routed to their owner and resolved.

Where does it usually go wrong?

Unapplied cash is ignored. The customer paid, the payment sits unmatched, and the agent chases. Check unapplied cash first; how that queue is cleared is the subject of a separate playbook.

The wrong contact gets the reminder. Chasing the person who signed the contract instead of accounts payable irritates both. Use the billing contact on file.

Promises are not tracked. The customer says "next Friday" and the agent sends a reminder on Wednesday. The promise must pause the schedule.

Reminders arrive on the customer's payment run day. Many businesses pay on a fixed cycle. Learn each customer's pattern and time reminders before it, not after.

Tone escalates too fast. Stage 2 reads like a final demand. Keep early stages factual and helpful; firmness belongs to the final notice a person sends.