Invoice admin
Invoice description examples: make the work easy to identify
A useful invoice description names the agreed service or deliverable and adds the job, date or service period needed to identify it. Include a quantity or milestone when it explains the charge. Replace vague labels such as “services” with facts the customer can match to the agreement, without adding work you did not perform.
By PayerPing · Published
Write for the person checking the charge
An accounts contact may never have seen the work. “As discussed” makes them search a separate conversation. “Content review of six agreed website pages, quote Q-18, completed 3 November 2026” gives them a recognisable item to send to the approver.
GOV.UK lists a clear description of what you are charging for among invoice requirements. The examples here improve that description; they are not complete invoice templates or a check of every requirement applying to your business.
Use the customer's established project name or reference where helpful. Avoid unexplained internal abbreviations, confidential details or claims of approval that your records do not support.
Six fictional before-and-after descriptions
| Vague description | Clearer description | What it clarifies |
|---|---|---|
| Consulting | Website content review: six pages listed in Q-18, completed 3 November 2026 | Deliverable and agreed extent |
| Maintenance | North Street office: scheduled heating inspection on 4 November 2026, job J-52 | Site, visit and job |
| Monthly support | Website support, 1–30 November 2026, monthly service agreed in Q-22 | Service period and agreement |
| Design stage 2 | Project Alder: second-stage packaging artwork delivered 5 November 2026, scope S-14 | Which stage and output |
| Training | Two agreed remote training sessions, 2 and 4 November 2026, booking B-31 | Quantity and session dates |
| Extra work | Three additional product pages under change request CR-7, confirmed 29 October 2026 | Specific addition and its authority |
These descriptions assume the underlying records support every statement. “Delivered” describes an event; it does not automatically mean the customer accepted the work. A change reference is useful only if that change was actually agreed.
Use a short pattern, then remove what does not help
[Agreed service or deliverable] — [project / site / job reference] [Relevant date or service period] [Quantity / milestone / scope reference, if it explains the charge] CHECK AGAINST THE RECORD Can the customer identify the work? Does the quantity match the charged line? Does the period overlap any earlier invoice? Is any claim of delivery or approval supported? Have I removed internal shorthand and unrelated personal information?
You do not need every element on every line. A single inspection may need a date and site; a monthly service may need a period; a fixed deliverable may need its scope reference. Keep rates, quantities and totals consistent with the actual invoice layout instead of hiding a different price inside descriptive text.
If the invoice is already issued, clarify the exact line
If a customer cannot identify “support”, ask what they need to match it. A useful answer might be: “Line 1 covers the website support period 1–31 October 2026 under Q-22; the November period is not included.” Check that against the agreement and earlier invoices before replying.
Use the invoice query response template when a customer questions a description. If the document itself needs correcting, follow the correction workflow and preserve the version history. Finish by checking the other invoice fields with the invoice details checklist.
Sources and further reading
Keep reading
- Correcting an invoice before sending another follow-up
- Invoice query response template: clarify the issue before chasing
- Invoice details checklist: remove payment admin blockers