How long should a line description be?

Long enough to identify the deliverable, the scope, and the period — usually six to twelve words. Beyond that you are writing a memo, not an invoice line.

Should I add notes for context the buyer already knows?

Only if a different reader (accounts payable, an auditor, a future colleague) might not. Useful context belongs on the invoice; conversational reminders belong in the email.

Is it OK to write the term as 'Net 30' if the buyer asked for it?

Use both: the term and the date. 'Net 30 — due 15 April 2025'. The term satisfies the buyer's process; the date removes ambiguity for whoever pays it.

Should I include 'Thank you' on every invoice?

It is a small, calm touch that costs nothing and changes the tone. One short line at the bottom is enough; a paragraph is too much.

Guide

How to avoid confusing invoice wording

Most slow invoices are not slow because of pricing or relationships — they are slow because the wording forces the reader to interpret. Every interpretation is a delay. This guide collects the specific wording fixes that consistently remove ambiguity from line items, notes, and payment terms.

Invoicing 6 min readUpdated Dec 15, 2025

SMBHelper editorial teamLast updated Dec 15, 2025Reviewed for clarityEditorial standards

Replace categories with deliverables

Single-word categories — 'Consulting', 'Design', 'Marketing', 'Services' — are the most-disputed line items in B2B invoicing. The buyer's accounts team cannot match them to a purchase order, the project lead cannot remember what they refer to, and the invoice goes into a queue.

Replace each category with a specific deliverable. 'Brand identity design — logo and type system (Phase 1 of 2)' takes ten extra seconds to write and removes the most common reason for slow payment.

Use the buyer's language

If the buyer issued a purchase order with a name for the work, use that name on the invoice. If the contract calls a deliverable 'Phase 1 — Discovery', the invoice should say 'Phase 1 — Discovery' — not 'Initial work' or your internal project code.

Accounts payable match by exact wording first, then by amount. Aligning your wording to theirs removes a step.

Make dates and periods explicit

On hourly or retainer work, always include the period: 'Marketing strategy support — March 2025 (8 hours @ £225/hr)' rather than 'Marketing — March'. The buyer can place the work in time and verify the math without asking.

On payment terms, convert all relative dates to absolute ones: 'Due 15 April 2025' instead of 'Net 30'. Different buyers count days differently.

Specify currency, even when it seems obvious

Write 'Total: £2,880.00 GBP', not just '£2,880.00'. The currency suffix prevents ambiguity on cross-border invoices and protects you when a buyer's accounting system stores amounts without symbols.

If the line items are in a different currency from your home, name both currencies explicitly and disclose the exchange method or rate used.

Worked example

Before, one line: 'Consulting services, March 2025, £4,800.00'. Notes: 'Net 30 from invoice date'. The buyer's accounts team has no PO match, no deliverable list, and a relative term. They send it back with questions. Net effect: 11 days lost.

After, three lines: 'Marketing strategy workshop — 6 March 2025 (1 day on-site), £1,800.00'; 'Strategy support sessions — March 2025 (8 hours @ £225/hr), £1,800.00'; 'Q1 strategy memo — final draft, 28 March 2025, £1,200.00'. Notes: 'Due 15 April 2025. Thank you.' Same total. Approved on the first pass.

Common confusing phrases and the fix

These are wording patterns we see slow invoices most often:

'Services rendered' → name the service and the period.
'Per agreement' → reference the agreement by name or date the buyer can find.
'See attached' → attach in the same email and repeat the total in the email body.
'Subject to terms' → reference the terms document name; do not bury terms in a long footer.
'TBC' or '~' on amounts → never on a final invoice; if uncertain, issue a pro forma instead.
'Various' as a line description → list the specific deliverables, even if there are several.

Frequently asked questions

How long should a line description be?: Long enough to identify the deliverable, the scope, and the period — usually six to twelve words. Beyond that you are writing a memo, not an invoice line.
Should I add notes for context the buyer already knows?: Only if a different reader (accounts payable, an auditor, a future colleague) might not. Useful context belongs on the invoice; conversational reminders belong in the email.
Is it OK to write the term as 'Net 30' if the buyer asked for it?: Use both: the term and the date. 'Net 30 — due 15 April 2025'. The term satisfies the buyer's process; the date removes ambiguity for whoever pays it.
Should I include 'Thank you' on every invoice?: It is a small, calm touch that costs nothing and changes the tone. One short line at the bottom is enough; a paragraph is too much.

Related tools

Invoice Generator
Create professional invoices with built-in completeness checks.

How to avoid confusing invoice wording

Replace categories with deliverables

Use the buyer's language

Make dates and periods explicit

Specify currency, even when it seems obvious

Worked example

Common confusing phrases and the fix

Frequently asked questions

How to write better invoice descriptions

What to put on an invoice

How to make invoices easier to pay

How to structure an invoice

Invoice fields explained

Invoice

Invoice due date

Payment terms

Outstanding invoice

Net amount

Invoice template guide