How the tie-out check works
Bookkeepers call it “tick and tie”: before trusting a list of transactions, you check that it adds up to the balances the bank printed. Tieout does that check for you, every time, and shows it.
1. Reading
An AI model reads the statement: every transaction, its date, description and amount, the running balance if the bank prints one, and the opening and closing balances. It writes down what it sees as text. It does not do the sums.
2. The sum, in plain arithmetic
Our code turns every amount into whole cents and adds them up: opening balance, plus money in, minus money out. If the answer equals the closing balance the bank printed, to the cent, the statement ties out and every row gets a tick.
3. Finding the row that's wrong
•
If the statement prints a running balance, we keep our own running balance alongside it. The first row where the two disagree is the row that was misread or is missing.
•
We show that row on the page with the amount it has to be (the bank’s balance after it, minus the balance before it), and you fix it in one tap.
•
If the statement has no running balance, we tell you exactly how far off the total is, and which page disagrees with its printed page total if there is one.
4. Many months
Add several statements from the same account and Tieout lines them up. Each month's closing balance has to be the next month's opening balance. A gap in the dates means a missing statement; the same transactions in two files means an overlap. Both are named, so they're caught before your books are.
What the check can't do
A statement that doesn't print both an opening and a closing balance can't be tied out; Tieout says so rather than guessing. And two mistakes that exactly cancel each other out would pass the total, though not the row-by-row running balance check.