Invoicing
Invoice Example: A Completed Invoice, Field by Field
Below is a real invoice, filled in, with each part explained beside it. It is rendered by the same code that produces documents in the generator, so what you see is exactly what the tool outputs. Underneath, the versions of each field that cause problems, and why.
By Arshad Hossain · Published
The short version
- Bill the legal entity, not your day-to-day contact.
- Print a real due date rather than the words "Net 30".
- Specific line descriptions are the cheapest defence against a delayed payment.
- Payment terms and bank details belong on the invoice, not only in the contract.
| # | Description | Qty | Rate | Amount |
|---|---|---|---|---|
| 1 | Brand identity system and logo suite | 1 | $4,200.00 | $4,200.00 |
| 2 | Packaging design — three SKUs | 3 | $850.00 | $2,550.00 |
| 3 | Photography direction | 2 days | $1,150.00 | $2,300.00 |
What the example gets right, and what a weak invoice does instead
Most invoices that get queried are not wrong. They are vague. Accounts payable cannot approve what they cannot match to something they recognise, so the invoice sits in someone's queue until they get round to asking.
| Field | On the example | What causes a query |
|---|---|---|
| Billed to | The client's registered company name | Your contact's personal name |
| Number | INV-2041, sequential | The project name, or a date |
| Dates | Issue date and an explicit due date | "Net 30" with no date printed |
| Line items | "Packaging design — three SKUs" | "Design services" |
| Quantity | 2 days at a stated day rate | A single flat amount |
| Tax | Rate and amount on their own line | Rolled into the total |
| Payment | Terms and bank details on the document | Referred to a contract |
The fields people leave off
Three omissions account for most of the delay. The first is a due date: without one there is no deadline, and an invoice with no deadline is scheduled whenever it suits the payer.
The second is payment detail. An invoice that does not say how to pay it has to come back to you before it can be paid, which adds a round trip to every single one.
The third is a purchase order number, where the client uses them. Many larger buyers will reject an invoice automatically, before a human sees it, if the PO reference is missing. Ask whether one is required at onboarding rather than finding out on day 45.
What changes by country
The example above is a general-purpose invoice. Tax jurisdictions add required fields on top: a GSTIN and a place of supply in India, an ABN in Australia, your VAT registration number and prescribed fields in the UK, the buyer's name once a Canadian invoice reaches $500.
The structure does not change. What changes is the identifiers you must show and how the tax has to be presented, so start from a document like this one and add what your jurisdiction requires.
Invoice examples: common questions
What does a proper invoice look like?
A header identifying it as an invoice, your details and the client's, a unique number, issue and due dates, itemised lines with quantity and rate, a subtotal, tax shown separately, the total, and the payment terms and bank details.
What is a good invoice line item description?
One a person outside the project can match to something they approved. "Packaging design — three SKUs" works; "design services" does not. Specificity costs you nothing and removes the most common reason an invoice is queried.
Should an invoice show the quantity and rate separately?
Yes. Showing 2 days at 1,150 lets the client verify the figure against what was agreed. A single flat total is harder to approve because there is nothing to check it against.
What should I put if there is no purchase order?
Reference whatever the client uses to recognise the work — a project name, a contract number, or the name of the person who commissioned it. Ask at onboarding whether a PO is required, because many large buyers reject invoices without one automatically.
Frequently Asked Questions
Can I use this example as a template?
Which template is the example using?
More on invoicing
- How to Create an Invoice: A Step-by-Step Guide
What an invoice must contain, how to number them, setting payment terms, and exporting a PDF.
- How to Create an Invoice for Free
Four routes to a free invoice compared on speed and accuracy, plus the pre-send checks that stop invoices being queried.
- Free Invoice Templates: Choosing a Format That Actually Works
Choosing an invoice template by file format and industry, the layout decisions that affect payment speed, and why template sites hold 1,000 near-identical files.
- Freelance Invoicing: A Complete Guide
Invoicing as a freelancer end to end: your first invoice, rates, deposits, international clients and records.
- Invoice Numbering Systems That Survive an Audit
Designing an invoice numbering system that survives an audit: sequential vs dated schemes, why gaps matter, resetting annually, and what to do after a mistake.
- International Invoicing: Currency, Fees and Getting Paid
Invoicing across borders: choosing the currency, who pays the transfer fees, exchange rate risk, and getting paid without losing a chunk to intermediary banks.
- Invoice Record Keeping: What to Keep and For How Long
How long to keep invoices, what counts as an acceptable record, digital versus paper, and building a filing system you can actually search under pressure.
- What Is a Proforma Invoice?
What a proforma invoice is, when to send one, and how it differs from a quotation and a commercial invoice.
- Receipt Template: What a Receipt Must Show
What a receipt has to show, how it differs from an invoice, and when a client is entitled to one.
- Purchase Order vs Invoice
Who issues a purchase order, who issues an invoice, and why a missing PO number stops you getting paid.
- Purchase Order Template: What a PO Must Include
Writing a purchase order that a supplier can act on and an invoice can be matched against.
Make one like this
Free, no sign-up, no watermarks. Your data stays in your browser.
Create an Invoice Free