← All guides · How-to & workflow
Invoice line items: how to write lines that validate and get approved
By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026
Convert an invoice free
Put this guide into practice now: convert one invoice free — validated UBL 2.1 XML plus a Factur-X PDF, with the acceptance checker for your client’s country. See pricing for bulk conversion, country rule packs and monitored clients.
Short answer
Write lines like data, because they are: one line per distinct item; one VAT category and rate per line (never blended); a name that states what was supplied ('Brand identity design', not 'Services'); a positive quantity in a real unit (days, hours, units — or 1 for a lump sum); and a non-negative net unit price. Lines written this way validate cleanly, produce a correct tax breakdown, and can be approved by your client's reader without a single email.
What makes a good invoice line?
A good line satisfies the line-level rules and the human reader at once. The rules (per line): item name present (BT-153), quantity greater than zero (BT-129), net price not negative (BT-146), VAT category valid (BT-151) and rate in agreement with the category (BT-152). The reader's test is stricter: the client's approver, who did not sit in your project meetings, must be able to approve the line from its text alone.
One line per item, one treatment per line
The two splitting rules do different work. One line per item serves the reader and the record: each thing supplied is visible, priced and approvable separately, and partial credits later can mirror individual lines exactly. One treatment per line serves the arithmetic: the tax breakdown groups by category and rate, so a line straddling two treatments corrupts its group whichever way it is coded. When an engagement mixes taxed and reverse-charge elements — or two rates — the split is not optional decoration; it is the only truthful representation.
Splitting costs seconds and buys three things: validation passes on structure, the client's booking is automatic per group, and disputes localise to a line instead of poisoning an invoice. The invoice that says 'Project work — EUR 9,000' in one line outsources its explanation to a future email thread; the invoice with six lines never needs the thread.
Names that carry the scope
A line name is a tiny contract summary. Include the deliverable and, where it helps, the period or unit basis: 'Manuscript translation, 12,000 words', 'Support retainer — October 2026', 'Integration consulting, 4 days'. Avoid internal codes unaccompanied by words, project nicknames the client never used, and the empty universals — 'Services', 'Work', 'Consulting' — that force the approver to reconstruct the engagement from memory or from your proposal.
Remember the approver's position: often not your day-to-day contact but their manager or finance colleague, approving a batch of invoices against budgets. A name that matches the purchase order's language, the contract's deliverable or the client's own project title is approved in the flow of work. A name that matches nothing becomes a query — and queries, not amounts, are what delay payments in practice.
Quantities and prices that mean something
Quantity times unit price is the line extension, so both factors should be real. Bill time as days or hours with the rate as the unit price; bill deliverables as units; bill a fixed-fee engagement as quantity 1 at the fee, with the scope carried by the name. Invented decompositions — quantity 1,000 at a fractional rate to reach a round sum — make the line unreproducible for anyone re-deriving it, and the BR-CO world re-derives everything.
Keep prices net and at two-decimal precision, with VAT expressed only through the category and rate. 'Price including VAT' lines smuggle a computation into a field and guarantee a mismatch between your gross thinking and the model's net arithmetic. If your commercial quote was gross, convert it to net before it becomes a line — the invoice is a net document with tax applied by rule, and every figure on it must be able to survive that reading.
Ordering and grouping on the page
Lines are read in order by humans and grouped by tax treatment by machines; serve both. A natural order — chronological for time-based work, deliverable order for projects, materials after labour or before, consistently — lets the approver follow the engagement's story. Tax grouping happens in the breakdown regardless of line order, so you never need to sort lines by category for the machine's sake; sort them for the reader's sake instead.
Consistency across invoices compounds: a client who sees the same line structure monthly learns to approve you quickly. Templates should therefore fix not just fields but line habits — the naming pattern, the unit choices, the ordering convention — so every invoice from you reads like the last one. Familiarity is a payment accelerator no one has to pay for.
Lines and the rest of the document
Lines interact with every other field. Allowances belong to specific lines or to the document — not smeared across line prices. Credit notes mirror lines exactly, so today's lines are tomorrow's credit vocabulary: a mushy line can only be credited mushily. The tax breakdown is the lines, restated by group — if the breakdown surprises you, a line is miscoded, and the breakdown is doing you the favour of showing it before the client does.
Finally, lines are where value is proven. The total asks for money; the lines justify it. In the structured era the justification is data — parsed, grouped, booked — but it is still read by the person who releases payment. Write lines that make that person certain, and the invoice's other virtues (valid, structured, on time) get the chance to matter.
Line-writing discipline in 5 steps
- Split: one line per item, and one VAT treatment per line — never blend categories or rates inside a line.
- Name the deliverable in the client's language: what it is, plus period or basis where that aids approval.
- Use real quantities and units (days, hours, units, or 1 for a lump sum) with the true net unit price.
- Keep prices net at two decimals; express tax only via category and rate, never 'included' inside a price.
- Keep the pattern identical every month — same naming, units and ordering — so approvers learn your invoices.
Worked example: one line becomes four, and approval speeds up
Before: a single line, 'Consulting — EUR 7,300.00', quantity 1, category AE. It validates — and stalls in approval for nine days while the client's manager asks what it covers. After: four lines — 'Discovery workshops, 2 days' at EUR 900.00; 'Integration build, 4 days' at EUR 950.00; 'Documentation pack' at EUR 700.00; 'Go-live support, 1 day' at EUR 1,000.00 — each quantity-bearing, each AE at 0%, totalling the same EUR 7,300.00.
Same money, same validity, different fate: the second invoice is approved on first reading because its lines answer the approver's questions before they are asked. Line craft is not formatting fussiness — it is the difference between an invoice that requests payment and one that explains itself into being paid.
Frequently asked questions
How many lines should an invoice have?
As many as the supply has distinct items and treatments — no more, no fewer. One line per item and per VAT treatment is the rule; padding and merging both harm you.
Can a line have quantity 0 or a negative price?
No — validation requires quantity above zero (BT-129) and a non-negative net price (BT-146). Credits and discounts have their own mechanisms: credit notes (381) and allowance fields.
Should line names include dates or periods?
Where the supply is time-based or recurring, yes — 'Support retainer — October 2026' approves faster than 'Support retainer' because it matches the client's records without a lookup.
Do lines need to be sorted by VAT category?
No — the tax breakdown groups them computationally. Order lines for the human reader: chronologically or by deliverable.
What unit should a fixed-fee engagement use?
Quantity 1 at the agreed fee, with the scope in the line name. The extension is then exactly the fee, reproducible by any system.
Keep going
Run the free tool this guide is about: convert an invoice · acceptance checker · pricing · about EInvoice Translator · all guides
Related guides
- Structured invoice fields: every field an EN 16931 invoice needs, checked
- VAT categories explained: S, Z, E, AE, K, G and O on an e-invoice line
- Invoice totals and the BR-CO rules: how e-invoice arithmetic must reconcile
- How to issue a credit note as an e-invoice (type code 381)
- Do structured e-invoices get paid faster? The mechanisms, honestly stated