$StatementProof

Guides

Which Banks Print a Running Balance on Statements?

By Tarun Vashishth · Published

Whether a statement prints a balance after every individual transaction, rather than just an opening and closing balance for the period, determines how thoroughly a conversion can be checked. This is a factual reference for the banks this tool has dedicated profiles for — seethe full supported banks matrix for the authoritative, dated version of this table.

BankStatement typeRunning balance per row
ChaseCheckingNo — Daily Ending Balance summary instead
Bank of AmericaCheckingYes
Wells FargoCheckingYes
American ExpressCardNo — card statements don't print one at all
Capital OneCheckingYes

Why this varies by bank at all

A running balance column takes up space and isn't universal even among checking accounts — some banks print a per-row balance as a matter of course, and others (Chase's personal checking layout, among the profiled banks here) summarize balances in a separate "Daily Ending Balance" section instead of attaching one to every transaction row. There's no accounting requirement either way; it's purely a layout choice each bank's statement design makes.

Why card statements are structurally different

A checking account's balance changes with every transaction in a way that's meaningful to track row by row. A credit card's "balance" during a billing period is really an accumulating total of charges and payments against a billing cycle — most issuers, American Express included, don't print an intermediate balance after each individual charge, only a previous balance and a new balance for the whole period. This isn't a layout choice a bank could easily change; it reflects how card billing actually works.

What running-balance presence changes about verification

When a per-row balance is present, this tool runs a balance-chain check: for every consecutive pair of rows, the previous balance plus the current row's signed amount must equal the current row's printed balance. That check pinpoints the exact row where something's wrong. When it's absent, the tool falls back to a statement-totals check — opening balance plus every transaction equals the closing balance — which still catches missing or misparsed rows, just without pointing to which specific row caused the mismatch. Neither check is silently skipped without saying so: a statement that can't support the balance-chain check shows that check as "skipped," not as a false pass. Seethe full verification guide for both checks explained in detail.

What about banks not on this list

Any bank without a dedicated profile still runs through the same geometric column-detection parser — it just doesn't get bank-specific section-heading hints. Whether the statement supports a balance-chain check depends entirely on whether that specific bank's layout prints a running balance, which this tool detects per-statement rather than assuming based on the bank.

Related: the full, dated supported banks matrix,how the reconciliation checks work.