Chasing overdue invoices is repetitive, but each message still needs accurate facts and an appropriate tone.

The workbook includes a sequence of accounts-receivable prompts for:

  • a friendly first reminder;
  • a firmer second reminder;
  • a final notice before escalation;
  • a payment-plan offer;
  • an internal receivables status summary;
  • a response to an invoice dispute;
  • a payment acknowledgment;
  • an automatic-payment request.

These can form a controlled follow-up workflow.

Stage 1: verify the invoice facts

Before drafting anything, confirm:

  • client or business;
  • invoice number;
  • amount due;
  • original due date;
  • payment status;
  • reminders already sent;
  • any agreed payment terms;
  • any permitted late fee, service pause, or escalation process.

AI should not be the source of those facts.

If the practice has not established a term or right, do not let the model invent one because it sounds standard.

Stage 2: first reminder — assume an ordinary oversight

The first reminder can usually be brief and neutral.

Supply:

  • invoice number;
  • amount;
  • due date;
  • payment instructions or approved link;
  • the response you need.

Ask for a friendly tone.

The purpose is clarity, not pressure.

A simple message that makes the invoice easy to identify is often more useful than a long explanation.

Stage 3: second reminder — make the status explicit

If the first reminder is unanswered, the next message can be firmer.

Provide the verified history:

  • when the first reminder was sent;
  • how many days overdue the invoice is;
  • the exact amount outstanding;
  • the next action required.

If the practice’s approved terms allow a late fee or service pause, include the actual rule.

If they do not, do not ask AI to create one.

Stage 4: final notice — separate drafting from escalation authority

The workbook contains a final-notice prompt, but formal escalation is the point where the practice needs to be especially careful.

The prompt can help organize a factual draft around:

  • previous reminders;
  • balance outstanding;
  • payment deadline;
  • the actual next step authorized by the practice.

The bookkeeper or practice owner must verify whether that next step is permitted and appropriate.

Collections, legal action, service suspension, contractual remedies, and jurisdiction-specific requirements are not decisions to outsource to a text generator.

Stage 5: payment-plan communication

A payment plan should begin with terms the practice has actually approved.

AI can help express:

  • total balance;
  • number of instalments;
  • amount per instalment;
  • starting date;
  • frequency;
  • what written confirmation is required.

It should not decide whether a payment plan should be offered or create commercial terms from scratch.

Keep the approved arrangement in the normal client and receivables record.

Stage 6: handle disputes as a separate branch

If the client disputes the invoice, stop treating the issue as a normal reminder sequence.

Create a factual summary of:

  • invoice;
  • services billed;
  • the client’s stated concern;
  • supporting records;
  • what is agreed and what is disputed;
  • the decision or review still required.

AI can help draft a calm response after the practice has decided the factual and commercial position.

Do not ask it to adjudicate the dispute.

Stage 7: update the internal receivables view

The workbook includes an internal accounts-receivable status summary.

A useful internal view can group invoices by age or status and record:

  • client;
  • invoice;
  • amount;
  • due date;
  • days overdue;
  • last contact;
  • next action;
  • owner;
  • next review date.

This can make the next step visible without relying on memory.

Use approved systems for the authoritative data and minimize what is copied into an AI tool.

Stage 8: close the loop when payment arrives

Once paid, a short acknowledgment can confirm:

  • invoice number;
  • amount;
  • payment received;
  • any relevant next step.

Then update the receivables record.

Do not leave the AI conversation as the only evidence that the balance was resolved.

A simple staged workflow

The sequence can be:

  1. verify invoice and terms;
  2. friendly first reminder;
  3. firmer second reminder;
  4. final notice only when the next step is authorized;
  5. payment-plan branch if approved;
  6. dispute branch if the invoice is challenged;
  7. record the status and next action;
  8. acknowledge payment and close the item.

At each stage, the prompt changes because the facts and purpose change.

Protect confidential payment information

Invoice communication rarely needs bank account numbers, payment-card data, or other payment credentials inside an AI prompt.

Use an approved payment link or standard payment instruction where appropriate.

For broader client-data checks, see Client Data and AI: A Privacy-Minimization Checklist for Bookkeepers.

Review tone as deliberately as the facts

A message can be factually correct and still create unnecessary friction.

Before sending, check:

  • does the tone match the stage?
  • is the amount correct?
  • is the due date correct?
  • are previous contacts described accurately?
  • is the requested action clear?
  • does the message threaten a step the practice has not authorized?
  • is any legal or contractual language being used without the correct review?

AI is useful here because the structure repeats.

Human review matters because the relationship, contract, policy, and jurisdiction do not disappear just because the words were drafted quickly.

Final rule

Use AI to make the follow-up sequence consistent.

Use the practice’s real records and approved terms to decide what the sequence is allowed to say.