The Error You Only See in a Lineup
Some mistakes look perfectly normal on their own. Put them beside their neighbors and they jump out.
Picture an aging report with thirteen open invoices. Twelve show how many days old they are: 8, 15, 31, 44. One shows only a date, with no day count. Easy to scroll past. Dates appear on reports all the time.
The cause is small. That invoice came in through an import where the date was written day first instead of month first. The system couldn't read it as a date, so it kept the raw text and moved on. No error. No warning. Just one line that looks slightly different from the rest.
Why it hid
Each piece did what it was built to do. The import accepted the file. The system stored what it couldn't parse as text. The report showed what it had. Every step worked. The result was wrong.
If that invoice had been the only line on the report, nobody would have noticed. One line with a date on it looks fine. It is only wrong next to twelve lines that look different. The mistake was invisible alone and obvious in a group.
The same shape all over the books
Most errors that survive in a set of books look like this. Not a crash. A believable value that every step accepted:
- A bill entered at $1,250.00 instead of $125.00, in a list of utility bills that never pass $200.
- A deposit dated a year early, outside every report anyone checks.
- One payroll run where the employer taxes were coded to wages.
- A month where one expense category is zero, when it has never been zero.
On its own, each one passes. Next to the same line from last month, or the same vendor's last ten bills, each one sticks out.
Build the comparison on purpose
The fix is to stop counting on luck and set up the comparison deliberately. Don't look at a number alone when you can look at it next to its peers:
- Show each vendor's bill beside that vendor's usual range.
- Show this month's P&L beside the last three months.
- Sort a list by amount and read both ends.
- Count the rows that didn't parse instead of quietly dropping them.
This is a standard step in how we review a month. Every line is compared to its own history before anyone signs off. Anything far outside its normal range gets a second look, even when the arithmetic is fine.
Alone, a wrong figure blends in. Placed next to similar figures, it is the one that obviously doesn't belong.
The takeaway: Review your monthly P&L with the prior three months beside it, and question any line that moved for a reason you can't name.
Want these checks running on your books?
We set this up on your books and your rules, and nothing posts without your approval.
Book a call