How do I get transactions out of a bank statement PDF?

Most statements arrive as PDFs with the transactions in a table, so extract that table into a spreadsheet rather than re-keying — a PDF-to-spreadsheet/CSV extraction maps the rows (date, description, amount, balance) into columns you can work with. Statement layouts vary a lot between banks, so the extraction quality varies, and you will sometimes clean up columns. If the statement is a scan or image, OCR it first to get text. The point is to turn the statement into transaction data you can reconcile and import, instead of manually copying line by line — but with the verification step below, because financial figures must be exact.

Why is verifying the extracted figures so important?

Because reconciliation is built on the statement being exactly right, and table extraction (and OCR, for scanned statements) can misread a digit, drop a row, or misplace a decimal — errors that look plausible but break the reconciliation or, worse, pass unnoticed into the books. So after extracting, verify against the original: check the opening and closing balances reconcile to the sum of transactions, spot-check amounts and dates, and confirm no rows were missed or merged. A misread "8" for a "3", or a transaction dropped at a page break, is exactly the kind of error that wastes hours hunting a reconciliation difference. Extract to save typing; verify because the numbers must be exact.

How does this fit into the reconciliation itself?

Once you have verified transaction data from the statement, you match it against the cash account in the books — ticking off cleared items, identifying outstanding checks/deposits and bank items not yet recorded (fees, interest), and resolving the difference to zero. The PDF work is the front end (getting clean, correct statement data); the reconciliation is your accounting process in your software or worksheet. Keeping the statement data in a spreadsheet makes matching and investigating differences far easier than working off the PDF visually. The cleaner and verified the extracted data, the faster the reconciliation and the more trustworthy the result.

What about statements that are scanned images?

Some clients provide scanned or photographed statements, which are images with no extractable text, so OCR them first to recover the transaction text, then extract and — critically — verify, because OCR misreads digits and a financial document cannot tolerate that. Scanned statements deserve extra verification care: reconcile the totals and spot-check liberally. If a client can provide the original digital PDF or a CSV export from their bank instead of a scan, that is far better and avoids OCR error entirely, so ask. For the scans you must work with, OCR-then-verify is the path, with verification weighted heavily.

How should I document and archive the reconciliation?

Keep a clear record: the reconciliation worksheet/report, the source bank statement PDF, and notes on any reconciling items and how they were resolved, organised per client and period. This documentation supports the books, satisfies review and audit, and lets you reconstruct what was done if a question arises later. Archive the source statements alongside the reconciliations so the trail is complete. Retain records for the period your professional and regulatory requirements specify. An organised, documented reconciliation with its source statement attached is both good practice and what protects you if the work is ever scrutinised.

How do I keep client financial data secure?

Bank statements and reconciliations are sensitive client financial data (account numbers, balances, transaction detail), so handle them confidentially: store encrypted with access limited to the engagement team, transmit through secure channels rather than plain email, redact account numbers when sharing beyond what is necessary, and retain/dispose per your obligations. Client financial data carries both professional-confidentiality duties and data-protection obligations. Process documents with tools that keep files local rather than uploading client statements to a cloud service you have not vetted. The combination of encryption, access control, and careful handling is standard duty of care for client financial information.

Is it safe to extract client statements online?

Client financial statements are confidential, so prefer a tool that processes files locally. ScoutMyTool extracts statement tables to spreadsheet, OCRs scans, and merges/archives entirely in your browser tab, so client data never leaves your machine. For client financial documents, confirm the tool does not upload before using it — and always verify extracted figures against the statement.

6 min read

PDF for accountants: bank statements and reconciliation

By ScoutMyTool Editorial Team · Last updated: 2026-05-22

Bank reconciliation is one of the most common — and most digit-sensitive — accounting tasks, and it usually starts with a statement PDF you need as data. The temptation is to re-key it; the better path is to extract the transactions into a spreadsheet, but with a verification step that accounting demands, because a single misread amount or dropped row turns into hours of hunting a difference. This guide is the PDF side of reconciliation: extracting statement transactions, verifying them against the source, feeding them into the reconciliation, documenting the result, and handling client financial data securely. (For the broader accounting and tax document workflows, see the companion guides.)

Statement to reconciliation

Step	Detail
Statement PDF in	Transactions as text/table (or scanned image)
Extract	Pull transactions into a spreadsheet
Verify	Check every amount, date, sign vs. statement
Reconcile	Match against the books; resolve differences
Document & archive	Keep reconciliation record + source statement

Step by step — reconcile from a statement PDF

Prefer a digital statement or bank CSV. If the client can supply the original PDF or a bank CSV export, use it — it avoids OCR error.
OCR scanned statements. For images, recover text with PDF OCR first (see OCR + reformat).
Extract transactions to a spreadsheet. Use PDF to CSV or PDF to Excel (see extracting complex tables), cleaning up columns as needed.
Verify every figure. Confirm opening + transactions = closing balance, spot-check amounts/dates, ensure no rows dropped at page breaks.
Reconcile against the books. Match cleared items, identify outstanding and unrecorded items, resolve the difference to zero (your accounting process).
Document and archive. Keep the reconciliation, the source statement, and notes per client/period — see accounting document organisation.
Protect client data. Encrypt with Protect PDF, restrict access, redact account numbers when sharing — process locally.

