# How to Chase Overdue Invoices With AI

> Most overdue invoices are late for a reason a reminder can't fix, and the reminders that sour good customers go to people who already paid, disputed or gave a date. Hand an AI agent the reading first, and remind only where nothing explains the balance.

By Vlad Shvets, Partner @ Qvery · Published 2026-11-03 · 11 min read
Canonical: https://qvery.ai/blog/ai-collections/

On a receivables desk, most of the time an overdue invoice takes goes into reading, not writing. Before anyone sends a reminder, someone checks the bank for a payment, opens the thread to see whether the customer answered, and digs out the PO number the customer's payables team asked for.

The reminder that costs goodwill is the one sent without that reading: to a customer who paid two days ago, who disputed a line on the invoice, or who already said when the money would land.

AI changes the order of the work, because an agent can read every reply and every incoming payment, for every overdue invoice, each morning before anything goes out.

So hand AI **the reading first** and the reminders second. Here's why a reminder fixes only some late invoices, the rules that keep an agent quiet, what it does with each reply, and how Qvery's agent takes the whole chase off your desk on autopilot.

One boundary: this is a company chasing its own invoices from other businesses. Collecting debts from consumers is a different job under different rules.

## Chasing an Overdue Invoice Is Mostly Reading

In Atradius's 2026 survey of 240 US companies that sell on credit, **about seven in ten** faced late payments, and late payments touched an average **22% of their B2B receivables**.

Here is a month on assumptions to replace with your own: 800 invoices on 30-day terms, about a fifth of them late, so 160 overdue invoices.

Each one takes about **10 minutes a touch**: 4 to check the bank and the ledger for a payment, 3 to read the thread, 3 to write and send.

Most business customers who pay late pay within a month of the due date, the same survey found, so call it three touches. That's **80 hours a month**, two full working weeks of somebody's time.

**Seven of those ten minutes** are checking and reading, so a better-written reminder saves only the cheapest three.

Hand the checking and reading to an agent and a person's minutes go only to the invoices that need a decision: if one in three needs ten minutes of someone's time, the month drops from 80 hours to **about 9**.

> If you start with AI writing better reminders, you start with the cheapest three minutes of the job. The hours sit in checking whether the money came in and what the customer last said, and that is also where the annoying reminders come from. Give that reading to an agent first and keep the reminders plain and firm. Tone was rarely the problem.
>
> Vlad Shvets, Partner @ Qvery

## A Reminder Fixes Only One Kind of Late Invoice

Ask why an invoice is late and the answer is rarely that the customer forgot. The same suppliers named the customer's **cash flow** first, then three reasons about the payment itself, and they could name more than one:

- **55%** named customer cash flow
- **28%** named banking delays
- **20%** named internal approval delays
- **17%** named e-invoicing or payment platform issues

Source: Atradius: Payment Practices Barometer, United States (2026)

**Three of the four** are about how the payment moves, not whether the money exists.

Add the two every receivables desk knows, the payment that arrives without saying which invoice it pays and the invoice the customer disputes, and an overdue list sorts into five reasons, each needing something different.

**Why an overdue invoice is late, and what gets it paid**

| Why it's late | What gets it paid | The reminder that sours the customer |
|---|---|---|
| Not paid, no reason given | A plain reminder with the invoice attached | None: this is what reminders are for |
| Short of cash | A conversation that ends in a date | A third reminder that ignores the date they gave |
| Stuck in their approvals or payment portal | The missing PO number, a form, the invoice sent to the right address | A nudge to the person who already approved it |
| Paid, but not landed or not matched | Matching the payment on your side | "Your invoice is overdue" after the money left their bank |
| Disputed | Someone who can fix the price, the quantity or the delivery | Any reminder at all |

For the first row, **firm is fine**: a reminder to a customer who simply hasn't paid is routine business, and a matter-of-fact tone keeps it that way, where an apologetic one invites a debate.

## Write Down When the Agent Must Stay Quiet

The reminder built into accounting software reads two things: the due date and whether the invoice is paid.

QuickBooks Online, for example, sends up to three reminders from one template, a set number of days around the due date, to any emailed invoice it shows as unpaid. It can't see the customer's reply, or a payment nobody has matched yet.

