What to include on an invoice: a checklist
A checklist of required, helpful and optional invoice fields, with a worked example showing how line items, tax and totals fit together.

A clear invoice can get paid sooner, because the person approving it does not have to ask a question first. Use this checklist to build a template, then check each invoice against it before sending. Legal requirements for invoices differ by country and sometimes by region, so treat the "required" list as a starting point and confirm it locally.
Required fields
These are the fields an invoice generally needs to be understood and processed:
- The word "Invoice" and a unique invoice number.
- Issue date and due date (or payment terms).
- Your business name and address, and a contact email.
- The client's name and billing address.
- A description of what was supplied, with dates or the project name.
- Quantities, unit prices and line totals.
- Total amount due, with the currency stated.
- How to pay: bank details, payment link or instructions.
Where sales tax, VAT or GST applies, you will also need tax lines and often your tax registration number. The rules vary, so check with a qualified adviser or the relevant tax authority. This is general information, not tax or accounting advice.
Helpful fields
These are not always required, but they remove questions:
- Project name or reference, so the client can match the invoice to a budget.
- Purchase order number, if the client uses them. Some clients will not process an invoice without one.
- Milestone or period covered, such as "Phase 2: design approved 14 October".
- Billing contact name, so it reaches the right inbox.
- Itemized hours and rate, for time-based work.
- Accepted payment methods and any fees for card payments.
- Late payment terms, stated in the same words as your contract.
If you invoice from time entries, show the hours and the rate on separate lines. Clients ask fewer questions when they can see how the total was built.
Optional fields
Add these when they help the specific client:
- A short thank-you or note about the next milestone.
- A link to the project summary or the approved deliverable.
- A breakdown by team member or task type.
- Expenses with receipts attached, listed separately from fees.
- Notes about a deposit already received, shown as a deduction.
Keep optional fields short. A one-page invoice is easier to approve than a three-page one.
A worked example
Say you invoice a client for two services. These figures are examples.
- Design, 12 hours at $95 an hour: 12 x $95 = $1,140
- Development, 20 hours at $110 an hour: 20 x $110 = $2,200
- Subtotal: $1,140 + $2,200 = $3,340
- Sales tax at an example rate of 8 percent: $3,340 x 0.08 = $267.20
- Total due: $3,340 + $267.20 = $3,607.20
If the client paid a $1,000 deposit earlier, show it as a line: "Deposit received 3 October: -$1,000.00". The balance due is $3,607.20 - $1,000 = $2,607.20. Showing the deposit and the balance, rather than just the balance, makes the document match the client's records.
Do the maths twice, and have your invoicing tool or a second person check the total. A wrong total is an easy reason for a client to send an invoice back.
Wording that gets invoices approved
Use plain descriptions. "Website design phase, approved 14 October" is clearer than "Services rendered". For retainers, say the period: "Retainer, 1 to 31 October". For milestone billing, name the milestone and the acceptance date, as covered in how to invoice from milestones and get paid faster.
Software teams often invoice from sprints, releases or phases. Project management for small software development shops describes how to structure that work so each invoice maps to a visible unit of delivery.
Adapt the template for different work
One template rarely fits every type of work, so keep a few variants:
- Fixed-fee project: milestone name, percentage of total, amount, and the acceptance date.
- Time and materials: hours by person or task, rate, and the period covered.
- Retainer: service period, the fixed fee, and any hours above the allowance listed on a separate line.
- Expenses: each cost with its date and amount, marked as a pass-through.
For example, a retainer invoice for 25 hours at $140 shows $3,500 for the period and, if the team logged 28 hours, a second line of 3 x $140 = $420, for a total of $3,920. Two lines make it clear what was included and what was extra.
Before you send
Run through a short final check:
- Is the invoice number unique and in sequence?
- Is the client name exactly as in the contract?
- Do the line items match what was agreed?
- Do the totals add up, including tax and deposits?
- Is the due date correct, and are payment details complete?
- Does it include any reference the client needs, such as a purchase order?
Then send it as a PDF or from your invoicing tool, to the billing contact, not only to the project lead. If it is not paid by the due date, follow a set sequence of reminders, such as the one in how to chase late invoices without damaging the relationship.
HireOrSell includes invoices and expense tracking among its financial features. Check the product pages for current details.
Next step
Open the last invoice you sent and tick it off against the three lists above. Note what was missing, add those fields to your template, and send the next invoice from the updated version.
Keep reading
- Expense tracking for agencies: simple categories and a monthly reviewTen starter expense categories, a 30-minute monthly review checklist and a worked subscription audit, so you see where money goes before it becomes a surprise.
- How to find out which clients and projects are really profitableRevenue is not profit. A four-step method to allocate labour, direct costs and overhead to each client, with a three-client example computed line by line.
- How to invoice from milestones and get paid fasterTie each invoice to a milestone you can verify, size the instalments from the project fee, and send the invoice the day the milestone is accepted.
In HireOrSell
Ready to run it all in one place?
Projects, clients, time tracking and invoicing in one platform.