A Pepsi bill filed under payroll taxes — for two months

Not every leak is at the register. The nightly close is one set of books; the bank statement is the other, and it hides a different species of mistake — quieter, slower, and just as real.

The finding

On a reviewed operator’s bank statement, a Pepsi bill had been booked under payroll taxes. Not once — two months running. Every debit that landed in that tab was trusted to be what the tab said it was, and nobody sat down to check that the label matched the payee.

A drink vendor filed as a tax payment isn’t dramatic. It doesn’t trip an alarm. But it means the books say you spent money on something you didn’t, and you can’t manage costs you’ve miscounted. Two categories are wrong at once, every month it persists.

Why the bank statement is where this hides

The close packet gets attention because a short is visceral — cash is missing tonight. A bank statement is the opposite: it’s a long list of debits that already cleared, reviewed on a Sunday if at all, and mostly skimmed for anything that looks obviously huge or fraudulent.

A misfiled vendor bill is neither huge nor fraudulent. It’s the right amount to the right company, filed to the wrong place. Skimming will never catch it. Only going line by line — every debit classified to the right expense, every check matched to a payee — surfaces it. And nobody has time to do that by hand, so it doesn’t get done, so the Pepsi bill sits under payroll taxes for two months.

Correct it once, and it should stay corrected

The useful version of this isn’t just catching the error — it’s catching it and not having to catch it again. When a debit is classified to the right place, the rule should stick: the next Pepsi bill lands where it belongs without anyone re-deciding.

That’s the whole idea behind watching the second set of books. Read the statement line by line, put every debit where it goes, and remember the correction so the same mistake can’t quietly run for another two months. The register short you feel. The misfiled bill you don’t — which is exactly why it needs the machine, not the memory.