How to Reconcile Chase Statements

Drag & drop statement PDFs hereor tap to choose files — multiple PDFs for batch mode

Privacy: uploaded files and generated exports are stored only briefly to complete your download and are automatically deleted within 15 minutes. Files are never used for any other purpose.

What you are checking against

Chase statements group activity into sections — deposits and additions, card withdrawals, electronic withdrawals and fees — and many account types also print a daily ending balance table.

Think of the statement as self-auditing. It opens at one balance, lists everything that moved, and closes at another — and if the list is complete and correctly read, the numbers cannot help but agree. Reconciliation is checking that they do, before the data is trusted downstream. Done at conversion time, the check has a practical shape: the file either reproduces the statement's balances or it is flagged with the exact rows where the walk breaks. The methodology page documents the method.

The Chase month-end reconciliation workflow

Prove the opening first. Before touching the month, confirm its opening balance equals last month's proven closing balance. If it does not, the problem is behind you, not in this month.
Convert with the check on. Run the month's PDF through the converter and take the reconciliation result seriously: reconciled, flagged or unverified are three different instructions.
Fix flagged rows at the source. Correct flagged rows against the statement PDF itself. Never adjust the books to match an unproven file.
Reconcile the software to the statement. Import the verified file and run the software's own reconciliation against the same closing balance and closing date.
Lock the month. Once both checks agree, the month is solid ground. Record it, and let next month build on it.

These are the general steps most banks follow for statement downloads; exact menu labels vary by bank and change over time.

Reading one Chase statement closely

Reconciliation goes faster when you know the document's habits. On a Chase statement, check where fees and interest sit — inside the chronological flow or in a closing section of their own — because that is where unrecorded items hide. Confirm the statement's closing date matches the period you think you are closing; cycle dates drift from calendar months. And keep the source straight: reconcile against the statement filed under Statements in Chase Online and the Chase Mobile app, the bank's own record of the month.

When a Chase statement does not tie out

The statement's opening balance belongs to a different period — usually a gap month in the set. Check that consecutive statements chain: each closing balance should equal the next opening balance.
A pending card transaction appears on one statement and posts on the next, so both statements are right and the import order is what needs care.
Two transactions with the same amount were collapsed or one was duplicated — compare the row count in the flagged region against the PDF.
The PDF is a scan and OCR misread a digit. The flagged rows name the expected and printed balances; correct those rows against the image.

Keeping a year chained together

The strongest property of a reconciled year is the chain: twelve statements where every closing balance hands over to the next opening balance without a seam. Build the chain and a whole class of errors — missing months, duplicated months, a statement converted twice — becomes impossible to hide. When a chain breaks, the break itself localizes the problem to the seam between two specific months, which is a five-minute investigation instead of a day of searching.

Questions and answers

What should I keep as evidence a month was reconciled?

The statement PDF, the converted file, and the reconciliation result for that month, filed together. That trio lets anyone re-perform the month later without asking you anything.

The difference is a few cents. Is that worth chasing?

Yes. Small differences are usually misread digits or rounding on a split transaction, and they compound silently if waved through. A reconciliation that tolerates cents teaches the whole file to drift.

Can I reconcile a quarter at once instead of monthly?

You can import in batches, but prove the months individually and in order. Three months reconciled as one blob hides which month owns a difference; the chain check needs each month's closing balance separately.

My software balance and the statement agree, but I never reconciled. Am I fine?

Not necessarily — two errors can cancel. Agreement of balances is a hint, not a proof; the proof is the transaction-level comparison a reconciliation performs. Convert and check the statements to be sure.

Who should reconcile — the person who enters transactions?

In larger setups, separation is a genuine control: the person reconciling is not the person who entered. In a one-person practice the monthly habit plus the filed evidence trio is the practical substitute.