“Invoice” is a word anyone can type at the top of a document, but a valid invoice is a defined thing: a document that a payer's finance system can process, that a tax authority accepts as evidence, and that a court can read as the record of a debt. The requirements differ in detail between jurisdictions, yet the core is stable across most of them, because the document serves the same three masters everywhere.
This article sets out that common core — the supplier and customer identities, the document's unique identity, the description and the arithmetic, the tax treatment — and explains what each element is for, since requirements memorised without reasons are the first to be dropped under deadline pressure. It then covers the additional rules that attach specifically to VAT invoices, where the document moonlights as the customer's evidence for reclaiming tax, and validity stops being your private concern.
Treat what follows as the anatomy, not the statute book: confirm the specifics against your own rules, especially if you trade across borders, where an invoice can be valid at home and deficient at destination.
The identity fields: who, whom, and which document
A valid invoice names the supplier completely — legal name, address, and the registration or tax number the jurisdiction requires — and the customer with the same completeness. These are not courtesies. The payer's system matches invoices against approved supplier records; the tax authority matches input claims against registered traders; a debt claim matches the document against the parties to the contract. A trading style alone (“Mike's Motors”) where a legal entity exists is the kind of small looseness that stalls all three matches.
The document then identifies itself: the word invoice (in some places, a distinction between a tax invoice and a lesser document), a unique sequential number, the issue date, and where they differ, the date of supply — the date the work was done or goods delivered, which decides the tax period the invoice belongs to. Two dates confuse newcomers until their purpose lands: the issue date times the payment terms; the supply date times the tax. Both earn their place on any document that crosses a period boundary.
The body and the arithmetic: what was sold, proved in numbers
The description must let a stranger identify what was supplied: nature of the goods or services, quantity, and the unit price or rate. “Services rendered: 1,000” is a sentence that satisfies nobody — not the approver matching it to an order, not the auditor testing whether the expense is what it claims, not the court reading the debt's origin. Specificity is the validity: dates of work, project names, deliverables, the nouns of the order being billed.
The arithmetic must close. Subtotal from the lines, discount shown where applied, tax at each rate shown separately with its amount, and the total — and the figures must reconcile: lines that do not sum to the subtotal they claim are the most common self-inflicted validity wound, usually born of editing a copied invoice. A document whose own numbers disagree invites every reader downstream to stop trusting the rest of it, and in a dispute the invitation is always accepted.
VAT invoices: where your document works for your customer too
Where VAT or GST applies, the invoice carries additional compulsory cargo: the supplier's VAT registration number, the customer's where the rules require it (notably for business-to-business and cross-border supplies), the tax point date, the rate applied to each line or category, and the tax amount expressed in the invoice's currency and, in some systems, the home currency where they differ. These fields exist because the customer's right to reclaim input tax is built on your document: no registration number, no compliant breakdown — no credit, and a customer who discovers their credit is void for your paperwork reasons becomes an ex-customer with a grievance measured in money.
Cross-border supplies add their own notations — references to reverse-charge or zero-rating treatment that tell the customer's system why no tax appears. The governing principle for the exporter is that the destination's rules, not home habits, decide what the document must say, and the time to learn them is before the first invoice of a new trade route, not from the customer's rejected-claim email.
Credit notes, corrections and the audit trail
Validity extends past issuing. When an invoice is wrong — wrong amount, wrong party, duplicated — the correct instrument is a credit note that mirrors the original's identity, references its number, and reverses it in whole or part, followed where needed by a corrected invoice. Deleting the original from your system and quietly issuing a different one breaks the sequence, erases the audit trail, and in several jurisdictions converts a clerical error into a compliance offence. The rule that keeps everyone safe: an issued invoice is history, and history is corrected by addition, never by erasure.
Retention completes the picture: invoices and their supporting documents kept, retrievable, for the period the law sets — years, not months — in a form that remains readable. A valid invoice that cannot be produced in year four has a practical value close to an invalid one, which is why the filing discipline of the previous article is not housekeeping. It is the second half of validity.
Key takeaways
- A valid invoice satisfies three readers at once: the payer's process, the tax authority, and a court reading the debt's record.
- Core requirements: full legal identities of both parties, unique sequential number, issue date and supply date where they differ, an identifying description, and arithmetic that reconciles.
- VAT invoices carry extra compulsory fields — registration numbers, rates per line, tax amounts — because your document is your customer's evidence for their input credit.
- Correct errors with credit notes referencing the original; never delete and reissue. History is corrected by addition, not erasure.
- Retention is part of validity: keep invoices retrievable for the full statutory period.
Mistakes to avoid
- Billing under a trading nickname where the payer's records and the contract hold a legal entity name — stalling every automated match.
- Copying a previous invoice and editing it, leaving lines that no longer sum to the subtotal beneath them.
- Omitting your VAT registration number or the per-rate breakdown, silently voiding your customer's input credit.
- Deleting a wrong invoice and issuing a fresh one with a reused number, destroying the sequence the whole system relies on.
Questions readers ask
Is an email saying “you owe me 500” an invoice?
It is a payment request, and possibly evidence of a debt — but it lacks the identity, numbering, description and tax fields that make an invoice processable and creditable. For any business purpose, issue the real document; it costs five minutes once the template exists.
Must an invoice be on paper or a special form?
Increasingly, no — electronic invoices are standard and some jurisdictions now mandate structured e-invoicing between businesses. What matters is content and integrity: the required fields, unaltered, retrievable. Follow your jurisdiction's format rules where they exist.
What if I discover an error after the invoice was paid?
Issue a credit note for the error and, if money must move, a corrected invoice or a refund against it — with the trail intact. The money being settled does not cancel the document problem; the documents must agree with reality at audit time, not just at payment time.
Put it into numbers
Check your template against the validity core before the next invoice leaves: identities, number, dates, description, reconciling arithmetic — then generate it cleanly, every time.
Open the Invoice Generator