What to put in overdue invoice follow-up notes

Use one record you can find before contacting the customer

Keep notes with the invoice or in your existing business records. Choose one place that you actually check before sending a message. You do not need a new customer-management system if a short spreadsheet entry or dated note already supports the work.

Use the invoice number as the link between the note, issued document and correspondence. If one customer has several invoices, record which ones a reply covers. “Customer promised payment” is incomplete when the customer has four different outstanding balances.

Keep the current position easy to scan, with dated history below it. That gives you the next action without deleting the earlier sequence of events. Avoid maintaining multiple competing action lists in email, paper and separate spreadsheets.

Record the fields that support your next decision

• Invoice number, customer and current checked balance.
• The date you last checked payments and invoice status.
• Contact date, person and communication route.
• The specific question or information exchanged.
• Any promised date, condition or unresolved query.
• Your next action, its owner and the next review date.

These fields are a practical checklist, not a product feature list. Record them using the tools you already have. Link to the underlying email or document where possible rather than copying an entire conversation into every note.

Keep customer information relevant to invoice follow-up. You need enough context to act accurately, not a personal profile of the payer or unrelated details from their messages.

Distinguish confirmed facts from reports and assumptions

Write “Accounts said payment is planned for 16 November” rather than “Paid on 16 November”. The first records a reported intention. The second claims a completed event and could cause you to stop checking the invoice too early.

Similarly, “Email sent to accounts on Tuesday” does not mean the invoice was approved. Record acknowledgements and approvals separately when you receive them. If you have inferred a possible explanation, label it as a question to investigate.

Keep the tone factual. A note such as “accounts awaiting project code from client contact” leads to a useful action. “Customer is difficult” does not tell you what happened or what information would move the invoice forward.

A usable note row: a fictional £300 invoice query

On 12 November, Morgan checks INV-516 for £300 and finds no matched payment. Accounts says the invoice is awaiting the project manager’s approval because the delivery reference is missing. Morgan’s next action is to confirm the reference with the project contact.

On 13 November, the contact supplies DR-81. Morgan adds a dated history entry and changes the live row to “DR-81 sent to accounts; awaiting their confirmation; review 16 November”. The 12 November entry remains. The status is still a reported processing problem, not a confirmed payment or approval.

You can reuse the columns in a spreadsheet. Keep an underlying correspondence link in the source cell so a concise note does not replace the evidence. If the review is missed, record the new action with its date rather than silently rewriting the original deadline.

Review notes before every new reminder

At your next review, check what happened to the previous action. Close resolved questions, update the current balance and choose the next review date. If you receive a new reply, record it promptly so a planned reminder does not contradict the conversation.

For manual invoice records, updating a note is separate from marking an invoice paid, disputed or cancelled in the reminder record. Keep both current. The note provides context; the invoice status controls whether ordinary follow-up should continue.