Skip to content
OperatorNest

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

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.

Illustrative example

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

Trigger
A scheduled check finds an invoice past the chosen due-date threshold.
Cadence
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

Reconcile before you remind

An invoice follow-up starts with the latest payment and credit records, including disputes and agreed extensions. Give OperatorNest the invoice source, the payment source and how often each updates. A reminder based on Monday morning’s ledger can be wrong by the afternoon.

For example, Sam asks for reminders on invoices more than seven days overdue. Acme’s invoice is open, but a client message disputes the amount. Put the invoice and message together for Sam to resolve; leave that reminder out of the send queue. The example output illustrates these checks.

Show the account behind each draft

For an ordinary overdue item, show the client, invoice number, verified balance, due date and payment route beside the exact message. Include the time of the latest payment check. If a client has several invoices, prepare one consolidated note for review rather than three accidental reminders.

Keep late fees and changes to terms under the owner’s control. The draft uses the supplied invoice terms; it cannot invent a penalty or claim a failed payment the records do not show.

The invoice follow-up use case covers the standing job. This workflow prepares the queue, with every recipient and message waiting for approval.

Recheck at the send

After approval, check for a payment or fresh client reply before sending. If either changes the balance or dispute, stop and show what changed. Canceling a stale draft is the right result.

The receipt keeps the original flag, final status check, approval and any send. Save corrections at the invoice source and carry agreed extensions into the next pass, so next Monday’s reminder uses the current record.

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.

  • 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.

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.