Convert bank statement PDF to Excel on iPhone (2026)

Your bank emails you a PDF every month. Twelve of them sit in Mail right now, unread for the purpose you actually need them: dropping the transactions into a spreadsheet so you can categorize spending, reconcile against a card, or hand a clean ledger to an accountant.

Doing this on a Mac is annoying. Doing it on an iPhone — where the PDFs already live, in Mail or Files — has historically been worse. The web tools want an upload. The Shortcuts app can’t really parse a layout. And the one thing you absolutely do not want to do with a PDF that contains your account number, your address, and twelve months of where you spent money is paste it into a free converter run by a company you’ve never heard of.

This walkthrough covers the workflow that actually works in 2026: extract bank-statement PDFs to Excel on iPhone — the statement file read on-device, never uploaded.

Why bank statements are uniquely hard

“PDF to Excel” sounds like one task. With bank statements it’s at least four overlapping ones, and most converters only solve the easiest:

1. Header noise. The first page has a logo, an address block, an account summary, marketing copy. The transaction table doesn’t start until midway down. Naive extractors grab everything and you spend ten minutes deleting rows.
2. Multi-line transactions. Many banks wrap a single transaction across two or three lines — merchant name on line one, location and reference number on line two, foreign-currency conversion on line three. The output should be one row per transaction, not three.
3. Debit/credit columns vs. signed amount. Some statements have separate Debit and Credit columns. Some have a single signed Amount. Some put deposits on the right and withdrawals in red. To do anything useful in a spreadsheet you need a single signed numeric column — and the extractor has to figure out the convention.
4. Running balance. Almost every statement has one, and it’s the easiest column to misalign because it’s right-justified and visually identical to amounts. Get this wrong and your reconciliation will be off by exactly one row, which is the worst possible failure mode.

A tool that handles only case 1 — the clean text-based PDF — is useless for the cases that actually waste your time. The right approach treats extraction as a language task: ask a model to find the transactions and return them in a defined shape, rather than trying to reverse-engineer table coordinates.

Why on-device matters for this specific document type

If you’re converting a textbook PDF or a research paper, “upload to a free web tool” is fine. Bank statements are a different threat model:

• They contain your full account number (or at minimum the last four plus enough metadata to be linkable).
• They reveal your monthly cash position, your employer, your landlord, and the names of every business you frequent.
• Most free web converters’ privacy policies explicitly allow them to retain uploaded files for “service improvement,” and the smaller ones don’t even pretend.

ignitai reads the statement on-device: the PDF itself is never uploaded, never sits in a web tool’s queue, never lands in a stranger’s storage bucket. Only the text recognized on the phone is sent to ignitai’s private hosted pipeline to build the XLSX. On iOS 26, Apple’s newest on-device document recognition reads the transaction tables natively, which makes the extraction noticeably sharper.

On iOS 17.4 through 18 — every supported version before 26 — the same flow works with Apple’s classic on-device text recognition; the file still never leaves the phone.

Method 1: ignitai (the no-upload way)

The full flow on iPhone, end to end:

1. Open the PDF in Mail or Files. Tap the share sheet. Pick ignitai from the share menu. (If you don’t see it, scroll right in the share sheet and tap “Edit Actions” to enable it.)
2. Describe what to extract. For a bank statement, the prompt that works for almost every US/EU bank format is something like: “For each transaction, return date, description, amount as a signed number (negative for debits), and running balance. Skip header rows and account summaries.” You can save this as a preset — ignitai keeps a library of prompts, so the second statement you process is one tap.
3. Pick XLSX as the output format. (CSV works too, but XLSX opens directly in Numbers or Excel for iOS with every field in its own column — no import dialog.)
4. Hit Convert. A typical 12-page statement takes seconds, with live progress as it runs.
5. Review the preview. ignitai shows a paginated table view of the extracted rows before saving. Spot-check the first few transactions, the last few, and any that look unusual — wrong-signed amounts and split rows are the two failure modes worth catching.
6. Save to Files. Drop it in iCloud Drive, OneDrive, or Dropbox. From there, Numbers, Excel for iOS, or Google Sheets will open it natively.

The whole thing fits in roughly 30 seconds of actual user time per statement. For twelve statements, see the batch section below.

Method 2: Files app + Numbers (if you only have one)

If you genuinely only have one statement and you don’t want to install anything:

1. Open the PDF in Files.
2. Tap and hold to select the text in the transaction table. iOS will let you copy it.
3. Open Numbers and paste into a new sheet.
4. Split the columns by hand — Numbers has no Text to Columns command, so the cleanup is manual.

This is brittle. It only works on text-based PDFs (not scans). Multi-line transactions will land on multiple rows and you’ll need to merge them by hand. Debit/credit columns will probably collapse into one. For a single one-page statement, fine. For anything more, the hand-cleaning time will exceed the time it would take to just install a real converter.

Method 3: AirDrop the PDF to a Mac

