Yes, for routine reminders. An AI agent can chase overdue customer invoices at depth 3 when the debt is undisputed, the ledger confirms it is unpaid and the reminder follows a sequence you approved. Disputes, payment plans, final demands, account stops and anything involving a customer in difficulty go to a named credit controller.
What conditions decide it?
Four things decide whether a reminder can go out without a person:
- The ledger says the invoice is unpaid. The agent checks the sales ledger and the bank feed for an unallocated receipt before every reminder. A reminder for an invoice the customer paid yesterday is the most common way automated chasing damages a relationship.
- Nobody has raised a dispute. A query logged against the invoice, an open credit note request or a complaint stops the sequence.
- The contact is the one on file. The agent writes only to the billing contact on the customer record, not to an address taken from a forwarded email.
- The step is in the approved sequence. A first reminder at a set number of days past due, a second a little later, and a statement. The wording is a template a person approved; the agent fills in the details.
When all four hold, the reminder goes out. When any fails, the agent holds and tells the credit controller why. Our step-by-step guide to chasing overdue invoices with an AI agent shows how to set the sequence up.
What does the agent do, and where does a person sign off?
| Activity | Agent | Named approver |
|---|---|---|
| Daily overdue list | Builds it from the ledger at depth 1 | None |
| First and second reminders | Sends from approved templates at depth 3 | None, unless a condition fails |
| Replies from customers | Reads, summarises, logs promises to pay | Credit controller for anything beyond a payment date |
| Disputes | Logs and pauses chasing | Credit controller resolves |
| Payment plans | Drafts terms within policy at depth 2 | Credit controller agrees |
| Final demand, stop or referral to collections | Prepares the file | Credit manager decides |
The line falls where a step changes the customer relationship or creates a commitment. A reminder restates what is already owed. A payment plan changes the terms. A final demand threatens consequences. Those are a person's calls.
Why do disputes matter so much?
Most overdue invoices are not unpaid because the customer refuses. They are unpaid because something went wrong earlier: the wrong purchase order number, a missing delivery note, a price that differs from the quote. Chasing hard on an invoice with a genuine problem wastes time and irritates the customer.
So the agent's most valuable work is often reading the reply, not sending the reminder. When a customer answers "we never received the goods", the agent logs a dispute, stops the sequence and routes the case with the delivery record attached. Many disputes trace back to the invoice itself, which is why the rules for issuing customer invoices are worth getting right first.
An illustrative example
Take a wholesale distributor with about 600 trade accounts. On Monday the agent finds 45 invoices more than 30 days overdue.
For 38, all four conditions hold and the agent sends the reminder due at that stage. For four, it finds receipts in the bank feed that match the amount but have not been allocated, so it sends nothing and passes them to cash allocation. Two have open queries about short deliveries; it pauses those and alerts the credit controller. One customer's last email mentioned that the business was entering administration. The agent holds that account entirely and flags it to the credit manager, because chasing an insolvent customer is a legal matter, not a reminder.
What controls make it safe?
- Pre-send check every time. Ledger, bank feed and dispute log are read immediately before each reminder, not once a week.
- Templates owned by a person. The agent fills fields; it does not write new wording for demands.
- Frequency caps. No customer receives more than the set number of contacts in a period, however many invoices are overdue.
- Vulnerability and insolvency stops. Any sign of financial difficulty or a formal process moves the account to a person.
- A record per contact. Each reminder, reply and verdict is filed, so you can show what was sent and why.
The same pattern, applied internally, works for chasing missing expense receipts. The wider finance controls are in AI agents for finance: books you can audit.
Where Pryme fits
In Pryme, "send reminder" and "agree payment plan" are separate capabilities that need separate depths. The agent earns depth 3, enough to send reminders, by passing Attest on your own past overdue cases, including ones where the customer had already paid or had raised a dispute. A run that clears only depth 2 drops it back to drafting the same day.
Questions people ask
Can the agent phone customers as well as email them?
It can, if your policy allows automated calls and the customer is told they are speaking to an AI system. Most firms start with email, where every word sent is on record.
Should the agent charge late payment interest?
It can calculate interest your terms allow and add it to the statement as a draft. Whether to charge it is a commercial decision, so a person approves.
What happens when a customer promises to pay on a date?
The agent records the promise and pauses chasing until that date. If the payment does not arrive, it resumes the sequence and notes the broken promise for the controller.