PRACTICAL INVOICE GUIDES
Invoice follow-up handover: what to leave your colleague
When the person following up invoices is away, a list of overdue balances is only half a handover. The next person also needs to know what has already been discussed and which actions are waiting. Use this checklist for a short absence, a project handover or a change of responsibility.
Give each invoice one clear next owner
Choose who will review each outstanding invoice during the handover period. A project manager may understand the client conversation while someone else checks payment records. Make that split explicit, with one person responsible for deciding whether another reminder should go out.
An email copied to several colleagues does not assign responsibility. Write down who will check the invoice, when they will check it and who can resolve a question. Keep the handover within the people authorised to see those business records. Do not share account passwords to make the arrangement easier.
Separate the balance from the conversation
Record the invoice reference, currency, agreed due date, invoice amount, cumulative payments recorded and remaining balance. Add the date those figures were last checked. A figure copied from last week may no longer describe what is owed.
Keep the client’s statement alongside the financial record rather than treating the two as interchangeable. “Client says payment was sent on Monday” is different from “payment checked and allocated on Tuesday”. The first needs investigation; the second can support an updated balance.
Check how cumulative partial payments change an invoice balance
Leave the last meaningful conversation, not the whole inbox
Summarise the latest relevant reply and link to the original conversation in your approved business records. Include a promised payment date, a missing purchase-order reference or an invoice query that someone needs to answer. The colleague should be able to distinguish an unanswered reminder from a reply awaiting your own action.
Use neutral descriptions. “Asked for the approved invoice copy; copy not yet sent” is actionable. “Difficult client” gives the next person no reliable instruction. Include only the information needed for the task and avoid copying unrelated personal details into notes.
- Last contact: date, channel and what was asked.
- Latest reply: the factual request or commitment.
- Open task: what your business still needs to do.
- Evidence: where the authorised colleague can find the original record.
Make the next action and review date specific
“Chase next week” leaves too much to interpret. “Check the payment record on 4 November; if unmatched, reply in the existing thread to ask for the transfer reference” tells the next person what to do and when. Use an actual calendar date rather than “tomorrow”, which becomes ambiguous when notes are read later.
A promised date is a review point, not proof of payment. If a query is unresolved, the next action may be to obtain an approval or correct a document before asking the client for an update. Do not silently replace an agreed payment arrangement with the usual reminder cadence.
Use this sample handover note
This fictional example keeps an invoice query separate from the balance. Replace the fields with verified information in your own approved records. The dates describe the example, not a recommended universal reminder schedule.
Invoice: DEMO-208 | Currency: GBP Invoice amount: £480 | Total paid recorded: £0 | Balance: £480 Agreed due date: 23 October 2026 Balance last checked: 27 October 2026 Last conversation: client requested the purchase-order reference on 26 October. Our open task: project lead to confirm the reference and send it in the existing thread. Follow-up state: paused while the query is being resolved. Next owner: designated accounts colleague Next review: 29 October 2026; confirm the reference was supplied, then ask whether anything else is needed. Original correspondence: approved internal thread link
Check scheduled reminders before and after the handover
Review any automatic sequence as part of the handover. A colleague can send a thoughtful reply while an unattended sequence sends a contradictory reminder. Record whether follow-ups are active or paused, and who will review that choice. Pausing future sends does not recall a message that has already been handed to an email provider.
When the original owner returns, reconcile the notes with payments and messages sent during the absence. Close completed tasks, review outstanding promises and choose the next action once. This avoids restarting a conversation that the covering colleague has already resolved.
Use the invoice follow-up checklist before sending the next reminder
Using the idea alongside Evrani
Evrani stores existing invoice details, a note and manually recorded payment totals, with optional automatic follow-ups. You can pause an invoice while a question is being checked. It does not verify bank payments. Keep handover responsibilities and original correspondence in your approved business process; this guide does not describe a shared-team access feature.
Evrani is an early-access development pilot for sample data while legal and data arrangements are completed. Practise with a fictional invoice and fictional contacts. Do not put real client personal data into the pilot. Subscription pricing has not launched.
Keep reading
An invoice follow-up checklist for small service businesses →
Payment reminder email templates for small businesses →
How to follow up an invoice after a partial payment →
Invoice tracker spreadsheet: a CSV preparation checklist →
Client says an invoice is already paid: what to check next →
Invoice held up by a missing purchase order: what to ask →
How to follow up several unpaid invoices with one client →