An invoice has one job and most of it is being easy to pay

A request that has to survive somebody else’s process

An invoice looks like a simple statement of what is owed. On the client side it enters a process — it is received, checked against something, approved, scheduled, paid — and at every one of those stages it can stop.

Most late payment that’s not deliberate happens because the invoice failed one of those steps. It went to the wrong address, lacked a reference the system requires, arrived after a cut-off, or described the work in terms nobody could match to an order. The supplier experiences this as a client who pays slowly. The client experiences it as an invoice that never properly arrived.

What has to be on it

The specific requirements differ by country and by what taxes apply to you, and where consumption taxes are involved the rules about wording, numbering and detail can be strict. That is a question for an accountant where you are, and getting it wrong can create problems for your client as well as for you.

Beyond the local requirements, the practical content is consistent: who is billing, who is being billed, a unique number, the date, a clear description of what was done, the amount, the due date stated as an actual date, and how to pay. Sequential numbering matters more than it appears, because it is what makes the records checkable and it’s required in many systems.

A due date written as a date rather than as a period removes an entire class of ambiguity. Terms expressed in days invite a calculation, and calculations are where disagreements about lateness begin.

Send it to the right place, immediately

Two habits recover more days than anything else. Invoice as soon as the work is complete rather than at the end of the month, because a delay in issuing is a self-inflicted delay in payment. And send it to whoever actually processes payments, not only to the person who commissioned the work.

In organisations of any size those are different people with different systems, and an invoice sitting in a project manager’s inbox is not late, it is lost. Asking at the start where invoices should go and what reference they need takes one sentence and prevents weeks of delay later.

Where a purchase order or job number is required, put it exactly where they asked for it. This is the single most common reason an invoice is rejected by an accounts system, and it’s entirely avoidable.

Remove every obstacle to paying

Each step between deciding to pay and the money moving is somewhere the process can stall. Bank details missing from the document, an unclear amount, an attachment that will not open, a payment method the client cannot use.

Offering more than one way to pay helps, though it is worth understanding what each costs you, since some methods take a percentage that turns out to be meaningful on larger sums. What matters is that the client can complete the payment at the moment they decide to, without having to ask you anything.

Making the amount unambiguous matters too. Where taxes apply, showing the components and the total clearly avoids the query that delays approval by a week.

Keep your own side in order

Record what was issued and, separately, what was actually paid and when. The gap between those two figures is your outstanding position, and knowing it at any moment is what makes chasing timely rather than reactive.

The record of payment dates has a second use. Over time it tells you which clients pay promptly and which don’t, which is information worth having when quoting for their next job or deciding whose work to prioritise.

Credit notes and corrections

Mistakes happen, and the temptation is to delete the wrong invoice and issue a new one. In many systems that is not acceptable, because the numbering has to be continuous and records cannot simply disappear.

The usual correct route is a credit note that cancels the original, followed by a fresh invoice. The exact requirement varies by country, so it is worth asking your accountant once and then doing it the same way every time. It takes slightly longer than deleting something and it keeps the records defensible, which is the entire purpose of keeping them.

All of which argues for building one template and then leaving it alone. Once the layout carries the required details, the numbering runs in sequence and the payment information is correct, issuing an invoice becomes a two-minute task with nothing to think about. That matters more than it sounds, because the invoice is the one piece of administration that has to happen after every single job, and anything that has to happen fifty times a year should cost as little attention as possible.