A freelancer submits a weekly invoice. The line items add up. The declared total matches the sum of those lines exactly. The formatting is right, the dates are in range, the VAT is correct.
It is still wrong, and nobody reviewing that invoice will catch it.
Why does a correct-looking invoice get through review?
Because every check a human performs looks at the invoice on its own terms. Does the arithmetic work? Does the total match? Are the dates plausible? An invoice that passes all of those is, from the reviewer's side, finished.
The error is not inside the document. It is the gap between the document and something the document never refers to.
What actually catches it
An independent record of the same work. In this case the company's own time-tracking data, which the invoice has no access to and cannot be made consistent with by whoever wrote it.
Three sources, compared against each other:
- What the person declared as their total
- What their own line items sum to
- What the company's independent record says the work was
Checks one and two catch a typo. Only the third catches work that was never done. The first two are what a human reviewer already does, which is why adding more review does not help.
Why this pattern shows up everywhere
Invoices are just the clearest example. The same shape appears in stock counts against purchase orders, hours against project budgets, and delivery confirmations against dispatch records.
Wherever one party both produces a number and reports it, internal consistency proves nothing. The check has to come from somewhere they do not control.
What it costs to find out
Usually nothing dramatic, and that is the problem. A small discrepancy every week is invisible in a month and material in a year. It surfaces during an audit, or when someone leaves and their replacement asks a question nobody had asked.
If you want to know whether this is happening in your business, that is the kind of thing an Ops Call is for. Twenty minutes, no pitch.