Reconciling from a Bank Statement: An Import Workflow

Most reconciliation guides start from your books and walk outward to the bank. This one runs the other direction: it starts from the bank statement itself. That order works well when the statement is the document you actually have in hand — a PDF the bank issued — and you want to bring it into your records and prove the two sides agree.

If you are new to the concept, read what a bank reconciliation is first. This guide assumes you know the goal and focuses on the import workflow.

Step 1: Get the statement into structured rows

A PDF statement is fine for reading but useless for matching — you cannot sort, filter, or compare a PDF against your ledger. The first job is to turn the transaction table into clean, structured rows: one line per transaction, with separate columns for date, description, and amount (or separate debit and credit columns if your bank splits them).

You have a few options here, covered in detail in how to convert a bank statement to Excel: type it in by hand, copy and paste from the PDF, or use automated extraction. For anything longer than a page or for a statement you process every month, a dedicated converter is one option — it detects the table and exports columns in a consistent layout. You can run a statement through the free bank statement converter and start from rows that are already aligned.

Before you move on, sanity-check the extracted data:

• Does the row count match the number of transactions on the PDF?
• Do the amounts carry the correct sign (money in positive, money out negative, or split across debit/credit columns)?
• Does the running balance, if present, tie back to the statement's ending balance?

A clean export at this stage saves you from chasing phantom differences later.

Step 2: Import into your books

With the statement in a spreadsheet, you can bring it into whatever system holds your books — accounting software or a ledger spreadsheet of your own.

Most accounting tools import a CSV file. Export your structured rows to CSV and map the columns during import: the statement's date column to the transaction date field, description to memo or payee, and amount to the debit/credit field. If your software lets you save the mapping, do so — next month's statement from the same bank will use the same layout.

If you keep books in a spreadsheet instead, paste the rows into a dedicated "bank" sheet and keep your own ledger on a separate sheet. You want the bank side and the book side visible but distinct, so you can match them without overwriting either.

Step 3: Match transactions

Matching is the core of the work: pair each transaction on the bank side with the corresponding entry on the book side. A payment you recorded when you wrote a check should line up with the same amount when the bank pays it; a deposit you logged should line up with the bank's credit.

Working from structured rows makes this manageable. Sort both sides by amount or by date so equal amounts sit near each other, then walk down the list marking pairs. A simple approach in a spreadsheet is to add a "matched" column and flag each pair as you confirm it. When you finish, the unmatched rows on either side are exactly the items that need explanation — which is the next step.

A few patterns to watch for while matching:

• One-to-many — a single bank line that covers several book entries, or vice versa.
• Same amount, different transaction — two payments of the identical value; match on date and description, not amount alone.
• Sign flips — a refund recorded as a negative expense rather than positive income.

Step 4: Handle timing differences

Not everything will match, and that is expected. Some items appear on one side but not yet on the other because of timing, not error:

• Outstanding checks — payments you have recorded in your books but the bank has not yet paid out. These appear on the book side with no bank-side partner. They are money already deducted in your records, so they temporarily make the statement balance look higher than your books.
• Deposits in transit — money you have recorded as received but the bank has not yet processed. These sit on the book side waiting for the bank to catch up.

Leave these unmatched on purpose and list them separately as reconciling items. They are not mistakes; they will clear on a later statement, at which point they match.

Other unmatched rows are not timing — they are entries you simply have not recorded yet, and they belong on the book side:

• Bank fees and service charges — the bank deducted them; record them in your books.
• Interest credited — the bank added it; record it as income.
• Returned or bounced items — reverse the original entry if a deposit failed to clear.

Add a book entry for each of these, then match it to its bank-side row.

Step 5: Confirm the balance

Now prove the two sides agree. Start from the bank statement's ending balance and adjust it for the genuine timing items:

• Subtract outstanding checks (the bank has not paid them yet, so the statement is too high).
• Add deposits in transit (the bank has not credited them yet, so the statement is too low).

The result is the adjusted bank balance. Separately, take your book balance after you have recorded the fees, interest, and any corrections from Step 4. If your matching and adjustments are complete, the adjusted bank balance and the adjusted book balance meet at the same figure. That matching number is the reconciled balance.

If the two sides do not meet, the gap equals something you have missed: an unmatched row you overlooked, a timing item left off the list, or a transaction entered with the wrong sign or amount. Work back through the unmatched rows until the difference is fully explained — a reconciliation is only finished when nothing is left unaccounted for.

Keeping the workflow repeatable

The reason to start from the statement is consistency. Each period you receive the same kind of PDF, run it through the same conversion, import with the same column mapping, and match against your books. Once the steps are settled, the only changing input is the statement itself.

If you reconcile monthly, save your column mapping and keep prior periods' structured exports — they make it easy to verify that an opening balance ties to the previous period's reconciled close. For the underlying concepts and a worked example of the adjusting entries, see what a bank reconciliation is. To start a new period from clean rows, run your statement through the bank statement converter.