What goes on an itemized receipt
Everything a plain receipt has — your business name and contact, the date, the payment method, the amount, and a receipt number — plus the part that makes it itemized:
The test of a good itemized receipt: someone who wasn't there can reconstruct the transaction from it. That's the whole feature.
- One line per item or service, described plainly: not "services rendered" but _"Replace kitchen faucet — labor"_.
- Quantity and unit price on each line, with the line total.
- Any discount as its own visible line, not silently absorbed.
- Tax shown as the amount charged, on its own line, if you charged it.
- The total — matching the payment — and the date and method it was paid.
Itemized receipt vs a regular receipt — and vs an invoice
A regular receipt proves _that_ a payment happened: who paid, whom, when, how much. An itemized receipt additionally proves _what for_. Same document family, different resolution.
The invoice comparison matters more than it seems: an invoice requests payment and lists what's owed; a receipt — itemized or not — confirms payment already made. One document cannot honestly be both, which is why "just mark the invoice paid" is the wrong answer to a customer asking for a receipt: the receipt's job is to say the money arrived, and it should say so in its own words, with its own date.
Itemized receipt example
A small repair shop, one visit, paid on the spot:
Receipt #R-0193 · Paid in full
Three lines instead of one, and the receipt now answers every question the payer's records will ever ask of it.
| Item | Qty | Price | Amount |
|---|---|---|---|
| Replace kitchen faucet — labor | 1.5 hr | 80.00 | 120.00 |
| Faucet cartridge (part) | 1 | 34.00 | 34.00 |
| Service call | 1 | 40.00 | 40.00 |
| Subtotal | 194.00 | ||
| Tax (if applicable) | — | ||
| Total before applicable tax | 194.00 |
Why customers ask for an itemized receipt
When a customer asks for "an itemized one", it's rarely fussiness — some system on their side won't accept a bare total:
None of this changes what you write — the receipt documents what actually happened, and one accurate version serves every purpose above. Issue it once, correctly, and the customer's paperwork problem is theirs to finish.
- Company records. A business paying you needs the line detail to post the cost to the right place; their bookkeeper, not the payer, is the real audience. An employee who paid you may also need the detail for an expense report — the itemized receipt you issue is simply the honest record of what they bought.
- Insurance and claims. Insurers reimburse specific items, not lump sums; a claim usually stands on the line detail.
- Health accounts. Some medical and health-account payments are only accepted with itemized documentation — the customer's administrator decides what qualifies, and your receipt just has to say truthfully what was provided.
- Warranty and disputes. A line naming the part and the date is what makes a warranty claim provable two years later.
When you don't need to itemize
The reverse rule is the one that matters: when a customer asks for itemization, the answer is yes. It costs a minute, it's their money traced to what it bought, and a business that resists writing down what it charged for invites exactly the suspicion it fears.
- Single-item payments. One thing, one price — the plain receipt already is itemized.
- Fixed-price packages sold as one unit. If the customer bought "the package", one line naming the package is the truthful level of detail; splitting an all-in price into invented internal prices is decoration, not accuracy.
- Deposits and part-payments. The receipt records the payment against the job ("Deposit received — kitchen remodel"); itemizing work not yet done would document things that haven't happened.
- When the invoice already did the work. If you issued a fully itemized invoice and were paid against it, the receipt can be short and reference it: _"Paid in full against invoice #214."_ The detail lives one document upstream.
Who uses the line-by-line detail
The payer may be only the first reader. A bookkeeper needs descriptions that map to the right expense, an employee needs enough detail to support a reimbursement request, and a customer may need the named part and purchase date for a return or warranty conversation. The same accurate receipt can serve those workflows without adding private information that was not part of the transaction.
If a third party has its own evidence rules, ask what fields it requires before promising that a generic receipt will qualify. The receipt should document the sale or service accurately; it should not guess what an insurer, employer, tax authority or benefit administrator will accept.
Australia: proof of transaction and itemised service bills
For Australian consumer transactions, Australian Consumer Law section 100 requires proof of transaction for goods or services valued at $75 or more and requires it within seven days when a consumer asks for proof of a transaction under $75. The ACCC consumer guidance explains the same receipt rules in practical terms.
For services, Australian Consumer Law section 101 allows a consumer to ask for an itemised bill within 30 days after receiving the original bill. The supplier must provide it within seven days, without charge. These are Australian requirements; they do not establish a universal $75 threshold or itemised-bill deadline for other countries.
Check the arithmetic before issuing the receipt
In the worked example above, the three line amounts are $120 + $34 + $40 = $194, so the subtotal and total before any applicable tax are $194. Recalculate the lines, subtotal, tax and total whenever a quantity, price or discount changes; the payment amount and the final receipt total should agree.