Every Line Accounted For: Designing a Fee Note That Earns Its Payment
Photo: Loz Pycock from London, UK, CC BY-SA 2.0, via Wikimedia Commons
By the time an invoice reaches a client's finance team, the work itself is usually well behind us. The meetings have been minuted, the deliverables signed off, the thanks exchanged. What remains is a document that has to stand on its own, in a room where nobody from the delivery team is present to explain it. That is the test a fee note must pass, and it is a test many firms fail not through dishonesty but through brevity.
A well-built invoice does a specific job: it lets a stranger approve a payment without needing a phone call. The suggestions below are aimed at that single outcome.
Lead with the scope, not the total
The first line a reader should meet is a reference they recognise — a scope document, a statement of work, or a purchase order number they issued themselves. A short descriptor such as 'Phase two advisory support, per Scope Note 24-07 dated 3 March 2026' does more for confidence than a paragraph of narrative. Where a project has run across several months, group the invoice by phase or by deliverable rather than presenting a single undifferentiated figure. Clients approve what they can locate in their own records.
Put assumptions on the page
Every engagement rests on assumptions: that the client's data will arrive clean, that a third-party supplier will respond within a fortnight, that one workshop rather than three will be needed. These are usually discussed at kick-off and then forgotten. Restating two or three of them on the invoice — briefly, without defensiveness — explains why the shape of the work may differ from the shape of the original estimate. It also gives the client a natural place to raise a concern before the payment run rather than after it.
Treat change as a line item, not a surprise
Where additional work has been requested and approved, it deserves its own section, however small. A subheading such as 'Variations approved during the period' followed by the date of approval, the person who gave it, and the value is sufficient. The discipline of writing this down has a useful side effect: firms that cannot populate the section tend to discover that the change was never formally approved, which is a conversation better had before invoicing than after.
Be plain about time, disbursements and tax
Time-based invoices should show enough structure to be intelligible — role or grade, hours, rate, and total — without lifting the timesheet wholesale onto the page. Category-level detail is usually the right balance. Expenses need their own clearly labelled block, with a note on whether they are recharged at cost or with an agreed handling fee. Anything passed through at cost should carry a supporting reference.
On tax, the essentials are not optional. A VAT invoice must show the supplier's VAT number, the rate charged and the VAT amount separately, and a limited company should display its registered name and company number. Where the client has supplied a purchase order number, a cost centre or a portal reference, quote it exactly as given. Mismatched references are one of the most common causes of an invoice sitting unpaid in an approval queue, and the fix costs nothing at the point of issue.
State what was excluded
A short closing note on what the invoice does not cover is a mark of confidence, not of caution. If travel to a second site was out of scope, if the retainer resumes on a set date, if a subsequent phase remains to be quoted, say so. This single paragraph prevents the most corrosive kind of dispute — the one founded on differing memories of what was agreed — and it does so before anyone has a reason to be defensive.
Make the mechanics effortless
Payment terms, the due date stated as a calendar date rather than an interval, bank details, and a named contact for queries should all appear in one place. A remittance address or portal where the client can confirm payment completes the loop. For clients operating under Making Tax Digital and quarterly reporting cycles, an invoice dated and referenced consistently is easier to reconcile; for everyone, a stated due date removes the small ambiguity that a payment team will resolve in favour of delay.
None of this requires new systems. It requires a template with fixed sections and a habit of completing them at the point the work is approved, not at the point the finance calendar demands it. Firms that adopt the habit tend to report the same two effects: fewer queries and faster settlement. The invoice, in other words, stops being a reminder of cost and becomes a record of what was delivered — which is exactly what a client needs in order to pay it.
