A weekly overdue invoice review for a small business owner

Prepare one list with a clear review date

Choose a regular slot and gather the invoice list, business mailbox and payment records you normally use. Record when the review takes place. A balance checked on Monday is a Monday snapshot; it does not prove the same invoice remains unpaid on Thursday.

For each invoice, show its number, customer, remaining amount, due date, last contact and current status. Keep future invoices separate from overdue ones. If you cannot explain a balance or date, flag it for checking rather than copying the uncertainty into your next email.

You do not need a new dashboard to start. A short table in your existing records is enough if you can keep it accurate and find the supporting documents. Use one current list so an old spreadsheet does not become a second version of events.

Check what has changed before choosing whom to contact

• Match received payments to the relevant invoices.
• Read replies that arrived since the previous review.
• Identify promised payment dates and requests for information.
• Check whether an invoice was corrected, cancelled or disputed.
• Look for reminders already scheduled or recently sent.

Update confirmed changes first. A payer’s statement that they sent money needs checking against your records; an unresolved query needs a response. Neither situation benefits from treating the invoice as an ordinary unanswered chase.

If your invoice list and accounting records disagree, write down exactly what differs. Keep routine reminders paused for that invoice while you establish the current position. The review should expose uncertainty, rather than hide it inside a total.

Give every invoice one next action

Choose the action that addresses the known blocker. That might be sending a copy to accounts, answering a work query, confirming a reference, checking a promised transfer or sending a factual overdue reminder.

Record who will act and when you will review the result. “Chase customer” is vague. “Ask accounts whether INV-231 is approved, then review their answer on Wednesday” tells you what to do and what information you need.

When time is limited, prioritise decisions you can move forward: missing information you can supply, promises due for review and conversations awaiting your answer. Invoice age and amount provide context, but neither tells you by itself which action will resolve the delay.

A compact weekly worksheet: four fictional invoices

Rowan checks four previously overdue invoices on Monday 9 November 2026. Copy these columns into your own worksheet and link each invoice number to its records. Rowan owns every action in this example; “review” is the next check, not a promised payment date.

Download a blank invoice review worksheet (CSV). Open it in your spreadsheet app and fill it with your own records. The download contains headings and an empty row; the invoices below are fictional examples.

The remaining total is £1,370: £450 + £600 + £320. The payment promise remains in that total until Rowan confirms receipt and allocation. Sending one identical chase to all four would ignore the paid invoice, the missing reference and the known payment estimate.

Finish with updates and a final pre-send check

Save the review date and action list. Update any reminder schedules affected by payment, cancellation or a query. For manual and CSV invoice records, the owner still needs to record changes promptly; a calendar review does not replace those updates.

At the next review, carry forward unresolved actions with their original dates. If a review date passed without an answer, write the new action rather than repeatedly moving the date. Close the paid row, retain its history and check fresh payments before sending from the remaining rows.