Invoice reminders for freelancers: from handover to payment

Check the first client’s billing path before handover

Read the agreed scope and billing stage. Identify exactly what you are handing over: named files, a completed session, a report or another specified deliverable. Record any review or approval step already agreed. Do not add a new approval condition simply because the client has an internal accounts process.

Ask the client who receives the work and where the invoice goes. For a first project, also ask whether accounts needs a supplier setup form, project code or confirmed purchase order. Record an unanswered requirement as outstanding rather than assuming it is complete.

Confirm a question raised by accounts through your established client contact. An unfamiliar request to provide sensitive business information deserves checking before you respond. The aim is to identify the submission requirements for this job, not collect extra client data.

Create a handover pack the client can check

Keep an inventory beside the delivered files and a separate copy of the issued invoice. Here is a fictional photographer’s pack. Replace the names and records with the actual job; “not confirmed” is an honest entry where information is missing.

Project: North Hall event photographs, 30 October 2026
Scope record: accepted quote Q-18, final image delivery
Delivery: 2 November; NorthHall-final-v1.zip
Inventory: 12 final JPGs, listed in delivery-index.txt
Work contact: Mara, client marketing contact
Receipt / review: awaiting Mara's response
Invoice: INV-718; £950; due 16 November
Accounts route: confirmed client accounts mailbox
Customer event code: requested, not yet confirmed
Owner's next check: delivery receipt, 3 November

The inventory makes a file problem answerable. Keep “files received”, “agreed review completed” and “invoice received by accounts” as separate entries. None of those entries establishes that payment has arrived.

Ask for the confirmation that is actually missing

A handover email can say: “The final ZIP and index contain the 12 agreed images. Please confirm that you can open the files and identify any missing agreed item by filename. INV-718 has separately been submitted to your confirmed accounts address.” Use that wording only where the inventory and submission are true.

If the agreed review is pending, ask the work contact about that review. If accounts has not acknowledged the invoice, ask accounts about receipt and processing requirements. If payment is overdue with neither issue open, ask for payment status using the checked balance.

Sending “Have you seen my invoice?” to the creative contact cannot establish whether accounts received it. Likewise, a payment reminder does not answer a missing-file complaint. Route the question to the person who can resolve that stage.

Fictional example: distinguish delivery from invoice approval

Sam uses the pack above. Mara confirms all 12 images open on 3 November and completes the agreed review on 5 November. Sam records both events. Accounts then asks for the event code needed to route INV-718 internally.

Sam obtains the confirmed code from Mara, supplies it to accounts and keeps its acknowledgement. The next question concerns accounts processing, not another review of the photographs. If Mara instead identifies an agreed image missing from the ZIP, Sam resolves that issue and pauses the routine chase.

The £950 remains unconfirmed as paid until Sam checks receipt and allocation. Client praise, completed review and accounts acknowledgement can all be recorded without turning them into payment evidence.

Use the pack to close the right stage

Before follow-up, check the unresolved line in the pack and your latest payment records. Close answered delivery or reference questions with dates and evidence, then move to the next missing confirmation. Keep the issued amount and due date unchanged unless a deliberate correction is required.

For manual reminder records, separately record confirmed paid, disputed or cancelled status. The handover pack explains the work history; that status update governs future reminders. Retain the completed pack so the next project starts with known contacts rather than assumptions.