What belongs on a professional invoice (and what doesn't)

An invoice is a legal document. It's also a sales tool, a payment prompt, and — if things go sideways — evidence in a small claims proceeding. Most freelancers under-do it, either because their tool doesn't ask for enough or because they've copied a friend's template without checking the rules where they actually live.

Here's what a good invoice actually contains.

The non-negotiables

Every jurisdiction agrees on roughly the same core fields. If any of these are missing, the invoice may be legally invalid — which means your client can't deduct it, and you may have trouble enforcing payment.

• The word "Invoice" — plain as it sounds. Not "Statement", not "Bill".
• A unique invoice number — sequential, with no gaps. Tax authorities check this.
• Issue date — the date the invoice is created.
• Your legal name and address — as registered, not your trade name.
• Your tax ID / VAT number — where applicable.
• Client's legal name and address — same rules.
• Client's tax ID / VAT number — mandatory in most of Europe for B2B invoices.
• Description of goods or services — specific enough that a stranger could tell what was sold. "Consulting — 10 hours" is fine. "Services" is not.
• Quantity and unit price for each line.
• Currency — clearly stated. Never assume the reader knows.
• Subtotal, tax amount, total — broken out separately.
• Tax rate applied — and if you're applying a reverse-charge or zero-rate, cite the reason (e.g. "Reverse charge — Article 196 of EU VAT Directive 2006/112/EC").
• Payment terms and due date.
• Payment instructions — bank details, payment link, or both.

The near-mandatory fields

Not universally required but you'd be foolish to leave them off:

• Delivery date or service period — when the work was actually done. Different from the invoice date, and often required (Germany, Hungary, Poland especially).
• Purchase order number — if the client uses one, missing it is the fastest way to bounce back through Accounts Payable purgatory.
• A statement of what happens on late payment — "Interest of 8% + base rate applies after due date" gives you a legal hook without being aggressive.

The stuff that actually gets you paid faster

None of this is legally required — but every one of them measurably reduces days-to-pay:

• A short due date. "Net 30" reads as "pay whenever." "Due on receipt" or "Due within 7 days" gets attention.
• A payment link. Stripe, PayPal, Wise, whatever your client uses. Bank transfers get paid last; one-click pays get paid first.
• The exact reference to use on the transfer. "Include INV-2026-042 in the payment reference" saves your reconciliation and speeds theirs.
• A thank you. One line. It sounds silly. It works.

What to leave off

• Long terms and conditions. They belong in your contract, not on the invoice. If the T&Cs are a surprise on the invoice, they're not binding anyway.
• Discount theatre. Made-up "usually €5,000, discounted to €4,000" pricing on an invoice looks like you're haggling with yourself. Put the real price.
• Your logo three times. Once, in the header. Nobody buys again because you rendered your logo bigger.
• Emojis. Yes, really, someone had to say it.
• Your personal email if you have a business one. Look professional.

Country-specific gotchas

• Hungary — real-time reporting via Online Számla is mandatory for every invoice. Manual PDF invoices without NAV submission are illegal.
• Italy — B2B invoices must be sent through the Sistema di Interscambio (SdI) in FatturaPA XML format. Paper or PDF alone is not compliant.
• Germany — from 2025 onward, B2B invoices between German companies must be in a structured electronic format (XRechnung or ZUGFeRD) — the era of the PDF invoice is ending here.
• UK — no VAT number needed if you're under the threshold, but the invoice must clearly say you are not VAT-registered when charging no VAT.
• US — no VAT, but state sales tax may apply depending on where the buyer is and what you sold. Digital services rules changed dramatically after South Dakota v. Wayfair (2018) — check nexus rules per state.

The one habit that changes everything

Number your invoices in a way you can defend. Sequential, gap-free, one series per legal entity per year. INV-2026-001, INV-2026-002, and so on. If your tax authority ever asks "where's invoice 007?" — because they will — you want to be able to point to it, not explain why the numbering skips.

Do that, keep the mandatory fields tight, and your invoices will look like the ones that get paid quickly and audited painlessly.