As of 13 August 2026, AI can only partly chase your overdue invoices.
This still needs a person who signs their name to it.
Can you do it?
5 minutesto a draft.
30 minutesto something you’d act on.
Cost, all in£0
Skill neededchat-fluent
Who has to check ityou
What the alternative costsThe supplied data gives no price for a human invoice-chasing service.
If this goes wrong: you chase a customer who has already paid or make an inappropriate demand during a dispute, damaging the relationship and complicating recovery.
What to actually do
Hand it to a person
The route this page recommends
A person who owns the outcome does this end to end, worth it when the failure is dear.
Use a tool built for this
Second choiceDo it yourself
The distant thirdA chat interface, chat-fluent skill, and roughly 30 minutes until you can act on the result.
How to actually do it
- Open your accounting system and bank feed, then export or copy a current list of unpaid invoices with invoice references, customer names, amounts outstanding, issue dates, due dates and recorded payments.
- Remove unnecessary personal data, then add the payment terms, previous chasing messages, promised payment dates and any known disputes for each invoice.
- Paste the prepared information into the prompt and ask the chatbot to produce the chasing plan and draft emails without sending anything.
- Compare every invoice reference, amount, payment and date in the response with your accounting system and bank statement, and replace any CHECK item with confirmed information before proceeding.
- Move disputed, unclear or potentially sensitive cases out of the routine list and ask your accountant or solicitor how to handle them.
- Paste each approved email into your business email or finance system, check the recipient and attachment, send it yourself, and record the contact and next follow-up date in your ledger.
Prompt
Act as an accounts receivable assistant for a UK business. Using only the invoice and customer information I provide, create a chasing plan for each overdue invoice. For each invoice, show the customer, invoice reference, original amount, amount outstanding, due date, days overdue, previous contact, promised payment date if any, and recommended next action. Separate invoices into: ready for a routine reminder, needing a personal follow-up, and blocked because of a dispute, unclear payment status or missing information. Draft a short, professional UK-English email for each invoice in the first category. State the invoice reference, amount outstanding, due date and a clear request for payment, but do not invent facts, threaten legal action, add interest or fees, or claim that legal steps have started. If a fact is missing or inconsistent, write CHECK instead of guessing. Do not give legal advice. Suggest a follow-up sequence only where the supplied facts support it, and flag any case that should be reviewed by an accountant or solicitor. Do not send anything. At the end, list every figure and date I must verify against my accounting records and bank statement before sending. Invoice and customer information: [PASTE MINIMISED INVOICE LEDGER, PAYMENT RECORDS, TERMS AND RELEVANT CONTACT HISTORY HERE]
Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.
What it gets wrong
- AI cannot see whether a payment is pending, misallocated or recorded in another system unless you provide current records.
- AI cannot decide whether a customer's explanation is a genuine dispute, a cash-flow problem or an excuse.
- AI cannot take responsibility for a demand that damages a customer relationship or breaches your agreed terms.
- AI cannot replace an accountant or solicitor when a debt is disputed, strategically important or moving towards formal recovery.
- AI cannot send messages safely without your final check of the recipient, amount, payment status and wording.
What caps this at PARTLY: private data access, judgement under ambiguity and legal accountability.
How we scored this
Five axes, each scored nought to two by hand: ten means AI carries the task cleanly, and the thresholds that turn a total into YES, PARTLY or NO are published in the methodology. Each axis name links to its definition.
| Axis | Score (0–2) |
|---|---|
| Output | 2 |
| Inputs | 1 |
| Verification | 1 |
| Liability | 1 |
| Effort delta | 2 |
| Total | 7 / 10 |
The methodology and its thresholds are published in full.
FAQ
- Can AI send overdue invoice reminders for me?
- It can draft and organise reminders, and some finance systems may support automated workflows. You should still approve the recipient, amount, payment status and wording before anything is sent.
- Can ChatGPT chase unpaid invoices?
- Yes, it can turn a supplied invoice list into a chasing plan and draft UK-English emails. It cannot access your live bank or accounting records unless you provide them, and it should not decide how to handle disputed debts.
- Can AI chase an invoice that is in dispute?
- It can summarise the correspondence and prepare questions for the next contact. It cannot reliably judge the merits of the dispute or give recovery advice, so a serious case needs an accountant or solicitor.
- Is it safe to use AI to chase customers for payment?
- It is reasonably safe for routine, verified reminders when you minimise the data and check every message. This is not professional advice; for a serious dispute, threatened legal action or insolvency concern, speak to an accountant or solicitor.
Nearby answers
Assessed by gpt-5.6-luna (gpt-5.6-luna) on 2026-08-13, second-checked by an independent model. Wrong somewhere? Email [email protected] and it gets re-checked.
The newsletter
AI news, new answers and product picks, straight to your inbox.