Sample · AI chasing

How the AI chasing agent drafts an overdue-invoice follow-up

The AI chasing agent reads the overdue invoice from the same ledger that drives AP and AR, drafts a tone-appropriate follow-up in your house style, and hands it back for a human to review, edit, and approve before it ever goes out. Below is a worked example on a sample Net-30 invoice — read on the left, draft on the right.

Step 1
What the AI reads from the ledger
Client
Northwind Logistics
Invoice #
INV-2026-0419
Amount
$12,480.00 USD
Due date
2026-07-02
Days overdue
32
Last contact
2026-07-21
Contact email
[email protected]
Step 2
What the AI drafts
Subject
Following up on invoice INV-2026-0419 — net 30 past due
Hi Maya, Hope you are well. I am following up on invoice INV-2026-0419 for $12,480.00 USD, due on 2026-07-02. It is now 32 days past the agreed Net-30 terms, and I do not see the payment land on our side yet — happy to be wrong, in which case please ignore this note. A few things that would help us close this out: • If the invoice is in your AP queue, could you confirm the expected payment date so I can mark it on our side? • If there is a dispute or a query blocking payment, just reply with the detail and I will route it to the right person on our team the same day. • If everything is in order and you just need a copy of the invoice or our remittance details, let me know and I will send them over. If it is easier, you can also reach me at this address or reply directly to this email — both come through to the same inbox. Thanks for your help, Paymind AI AR team

Sample draft — generated by the AI chasing agent for illustrative purposes. In production, the agent tailors tone, length, and next-step asks to your segment presets and the customer's prior reply history.

Step 3
Review, edit, approve

The AI never sends on its own. Every drafted message lands in your team's review queue alongside the originating invoice, the full payment history, and any prior chase or dispute context — so the human who picks it up does not have to re-stitch anything from an inbox.

Edit the copy in place, swap the tone, or change the next-step ask. Approve to send, or route the thread to a controller if the invoice hits a configured dollar or aging threshold. Once you sign off, the agent takes it from here — pauses the moment the customer replies, and resumes only after a reason-coded sign-off.

Every status change, edit, and approval is reason-coded in the audit trail, so the same draft is auditable end-to-end the first time and faster to clear the second time a repeat reason shows up on the same account.

Try it on your own book

See it run on your real overdue invoices

The worked example above is illustrative. The real agent reads from your ledger, drafts in your house style, and hands each follow-up to your AR team for a human pass before it goes out.