Bank statement converter FAQ

A bank statement converter reads the transaction table in a bank statement PDF and turns it into structured rows – date, description, debit, credit and balance – that you can open in Excel, Google Sheets or accounting software. FinParse does this directly in your web browser.

Upload the PDF using the converter on the home page. FinParse reads each page, detects transaction rows and shows them in a table. Check the rows, edit anything that needs correcting, then click “Download Excel” to save an .xlsx file.

No. The PDF is read and processed by JavaScript running in your browser tab. The file and the extracted transactions are not sent to our servers or to any third-party service. The website itself is served like any other website, so your browser does request its pages and scripts.

Yes, with limits. If a PDF contains only images, FinParse offers optional text recognition (OCR) that runs in your browser. The OCR engine is about 7 MB and loads the first time you use it. Up to 25 pages are processed, and accuracy depends on scan quality, so review scanned results carefully. A digital PDF downloaded from online banking gives the best results.

Yes. After reviewing the transactions, click “Download CSV”. The file uses UTF-8 encoding, comma separators, ISO dates (YYYY-MM-DD) and plain numbers, so it opens cleanly in Excel, Google Sheets, Numbers and most accounting imports.

Yes. FinParse is free to use and does not require an account. There are no conversion limits beyond the technical file limits shown in the upload area.

FinParse uses a general-purpose parser rather than bank-specific templates. It works best with text-based PDFs where each transaction row starts with a date and amounts have two decimal places, including layouts with separate debit and credit columns or a single signed amount column. Because layouts vary widely, some statements may not convert correctly; you will see a clear message if no transactions are detected.

Yes. You can search, sort and filter the table, edit or delete any row, add missing transactions, and reset to the originally extracted rows. Rows that fail a balance check are marked for review.

No. FinParse does not store your PDF or transactions in a database, cookies, localStorage or any other browser storage. The data exists only in the memory of your open tab and is cleared when you remove the file, convert another statement or close the tab.

Yes. The converter works in modern mobile browsers, and the transaction table switches to a card layout on small screens. Very large statements and OCR are faster on a desktop or laptop because they need more memory and processing power.

PDFs up to 100 MB and 150 pages can be processed. These limits keep conversion reliable inside a browser. For longer statements, download shorter date ranges from your bank.

Yes. If a PDF is password-protected, FinParse asks for the password and uses it only to open the file in your browser. The password is not stored or sent anywhere.