If you happen to have a Mac nearby and don’t need this workflow to be iPhone-native, AirDrop the PDF and follow the Mac walkthrough instead. The Mac version of ignitai handles batch jobs in a single drag-and-drop and has a wider screen for reviewing the output.

This is a perfectly fine fallback. The reason this guide exists, though, is that for most people the PDF arrives on their phone, gets read on their phone, and ideally gets dealt with on their phone — context-switching to a Mac for a 30-second task is its own friction.

Method 4: Web converters (and why not for this)

You can find half a dozen “PDF bank statement to Excel” web tools by searching. They work, in the technical sense. The reasons not to use them for this specific document:

• You’re uploading. Even the ones with “private” or “secure” in the name are sending your file to a server you don’t control. For a bank statement this is unambiguously bad.
• They monetize the free tier with friction, not by actually being free. Expect rate limits at 1–3 files/day, watermarks, or download caps that conveniently push you to a paid plan after the third statement.
• Most don’t handle multi-line transactions or debit/credit columns properly. They were designed against a generic “table in a PDF” assumption, not bank-specific layouts.

If the document is genuinely public — a synthetic statement, a sample, a tutorial fixture — they’re fine. For your actual finances, no.

Cleaning the output: the three details that matter

Once the XLSX is in Numbers or Excel, three quick checks separate “I have a file” from “I have a usable ledger”:

1. Sign convention. Open the amount column. Sort ascending. The negative numbers should all be debits (purchases, withdrawals, fees) and the positive numbers should all be deposits. If any positive number is a debit or vice versa, your prompt needs tightening — re-run with explicit instruction like “deposits are positive, all other transactions are negative.”
2. Date format. Bank PDFs use everything from 04/17/26 to 17 Apr 2026 to 2026-04-17. Standardize on ISO (YYYY-MM-DD) before doing any date arithmetic. In Numbers, select the column → Format inspector → Date & Time, then create a custom YYYY-MM-DD format.
3. Running balance sanity check. Add a column: =previous_balance + amount. It should equal the extracted running balance for every row. Where it doesn’t, you’ve found a missed or duplicated transaction. This single check catches almost every extraction error.

If you skip step 3 you’ll find out about a misread row when your reconciliation is off by $47.83 and you have no idea where to look. Five minutes here saves an hour later.

Batch mode: a year of statements in one pass

The real win is when you have twelve statements (or twenty-four, or all of last year for tax season) and you want one consolidated XLSX, not twelve separate ones.

On iPhone, the workflow is:

1. In Files, select all the PDFs. Hit Share → ignitai.
2. Apply the same extraction prompt across the batch (or pick a saved preset).
3. ignitai reads them on-device and produces a single consolidated XLSX. Ask for account_last_four and statement_period columns in the prompt — pulled from each statement’s own header — so every row stays attributable to its statement.
4. Save once. Open in Numbers. You now have a year of transactions in one sheet, ready for a pivot table by month or category.

For tax prep this is the difference between an evening and a weekend. For monthly budgeting it’s the difference between actually doing it and not.

When this workflow doesn’t fit

Be honest about edge cases:

• Brokerage statements with positions, lots, dividends, and corporate actions are a different beast. The transaction-extraction prompt above won’t capture the structure — the iPhone brokerage-statement guide has the prompt built for it. (If your broker offers a CSV download in account settings, that’s also worth checking first.)
• International statements with mixed-currency transactions need a slightly richer prompt — ask for original_amount, original_currency, and converted_amount as separate columns. ignitai handles the prompt; the bank’s PDF format is the variable.
• Crypto-exchange “statements” are usually CSV-native to begin with. Don’t extract from a PDF screenshot of one.

Bottom line

For one bank statement, on iPhone, that you don’t want to upload anywhere: install ignitai, hit Share → ignitai, save the XLSX. For a year of them, the same workflow batches transparently. For the actual edge cases — brokerage, crypto, mixed currency — fall back to native exports where the bank offers them.

The point of doing this on iPhone specifically is that the PDFs are already there, the on-device document reading means the file itself never has to move, and the Mac workflow is one AirDrop away if you want the bigger screen for review. Pick the one that matches where you actually are when the email arrives.

Get ignitai on the App Store — free download, $19.99/mo unlocks unlimited extractions and batch mode after the 3-day trial.

FAQ

How do I convert a bank statement PDF to Excel on iPhone?

Open the statement in Mail or Files, share it to ignitai, describe the columns in plain English, pick XLSX, and tap Convert. The statement is read on the phone and a clean Excel sheet lands in seconds.

Does the statement leave my iPhone?

The PDF itself never does — it is read on-device and never uploaded. Only the text recognized on the phone is sent to ignitai’s private pipeline to build the sheet.

How do I verify the Excel rows are correct?

Open the sheet in Numbers or Excel and run the balance tie-out: opening balance plus the sum of the amount column must equal the printed closing balance to the cent. A mismatch means a missed or misread transaction — tighten the prompt and re-run.