There are two different questions hiding inside "what should an invoice include". One is what the law requires, which is a jurisdictional question with a statutory answer — covered separately in our guide to what makes an invoice legally valid. The other is what makes an invoice actually get paid, which is a practical question, and the answer is a longer list.
This guide takes the second question. A legally perfect invoice can still sit unpaid for six weeks because it was missing a purchase order number, or because nobody could tell which project it related to. The fields that prevent that are mostly not the ones any statute mentions.
The three zones of an invoice
Every invoice, however it is laid out, answers three questions in sequence. Thinking in these zones makes it obvious what is missing when something feels incomplete.
**Who and what document is this?** Your business name and contact details, the client’s name and address, the word "Invoice" so it is not mistaken for a quote or a statement, a unique invoice number, and the dates. This zone exists so the document can be identified and filed.
**What is being billed?** The line items: a description of each thing supplied, quantity, unit price and line total, plus any reference tying the work to what was agreed. This zone is what the client checks before approving.
**What happens now?** The subtotal, tax, total due, the due date, how to pay, and where to raise a query. This zone is what turns a record into an action.
The fields that speed up payment
Beyond identification and arithmetic, a handful of fields do disproportionate work in getting an invoice through a client’s process. Most cost nothing to add.
- **Purchase order number** — the single highest-value field when invoicing any organisation with a procurement function. Without it, your invoice cannot be matched automatically and becomes manual work.
- **A description tied to what was agreed** — line descriptions that mirror the purchase order or statement of work, so the approver can recognise them without cross-referencing.
- **The due date as an actual date** — not just "Net 30". Printing "Due 31 March 2026" removes every counting argument.
- **Payment instructions in full** — bank details, or a payment link, with the reference the client should quote. Retyping details from a PDF is friction that delays payment.
- **A named contact for queries** — so an exception is resolved with one email rather than a search for who to ask.
- **The project or cost centre reference** — where the client uses them, this determines who approves it and how fast it is coded.
- **Your tax registration number** — required in VAT and GST jurisdictions, and its absence can invalidate the client’s reclaim.
Writing line items people can approve
Line descriptions are where most invoices are weakest, and the weakness is expensive because the approver is often not the person who commissioned the work.
"Consulting services — £4,000" tells an approver nothing they can verify. "Q1 brand strategy workshop and report, per SOW-2026-14 — £4,000" lets them match it against something. The second costs eight extra words and removes a round trip that might take a fortnight.
Granularity should follow how the work was agreed. If you quoted a fixed price for a defined scope, one line referencing that scope is right and itemising it into components invites line-by-line renegotiation. If you bill by time, show the periods and rates, because that is what the client agreed to check. Splitting a fixed-price engagement into invented sub-items is a common way to create questions nobody needed to ask.
What to leave off
A crowded invoice is harder to process, and some additions actively cause problems.
Leave off internal codes that mean nothing to the client, long terms and conditions that belong in the contract, and anything that reads as a lecture about payment. A single clear line on terms is effective; three paragraphs of warnings suggest a history of being paid late and set an adversarial tone before the invoice has even been read.
Leave off prices on documents that are not invoices — a delivery note with prices invites a warehouse signature to be treated as agreement to commercial terms. And leave off any late fee that was not agreed in advance: introduced for the first time on the invoice, it is a request rather than a right, and it undermines the terms you do have.
One thing worth including that people often omit: your own logo and consistent formatting. This is not vanity. An invoice that looks like your previous invoices is recognised faster, and invoice fraud frequently works by sending a plausible-looking document with altered bank details. Consistency is a small security control as well as a presentation choice.
A worked checklist
Before sending, the invoice should let a stranger in the client’s finance team answer every one of these without contacting you: who sent this, who is it for, what is it for, what did we agree, how much, when is it due, how do I pay, and who do I ask if something is wrong.
If any answer requires a phone call, that call is a delay you have built into your own payment cycle. Most of the time the fix is one missing field.
Common Mistakes
Vague line descriptions
"Services rendered" cannot be approved by anyone who was not in the room. Reference the agreement, the period or the deliverable so an approver can verify it without asking you.
Omitting the purchase order reference
For any client with a procurement process this is the field that decides whether your invoice matches automatically or becomes a manual exception nobody is in a hurry to resolve.
Burying the payment instructions
The client has decided to pay you; make the next step obvious. Bank details or a payment link, with the reference to quote, near the total.
Loading the invoice with contract terms
Terms belong in the agreement, made before the work. An invoice thick with conditions is harder to process and cannot introduce obligations the client never accepted.
Frequently Asked Questions
Does an invoice legally have to include specific fields?
In VAT and GST jurisdictions, yes — there is a statutory list, and it is covered in our guide to what makes an invoice legally valid. In the United States there is no federal prescription, though state sales tax rules and your own record-keeping obligations still apply.
Do I need to include my address?
Generally yes, and in many jurisdictions it is required content. Practically, a client’s finance system usually needs a supplier address to set you up as a payee, so omitting it creates a request you will have to answer anyway.
Should I put payment terms on the invoice if they are already in the contract?
Yes. The invoice is what the person paying it actually reads, and they will rarely have the contract to hand. Restating the terms costs nothing; introducing new ones there is what does not work.
How detailed should line items be?
Detailed enough to be recognised and verified, structured the way the work was agreed. Mirror the purchase order or scope; do not invent sub-items on a fixed-price engagement, and do show periods and rates when billing by time.
Sources & Further Reading
- Invoicing and taking payment from customers — GOV.UK
- Payments and invoicing for business — business.gov.au, Australian Government
Ready to put this into practice?
Create a professional invoice in your browser — free, no sign-up, no watermark.
Open the Invoice Generator