An agent reads what the ledger can't: every morning it takes the open invoices from your accounting system, the bank feed, the remittance emails that say which invoices a payment covers, and the collections inbox, and decides for each overdue invoice **whether anything goes out today**.

![An agent’s five morning steps on an overdue list: match payments, read replies, apply the stop rules, remind only where nothing explains the balance, pass disputes to the customer’s owner.](https://qvery.ai/blog/ai-collections/illustration-morning-read.webp)

*Only the invoices nothing else explains reach the fourth step.*

These are the stop rules, each one a line your receivables lead could check:

- No reminder on an invoice whose latest customer reply hasn't been answered.
- No reminder while an incoming payment could be this invoice and isn't matched.
- No reminder on a disputed invoice until whoever owns the dispute closes it.
- No reminder before a date the customer promised.
- No reminder to an account a person has put on hold.

What passes the rules gets a short ladder: a note a few days before the due date asking whether the invoice reached their payables team, a reminder on the due date, another a week later, and then a person picks up the phone.

The note before the due date **does the most work**: it finds a missing PO or a wrong address while there's still time to fix it.

## Turn Every Reply Into a Date, a Missing Document or a Dispute

**A promise becomes a date.** "We'll pay on the 15th" is recorded against the invoice, the reminders stop, and the agent checks the bank on the 16th.

If the money is there, nothing goes out. If it isn't, the chase resumes, and the first message names the date they gave: a promise that slipped is **a different conversation** from a first reminder.

**A stuck approval** becomes the missing piece. If their [payables team](https://qvery.ai/blog/ai-accounts-payable-automation/) needs a PO number, a tax form or the invoice sent to a different address, the agent sends it from your records.

Where the customer pays only through a supplier portal, it gives your team the list of uploads to make, unless the portal's own terms allow automated use.

**A dispute leaves collections.** The agent passes it to whoever can settle it, in sales or operations, with the invoice, the order and the delivery record attached. Only that invoice stops; the rest of the account carries on.

**A question gets its answer** from the invoice, the contract or the statement.

**Tips**

> But also, if you are less apologetic and more matter-of-fact about this totally routine business practice, I bet you’ll hear a lot less about their feelings.
> ([r/Accounting · May 2024](https://www.reddit.com/r/Accounting/comments/1cwij0v/how_do_you_remind_your_customers_for_unpaid/l4w13l5/))

> Contact them once and make them commit to a pay date. If they can’t commit or flake on their date, you need to cut them off until they pay.
> ([r/Accounting · May 2024](https://www.reddit.com/r/Accounting/comments/1cwij0v/how_do_you_remind_your_customers_for_unpaid/l4w5pup/))

> It is the ones who promise the check is in or the wire will show in the morning and they do not that get people blackballed.
> ([r/smallbusiness · Oct 2026](https://www.reddit.com/r/smallbusiness/comments/1x9dqz8/had_the_money_and_still_paid_our_vendor_late/phlioxc/))

## Credit Holds, Payment Plans and Write-Offs Stay With a Person

Settling a dispute and the call once the reminders run out belong with them: each changes the relationship with a customer, so **none goes to the agent**. Nor do the few accounts the owner wants to handle personally; there the agent drafts, and the owner sends.

The agent gives each of those people **a better starting point**: the account's open invoices, every promise and whether it was kept, and the whole thread in one place.

> 📌 **For US readers** Federal debt-collection law covers debts consumers owe, so chasing another business for your own invoice, in your own name, sits outside it. Your contracts and local law still apply.

## Qvery's Agent Reads Your Inbox and Bank Feed Before It Chases

Our collections agent is built for one company and the way its team chases. It connects to your accounting system, your bank feed and the collections inbox, and every morning it reads all three before it does anything else.

Then it runs the chase on its own, on autopilot: it matches the payments that came in, sorts each overdue invoice by why it's late, and sends the reminders your stop rules allow.

It records every promised date and checks it, and sends the paperwork customers' payables teams ask for. Disputes and broken promises go to **whoever owns that customer**, with the thread attached.

The work starts with how your team chases today, written down as your stop rules. Inside **two weeks** the agent's first working version is reading your real overdue list, and whoever owns receivables is trained to run it beside their own work.

From then on each week has two counts: **hours saved** on the chase, and **errors avoided**, meaning every reminder it held back from a customer who had paid, disputed or given a date.

Hand Your Overdue List to an Agent That Reads First: https://calendly.com/qvery-vlad/30min

## Let the Agent Read for Two Weeks Before It Sends Anything

For two weeks the agent reads your inbox and bank feed every morning and marks each overdue invoice with its reason, the reminder it would have sent, and the reminders it would have held. Your team chases exactly as before.

At the end you have two numbers from your own month: the hours of reading the agent did, which your team does by hand today, and **how many reminders** would have reached a customer who had already paid, disputed or promised.

If that second number is small, the reminders in your accounting system are enough. If it isn't, the reading is the job, and it's the part to hand over first.

Pick the Next Job on Your Finance Desk to Hand Over: https://calendly.com/qvery-vlad/30min

## Frequently asked questions



### Can AI write our collection emails?

Yes, and it's the easy part. An agent writes a clear reminder from the invoice, the amount, the days overdue and the customer's last reply, in your company's voice. The part worth automating first is deciding whether a reminder should go at all, which takes reading the replies and the bank feed.

### Why do business customers pay late?

In Atradius's 2026 survey of US suppliers, the reason named most was the customer's cash flow (55%), then banking delays (28%), slow internal approvals (20%) and e-invoicing or payment platform problems (17%). On most receivables desks, disputes and payments that arrive without saying what they pay add to that list.

### How do we stop AI chasing invoices that are already paid?

Make matching the first thing the agent does each morning, before any reminder. It reads the bank feed and remittance emails, matches what it can, and holds any invoice a payment of the right amount might cover until someone confirms the match. A reminder goes only where nothing explains the balance.

### Can AI tell a payment promise from a dispute?

Most replies say which they are. A reply with a date and no objection is a promise; one that questions the price, the quantity or the delivery is a dispute. A reply that mixes the two goes to your receivables lead with the thread, and the chase on that invoice waits.

### What happens when a customer pays only part of an invoice?

The agent matches what arrived, records the short amount and reads the remittance or the thread for the reason, often a deduction for damaged goods or a price difference. A short payment with a reason is a dispute and goes to its owner. One with no reason gets a reminder for the balance.

### When should a collections email turn into a phone call?

When the email ladder ends, or sooner when the amount or the account matters enough. A common shape is a note before the due date, a reminder on it, another a week later, then a call. A broken payment promise goes straight to a person.

### Will customers know the reminders are automated?

Only if they read like it. The agent writes from the invoice and the thread, so a reminder can name the PO number, a partial payment or the date the customer gave, which most hand-written reminders don't. It sends from the collections address customers already know.

### What does a collections agent need access to?

Read access to open invoices and payments in your accounting system, your bank feed or remittance emails, and one shared collections inbox it can read and send from. It needs no access to release payments, change customer records or issue credit notes. Those stay with people.

### Does debt-collection law apply when we chase business customers?

The US Fair Debt Collection Practices Act covers debts consumers owe for personal, family or household purposes, and it doesn't count a company's own staff collecting in its name as debt collectors. Chasing another business for your own invoice generally sits outside it. Contracts, late-fee terms and local law still apply; check them with counsel.

### Should we buy AR software or build a custom agent?

Start with what you have. The reminders inside your accounting system send on due dates and unpaid status, which suits a short list. Receivables software adds schedules, a payment portal and matching. A custom agent pays when the work is reading your own inbox and bank feed and following rules specific to your customers.

### Which numbers show the agent is working?

The hours your team spends chasing each week, the reminders held back from customers who had paid, disputed or promised, the share of promised dates that were kept, and the balance more than 60 days overdue. Count reminders sent last; more of them is not progress.

### How do we handle a customer who keeps promising and not paying?

Treat the second broken promise as a decision for a person, not another reminder. The agent lays out the history: every date given, every date missed and what's still open. Whoever owns the account then decides whether to call, agree a payment plan or hold new orders.

### How soon can a collections agent be running?

Qvery has a first working version reading your overdue list within two weeks. Most of that time goes into writing your stop rules and connecting the accounting system, bank feed and inbox. The first two weeks can run silent, the agent reading and marking, so customers see no change until you switch sending on.