Name the Excuses Next to Every Rule
Most bookkeeping rules don't get broken on purpose. They get talked around, one reasonable sentence at a time.
Every finance team has rules. Reconcile every account every month. Never post an entry you can't trace to a document. Explain every difference, however small. Nobody argues with them. They sit in the procedures binder and everyone agrees.
And they get skipped. Not out of carelessness. Agreeing with a rule costs nothing in the moment. The excuse is what actually decides what happens next.
What the excuses sound like
The rule says explain every difference. Skipping it never sounds like skipping it. It sounds like this:
- "It's probably a timing difference."
- "It's under fifty dollars, it's immaterial."
- "I'll clean it up at year-end."
- "The feed said it matched."
- "It tied last month, so it's fine."
None of those are lies. Each one sounds like progress. Each one is how a difference gets carried forward until it is too old to trace.
Pair each rule with its excuses
A sharper rule won't solve it. Listing the excuses beside the rule will.
For "explain every difference": if you hear "probably" or "timing," stop and name the specific item that will clear and the date it will clear. If you can't, it isn't timing.
For "trace every entry": if the only support is "the client said so," get it in writing or flag the entry.
For "reconcile every account": if the reason to skip one is that it rarely moves, that is exactly the account where an error can sit for a year.
The rule describes the standard. The list of excuses describes the specific moments people drift from it. Write those moments down and they become easy to spot.
Machines make the same excuses
Automated systems make these moves too. A process built to finish will look for the shortest route to "done." "Matched within tolerance." "Skipped three rows with bad dates." "Will reconcile it later." Each is the rule bending inside a sentence that reads like a status update.
So we build the excuses into the system as things it may not say. A reconciliation can't call itself complete with an unexplained difference, however small. A batch can't report success if any row was skipped. "Probably" isn't an allowed status.
Holding software to that standard has a side effect. Once the excuses are on paper, you start noticing when you use them yourself.
The takeaway: For each rule your books depend on, write the two or three sentences people use to skip it, and post them next to the rule.
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