The most expensive leak that a business based in Birmingham is likely to experience, isn’t usually fraud.
UK Finance reports that card fraud as a proportion of card purchases was 6.9p per £100 in H1 2025 (0.069%). If your firm puts £100,000 a year through company cards, the “expected” loss at that rate is about £69.
Take a five-person consultancy on a £75/hour blended rate. If each person forgets to log just 15 minutes a day (a quick call, a “tiny” tweak, a bit of scope creep), over roughly 230 working days a year, that’s:
0.25 hours × 230 days × 5 people = 287.5 hours that never reach an invoice — or about £21,563 a year.
Fraud is still a big national problem — UK Finance says criminals stole £1.17bn through authorised and unauthorised fraud in 2024 — but for the average business, the day-to-day, repeatable leak is more likely to be unrecorded time and unclaimed expenses, not a dramatic one-off scam.
What leakage actually looks like (and why it feels so normal)
Revenue leakage is boring by nature. It doesn’t arrive with a siren. It arrives disguised as “I’ll sort that later”.
It’s the half hour you spent on a client call while walking through New Street station, then forgot to log because you were straight into the next thing. It’s the cab home after a late site visit in Digbeth that sits in your photo roll until it disappears into the digital void. It’s the “quick tweak” on a deck that turns into two hours of revisions, quietly absorbed because nobody wants to look petty.
Consultancies and SMEs are especially vulnerable because the work is messy in a way spreadsheets aren’t. People jump between clients, proposals, internal projects, training, chasing invoices, fixing scopes, calming stakeholders. If your admin process can’t cope with the real world, the real world wins.
The three places the money vanishes first
1) Unbilled time that doesn’t feel billable
This is the classic. The work happens, the value is real, but it doesn’t get captured because it’s “just support”, “just a quick one”, “just me being helpful”.
A useful test is brutal but fair: if you’d mention it in a project update, it deserves a category in your time log. The category might be “client support”, “change request”, or “project management” — but if it’s part of delivering, it shouldn’t be invisible.
2) Expenses that never become recoverable
Expenses die in three ways:
- receipts don’t get recorded
- receipts get recorded but not allocated to a project/client
- receipts get recorded and allocated, but nobody approves them in time to bill
The quieter your company culture is about expenses (“don’t make a fuss”), the more likely people are to shrug and absorb costs personally — which sounds noble until you realise it trains your business to underprice itself.
3) Approval delays that wreck cash flow
You can do everything right — log time, upload receipts, allocate correctly — and still leak money if approvals stall.
Most delays aren’t malicious. They’re operational. Somebody’s in back-to-back meetings. Somebody’s travelling. Somebody thinks approvals are “admin” rather than “cash”. But when approvals slide, invoices slide, and suddenly you’re funding client work out of your own overdraft.
The fix isn’t “more admin”. It’s fewer decisions.
Time and expense tracking software reduce friction. They make the right thing the easy thing — and they cut the number of moments where a human has to remember, chase, or interpret.
What that looks like in practice:
Make logging the default, not the exception
Set a rule that time gets captured daily (or at least by close of play). Not because you love timesheets, but because memory is a creative writing tool, not an accounting system. The more days you leave it, the more your week turns into a vibe rather than a record.
A simple trick that works in real teams: anchor it to a routine that already exists. First coffee. Last Slack check. The moment you close your laptop. Don’t create a new ritual — hijack an old one.
Create “honest” categories people actually use
If your timesheet options don’t match reality, people will pick the nearest thing and move on, and your reporting becomes fiction.
For a typical consultancy/SME, the categories that prevent leakage are often:
- delivery (by project)
- project management
- client comms
- change requests / out-of-scope
- proposals / pitching
- internal ops
- training / CPD
That one category — “change requests / out-of-scope” — is where a lot of hidden money lives. You’re not using it to punish clients. You’re using it to see patterns and price properly next time.
Don’t let expenses float around without context
The golden rule: if it’s for a client, it gets tagged to a client at the moment it’s submitted.
The second rule: set a clear threshold for what needs pre-approval (for example, anything over £X, or anything involving travel). People don’t mind rules; they mind vague rules they can be told off for later.
Treat approvals as a weekly deadline, not an optional task
If approvals happen “when someone gets a minute”, you’ll always be late because nobody has a spare minute.
Teams that tighten leakage usually do something unsexy and effective: a fixed approval window. Wednesday 4pm. Friday 11am. Pick one that fits your rhythm. Make it short, predictable, and non-negotiable — like payroll.
The moment you’ll notice it working
It won’t feel dramatic. There won’t be a big “we’ve transformed the business” speech.
You’ll notice it when a client queries an invoice and, instead of reconstructing the month from calendars and half-remembered calls, you can answer calmly with dates, time entries, and the exact expense attached to the exact job.
And you’ll notice it when your team stops feeling like they’re “doing admin” and starts feeling like they’re simply recording what happened.