What to Put in Every Invoice Field
An invoice has about a dozen fields, and every one exists because someone's records need it. Seller identity, buyer identity, invoice number, issue date, due date, item lines, subtotal, discount, tax, total, payment details, and notes — here is what each field means, why it exists, and what a beginner should put in it.
From (you)
Your real name or business name, your address, and a contact. This is who is billing — the client's accounts team matches it against whoever they agreed to pay. Working under a brand name? Put the brand and your real name, so the document ties to an actual person or business.
Bill to (the client)
The client's name and address exactly as they gave them. If the client is a company, the company's name — not your contact person's. A document addressed to the wrong entity is the most common beginner reason an invoice comes back for a redo.
Invoice number
Your unique, sequential identifier — 001, then 002. It is how you, the client, and any tax process refer to this exact document forever. Never reuse one, never skip worrying about the pattern; just count up.
Issue date and due date
Issue date: the day you create the document. Due date: the calendar day payment should arrive, per your agreement. Both are real dates, always — “upon receipt” as a due phrase produces payments whenever the reader feels like it.
Item lines
The work, one line per piece, each with a description and an amount — quantity × price or hours × rate where that is the agreement. Descriptions are the field beginners underinvest in; five weak-to-strong rewrites show the difference.
Subtotal, discount, tax, total
Subtotal: the lines added up. Discount: shown as its own reduction if you gave one — never hide it inside lowered line prices. Tax: only if you are registered, at your rate, on top. Total: the single figure the client pays, impossible to misread.
Payment details
How the money should reach you — your bank details, your payment handle, whatever you agreed. Put them on the document itself; an invoice without a route to pay it adds a round of messages to every job.
Notes
Anything the client needs that fits nowhere else: the project reference, the milestone this document covers, a thank-you with your availability for the next piece. Notes print on the document — keep them factual and brief.
Every field above is on the maker in this order, labeled in plain words. The first-invoice walkthrough strings them into the full process; this page is the reference to keep open beside it.
The fields beginners most often leave blank
Three fields get skipped by first-timers, and all three cause returns. The client's reference: if they gave you a purchase order or project code, it belongs on the document — their system literally cannot match your invoice to their order without it. Your tax number: if you are registered, it is not decoration; in many jurisdictions the invoice is not fully valid without it, and clients' accounts teams check for it before anything else. The description's anchor: not a field with its own box, but part of every line — the project or context the work belongs to. A line that floats free of any project forces the approver to go and ask someone what the charge is for, and documents that make people ask questions wait at the bottom of the pile. Fill the three, and your first invoice is already better formed than most.