From ticket to invoice without a break in the chain

What a break in the chain actually costs

A break is any point where data leaves one system and is entered again in another - by export, by copy and paste or from memory. The obvious price is time. The more expensive one is that something is lost at every handover: a line, an extra, an hour.

What makes it particularly unpleasant is that the loss does not stand out. No invoice is missing - it is merely too low. If you want to know how big the effect is in your own business, compare recorded time with billed time for one month. The difference is rarely zero.

The four typical breaks

• Between ticket and time tracking: time is written up in the evening from memory. Anything more than a day old is systematically underestimated - never overestimated.
• Between time and contract: the hour is recorded, but nobody knows whether it falls under the quota or is billable. In doubt it is not billed, because clarifying takes longer than the amount is worth.
• Between work and document: material from stock, travel time, a service report on paper - three sources somebody has to assemble for the invoice. Whatever they do not find does not appear on it.
• Between invoice and payment: the invoice has gone out, but the payment lands in accounting, not on the job. Whether the job worked out commercially, nobody ends up knowing.

The bracket is the order, not the document

The most effective lever is a shared bracket across every document. When the quote, delivery note, service report and invoice for one job all carry the same order number, one place shows what was quoted, delivered and billed - and what is still open.

Without that bracket you get documents that are individually correct and collectively incomplete. With it, the question did we actually bill that becomes a view instead of a search.

Time has to arise where the work happens

Time tracking that lives in a second application gets done afterwards - and afterwards means estimated. Recorded on the ticket itself, it assigns itself to the right customer and contract, and the decision billable or not is made immediately, with what you know in the moment.

The same applies more sharply to on-site work: whatever is not signed at the customer gets discussed later. A service report that already carries the recorded time and the material used and is signed on site leaves the later invoice nothing to argue about.

Recurring work should be automated, not disciplined

Part of the loss comes not from individual work but from recurring items: maintenance retainers, licences, rentals. Individually small and substantial in total, and tied to no action that reminds anyone - which is why they get forgotten.

Whatever is billed the same way regularly should therefore arise automatically from a contract rather than depending on somebody remembering at the start of the month. Human discipline is the most expensive form of scheduling.

How to recognise an unbroken chain

• A document can be produced from a ticket without re-entering anything
• Recorded time is assigned to a contract automatically and marked billable
• Every document in a case carries the same order number
• The payment shows up on the document, not only on the account
• At month end there is a list of work delivered but not billed - and it is short
• Nobody has to open a second application to write the invoice

The pragmatic route

A chain cannot be closed in one step, and trying usually ends in a project nobody finishes. It is more practical to close the most expensive break first - for most businesses that is the stretch between recorded time and invoice, because revenue hangs on it directly.

Only then is it worth looking at stock, purchasing and payment matching. Starting the other way round optimises processes whose output still travels into billing by hand.