How to convert a PDF bank statement to Excel without losing the audit trail
A spreadsheet is useful only when you can trace its rows back to the source. Use this workflow to keep that connection intact.
Start with the original statement
Download the statement directly from your bank's website or app, and keep the original file unchanged. Choose the correct account and period before converting. If the statement is password-protected, obtain an unlocked export you are permitted to process. A screenshot of one page is not a substitute for a complete statement when you need a full-period result.
Check the source for page numbers, the statement period, opening and closing balances, and any notes explaining how the bank presents pending items or card activity. These details give you a way to test the spreadsheet later.
Extract the rows into a consistent structure
A PDF table may look orderly on screen while its text is stored as separate fragments. Copying it into a spreadsheet can split descriptions, move a minus sign, or attach a balance to the wrong transaction. A converter maps each posted transaction into fields such as date, description, reference, debit, credit, signed amount and running balance.
In BankStatementConverter, upload a PDF, PNG or JPG up to 10 MB. The document is sent for AI extraction, and the rows appear in an editable browser table. The result is a working interpretation of the document, not an official bank record or a guaranteed accounting entry.
Keep money out and money in distinct
Many workflows need both separate debit and credit columns and one signed amount. A debit is shown as a positive number in the debit column and a negative number in the signed amount field. A credit is positive in the credit and signed amount fields. This makes the sheet easier to read while preserving a simple calculation for reconciliation.
Pay special attention to refunds, reversals, cash withdrawals and fees. A description can sound like a credit even when the bank shows it as money out. Use the source statement's column headings and balance movement, not the transaction name alone, to decide the sign.
Review uncertain or missing values
Scans, wrapped descriptions, faint text and multiple dates on one row can make extraction uncertain. Review any flagged cell and compare it with the original page. If the source omits a running balance, leave that field blank rather than inventing one. Check the first and last rows of every page as well as the largest transactions; page breaks are a common place for omissions.
Reconcile the balance sequence
When the statement supplies a running balance, compare each row with the previous balance plus the signed amount. For example, a balance of 1,000 followed by a debit of 75 should normally produce 925. A mismatch may indicate a missing transaction, a sign error, a duplicated row or a bank-specific convention. Do not force the numbers to agree by changing a row without checking the source.
Then compare the final transaction balance with the printed closing balance. Some statements show a balance carried forward or include non-transaction lines; those should not be treated as posted transactions merely to make the table add up.
Export and preserve context
After review, download the genuine Excel .xlsx workbook, CSV or JSON. The workbook includes a Transactions sheet and a Statement details sheet. CSV is a plain-text option for imports; check date and decimal settings in the receiving system. Keep the source PDF with the export and record any manual corrections you made, particularly if the data supports an audit or formal application.