What’s inside: output checking · audit trail
The question this file answersHow many of the receipts my finance team reviews each week would have passed the policy anyway?
Fits: finance teams handling 500–5,000+ invoices and receipts a month.
Typical, from the professional-services playbook: a weekly cycle, every employee generating claims, no receipt count published. Staff photograph receipts late; a reviewer checks merchant, amount, VAT line and the alcohol rule, one claim at a time. It hurts at month-end, when the backlog and the close collide.
On payroll week the reviewer opens a list of the claims that broke a rule — over cap, no tax line, an unusual merchant — not the whole month of receipts. Entertainment and anything client-billable still stop at a person, and you can see per claim which rule it hit.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
the same exception build as timesheet review — no dated figure for expense review
Before: a reviewer reads every receipt, including the ones that pass. After: in-policy claims go through to the ledger and the reviewer sees only the breaks. No percentage here — the only dated figure we hold is about time entry, on the parent file.
The professional-services playbook cites Big 4 internal pilots at ~50% less expense-review time, but that cannot be pinned to a dated public document, so this file carries no percentage. Toggl/Harvest (2023) 40–60% is about time entry and stays on the timesheet file. Not a client KPI.
Your expense and billing tools stay — Toggl, Harvest, BigTime or the one you run — and the ledger behind them. This is the same exception build as our timesheet file, pointed at receipts:
Nothing is reimbursed without your normal sign-off.
Client-billable judgement. Entertainment. The receipt that is really a story.
Not a client KPI.
If the policy lives in people's heads rather than on paper, the check has nothing to test against — writing it down is audit work first. Receipts are photographs of variable quality; an unreadable one goes to the reviewer as before, and a merchant the model cannot place is treated as an exception, not a pass.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Finance.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.