PDF for accountants: the broader accounting workflow.
PDF for tax season: source documents and packets.
Extracting complex tables: statement-table extraction.
PDF to spreadsheet: the extraction workflow.
Receipts to expense report: a related data-capture task.
PDF to CSV tool: extract statement data in your browser.
All ScoutMyTool PDF tools: the full toolkit.

FAQ

How do I get transactions out of a bank statement PDF?: Most statements arrive as PDFs with the transactions in a table, so extract that table into a spreadsheet rather than re-keying — a PDF-to-spreadsheet/CSV extraction maps the rows (date, description, amount, balance) into columns you can work with. Statement layouts vary a lot between banks, so the extraction quality varies, and you will sometimes clean up columns. If the statement is a scan or image, OCR it first to get text. The point is to turn the statement into transaction data you can reconcile and import, instead of manually copying line by line — but with the verification step below, because financial figures must be exact.
Why is verifying the extracted figures so important?: Because reconciliation is built on the statement being exactly right, and table extraction (and OCR, for scanned statements) can misread a digit, drop a row, or misplace a decimal — errors that look plausible but break the reconciliation or, worse, pass unnoticed into the books. So after extracting, verify against the original: check the opening and closing balances reconcile to the sum of transactions, spot-check amounts and dates, and confirm no rows were missed or merged. A misread "8" for a "3", or a transaction dropped at a page break, is exactly the kind of error that wastes hours hunting a reconciliation difference. Extract to save typing; verify because the numbers must be exact.
How does this fit into the reconciliation itself?: Once you have verified transaction data from the statement, you match it against the cash account in the books — ticking off cleared items, identifying outstanding checks/deposits and bank items not yet recorded (fees, interest), and resolving the difference to zero. The PDF work is the front end (getting clean, correct statement data); the reconciliation is your accounting process in your software or worksheet. Keeping the statement data in a spreadsheet makes matching and investigating differences far easier than working off the PDF visually. The cleaner and verified the extracted data, the faster the reconciliation and the more trustworthy the result.
What about statements that are scanned images?: Some clients provide scanned or photographed statements, which are images with no extractable text, so OCR them first to recover the transaction text, then extract and — critically — verify, because OCR misreads digits and a financial document cannot tolerate that. Scanned statements deserve extra verification care: reconcile the totals and spot-check liberally. If a client can provide the original digital PDF or a CSV export from their bank instead of a scan, that is far better and avoids OCR error entirely, so ask. For the scans you must work with, OCR-then-verify is the path, with verification weighted heavily.
How should I document and archive the reconciliation?: Keep a clear record: the reconciliation worksheet/report, the source bank statement PDF, and notes on any reconciling items and how they were resolved, organised per client and period. This documentation supports the books, satisfies review and audit, and lets you reconstruct what was done if a question arises later. Archive the source statements alongside the reconciliations so the trail is complete. Retain records for the period your professional and regulatory requirements specify. An organised, documented reconciliation with its source statement attached is both good practice and what protects you if the work is ever scrutinised.
How do I keep client financial data secure?: Bank statements and reconciliations are sensitive client financial data (account numbers, balances, transaction detail), so handle them confidentially: store encrypted with access limited to the engagement team, transmit through secure channels rather than plain email, redact account numbers when sharing beyond what is necessary, and retain/dispose per your obligations. Client financial data carries both professional-confidentiality duties and data-protection obligations. Process documents with tools that keep files local rather than uploading client statements to a cloud service you have not vetted. The combination of encryption, access control, and careful handling is standard duty of care for client financial information.
Is it safe to extract client statements online?: Client financial statements are confidential, so prefer a tool that processes files locally. ScoutMyTool extracts statement tables to spreadsheet, OCRs scans, and merges/archives entirely in your browser tab, so client data never leaves your machine. For client financial documents, confirm the tool does not upload before using it — and always verify extracted figures against the statement.

Verify extracted figures. Table extraction and OCR can misread financial data. This article covers handling statements as PDFs; always reconcile extracted figures to the source, and follow your professional and data-protection obligations for client financial information.

Citations

Wikipedia — “Bank reconciliation,” the process this supports. en.wikipedia.org/wiki/Bank_reconciliation
Wikipedia — “Bank statement,” the source document. en.wikipedia.org/wiki/Bank_statement
Wikipedia — “Bookkeeping,” the accounting context. en.wikipedia.org/wiki/Bookkeeping

From statement PDF to a clean reconciliation

Extract statement transactions, OCR scans, and protect client data with ScoutMyTool’s in-browser tools — client financials never leave your machine. Always verify the figures.

Open PDF to CSV →