What belongs on a freelance invoice — and what actually gets it paid
The fields every freelance invoice needs, the ones that quietly cause late payment, and how to keep track of what is sent, paid and overdue.
An invoice has two jobs. It has to satisfy an accountant, and it has to get paid. Most advice covers the first and ignores the second, which is why plenty of correctly formatted invoices sit unpaid for two months.
A note before the list: the legally required minimum depends on where you and your client are registered and whether you are VAT-registered. Nothing here is tax advice — confirm the statutory fields with your accountant once, then reuse that as a template forever.
The fields that make it an invoice
- A unique invoice number. Sequential, never reused. This is the one your accountant cares about most, and the one people improvise worst.
- Issue date, and a due date — an explicit date, not “30 days”.
- Your details: legal name or trading name, address, and your business and tax identifiers.
- The client’s details, including their own identifiers where applicable.
- Line items: what was done, quantity or hours, unit price, line total.
- Subtotal, tax, total — and if you are not charging tax, the reason, which is often a legal requirement rather than a courtesy.
- Payment details: account number, IBAN, whatever the client actually needs to send money without writing back to ask.
- Currency, stated explicitly. “1 500” is not an amount if you work across borders.
The fields nobody lists that decide whether you get paid
A due date written as a date. “Net 30” requires arithmetic from someone who has no reason to do it in your favour. “Due 2 October 2026” does not.
Line items in the client’s language, not yours. “Discovery phase” means nothing to the person in accounts payable holding your invoice next to a purchase order. “Website redesign — research and wireframes, 12 h” can be matched to something they recognise and approved.
A purchase order or reference number, if the client uses them. In any company larger than a handful of people, an invoice without the reference goes into a queue for someone to work out where it belongs. That queue is where invoices spend their unpaid months. Ask once, at the start of the project, then put it on every invoice.
One named recipient. Sending to a generic company address is sending to nobody in particular. Ask who receives invoices — it is usually not the person you did the work for.
A PDF, not a document. Send a PDF. Anything else invites the client to open, reflow or accidentally edit it, and looks provisional.
Then track what happens to it
This is the part most freelancers do worst, because it happens after the satisfying bit is over. An invoice is not finished when you send it. It has a state, and the state matters:
- Draft — written, not sent.
- Sent — with the client, clock running.
- Paid — closed.
- Overdue — past the due date and now your job again.
Without those states you are searching your sent mail in December trying to work out whether the June invoice was ever settled. With them, chasing is a five-second look at a list rather than an unpleasant investigation.
Invocat ByEase is built around exactly that loop: line items, discounts, taxes and multiple currencies on the invoice, a polished PDF to send, and status tracking through draft, sent, paid and overdue. Because the hours and expenses already live on the project, the invoice is assembled from what you tracked rather than retyped.
Your data stays on your device and your own iCloud. For a file that contains every client you have and what each of them pays, that is not a small detail.
On chasing late payment
Chase early and unemotionally. A short message the day after the due date — “invoice 2026-041 was due yesterday, could you confirm it is in the run?” — recovers most late payments, because most late payments are not refusals. They are an invoice sitting in the wrong inbox.
The freelancers who get paid on time are not tougher negotiators. They just notice sooner.