Home › Blog › Reconciliation & Verification › Why a converted statement does not tie out
The nine most common reasons a converted statement does not tie out, how each one changes the difference, and how to isolate the real cause fast.
By StatementVerified Editorial · November 4, 2026 · 8 min read · Filed under Reconciliation & Verification
A converted statement ties out when the opening balance plus every signed transaction equals the closing balance printed on the statement. When it does not, the gap is not a mystery to be absorbed. It is a measurement. Its size, its sign, and whether it equals or doubles a transaction on the statement will point to a short list of causes, and working that list in order finds the problem far faster than rereading every row hoping something looks wrong. This guide covers the causes experienced bookkeepers check first.
Each cause below leaves a different fingerprint. A dropped row makes the gap equal that row exactly. A duplicated row does the same in the opposite direction. A flipped sign makes the gap exactly twice the transaction. A subtotal counted as a transaction inflates the total by a number the statement prints in bold. Learning to read the gap before touching the rows turns a frustrating hour into a structured ten minute diagnosis, and it prevents the worst response of all, which is adjusting a correct row to force a false tie.
A dropped row happens most often at page boundaries, where the last line of one page or the first line of the next is visually separated by a header, a footer, or a continued notice. It also happens in multi column layouts where a second activity column is easy to miss, and in statements that list a fee or interest section apart from the main activity. The fingerprint is simple: the unexplained difference equals the missing amount exactly, with the sign telling you which side lost the row. Search the converted file for that exact amount. If it is absent, search the PDF page by page until you find the line that never made the journey.
A duplicated row is the mirror image, most often caused by a page uploaded twice, a statement range that overlaps a prior conversion, or an activity block repeated in the PDF itself as a summary and then again in detail. The gap again equals the amount, in the opposite direction. Search for the amount and inspect every occurrence with its date and description. Genuine repeats do exist, especially for identical recurring charges, so prove duplication by comparing the full line, including any reference or check number, against the statement count for that description. Delete only a row you have proven appears once on the statement and twice in the file.
A flipped sign means a debit was converted as a credit or the reverse. Because removing the correct effect and adding the wrong one moves the total by twice the value, the fingerprint is unmistakable: the gap is exactly double a transaction in the file. Halve the gap, search for that amount, and check the sign of each match against the statement column or indicator it came from. Sign errors cluster around layouts that use parentheses, trailing minus signs, or separate debit and credit columns, and around credit card statements where payments and charges carry the opposite intuition to a deposit account.
A misread digit produces a gap that matches no transaction. Classic patterns include a transposition, where two adjacent digits swap places and the resulting gap divides evenly by nine, a substituted digit from a scan, such as a three read as an eight, and a dropped or added zero that shifts a value by a factor of ten. When the gap follows one of those patterns, compare amounts in the file against the PDF in the section where any running balance also steps out of line. Fix the digit to what the statement prints, even when the file value looks more plausible, because the statement, not plausibility, is the source of truth.
Statements are designed for humans, so they contain numbers that are not transactions. Section subtotals for deposits, checks, fees, and interest, daily balance summaries, and year to date totals all sit in the same visual space as real activity. If a converter or a hurried manual cleanup counts a subtotal as a transaction, the gap will equal that subtotal, a number you can find printed prominently on the statement. The fix is to remove the subtotal row from the transaction list while keeping it in your workpapers, because subtotals are excellent checkpoints for verifying each section separately once they are out of the transaction total.
Page header rows cause a quieter version of the same problem when a statement repeats column headings mid file and a header or a repeated opening line is parsed as data, or when a fee section at the end of the statement is overlooked entirely because it appears after the closing balance summary. Section fees deserve a dedicated check. List every fee named in the statement summary, such as service charges, paper statement fees, and wire fees, and confirm each appears once as a transaction. A missing fee section is one of the most common reasons a file is short by a small, unglamorous amount that matches nothing in the main activity list.
Sometimes every transaction is perfect and the file still does not tie, because the opening balance used in the check is wrong. That happens when the prior month had a late correction, when the statement cycle does not match the calendar month, or when the opening figure was taken from the accounting system instead of from the statement itself. Always take both anchors from the same statement you converted. Then confirm the statement opening balance equals the prior statement closing balance. A break in that chain is real information: it can reveal a missing statement in the sequence or a period that was converted twice with different boundaries.
Pending transactions create a related trap. Some statements list pending or memo items that have not yet posted, sometimes inside the activity area and sometimes in a separate block, and they are not part of the closing balance arithmetic. Including them breaks the tie by exactly their total, and excluding genuinely posted items that merely look pending breaks it the other way. Read the statement labels carefully. Posted dates, running balance inclusion, and the statement own totals will tell you which block belongs in the arithmetic. When in doubt, test both ways in your workpaper. The version that ties exactly to the printed closing balance is the version the bank itself used.
Work in a fixed order so you do not chase the rarest cause first. Step one, recheck the anchors from the statement. Step two, compare transaction counts and section subtotals if the statement prints them. Step three, test the gap against the fingerprints: equal to a row, double a row, divisible by nine, or equal to a printed subtotal. Step four, if the statement prints a running balance, find the first row where the file running balance diverges, because the cause lives at or immediately before that row. Step five, inspect page boundaries and the fee section in the PDF with your own eyes, since those are the places automated reading and tired human reading both fail most often.
Document the cause when you find it, in one plain sentence on the workpaper, and correct only the proven error. Then rerun the full tie from the opening balance, not just a check that the gap closed, because a fix can close one gap while opening another if the wrong row was touched. A file that ties after a documented, proven correction is trustworthy. A file that ties after unexplained fiddling is not, even though both show the same zero difference. The discipline of diagnosis over adjustment is what separates verification from wishful thinking, and clients pay for the former.
That pattern almost always means a sign flip. The transaction was added when it should have been subtracted, or the reverse, so the total moved by twice its value. Halve the difference, find that amount, compare its sign to the statement column it came from, and correct the sign only.
Never. The closing balance printed on the statement is an anchor, not a variable. Adjusting it manufactures a tie and destroys the proof. Find and correct the row, the sign, the subtotal, or the opening balance that is actually wrong, then prove the tie again from scratch.
Follow the statement own arithmetic. If pending items are listed separately and excluded from the printed closing balance, exclude them from the conversion total and note them for next period. If an item carries a posted date and is included in the running balance, treat it as posted activity.
Reconciliation & Verification · November 2, 2026
Find a missing transaction fast by bisecting the statement balance, comparing mid period checkpoints, and narrowing the window until the row appears.
Reconciliation & Verification · November 3, 2026
Understand what reconciled, flagged, and unverified verification outcomes mean for a converted statement, and what to do next with each one.
Reconciliation & Verification · November 3, 2026
Why duplicate transactions appear after imports and bank feeds, how to prove a true duplicate against the statement, and how to remove it safely.
Convert a statement now and watch the reconciliation check verify it against the statement itself.
Your first conversion is free — no card, no sign-up — and every result is reconciled against the statement itself before you download it.