Invoices are not read, they are processed. Somebody in a finance team opens twenty of them in an hour, and each one is either approvable at a glance or set aside for a question. Almost everything in this layout exists to keep an invoice out of the set-aside pile: the number where they look for it, the purchase order reference in the header, one line per thing that was agreed, and the total in the bottom right in the largest type on the page.
The single highest-value field is the reference. If your customer raises purchase orders and the PO number is absent, the invoice cannot be matched, and it will sit until somebody has time to ask you for it. Ask for the PO number when the work is agreed, not when the invoice is due, and put it in the header rather than the notes.
Describe the supply the way your customer describes it, and cite the agreement. “Brand identity — phase 2, per SOW clause 4” is approved by somebody who has never met you; “design work” is not. Where a line is a disbursement recharged at cost, say so and show it at zero or the correct rate, because that is where VAT errors on small invoices cluster.
On terms: state them, then enforce them once. Net 30, a due date computed rather than implied, and one line naming statutory interest under the Late Payment of Commercial Debts (Interest) Act 1998. You will rarely charge it. Its presence changes the conversation on day thirty-five, which is the entire point.
Perrin Studio, an eight-person design practice, moved from a lump-sum invoice with terms in the footer to this layout. Same customers, same work, same amounts.
A well laid out invoice removes the queries. It does not remove the work of raising forty of them from delivered time, checking they match what was agreed, and knowing on any given morning which are overdue and by how much.
Books does that part: invoices assembled from delivered work rather than retyped from a timesheet, VAT handled by rate, and an overdue view nobody has to build. The layout in this template is the one it issues.
Every retyping is a chance to bill the wrong hours, and the errors run in both directions.
If the answer needs a spreadsheet and an afternoon, cash is being managed retrospectively.
A manual sequence across two people and three folders will drift. It always drifts.
Mixed rates and disbursements are exactly where hand-calculated VAT goes wrong quietly.
The elements listed are those required for a valid UK VAT invoice, and the template shows all of them. It is a template rather than advice — if you trade internationally or in construction, confirm the variant with your accountant before you issue.
The same layout works and the required elements are near-identical; the VAT number format and rates differ. The XLSX has an IE tab with Irish rates prefilled.
Yes, top left, and keep it under about 40mm wide. The template is free of any Treepie branding — there is no watermark and no attribution requirement.
Show it whenever it differs from the invoice date — with staged payments or a deposit, it often does, and getting it wrong puts the sale in the wrong VAT period.
Terms on the invoice give you statutory interest and a fixed sum per invoice without a contract clause. In practice the value is that day-thirty-five conversation, not the interest.