How to Create an Invoice for Products and Services

One invoice, two species of line

Physical goods and performed services share a column structure — description, quantity, rate — but the meaning of those columns diverges. A quantity of 12 could be boxes on a pallet or hours on a timesheet, and the client's expectation of what the number covers changes completely with the answer.

The invoice's job is to make the species obvious at a glance: what was supplied, counted in the right units, priced so the arithmetic can be checked. The 12-point invoice checklist covers the fields themselves; this guide is about the two species of line that live inside them.

Line items that answer questions before they are asked

The last row is the quiet one: whenever a reader can multiply quantity by rate and arrive at the amount, the line has done its job. When they cannot, a query starts forming whether or not it is ever typed.

Units and quantities prevent most disputes

The word "unit" sounds bureaucratic until you have watched two reasonable people disagree about what "one" meant. An invoice line for "1 project" cannot be checked by anyone; a line for "12 hours" can be checked against a timesheet; a line for "1 print run" should say what a print run contains.

The editor gives every line a unit field precisely for this — hours, pages, boxes, visits, kilometres — and it prints under the quantity where the client can see the measure. Pick a unit for every line before you pick a price for any of them.

Itemise or bundle? The honest test

• Itemise when the client is comparing. If a quote, a catalogue or a competitor's breakdown exists, matching lines make your invoice easy to accept rather than easy to debate.
• Bundle when the client bought an outcome. A fixed-fee landing page does not become clearer because it is split into design minutes and typing minutes — it becomes arguable.
• Never bundle what has already been questioned. Once a client asks about a component, its cost is a live question; hiding it inside a package reads as evasion even when the total is fair.

Worked example: one invoice, both kinds

A garden service — not registered for VAT, so the invoice carries no tax line — bills a client after a full day. The same document contains counted goods, measured labour and one fixed-scope service:

Each line sums itself: twelve hours at R180, six bags at R95, and a fixed job at a price the client approved in the quote. Nobody has to phone anyone to know what the R3,580 bought.

Using a catalogue so the typing never repeats

Repeat business should not mean retyping the same lines. Save recurring items — a standard bag of compost, a retainer hour, a print run — in the products catalogue, and adding one to an invoice copies it onto the line, where it stays editable for that document only. Update the catalogue entry later and past invoices are untouched; retire an item and it stops being offered.

Stock, shipping and the awkward extras

Charges that surround the goods deserve their own lines, or an explicit statement that they are already inside the price. Delivery is the classic case: a client who returns part of an order will expect a proportional answer, and the honest one is easier to give when the shipping was never smuggled into the item rate. If delivery is free, say so in words — "included" is a term, and terms are what the document is for.

Returns are where these choices get tested. A partial return is easiest to settle when the item, its unit and its delivery charge were shown separately, because each can be credited line by line; an all-in price forces both sides to invent a fair split after the fact, which is a negotiation nobody wanted.

Frequently asked questions