Counting the Cost of the In-Tray: A Capture Business Case That Holds Up

Begin with the work, not the wish list

Many capture proposals fail before the first question is asked because they begin with equipment. Finance sees another scanner, another licence and another implementation project. The case may be sound, but the framing invites a simple response: not this year.

A stronger proposal starts with a process that is already costing money. It identifies where paper enters the business, how many times each document is touched, who waits for it and what happens when it cannot be found. The question is not which device to buy. It is which work can be removed.

That distinction matters in 2026 because many UK SMEs already have more capture hardware than they use. Multifunction devices sit on office floors, phones take usable images, and managed print estates often include scanning functions that have never been configured for workflow. The missing ingredient is usually process design, not another box with a lid.

Quantify the invisible in-tray

Paper handling is distributed across the business, which is why it is rarely measured. A few minutes here and a short walk there do not appear on any budget line. Add them together and the cost becomes visible.

Use a simple time study rather than a grand survey. Pick one document type, such as supplier invoices or client onboarding forms. Count the documents received in a typical week. Ask the people who handle them to estimate each touch: opening post, sorting, date-stamping, routing, copying, filing, retrieving, re-filing. Use a fully loaded hourly cost that includes employer National Insurance and pension contributions, not just salary.

An illustrative calculation makes the point. If 40 staff each handle 15 paper documents a day and each document takes three minutes across its life, that is 1,800 minutes a day, or 30 hours. At a loaded cost of £22 an hour, the annual figure runs to six figures before storage, errors or delays are counted. The number will not all be removable, and the proposal should say so. Presenting a range is more credible than claiming every minute will be saved.

The rekeying tax

Manual rekeying is the quiet cost that finance teams recognise immediately. A paper invoice is read by a person and typed into the finance system. A paper form is read and typed into the CRM. A paper timesheet is read and typed into payroll. Each transfer creates an opportunity for error and a second transfer to correct it.

Measure a sample. Take 100 documents and count how many require correction after entry. Estimate the time spent correcting them, including supervisor review and supplier or customer correspondence. Add the cost of credit notes, duplicate payments or delayed approvals where they can be evidenced. Do not assume a perfect error rate. Use the organisation's own sample.

Capture with recognition and validation does not eliminate every error, but it changes the work. Fields can be checked at the point of capture. Exceptions can be routed to a person. The business case should show the reduction in rekeying and correction time, not just the speed of scanning.

Missed records and the cost of delay

A missing purchase invoice is not merely a filing problem. It becomes a phone call, a delayed payment, a supplier query and sometimes a duplicate payment. A missing client file becomes a slow response, a compliance question or a lost billable hour. A missing VAT receipt becomes an afternoon of reconstruction.

UK records underpin tax returns, payroll, audit, insurance claims and due diligence. The business case does not need to exaggerate penalties. It needs to describe the ordinary cost of delay: the person who stops work to search, the customer who waits, the query that escalates. Where possible, record retrieval times before and after a pilot. A service-level measure is often more persuasive than a risk warning.

Frame savings in finance's language

Finance teams trust models that show their workings. Separate cashable savings from operational benefits. Cashable savings might include reduced offsite storage, less overtime, fewer temporary staff or avoided duplicate payments. Operational benefits might include faster retrieval, better resilience and less time spent searching. Both matter, but they should not be blended into one optimistic figure.

Build three scenarios: conservative, central and optimistic. State the assumptions behind each. Include software, implementation, training, support and internal staff time. Show payback in months and the sensitivity of the case. If document volumes fall by 20%, does the proposal still work? If OCR accuracy is lower than expected, what is the effect? A capture business case is a small financial model, not a brochure.

A pilot that produces evidence

A budget meeting is easier when the argument has already been tested. Choose one workflow with high volume and a clear metric. Run a six to eight week pilot using existing equipment where possible. Measure documents processed per hour, retrieval time, exception rates and rekeying corrections before and after. Define success criteria in advance and agree what would cause the project to stop.

This discipline does two things. It produces evidence for the next budget round, and it protects the organisation from a large commitment based on a demonstration. A modest pilot is often the most finance-friendly request in the room.

What to leave out

Avoid claims about the paperless office unless the term is defined. Avoid a long hardware specification in a business case. Avoid counting time savings as cash unless a budget line will actually change. Do not ignore retention, data protection or accessibility, because those requirements will return later as unbudgeted work.

The strongest proposal asks for a bounded decision: approval for a pilot, a software subscription and a process redesign, not permission to buy another scanner. It shows the cost of the current in-tray and the evidence that a different workflow can reduce it. That is a case a sceptical budget review can accept.