To convert a bank statement PDF to Excel on Mac, open Bank Statement PDF Converter, drop the PDF in, let smart transaction detection find the rows, verify the output against the original in the side-by-side preview, and export to XLSX. One statement takes under a minute for native PDFs and about one to two minutes for scanned ones. The output is a real spreadsheet — dates in date cells, amounts as numbers, descriptions intact — not the broken copy-paste soup you get when you fight this job manually. The steps below walk through the full workflow, including what to do when a scanned statement or an unusual layout throws a wrench in.
Why "copy-paste into Excel" keeps breaking
This is worth a minute because it tells you why the dedicated tool exists. Bank statement PDFs look structured to a human, but the table you see on the page is not a real table.
PDF is a presentation format, not a data format. What looks like a column is text positioned at specific x/y coordinates on the page — there's no underlying table structure the way there is in a spreadsheet. When you drag-select a transaction table in Preview and paste into Excel, you get text in one tall column with everything smooshed together, descriptions wrapping into the wrong cells, debits and credits colliding, and a wall of cleanup that takes 15–30 minutes per statement.
Multiply that by a year of statements across three accounts and you can see why a dedicated converter pays for itself on the first use. The tool reads the layout, identifies transaction rows, and writes a real spreadsheet structure — one transaction per row, stable columns, preserved signs.
What you need
- A Mac running macOS 13.5 or later (Apple Silicon or Intel)
- Bank Statement PDF Converter from the Mac App Store — free to download, free to try
- Your bank statement PDF (native or scanned)
If you also want to convert on iPhone or iPad, the iOS version handles Files, Mail attachments, and iCloud Drive with CSV, Markdown, and TXT export.
The workflow, step by step
1. Open the app and import your PDF
Launch Bank Statement PDF Converter. Drag your statement PDF onto the main window — or use File → Open — and the app loads the document with a live preview. Digital statements downloaded directly from online banking work out of the box. Scanned statements do too (see the OCR section below).
You can import a single statement, a handful selected with Cmd-click, or an entire folder. For batch folder imports, jump to the batch section.
2. Let smart transaction detection find the rows
The app scans the PDF, identifies the transaction table, and pulls out dates, descriptions, amounts, and running balances. It works across formats because it reads content semantically rather than relying on per-bank templates — no pre-loaded list of "supported banks," no configuration step.
Detection takes a few seconds on a native PDF. For scanned or OCR-heavy statements, allow a little more time while the image is processed.
3. Review side-by-side with the original
This is the step that separates a usable export from "trust me, it's fine." The Mac workspace shows the original PDF on one side and the extracted transaction table on the other. Click any row in the table and the PDF preview scrolls to the matching line in the source.
Walk through the rows quickly and check:
- Signs preserved. Debits as negatives (or in the debit column), credits as positives.
- Dates parsed correctly. US banks use MM/DD/YYYY; UK and most EU banks use DD/MM/YYYY. Dates from the 1st to the 12th are ambiguous without context — the detector handles this, but spot-check the first couple of rows.
- Descriptions intact. A merchant description that wraps across two physical lines should still be one row in the output.
- No summary rows. If the extractor picked up statement totals or "running balance" rows, switch on transactions-only mode to strip them.
Transactions-only mode is the fastest shortcut to a clean export — it hides statement headers, footers, account summaries, and legal disclaimer boilerplate, leaving only the rows that belong in a reconciliation sheet.
4. Pick your output format
Click Export. The app writes the same underlying transaction data to whichever format you pick. For Excel, pick XLSX — dates land in date cells, amounts as numbers, descriptions as text. No "numbers stored as text" warning, no "convert to date" babysitting.
5. Verify the totals
One last sanity check before you move on. Sum the amount column in Excel and compare to the statement's ending balance (or the net change for the period). If the totals match, you're done. If they don't, jump back into the app, re-check any row with an unusual description — OCR occasionally drops a character on scanned statements — and re-export.
Keep the original PDF. The spreadsheet is a working copy for analysis; the PDF is the source of truth for any audit, tax, or compliance question.
The format matrix — XLSX, CSV, TSV, Markdown, XML, TXT
Most converters cap you at XLSX and CSV. The Mac app writes all six of these from the same extraction, so you can pick by use case instead of running the conversion twice. On iOS, the exports are CSV, Markdown, and TXT.
| Format | Best for | Why |
|---|---|---|
| XLSX | Excel and Numbers review | Typed cells (date, number, text), filters, and handoff to accountants |
| CSV | QuickBooks, Xero, Wave, FreshBooks imports | Universal; every bookkeeping tool reads it |
| TSV | Pasting into text tools that choke on commas in descriptions | Tab-separated — no quoting weirdness around merchant names |
| Markdown | Notes, docs, Notion/Obsidian, wiki handoff | Human-readable table you can drop straight into a note |
| XML | Structured pipelines, custom automation | Strict schema for scripts that parse bank data programmatically |
| TXT | Archiving, diffing, scripting | Plain text is the most portable long-term format |
Two common pairings: CSV + XLSX (CSV for the accounting import, XLSX for the human-facing review copy), or XLSX + Markdown (Excel for the accountant, Markdown for the internal notes you'll share with your bookkeeper over Slack).
Scanned statements and OCR
If your statement is image-based — a photograph, a fax, or a scanned archive — the app runs OCR automatically. A few practical tips:
- Scan at 200–300 DPI, grayscale or color. Anything lower eats the decimal points; anything higher wastes time.
- Flatten rotated pages. If a page imported upside-down or sideways, rotate it in Preview before you feed it in.
- Crop dark margins. Heavy black borders confuse layout detection. Trim them in Preview's Markup toolbar.
- Double-check signs. OCR occasionally drops a minus sign. Always reconcile the total against the statement's ending balance.
For a deeper dive on scanned statement workflows, see the dedicated scanned statement guide.
Batch a whole folder of statements
For year-end tax prep, a client handoff, or a month-end close across multiple accounts, single-statement workflows get tedious fast. The Mac app batches an entire folder in one pass.
- Organize the folder. Keep the PDFs for a single account together —
/Client-A/Chase-Checking/2025/, for example. The app applies consistent extraction settings to every file in the batch, which works best when the statements share a format. - Drag the folder onto the app window (or use File → Open Folder).
- Pick per-file output or merged workbook. Per-file gives you 12 XLSX files (one per month) with identical columns. Merged produces a single workbook with one sheet per statement — useful for building a full-year pivot.
- Kick off the run. The app processes files in the background while you do other work; you get a notification when every statement is done.
- Spot-check the outliers. Review the first and last statement of the batch end-to-end; spot-check the middle ones.
Common snags and how to fix them
Wrapped merchant descriptions
A single merchant name ("AMAZON WEB SERVICES CLOUD COMPUTING") wraps onto two lines in the PDF. Smart detection keeps it as one row in the output by default. If it ever splits, re-run with transactions-only mode off and merge the rows manually in Excel.
Mixed date formats in the same PDF
Some statements include a short-form date in the transaction row and a full "posted date" in small print — the app uses the transaction date by default. If your downstream tool wants the posted date, switch columns in the app before exporting.
Credit card statements with summary and detail blocks
Credit card statements often put payment summary, interest, fees, and transactions all on the same page with similar layouts. Transactions-only mode strips the summary block; check the extracted rows against the "Transactions this period" section of the source PDF.
Multi-currency statements
If your statement mixes currencies (some UK and EU business accounts do), the app captures the currency symbol in the description but writes the numeric amount into the amount column. Add a Currency helper column in Excel if you need to pivot by currency.
Where this fits in a bigger workflow
A PDF-to-Excel conversion is usually one step in a longer job. Common downstream uses:
- Month-end reconciliation. Convert the statement, match rows against your ledger, flag exceptions. Full SOP in the month-end reconciliation guide.
- Tax prep. A year of statements into one workbook with a Category column and a SUMIF per category.
- Retailer review. Pull all Amazon, Apple, or Stripe charges into one tab for refund and subscription review.
- Handoff to an accountant. An XLSX with one sheet per month beats emailing 12 PDFs.
For the full comparison against other Mac options, see the best converter for Mac in 2026 guide. For the official Excel number-format primer, Microsoft's number-formats documentation is the canonical reference.
Get the Mac app
Bank Statement PDF Converter is free to download and free to try on real statements. If you also convert on the go, pair it with the iPhone and iPad app — same extraction, CSV/Markdown/TXT export.
Download on the Mac App Store · Get the iPhone and iPad version
FAQ
How do I convert a bank statement PDF to Excel on Mac? +
Open Bank Statement PDF Converter on your Mac, drop in the PDF, let smart transaction detection find the rows, verify the output against the original PDF in the side-by-side preview, and export to XLSX. The whole process takes under a minute per statement for native PDFs and roughly 1–2 minutes for scanned ones.
Why does copy-pasting a bank statement into Excel break the columns? +
Because tables in PDFs are not real tables. PDF is a visual layout format — what looks like a column is just text positioned at specific x/y coordinates. When you paste into Excel, the text lands in one tall column and you end up re-aligning every row by hand. A dedicated converter reads the layout, finds the transaction table, and writes a real spreadsheet structure.
Can I convert scanned bank statement PDFs to Excel on Mac? +
Yes. Bank Statement PDF Converter runs OCR automatically when it detects an image-based PDF. For best results, scan at 200–300 DPI in grayscale or color, and flatten rotated pages before you import.
How do I batch-convert a folder of bank statement PDFs? +
On the Mac app, open the folder picker or drag an entire folder of PDFs onto the window. The app queues every file, applies the same extraction settings to each, and produces individual XLSX files (or a merged workbook) with consistent columns across every statement. Ideal for year-end prep and month-end close.
XLSX, CSV, TSV, Markdown, XML, or TXT — which format should I export? +
XLSX for Excel and Numbers review. CSV for importing into QuickBooks, Xero, Wave, or any bookkeeping tool. TSV for pasting cleanly into text-based tools that choke on commas. Markdown for docs and notes. XML for structured pipelines. TXT for scripts and raw archiving. Bank Statement PDF Converter writes any of them from a single extraction on macOS.