Password-protected bank statement to Excel

A bank can encrypt a PDF so that it will not open without a password, or restrict copying and printing on a file that already opens. Those are different situations. Sonomir first tries to open a restricted file without asking you for an unnecessary password. An encrypted statement brings up the PDF password field before upload or processing.

This workflow is for a statement you are entitled to open and a password you already know. It does not crack passwords, guess personal details or obtain an account's credentials. If you do not know the password, read the email or letter that accompanied the statement, or ask your bank for its current instructions. No universal bank-statement password exists. We do not publish unverified rules for particular banks, because an incorrect format can send you searching through sensitive personal details for no reason.

Opening a file and reading transactions are separate steps. The browser can unlock a valid PDF even when its scan is too faint for accurate conversion. Inspect the preview before approving paid pages.

Choose the PDF in the upload area. If it is encrypted, the page asks for its password. Enter it exactly as the bank described, including capitalisation, spaces and separators. Press Unlock. Once the file opens, the normal page estimate and conversion controls appear; unlocking does not itself buy credits or start model processing.

The password is passed to the local PDF worker running in your browser. The worker creates an unlocked copy, and the upload path receives that copy rather than the password. The input field is cleared after success. There is no password in the upload payload or the conversion request, and it is not stored with your result. An unlocked file still contains your financial statement, so local unlocking does not make the subsequent conversion local or anonymous to its processing services.

When you choose to convert, the unlocked statement goes to the cloud reading model. Source uploads are deleted when the job ends; retained results follow the period you selected and can be deleted sooner. Read how files are handled for the distinction between the password, the uploaded document and the extracted result. This description was checked against the browser worker and upload code on 7 October 2026.

"That password did not open it" means the browser could not decrypt the PDF with the supplied value. Compare the format with the bank's own message, including whether a date needs leading zeroes. Avoid repeatedly trying account credentials: a PDF password is not necessarily your online-banking password. Do not email a password together with a statement to support.

"This PDF could not be unlocked here" can mean the PDF is damaged or uses a structure this browser worker cannot read. Download a fresh copy from the bank, or open it locally with software you trust and produce a readable copy if your bank permits that. A failed unlock does not send the document for conversion and does not consume processing credits.

After unlocking, "No transactions were found" means the reader found no usable activity rows. Check that you selected the itemised statement rather than a cover letter. An unlocked file can still have ambiguous dates, poor images or an unfamiliar layout. Review the first and last transaction, a payment and a deposit, and any balance-check flags; a matching total is not an accuracy guarantee.

Unlocking has no separate fee. Reading the first two pages a day is free. A three-page statement with that allowance unused needs one paid page: $0.25 at the $5-pack rate or $0.30 at the $3-pack rate, and includes the Excel workbook and accounting downloads. The smallest purchase is $3 for 50 credits; credits left over remain available and never expire. Taxes are shown at checkout.

A statement processed only with free pages costs 4 credits for Excel or 2 for CSV, QBO, QFX, QIF or OFX, once per result. One CSV purchase includes the full transaction table and the QuickBooks Online, Xero and YNAB layouts. There is no direct connection to an accounting account and no recorded import pass in those apps yet.

For many statements each month, compare an unlimited subscription. ProperSoft also offers local desktop processing; that may suit a document you cannot send to a cloud service. If your bank can supply CSV or OFX directly, use it instead of reading the PDF. For the next step here, follow the PDF statement review guide, bank statement to CSV or bank statement to Google Sheets.

Upload a bank statement — the PDF your bank emailed, a scan, or phone photos of the pages — and every transaction comes back as a row: date, description, money out, money in, a signed amount and the running balance. Transactions from every page land in one table, so a twelve-page statement is one list, not twelve fragments to stitch together.

Then comes the part that matters: the tool checks its own work. It adds up what it read and compares the result with the balances printed on the statement. When they agree to the cent, the extracted amounts are consistent with those balances. Offsetting errors can still cancel out, so a passing check is a useful review aid, not proof of accuracy. When they do not, it tells you by how much and flags the rows where the running balance breaks, so you check three lines instead of three hundred.

Two independent checks run on every statement.

1. Opening + money in − money out = closing. The opening and closing balances are read from the statement's summary or its first and last lines. If the transactions read in between do not produce the closing balance exactly, something is missing or wrong, and the difference is shown.
2. Row by row. Where the statement prints a running balance, each one must equal the previous balance plus that line's money in minus its money out. A break points straight at the problem: the flagged row, or the one just above it.

