Every [day] at [time], check [invoice source] for invoices more than [number] days overdue. Reconcile each one against the latest payment and credit records. Skip invoices marked paid, disputed, or extended. For each remaining invoice, draft a polite reminder using its verified invoice number, amount, due date, and payment route. Show me the client, record link, exact message, and any uncertainty. Do not send a reminder, add a late fee, or change terms without my approval. Recheck payment status before any approved send.
Invoice follow-up with a reviewed reminder
Check overdue invoices against payment records, prepare a precise reminder, and require approval before contacting a client.
Copy-ready brief
Example output
Example output for illustration only: Invoice INV-104, Acme Inc, due [date], [amount] outstanding in the invoice record. Payment check: no matching payment in the current record as of [time]. Draft: “Hello, our record shows INV-104 remains open. Could you confirm whether payment is in progress? I can resend the invoice if useful.” Status: Held for owner review. No reminder sent. Invoice INV-099: removed from queue after a payment appeared in the latest check.
Trigger and cadence
- A scheduled check finds an invoice past the chosen due-date threshold.
- Check each Monday morning, or on the day after a chosen overdue threshold.
Inputs
- Invoice records, due dates, amounts, and payment status.
- Client contacts, exceptions, and any agreed extension.
- Reminder tone and the days after due date that warrant contact.
Steps
- Reconcile invoice status with recent payments and credits.
- Remove disputed, extended, and already paid invoices from the reminder queue.
- Draft a message with invoice number, amount, due date, and payment route.
- Show the supporting record and exact recipient for review.
- Record the decision and check for payment before any approved send.
Approval boundary
Sending a reminder or changing payment terms requires the owner's approval.
Stop conditions
- Payment status is stale or conflicts with another record.
- The client has disputed the invoice or has an agreed extension.
- Contact details or amount cannot be verified.
Expected output
An overdue list with reviewed reminder drafts and clearly marked exceptions.
Receipt fields
- Invoice records and payment status checked.
- Exceptions, drafts, approval decisions, and send times.
Recovery when it fails
- Recheck payment and client messages before resuming a held reminder.
- Keep a disputed invoice out of the queue until the owner resolves it.
On this page
Check the account before writing the reminder
An invoice follow-up starts with the current payment record. A due date is one input; the account may also show a payment in transit, a credit, a dispute, or an agreed extension. OperatorNest can prepare the overdue list and draft reminders, then hold each client message for your approval. The example here is illustrative and does not describe a completed collection run.
The instruction needs a source of truth for invoice status. State which system holds the invoice, where payments appear, and how recent that payment view is. If the invoice source updates slowly, build in a recheck before any send. Otherwise a correct Monday morning draft could become wrong by Monday afternoon.
Sort exceptions before contact
The queue should separate invoices that are overdue in the ledger from invoices that are ready for a reminder. A client may have written about an error. A team member may have granted an extension. An account may have a partial payment that changes the balance. Each case requires a different decision.
Say Sam asks for reminders on invoices more than seven days overdue. Acme’s invoice appears open, but a message from the client says the amount is disputed. The workflow should flag the dispute and hold the reminder. It should show Sam the invoice record and the client’s message together, so Sam can decide whether to correct the invoice or respond to the dispute.
For an ordinary overdue item, the draft should name the invoice number, verified amount, due date, and a way to view or pay the invoice. A polite request for status often works better than an accusation. The workflow should not add a late fee, threaten action, or claim a payment failed unless the records support that wording and you approve it.
Make one decision per recipient
Put each proposed reminder beside the client name, invoice record, and most recent payment check. That gives you enough context to approve, edit, or hold it. If one client has several overdue invoices, choose whether a single consolidated note is appropriate; avoid sending three separate messages by accident.
The invoice follow-up use case describes the broader accounts receivable task. This workflow gives the exact checks that make a reminder safe to send. A standing schedule can prepare drafts each week, but the final recipient and wording should remain visible at approval.
After approval, recheck for a payment or fresh client reply. If one appeared, stop the send and show you what changed. The receipt should show the original flag, the final status check, your decision, and any actual send. A canceled draft is a successful outcome when it prevents a paid client from getting chased.
Keep the next pass accurate
Update the exception list after each review. If a client has an extension through Friday, the next Monday check should use that agreement instead of the original due date. If you corrected an invoice number or contact, save the corrected record at its source. The next reminder should be based on that record, not on an old draft.
Run it on a schedule
Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.
Related tools
- AI agent approval policy
Set clear approval rules for an AI agent. Choose systems and risk limits, then copy a policy that says what waits and what can run.
- AI agent receipt template
Make a task receipt with the request, actions, sources, approvals, uncertain steps, result, model usage, and cost. Copy or download it.
- Recurring task planner
Map repeat work to a week or month, estimate monthly hours, decide what to delegate, and download calendar events with recurrence rules.
Common questions
What if a payment arrives after the draft is written?
Recheck the payment record before an approved send. If the invoice is paid, cancel the reminder and record why.
Can the draft mention a late fee?
Only if the owner supplies the governing terms and approves the exact message. The workflow should never invent a fee or change terms on its own.
How should a disputed invoice appear?
Mark it as an exception with the dispute note and leave it out of the reminder queue until the owner decides the next step.
Keep reading
- An AI invoice follow-up assistant that chases payment for youIt checks overdue invoices, drafts a reminder that fits how late they are, and waits for your OK before anything sends.
- Approvals before anything that mattersIt asks before it sends, pays, books, deletes or posts. You approve, edit or hold from any channel.
- A receipt for everything your operator doesEvery task keeps a receipt: what was asked, what ran, which model did it, what it cost, and every approval.
- An AI operator for small business owners doing every job themselvesInvoice reminders, customer email, vendor and customer follow-ups and competitor checks, with every send and payment approved by you.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.