Drop a register โ a check book, a petty cash sheet, any export with an amount column and a running balance beside it. This walks the two columns together and stops at every row where the balance does not move by the amount next to it, then tells you what the difference looks like: a sign flipped, an amount applied twice, or two digits swapped.
One thing, precisely: for every row, does previous balance + this amount equal
this balance? That comparison localises the problem to a single line, which is the
part that takes a human an hour of squinting.
It deliberately measures each step against the stated previous balance rather than a running total of its own. Those differ in an important way: a total of its own would mark every row after the first mistake as wrong, burying the one row you need. Measuring step by step means three separate typos show up as three findings instead of one finding and two hundred false ones.
The size of the gap is usually a fingerprint, so each break is labelled where the arithmetic supports it:
It reads and reports; nothing is written and there is nothing to save. It will not repair the column for you, because the correct fix depends on which of the two numbers is the true one โ and only you know whether the bank agrees with the amount or with the balance.