A usable invoice needs an invoice number, an issue date, who's being billed, what for, and how much is owed — everything else is a refinement on those five things. This is a practical checklist, not tax or legal advice; requirements vary by country, so confirm anything jurisdiction-specific with an accountant.
The fields that make an invoice work
- Invoice number. A unique identifier for this specific invoice — never reused. This is what you and your client both refer to when discussing payment.
- Issue date. When the invoice was created — the anchor point for any payment terms.
- Due date. When payment is expected. Often calculated from the issue date plus your standard terms (e.g. 30 days).
- Client name and contact details. Who's being billed, and how to reach them — at minimum a name; email and address are usually expected too.
- Line items. A description, quantity, and rate for each thing being billed. This is the part that actually explains the number at the bottom.
- Currency. Especially if you bill clients in more than one country — ambiguity here causes real disputes.
- Tax, if applicable. Shown per line or as a total, depending on what your local rules require.
- Total due. The number that matters most to the reader, and the one most worth double-checking.
Fields that are optional but earn their place
- Notes. Payment instructions, a thank-you, or context for the line items — anything that would otherwise be a separate email.
- Discounts. If you negotiate discounts, showing them as their own line (rather than baking them into a lower rate) keeps the original price and the deal both visible.
- Your business details. Name, address, and tax ID if you're required to show one — usually set once as part of your branding rather than typed per invoice.
A structural mistake worth calling out: reused invoice numbers
An invoice number that gets reused — even accidentally, across a new financial year or a copy-pasted template — breaks your ability to reconcile payments and can complicate an audit. See invoice numbering best practices for what a system that doesn't do this looks like.
Keeping this consistent across many invoices
All of this is easy to get right on one invoice and easy to drift on the fiftieth — a forgotten due date here, a mismatched currency there. If your invoicing already starts from a spreadsheet, the fix is validating the whole batch before anything is generated rather than checking each PDF individually afterward. See common spreadsheet invoicing mistakes for the specific things worth checking for.
Doing this at volume
If you're producing more than a handful of invoices per cycle, a tool that enforces these fields — flagging a missing quantity or an unparseable date before it generates anything — catches what a quick visual check on invoice #40 won't. BulkyGen validates every row of a spreadsheet against exactly this list before generating; see preparing a spreadsheet for bulk invoicing.