The arithmetic is done in whole cents, never in floating point, so a check cannot pass by rounding. Statements listed newest-first are recognised, and so are card and loan statements, where the balance is money owed and runs the other way.

A passing check shows that the extracted amounts agree with the balances that were read. It cannot rule out offsetting errors, omitted pairs of transactions, or incorrectly read balances. Check dates and descriptions, compare the row count with the source, and review important amounts before importing.

The Excel workbook has three sheets:

• Transactions — one row per transaction, in the order printed, with the page it came from and a Check column that says why a row was flagged.
• Balance checks — each check, whether it passed, and the numbers behind it.
• Statement summary — bank, the last four digits of the account, period, currency, opening and closing balances, totals, and whether it reconciles.

Amounts are stored as numbers, not text, so SUM works straight away. Dates are written as year-month-day when the statement makes the year clear, which sorts correctly everywhere. Choose the full transaction CSV to keep the review columns, or a QuickBooks Online, Xero or YNAB CSV layout for its documented import fields. All layouts share one CSV purchase for the same result. Accounting layouts leave out balances and check notes; each statement has a separate file, and multiple files download as a ZIP.

Upload several PDFs at once — twelve monthly statements, say — and they come back in one workbook with a Statement column, plus a summary row for each.

A PDF downloaded from online banking often already contains its text. That text is read with its printed column positions before a model turns it into records. This avoids recognising letters and digits from pixels, but the model can still misinterpret a column or a wrapped description.

A scanned statement, or photos of printed pages, is read from the image. That works well on a flat, straight, well-lit page. It struggles with faint thermal-style printing, pages shot at an angle, and folds across the amount columns. The balance check is your safety net here: if a digit was misread, the running balance breaks at that row.

Photos uploaded together are treated as the pages of one statement, in the order you chose them. Each PDF is its own statement.

It is built for current, checking and savings account statements, and reads card and loan statements too. It is not built for investment or brokerage statements, where a row is a holding rather than a movement of cash. If your bank locks its statements with a password, enter it when the page asks: the PDF is unlocked in your browser, the password never leaves your device, and only the unlocked copy is uploaded. Without the password the tool cannot open it and will not try to get around it.

It has not been tested against a named list of banks, and this page will not pretend otherwise. Statement layouts vary enormously; what the tool offers instead is a result you can verify. If the checks pass, the extracted numbers agree with the balances read from the source. If they fail on your bank's layout, the job tells you so plainly.

We compared the model's extracted rows with labelled, fictional statements: separate debit and credit columns, signed amounts, German decimal commas, Indian number grouping, wrapped descriptions, a dense multi-page list, a credit card, scans and phone photos. These are synthetic examples, not a certification for any named bank.

The eight text-PDF cases and two scanned-PDF cases matched every labelled date, description, amount and direction in this run. A photographed statement lost a digit from two transaction descriptions even though its balance checks passed. Review the source rows, especially long reference numbers in photos. Results can vary between runs; this test does not establish an accuracy percentage for your files, mixed-currency support or successful imports into accounting software.

Compare QBO, QFX, OFX and QIF before importing. The Xero CSV page explains its preset, while password-protected statements covers opening a PDF with your own password. For spreadsheet review, use Google Sheets. Each route uses the same converter; no accounting-app import pass is claimed.

Statements are sensitive, so here is exactly what happens. The uploaded file is sent to the reading model and deleted from storage when the job ends, whether it succeeded or not. Only the last four digits of an account number are kept. The transactions you see are stored with your job so the download still works if you come back later; use Delete this result to remove it sooner. Nothing you upload is ever published.

The first 2 pages a day are free, with the balance checks, and you can copy every row you see. That is enough to see whether the tool reads your bank's layout correctly before you pay anything.

Past that, pages are $0.25 each (5 credits, at the $5-pack rate), and a statement with paid pages gets every download free: Excel, CSV, QBO, QFX, QIF and OFX. With the two free pages still available, a six-page statement costs 20 credits for the other four pages, workbook included. If you have no credits, the smallest purchase is $3 for 50 credits, before any applicable tax; the statement uses $1.20 of it and 30 credits remain. A statement that fits inside the free pages pays only for its download: 4 credits for the workbook, 2 for the other formats, once per job. Credits never expire, there is no subscription, and a job that fails is not charged.