Which Overdue Invoices Should AI Email Automatically?

Whether an overdue invoice should get an automated reminder depends less on its size than on what has happened since it was issued. An open dispute or a payment that arrived this morning and hasn’t been matched yet can turn a routine reminder into a complaint.

CollectionsBy George Kurdin9 min read

Whether an overdue invoice should get an automated reminder depends less on its size than on what has happened since it was issued. An open dispute or a payment that arrived this morning and hasn’t been matched yet can turn a routine reminder into a complaint.

Our post on whether AI can email your customers safely covers the general controls for a collections agent. This post sorts each overdue invoice into a send mode, with the checks to run before anything goes out.

What decides how an overdue invoice should be handled?

Six signals cover most cases. Check them for every overdue invoice before a reminder is drafted:

  • An open dispute. Any disputed line on the invoice, or a reply questioning the amount.
  • A promise to pay. A date the customer has committed to, and whether it has passed.
  • A payment plan or legal hold. An agreed schedule of payments, or a legal notice such as a bankruptcy filing.
  • Recent payment activity. Unapplied cash from the customer, or a partial payment that changes the balance.
  • Contact health. Whether the last email to this contact bounced, or the contact has left the company.
  • Portal status. For buyers who only pay through an AP portal, whether the invoice was accepted there.

These signals can change from one day to the next, so they need checking each time a reminder is due.

What does a send-mode matrix look like?

The matrix maps each situation to a send mode, from sending automatically to stopping contact altogether.

Situation Send mode Why
Small invoice with no recent activity Send automatically Low risk and nothing has changed
Unapplied cash from the same customer Hold until cash application finishes The payment may cover this invoice
Partial payment received Draft for approval The balance in the reminder has to be recalculated
Promise to pay, date not yet reached No reminder A reminder now would ignore what the customer said
Promise to pay, date passed Draft for approval The message should reference the missed date
Open dispute on the invoice Hand to a person Disputes need judgment and evidence
Active payment plan Follow the plan’s schedule only Standard reminders would contradict the agreement
Portal-only buyer, invoice rejected in the portal Hand to a person The invoice has to be fixed and resubmitted before chasing payment
Contact bounced Hold, then find a new contact The reminder would go nowhere
Bankruptcy filing or legal hold Stop all contact Further messages may breach legal requirements
Strategic account Draft for approval Someone who knows the account should read it first

On most aging reports, the bulk of invoices fall into the first row. The other ten rows cover the cases where automated reminders tend to cause complaints. The wording of each message is a separate question, covered in our post on chasing invoices without annoying customers.

Which checks should run at the moment of sending?

Many systems check an invoice when the reminder is drafted and send it hours later, by which point a payment or a reply may have arrived. Run these checks again immediately before the email leaves:

  1. Re-read the open balance from the ERP or billing system.
  2. Look for unapplied cash or new credit memos on the customer’s account.
  3. Confirm no new reply has arrived in the thread since the draft was written.
  4. Check that the contact hasn’t bounced since the last message.
  5. For portal buyers, confirm the invoice status in the portal hasn’t changed.

If any check fails, the email should stop and the invoice should go back through the matrix. Our posts on email deliverability for collections and AP contacts whose email bounced cover the contact side in more detail.

When should automated reminders go out?

Timing affects whether a reminder gets read. Most AP teams pay in scheduled runs, often weekly, so a reminder that lands two or three days before the customer’s run is more useful than one that arrives the day after. If you don’t know a customer’s payment day, their payment history usually shows it.

A few other timing rules help:

  • Local time. Send during the customer’s business hours. This matters most for accounts in other time zones.
  • Holidays and year-end freezes. Many companies pause payments over holidays and around year-end, so reminders sent then mostly go unanswered.
  • Spacing. Avoid sending a reminder on the same day as a statement or an invoice copy, since two emails about the same balance read as pressure.

How do you stop customers from getting two reminders?

Duplicate reminders are a frequent complaint after an AI collections agent goes live. They usually come from reminders still switched on in the billing system or ERP, running alongside the new agent.

Before go-live, list every source of overdue reminders, including billing tools such as Stripe and sales reps who chase accounts directly. Switch off the automated reminders and agree with sales on who contacts which accounts. Sending everything from one AR address also makes duplicates easier to spot.

What does this look like across five invoices?

Here is how the matrix sorts five overdue invoices on a Monday morning.

Invoice Signals Send mode
$640, 12 days overdue Verified contact, no activity Send automatically
$18,200, 30 days overdue $18,200 of unapplied cash arrived Friday from that customer Hold for cash application
$4,300, 45 days overdue Customer promised payment by the 20th, which is next week No reminder until after the 20th
$9,750, 21 days overdue Partial payment of $6,000 received Draft for approval with the $3,750 balance
$52,000, 60 days overdue Open dispute about two line items Hand to the account owner

Only one of the five gets an automatic reminder. A system that chased all five by amount and age would have asked a customer to pay an invoice they had probably paid already, and sent a full-balance reminder on an invoice that was mostly settled.

How do you tune the matrix over time?

Review the outcomes every week for the first month, and watch for:

  • replies saying the invoice is already paid, which point to a gap in the unapplied cash check
  • bounces and replies from the wrong person, which point to stale contact data
  • promises to pay that are kept or missed, by customer
  • complaints about frequency or tone

Change one row at a time and note the date, so the effect of each change is clear. After several quiet weeks, a row can move toward automatic sending. Repeated “already paid” replies on a row mean its unapplied cash check needs tightening.

How does Monk handle this?

Julia, Monk’s AI agent for Intelligent Collections, reads each customer reply and picks out any promise to pay, with a confidence score attached. Your team decides, segment by segment, whether drafts wait for approval or send automatically. Every message passes a deterministic check first, and Julia holds anything she isn’t sure of as a draft for your team to review.

Messages go out from your existing Gmail or Outlook address, so customers see the same sender they already know. For buyers who invoice through portals, Monk submits into more than 600 corporate AP portals and tracks each invoice until the buyer confirms it.

Julia’s response rate is 24% higher than standard dunning. Our post on promises to pay covers how those commitments are tracked.

Where should you start?

Take last month’s overdue invoices and sort them through the matrix by hand. Count how many would have qualified for an automatic reminder, and look closely at the ones that wouldn’t. Those show which signals your data can’t support yet, such as promise dates nobody records.

To see how Monk would sort your overdue invoices, book a demo.

Frequently Asked Questions

Should the matrix use invoice value at all?

Yes, but as one input. A high value can move an invoice to draft for approval, though a small invoice with an open dispute still belongs with a person.

What if a customer has several overdue invoices?

Send one message that covers all of them. The matrix should run on each invoice, and the most cautious result decides the mode for the combined message.

How long should a reminder wait after a promise to pay is missed?

A day or two after the promised date is common, to allow for bank processing time. The reminder should mention the date the customer gave.

What should happen when a payment plan is agreed?

Standard reminders should stop for the invoices it covers. Follow-up then runs only on the plan’s dates, and a missed installment goes to a person.

Do reminders need to stop for customers who pay through a portal?

They should stop while the invoice is rejected or pending in the portal. Once the buyer has accepted it, normal reminders can resume if the due date passes.

Who should own the matrix?

The AR lead, with the controller signing off on changes to rows that involve disputes or legal holds.