Why your converted bank statement does not balance

A converted statement that does not balance almost always has a missing row, a doubled row or an amount with the wrong sign. Compare the gap with the transaction amounts, walk the running balance until it first disagrees with the PDF, and check page breaks, carried-forward lines and pending items first.

Last updated: November 2, 2026

You converted a PDF bank statement to Excel or CSV, added up the rows, and the result does not equal the closing balance. The size of the gap usually tells you what went wrong. This page goes through the checks in the order that finds the problem fastest.

First, confirm what “balanced” means

A statement balances when:

opening balance + money in − money out = closing balance

Use the opening and closing balances printed on the PDF itself, not the ones in your accounting software. Then total the converted money-in and money-out columns separately. If your file has a single amount column, make sure money out is negative.

Write down the gap: closing balance on the PDF minus your calculated closing balance. Keep its sign. A positive gap means your rows are short of money in or carry too much money out.

Read the gap

  • The gap equals one transaction amount. A row is missing (the gap has the sign of that row) or doubled (the opposite sign). Search the PDF for that amount.
  • The gap is twice one transaction amount. That row has the wrong sign: a refund read as a purchase, or a payment read as a deposit.
  • The gap divides evenly by 9. Two digits were probably swapped, for example 1,270.00 read as 1,720.00, which leaves a gap of 450.00.
  • The gap equals a fee or interest line. Small lines at the end of a statement, such as monthly fees or interest, are easy to skip because they often sit outside the main table.
  • The gap equals the sum of a whole page. A page was not read at all, or read twice.

Where conversions usually go wrong

Page breaks. Many statements repeat a “balance brought forward” or “carried forward” line at the top and bottom of each page. That line is a balance, not a transaction. If it is counted as money in, the total jumps by a large round-looking number. Delete those rows.

Lines split over two rows. A long description can wrap onto a second line. A converter that treats the second line as its own transaction may also pick up a number from it, such as a reference or a card number fragment, as an amount.

Debit and credit columns. Statements that print money in and money out in separate columns depend on the column position. If the columns are narrow or the PDF’s text is slightly offset, an amount can land in the wrong one. That shows up as a gap of twice the amount.

Pending or “not yet posted” items. Some online banking exports and some statements list pending card payments separately. They are not part of the statement arithmetic. Remove them.

Foreign currency lines. A card payment abroad can show the original amount, the exchange rate and the converted amount. Only the amount in the account’s currency belongs in the total.

Two accounts in one PDF. Combined statements may hold a current account and a savings account. Each one has its own opening and closing balance and has to be checked on its own.

Walk the running balance

If the bank prints a balance after each line or each day, this is the fastest check. Put the converted rows in date order as they appear on the statement. Start from the opening balance and keep a running total. The first row where your running total differs from the printed balance is where the error is, or the row just above it.

In Excel, with amounts in column C and the printed balance in column D, put the opening balance in E1, then =E1+C2 in E2 and copy it down. A column =D2-E2 shows zero until the first bad row.

A converter that checks this for you

The Rowkeel converter runs the same test as soon as the statement is read, before you export. It compares the rows with the opening and closing balances printed on the statement and, where the bank prints a running balance, checks every row against it. If something does not add up, the result says by how much and highlights the rows where the balance stops following, so you know where to look in the PDF. Conversion runs in your browser, and the PDF is not uploaded.

It cannot fix every statement. Scanned PDFs without a text layer are reported as scans and not converted, and banks without their own page are converted as unlisted banks, where the balance check is the main signal that it read the statement correctly. When the check passes you can export to Excel, CSV or QBO.

When the statement itself is the problem

Rarely, the statement is right but your starting point is not. If you are comparing against your books rather than against the PDF, the gap may come from an earlier period, a timing item or a bank charge that was never recorded. That is a reconciliation question, not a conversion one. The step-by-step reconciliation guide covers it.

Questions

How big is a normal rounding difference?

There should be none. Bank statements print amounts to the cent and the arithmetic is exact. A gap of a few cents points to a misread digit or a fee line that was dropped, not to rounding.

The totals balance but one row still looks wrong. Is that possible?

Yes. Two errors can cancel out, such as two swapped amounts, or a date that was read from the wrong column. A balance check catches missing and changed amounts; it does not prove every date and description is right.

Should I just add an adjustment line to make it balance?

Only after you know what it is. A forced adjustment hides the missing transaction, and next month's opening balance will carry the error forward.

My statement has no running balance column. How do I find the bad row?

Total each page or each day and compare it with any subtotal the statement prints. Without subtotals, compare the converted rows with the PDF page by page, starting with the pages that have the most lines.