Revenue leakage from manual administration

Revenue leakage from manual administration happens at every step where a person transfers data from one system or piece of paper to another. A job sheet that never gets handed in, extra work agreed over WhatsApp, an order retyped by hand into the accounting package: every handover is a place where a line can vanish or an amount can change. The answer is not necessarily to automate everything, but to reduce the number of manual handovers and to reconcile the ones that remain.

Why does manual work leak?

People make mistakes, but that is not the main problem. The main problem is that a manual step leaves no trace when it does not happen. A system that forgets an invoice can often be traced through a log. An engineer who leaves a job sheet in the van leaves nothing behind. The invoice is never created, and nobody knows it should have existed.

That makes manual administration a particular kind of revenue leakage. The leak is not in the error, but in the absence. An error sometimes stands out. Something missing only stands out if you know what should have been there.

Where does it go wrong in practice?

Job sheets and timesheets. The engineer fills in a job sheet on paper or in an app. It has to reach the office, be checked and be turned into an invoice line. At every step it can get stuck. A job sheet that has not been invoiced after three weeks often never is: the work is done, the customer no longer expects an invoice, and nobody remembers the details.

Extra work outside the system. The project manager agrees with the customer on site that an extra wall will be put up or an extra integration will be built. That happens in a conversation, by phone or over WhatsApp. The work is carried out. But unless someone records the extra work in the system used for invoicing, it does not appear on the final account.

Retyping from order to invoice. The order is in the CRM or a quoting tool. The invoice is created in Exact, AFAS, Xero or SAP. Between the two sits a person retyping the lines. A quantity of 12 becomes 1.2. A 5 percent discount becomes 15. A line is skipped because the screen had to scroll. The pattern of revenue leakage between CRM and billing often starts right here.

Spreadsheets as a staging post. Many companies have a spreadsheet sitting between two systems: an export from time tracking, edited and then imported into billing. Formulas get overwritten, rows shift, filters stay switched on. A filter accidentally left on can drop an entire customer from an invoice run.

Dependence on one person. The monthly invoicing is done by one employee who knows which customers have a different arrangement. When that person is on holiday, falls ill or leaves, that knowledge goes with them. A colleague who takes over invoices what is in the system, not what was in someone's head.

Exceptions that were never recorded. "We don't charge this customer a call-out fee." "This customer gets the report for free." As long as this is a verbal arrangement, nobody knows whether it still applies, whether it was ever agreed, or whether it has simply become a habit.

Worked example

Worked example: suppose an installation company with 25 engineers completes around 12,000 job sheets a year, with an average invoice value of EUR 380. A sample shows:

• 1.5 percent of job sheets were never invoiced: 180 sheets × EUR 380 = EUR 68,400.
• On 4 percent of the invoiced sheets, materials that were used are missing, on average EUR 45: 473 sheets × EUR 45 = EUR 21,285.
• Extra work agreed on site goes uninvoiced in one case in five. With 300 extra-work agreements a year averaging EUR 600, that is 60 × EUR 600 = EUR 36,000.

Together more than EUR 125,000 a year. These are illustrative percentages to show the calculation, not averages. The point is that a small percentage of a large number of transactions quickly adds up to an amount that could pay for a full-time employee.

What else does it cost?

Manual administration does not only cost the revenue that leaks away. It also costs time to correct, issue credit notes and explain to customers why an invoice was wrong. It slows invoicing, which lengthens the time to payment. And it makes every analysis unreliable, because the data itself is wrong. That last point is a category of its own, which we describe in revenue leakage from data problems.

Why "automate everything" is not the answer

The reflex is to replace every manual step with an integration. Sometimes that is sensible. But not every step can be automated, and a poorly built integration can make errors at a larger scale than a person. An import script that maps a field wrongly does so on every invoice.

A different order works better:

1. Map the handovers. Where does information move from one medium to another? From paper to system, from system to spreadsheet, from spreadsheet to system.
2. Remove handovers that are not needed. A job sheet filled in digitally that lands directly in the billing system no longer has a handover.
3. Automate handovers that are always the same. An order marked as won in the CRM can automatically create a draft invoice.
4. Reconcile the handovers that stay manual. Every manual step needs a closing check: what goes in must come out.

That last step is the most important and the one most often skipped.

Which three checks recover the most?

If you want to start tomorrow, these are the three checks that bring money back fastest in practice.

1. Unbroken numbering of job sheets and orders. Every job sheet or order has a unique number. Each month you check that every number has either been invoiced or has a recorded reason for not being invoiced. A number with no invoice and no reason is a leak.

2. Hours against invoicing. For each customer or project, add up the billable hours booked and compare them with the hours invoiced. Investigate differences above a threshold.

3. Materials issued from stock against materials on the invoice. What was booked out to a project or job sheet, and what is on the invoice? For companies with a lot of stock in vans or on site, this is often the largest item.

Checklist for your invoicing process

• Is every arrangement with a customer recorded in one place that invoicing uses?
• Is there a closing check for each source (job sheet, order, hours, extra work)?
• Could someone other than the regular employee do the invoicing without errors?
• Are customer-specific exceptions recorded, with a reason and an end date?
• Is extra work recorded before it is carried out, not afterwards?
• Is there a deadline by which a job sheet must be invoiced, and is it monitored?
• Are spreadsheet staging steps protected against overwritten formulas and active filters?

Frequently asked questions

Is manual administration always bad?

No. Manual work is fine as long as there is a check behind it showing that everything that went in also came out. The problem is not the person, but the missing check.

Where do I start if I do not know where it leaks?

Start with the source that has the highest volume and the most manual steps. For an installation or service company that is usually job sheets. For a professional services firm, hours. For a wholesaler, orders that are retyped by hand.

How large is this leak on average?

There is no reliable average. It depends on the number of manual handovers, the volume and whether checks are in place. A sample of a few hundred job sheets or orders gives you your own estimate within a day, and that tells you more than any average.

Do I need to buy a new system first?

Usually not. Most leaks caused by manual work can be found with the systems you already have and an export to a spreadsheet. A new system only helps once you know which handovers you want to replace.