How to make an invoice, field by field

An invoice has one job: get you paid without a follow-up conversation. Every field on it exists because somewhere, at some point, its absence caused a payment to stall. This guide walks the document top to bottom — what each field is for, what to put in it, and where people go wrong. If you’d rather learn by doing, the generator is preset with sensible defaults and shows a live preview as you type.

The header: who, and which document

Your details go top-left by convention: your name or business name, address, email, phone. If you trade under a business name, show both (“Jane Smith, trading as Brightside Design”) — in some places, like the UK, that’s a legal requirement for sole traders. Add a tax identifier where your jurisdiction uses one on invoices (VAT number, GSTIN, ABN); US freelancers generally keep tax IDs off the invoice and handle them once, on the W-9.

The client’s details matter more than people think. Bill the legal entity that owes you, not the human you talked to — “Acme Corp, attn: Sam Lee” beats “Sam”. Large companies route invoices by entity name; the wrong one can genuinely dead-end in the system.

The word INVOICE should appear plainly. Accounts-payable software and tired humans both sort documents by that word. If it’s a receipt or a quote, say that instead — they’re different documents.

The identity block: number and dates

Invoice number. Unique, and ideally sequential — INV-001, INV-002 and onward. It’s how both sides refer to the document forever after (“re: INV-014”), and a continuous series is quiet evidence of orderly books. Gaps aren’t illegal in most places, but several tax systems (UK VAT, Indian GST) do expect sequential series, and there’s no downside to just doing it. There’s a whole guide on numbering schemes if you’re choosing one.

Issue date is when you send it; it starts the payment-terms clock. Due date is that clock’s alarm. Write the actual date, not only “Net 30” — “Due August 17” survives forwarding, timezone confusion and the client’s intern. The generator computes it from your chosen terms automatically.

The body: line items

This is the part the client actually reads. Each line carries a description, a quantity, a rate, and their product. Three rules cover most of what goes wrong:

1. Describe in the client’s language, not yours. Mirror the words from the proposal or the email where they said yes. The person approving payment recognizes what they bought.
2. One line per agreed thing. A $4,000 “Design services” blob invites questions; four $1,000 lines that map to the quote answer them in advance.
3. Make the math visible. Hours × rate for time (use decimals — 1.5 is ninety minutes; see hourly billing), counts × unit price for things. Numbers a client can re-derive are numbers they don’t email you about.

The math block: subtotal, discount, tax, total

The conventional order — and the one the generator enforces — is: subtotal, minus discount, then tax on the discounted amount, giving the total. If you’ve taken a deposit, show it: an “amount paid” line turning the total into a balance due is clearer than invoicing only the remainder and hoping everyone remembers why.

Show discounts explicitly rather than quietly lowering your rate — “Discount (10%) — returning client” documents generosity that would otherwise be invisible, and keeps your rate card intact for next time.

Tax is the field with real rules attached, and they’re jurisdiction-specific: US sales tax applies mostly to goods and certain services and varies by state; UK VAT applies only once you’re registered; Indian GST has defined invoice formats above the registration threshold. The generator lets you name the tax line whatever your jurisdiction calls it. If no tax applies to you, the honest move is a zero-tax invoice — not a made-up “service charge”.

The payment block: how the money moves

The single highest-leverage sentence on an invoice is the one that says exactly how to pay. Bank name and account details, the check payee, the PayPal address, a payment link — whatever routes money to you, spelled out so the client’s finance person needs nothing else. Vague (“payment by bank transfer”) means an email round-trip; specific means money.

Notes close the document: a thank-you, the late-fee policy your contract sets (in the US, 1–1.5% per month is conventional), or delivery terms like “final files on receipt of payment”. Keep it to a sentence or two — the notes field is for things the client should read, not boilerplate they’ll skip.

The mistakes that actually delay payment

After all the theory, stalled invoices usually trace to one of five mundane causes: the invoice went to a person instead of the accounts-payable address; the entity name didn’t match the client’s records; there was no PO or reference number the client’s system required; the amounts didn’t match the quote and nobody explained why; or the payment details were missing or wrong. Every one of them is preventable at sending time — a minute of checking beats a month of chasing, and there are tactics for the chasing too.

One last thing, since you’re building this document in a browser: everything you type into this site’s generator stays on your device. The PDF is assembled locally; there’s no server holding your client list. For a document that describes your income, that’s worth knowing — and worth verifying.