Correcting an AI's Mistake With a Reversing Entry

Say your AI assistant categorizes a $1,200 payment as Rent, when it was actually a payment to a contractor and should have been Subcontractors. The books never let anyone edit a posted entry, by design — so how do you actually fix this?

The mechanism is a reversing entry: a brand-new journal entry that's the exact mirror image of the original, every line's amount flipped in sign, same accounts. It doesn't erase the mistake — it cancels the mistake's effect while leaving both the original error and the correction permanently visible in the journal, in order. Put real numbers through it: the original entry debited Rent $1,200 and credited Checking $1,200. The reversing entry credits Rent $1,200 and debits Checking $1,200 — netting Rent's effect back to zero and restoring Checking to what it was before the original entry posted. From there, a fresh, correctly categorized entry posts: debit Subcontractors $1,200, credit Checking $1,200. Three entries total, all permanently visible, telling the complete story of what happened and what was fixed.

For the common case — a mistake that came from categorizing a bank transaction, rather than a manual entry — the fix is even more direct than writing that third entry by hand. Reversing the entry automatically frees the underlying bank transaction back to "uncategorized," so the actual fix is just categorizing it again, correctly this time. You don't reconstruct the correcting entry yourself; categorizing it properly creates it for you, the same way the original (wrong) categorization did.

The reversal mechanism itself has real guardrails, and they're worth understanding as protections rather than friction. You cannot reverse a reversal — trying to "undo the undo" is refused outright. The reasoning is concrete: the first reversal already freed the original bank transaction back to uncategorized, so reversing the reversal as well would restore the original entry's effect while that transaction is separately sitting there ready to be categorized again — which would post the same money twice, and nothing in any report would show the duplication, since both postings individually balance. If you decide the first reversal itself was the wrong move, the actual fix is to categorize the freed transaction the way you meant it originally, not to try to reverse the reversal.

The same mechanism works just as cleanly for a mistake with no bank transaction behind it at all — say, a manual entry recording $2,000 of owner's contribution that should have been a $2,000 loan from the owner instead, equity versus liability, a real difference for the balance sheet. There's no bank transaction to free here, so after reversing the original entry, the fix is simply posting a new, correct manual entry for the loan — the same two-step shape, just without the automatic categorization step a bank-driven mistake gets for free.

The second guardrail: if the original entry falls inside a period you've already locked closed, the reversal can't be dated back into that same locked month — it needs a date in the period that's currently open. That's not a limitation getting in your way; it's the same principle from the locking guide applied here specifically — the correction shows up when you actually found and fixed the mistake, not retroactively smuggled into a month you'd already reported as final.

Why this matters specifically for AI-driven bookkeeping: an AI assistant can be instructed to reverse an entry and re-categorize the underlying transaction on your behalf, and doing it that way is exactly as safe as doing it by hand yourself, because the mechanism itself refuses to let a correction take an unsafe shape — there's no way to hand-construct a malformed reversal, and no risk of accidentally posting fresh value onto an account that's since been archived, since a reversal only ever negates the original entry's own lines rather than accepting new ones.

Because BalanceMCP fills in a reversal's memo automatically — something like "Reversal of: [original memo]" — with the option to write your own instead, it's worth taking that option when the reason matters. "Reversal of: Home Depot #4021 — miscategorized as Rent, should be Subcontractors" tells a future reader, whether that's you, your accountant, or an AI assistant reviewing the month later, exactly why this correction exists, rather than leaving them to guess from two entries that otherwise look identical except for their signs.