PDF Bank Statement to Excel Converter

A bank statement PDF has no table inside it — only text positioned at coordinates on a page, and every bank lays those coordinates out differently. Copy the data by hand or through a generic PDF-to-text tool and multi-column layouts collapse into one long column, the letterhead and footer repeat on every page so a 12-page statement gives you the same "transactions" a dozen times, a wrapped description becomes an orphan row with no date or amount, and the debit sign — a trailing minus, parentheses, or plain text with no minus at all — gets dropped or read backwards.

• Columns collapsed back into columns. This tool reads the position of every text fragment on the page and regroups the ones on the same line, left to right — rebuilding each row the way your eye already reads it.
• Repeated headers and footers filtered out. Lines that repeat across pages, or carry neither a date nor an amount, are never treated as transactions.
• Wrapped descriptions rejoined. A continuation line with no date of its own is merged back onto the transaction above it instead of becoming a blank row.
• Every negative-sign convention normalized. Parentheses and a leading or trailing minus are all read as negative and written into one signed Amount column, so Excel totals come out right without manual fixing.
• The running balance kept separate. The last number on a line is almost always the balance carried forward, not part of the transaction — it's recorded on its own and used for the balance check below instead of being summed into your totals.

Every other tool that solves this exact problem works the same way: you upload your PDF to its server, it runs the extraction there, and streams a file back — so your account number, balance and every transaction sit, even briefly, on infrastructure you don't control, for a task that is really just re-reading a file you already have. This tool does it the other way round: a PDF engine running inside your own browser tab reads the file, JavaScript on your machine rebuilds the rows, and the output goes straight to a download — no round trip. Open your network panel while converting and watch it stay empty.

• Text-based PDFs work; scanned ones don't. A statement exported or printed "to PDF" has a text layer this tool can read. A photograph or scan is only a picture of text, and this tool will not quietly send it to an OCR server to fake a result — if you can't select the text in a normal PDF viewer, it won't work here either.
• Layouts vary between banks. This tool reads position and pattern rather than a per-bank template, which covers most statements but not all of them. Always check the preview table and the balance check below before importing a file into your books.
• Nothing is uploaded, ever. Not to check the layout, not to "improve accuracy" — the file never leaves the tab it was opened in.

QuickBooks Desktop only accepts a .qbo file when its INTU.BID matches a financial institution it recognises — your bank's real value normally appears in any statement it has imported before, but a PDF carries no such identifier, so this converter fills in a placeholder. If QuickBooks rejects the file with "this bank isn't set up for download," use the OFX download instead: it has no such requirement and imports directly into Quicken, Xero, Wave, MoneyMoney and most other accounting software.