How to create and manage client invoices

There are two quite different things people mean by "managing invoices". One is the statutory version — tax treatment, registration numbers, sequential numbering, legal retention. The other is the practical version: producing a clear document that says what is owed, and keeping it consistent with what you are actually tracking.

This article is about the second. If your business needs the first, use software built for it — and be wary of any tool that implies it handles compliance without saying which rules it implements.

What an invoice actually needs

A working invoice answers five questions without the reader having to think:

1. Who is asking? Your name or business name, address and a contact number.
2. Who is being asked? The client name, and where they are based if it is relevant.
3. For what? A description of the work specific enough to be recognised — the reference you already use on that engagement.
4. How much? The agreed fee, anything already received, and the balance now due. All three, not just the last one.
5. As of when? A date, so a later version is distinguishable from an earlier one.

The third figure — what has already been received — is the one most often left off, and the one that prevents the most confusion. An invoice showing only a balance invites the question "is this the whole fee or what is left?", and that question costs a round trip.

When to send one

Not every payment needs an invoice, and producing one for each instalment creates work without adding clarity. The moments that genuinely warrant one:

• On agreement, if you are taking an advance. The document justifies the request and sets the tone.
• On completion. This is the important one. It marks the work as finished, states the balance, and starts the payment terms.
• When the client asks. Some businesses cannot release a payment without a document to attach to it. Produce one when they need it rather than arguing about whether it is necessary.
• When a balance has been outstanding a while. A fresh invoice showing the current position is sometimes a more effective prompt than another message.

Between those points, a reminder is usually the better instrument — faster to send, easier to reply to, and less ceremony for what is often just an oversight.

Invoices and balances have to agree

This is where invoicing goes wrong in a small business. The invoice is created in one place — a word processor template, a design file, an invoicing app — and the payment record lives somewhere else. Each is maintained separately, and they drift.

The symptom is familiar: an invoice stating a balance that does not match what your spreadsheet says, discovered when a client points it out. Every instance of this costs credibility, because from the client's side it is indistinguishable from carelessness about their money.

The fix is structural, not procedural. Generate the invoice from the payment record rather than alongside it. If the document is composed from the same client file that holds the entries, the two cannot disagree — there is only one set of figures.

That is how invoices work in Umikflow: the page is assembled from your profile and the client record, so the agreed fee, the amount paid and the balance are the same three numbers the client file shows. There is no separate invoice to keep in step.

Advances and partial payments

Partial payment is the normal case for project work, and the invoice should reflect it rather than pretending otherwise.

The clearest treatment is a single running statement: the full agreed fee, the total received to date, and the balance. Each time you produce the document it reflects the current position. The client sees the whole arrangement at once, including the payments they have already made, which is both reassuring and harder to dispute.

The alternative — a separate invoice per instalment, each for a portion of the fee — is standard in larger organisations and requires more bookkeeping than it is worth at small scale. It only really pays off when someone else needs to match individual payments to individual documents.

Storing and sending

Send a PDF. Not a link that expires, not a word processor file the client can edit, and not a screenshot. A PDF opens on everything, prints correctly, and looks the same on their screen as on yours.

Keep a copy of anything you send. Even where the invoice can be regenerated from the record, the version the client actually received is the one that matters in a disagreement — and if the fee changed afterwards, a regenerated document will not match what they hold.

A filename containing the client name and the date saves more time than it seems to. "Invoice_PRIYA_MEHTA.pdf" is findable; "invoice(3).pdf" is not.

Know what your tool does not do

Invoicing is an area where software makes implied promises it should not. Be specific about what yours actually handles, and fill the gaps deliberately rather than assuming.

Umikflow can create tax-aware invoices with line items and rates you set, then print or download an A4 PDF. It does not file tax returns, process payments through the document, or keep a general ledger. Outstanding balances still live on the client file. That is stated on the invoice page. If you need books or returns, use software built for that part of the job.

What matters is that the document you send is correct, consistent with your records, and easy to act on. Everything else is a separate question.