How to Write Invoice Line Item Descriptions
Vague lines delay payment. Learning how to write invoice line item descriptions is the cheapest way to cut "what is this for?" emails. A good description names the work, the quantity and enough context that someone who was not in the meeting can approve the bill. This guide gives patterns you can reuse.
Use a Noun, a Scope and a Boundary
Start with what was delivered, then limit it. "Website work" is weak. "Homepage layout, desktop and mobile, two revision rounds" is strong. "Consulting" is weak. "Discovery workshop, 18 June, half day" is strong. If you billed hours, add the date range. If you billed a package, add what the package included.
Put optional detail in a second sentence on the same line if your tool allows a longer description. Our invoice form uses a description field that can hold more than one line, so you can add the extra context without a second row.
| Weak | Stronger |
|---|---|
| Design | Logo concepts, 3 options, plus final files |
| Hours | Development, 8–11 May, 6.5 hours |
| Retainer | June marketing retainer, 8 hours included |
| Expenses | Stock photos for homepage, 4 images |
Match the Quote
If the proposal said "Phase 2 — checkout flow", the invoice should say that too. Matching language is how accounts teams tick a box. For the rest of the document, see what to include in an invoice and the pre-send checklist.
Tip: Read the line as if you were a new accounts clerk. If you would have to ask a colleague what it means, rewrite it.
Do Not Write a Novel
One or two short sentences per line is enough. Keep the contract, the Slack thread and the file list elsewhere. The invoice is the summary, not the archive.
A line item is a label for money. Make the label specific enough that the money looks earned.
Frequently Asked Questions
Should I list every task in a sprint?
Group them. "Sprint 14 development, 10–14 March, 16 hours" plus a short note is clearer than 20 tiny rows.
Can I use codes or SKUs?
Yes, if the client asked for them. Put the human description first, then the code.
What about confidential work?
Use a project code you both already share, and keep sensitive detail off the PDF if the client requested that.
Rewrite the vague line, then bill it. Create a free invoice with clear descriptions.