Convert bank statement PDF to Excel

The point of converting to Excel — not CSV — is that you want to open the file and start working. So the workbook is built for that.

Dates land in column A as Excel date values, which means date filters, MONTH() and YEAR() formulas, and pivot-table time grouping all work on the file as delivered. Amounts sit in column C as numbers with decimal places, which means SUMIF, conditional formatting, and negative-value highlighting work without a "convert text to number" dance first. Balance is the running balance printed on the statement, forward-filled when the bank only prints it on the last row of the day.

Header row is frozen so it stays visible while you scroll. Autofilter dropdowns are pre-installed on every column. No macros, no hidden sheets, no worksheet protection — the file is plain enough to open cleanly in Apple Numbers, Google Sheets, LibreOffice, and older Excel versions.

This is the reason Excel exists for you instead of CSV. Once the columns are typed correctly (we do that), every native Excel feature works on the file without setup.

A few pivots worth trying on a month's statement:

• Top merchants. Description → Rows, Amount → Values (Sum). Sort descending. Your top 10 outflows surface in 20 seconds.
• Category snapshot. Add a column called "Category," type it manually or use VLOOKUP against a cleaned merchant list, then pivot on Category instead of Description. First useful monthly budget in one sitting.
• Day-of-week spend. Insert a helper column =WEEKDAY(A2, 2), pivot on it. Tells you which day of the week your discretionary spend clusters on.

None of these require formulas beyond what ships with Excel. The workbook is the starting point, not the finished artifact.

Every Transactions sheet we return has the same four columns in the same order. That's on purpose — it makes multi-month consolidation trivial.

Two common workflows:

• Manual append. Open last month's workbook, open this month's, copy rows from this month, paste below. Autofilter adapts, pivots refresh on F5.
• Power Query. In a new workbook, Data → Get Data → From Folder. Point it at the folder where you save monthly conversions. Power Query stacks the sheets and refreshes on command when a new file lands. The column types hold because we wrote them correctly on the way out.

For year-end or quarterly reviews, this scales to 12 or 24 months without reformatting once. If you process statements for clients, the accountants use case walks through the multi-client version of this flow.

A dedicated parser knows where a specific bank places value dates, how it handles multi-line merchant names, and whether it splits withdrawals and deposits across columns. That matters for Excel output because bad row detection leaves gaps in the running balance and breaks pivot accuracy.

When your bank has its own page under /convert/[bank]-to-excel, we've already tuned for those quirks. When it doesn't, the generic parser takes a first-page read, infers the column layout, and applies it across the file. If extraction fails, you see a "we couldn't read this" message and the free-tier credit isn't used.

Three high-traffic bank converters:

We don't gate the preview. You see the workbook before you pay anything — if the extraction is wrong, don't buy.

The paid options:

• Pay-per-document — $2.99. One statement, one workbook, no subscription.
• Starter — $29/month, 500 pages. For someone converting their own statements every month.
• Professional — $49/month, 1,000 pages. Batch upload. Most accountants and bookkeepers sit here.
• Business — $79/month, 5,000 pages. Batch upload + API access for firms running dozens of clients.

If you're reading this page with month-end close in mind, Professional is usually where you land. Pay-per-doc works fine for one-off file rescues. Full tier details on the pricing page.

A handful of details that matter when the file leaves your machine:

• Version safe. Saved as .xlsx (2007+), not .xlsm. Corporate email filters that strip macro files let this through.
• No external references. The workbook doesn't link to any local file or network path, so it renders identically on your accountant's machine.
• Numbers app and Google Sheets safe. Real Excel dates and typed numbers round-trip through both without losing format.
• Track changes if you use OneDrive or Google Drive. Upload the workbook once per month, and the cloud copy handles version history without you doing anything.

For client-facing workflows, the accountants use case covers the handoff in more detail — naming conventions, multi-client folder structures, and how to label categorized versions.

If you close the tab before downloading, the workbook is held for 24 hours — reopen the URL you got and it's still there. Need longer? Signed-in users can bump retention to 72 hours per file in account settings, which is useful when a client takes a few days to confirm the extraction before you archive the workbook on your side. After the retention window, the file is deleted and not recoverable on our side. Storage is encrypted at rest for the duration.

If you're processing client statements, the security and compliance page carries the full retention, access control, sub-processor, and region detail that your firm's compliance reviewer will want.