Skip to content
ignitai
Get the app
← Back to blog · · 14 min read

Convert credit card statement PDF to Excel on iPad

Turn monthly credit card statement PDFs into a clean Excel workbook on iPad — statements read on-device, never uploaded — merchants normalized, categories ready.

guides credit-cards ipad budgeting

ignitai turns PDF bank, card, and brokerage statements into a clean transactions spreadsheet on your iPad — your first conversion is free, then $19.99/mo after a 3-day free trial.

Download on the App Store ignitai — free download

The Amex bill arrived in Mail this morning. The Chase Sapphire statement landed yesterday. The Apple Card monthly statement is in Wallet on your iPhone (or a download away at card.apple.com). Three PDFs, three different layouts, and one budgeting spreadsheet that’s been waiting for last month’s numbers since the second of the month. You’re on the couch. The Mac is upstairs. The iPad is in your lap and the PDFs are right there in Mail.

The iPad is, for this specific job, the right tool. The screen is big enough to read a forty-line statement without zooming. The keyboard is good enough for the spot-checks. And ignitai can read three statements from three issuers on-device and write one consolidated Excel workbook — the statement files are never uploaded.

This guide is the workflow that gets you from “three credit card PDFs in Mail” to “one Excel workbook on its way to my budget tool” without uploading the merchant pattern of your spending to a free-tier web converter, and without waiting until you’re back at the Mac.

Why credit card statements aren’t just bank statements

The iPad bank-statement guide handles checking-account PDFs. A credit card statement looks superficially the same — date, description, amount — but structurally it’s a different document with different extraction needs:

  1. Merchant descriptions are dirtier. A checking-account statement shows wire transfers, ACH credits, payee names you set up yourself. A credit card statement shows merchant strings as the network passed them: SQ *BLUE BOTTLE COFFEE, TST*PIZZA HOUSE PHX 0431, AMZN MKTP US*PB4XD8RC2. The same coffee shop you visited three times can appear as three different strings.
  2. Fees and interest live in their own band. Bank statements show fees as line items in the same table as transactions. Credit card statements typically separate fees and interest into a “Fees” and “Interest Charged” section that visually looks like the transactions table but isn’t part of it. A naive table extractor either drops these or mashes them into the main charge list.
  3. Payments are credits, charges are debits. On a bank statement, debit is money out. On a credit card statement, debit-side is the new charge, and credit-side is your payment to the card — the opposite sign convention. A consolidated spreadsheet across both account types needs explicit transaction_type columns, not just signed amounts.
  4. Categories are inferable. Credit cards charge by merchant, and merchants have categories: BLUE BOTTLE COFFEE is food/dining, UNITED 0163 is travel, APPLE.COM/BILL is software/subscriptions. Bank statements are usually just transfers and a few direct deposits. A credit card extraction wants categorization built in; a bank extraction usually doesn’t.
  5. Statement periods don’t align with calendar months. Amex closes around the 15th. Chase closes around the 6th. Apple Card runs the calendar month. A budget that wants “April spending” needs to filter on transaction date, not statement issue date. Putting the statement period in metadata and the transaction date on every row is the only way to make multi-card aggregation work.

A tool that solves the bank-statement case but misses the credit-card-specific structure produces a spreadsheet that’s superficially right and quietly wrong: payments and charges with the same sign, fees buried inside merchant rows, and BLUE BOTTLE COFFEE split across four merchant-name spellings in your monthly pivot.

Why iPad (not iPhone, not Mac) for credit card statements

The iPhone could do this — capture statement PDFs in Mail, share to ignitai, get back an XLSX. The Mac could do this — drag the statements onto a window, get the same result. The iPad is the sweet spot for the credit-card-statement workflow specifically:

  • Statements arrive monthly, not weekly. This isn’t a daily flow. It’s an end-of-statement-cycle review, three to five times a month as the issuers close their periods. The iPad is the device people pick up in the evening when “review my spending” finally surfaces on the to-do list.
  • The page is big enough to verify. A forty-line statement on an 11-inch or 13-inch iPad shows the source PDF and the extracted rows side by side in Split View. Spot-checking thirty merchant rows takes two minutes; on the iPhone it’s six, on the Mac it’s two but the Mac is upstairs.
  • Apple Card statements reach the iPad in one hop. There is no Wallet app on iPad (through iPadOS 26), but the monthly statement PDF downloads from card.apple.com in Safari on iPad — or AirDrops over from Wallet on your iPhone in two taps. Either way it lands in Files, and from there you share it into ignitai, get the XLSX back, and feed the budget — all without leaving the couch. Same for Mail with Amex and Chase PDFs.
  • iCloud Drive sync to the budget workbook. Whatever your destination — a Numbers budget, an Excel workbook for YNAB or a custom spreadsheet, a CSV to feed a budgeting tool — the iPad writes the XLSX to iCloud Drive, the Mac sees it instantly, and the iPhone sees it on the next sync.

The iPhone wins for the one-off statement that demands attention now. The Mac wins for the year-end consolidation across twelve months of statements. The iPad is right for the monthly rhythm.

Method 1: ignitai from the iPad share sheet (the main path)

ignitai handles credit card statement extraction as a language task: take the PDF, describe the schema you want, get back a structured XLSX. From the iPad share sheet:

  1. Open the statement in Mail. Tap the PDF attachment. If the source is Apple Card, download the monthly statement PDF from card.apple.com in Safari on iPad, or AirDrop it over from Wallet on your iPhone — there is no Wallet app on iPad.

  2. Tap the share button. On the PDF preview, top-right.

  3. Pick ignitai from the share sheet. Long-press to pin it to the top row if you’ll do this every month.

  4. Apply the saved credit card prompt. First time, write it once. The prompt that works across Amex, Chase, Citi, Capital One, Apple Card, and most US issuers:

    *“Return one row per transaction with: transaction_date (ISO 8601), post_date (ISO 8601), merchant_raw (the original string as printed on the statement), merchant_normalized (the canonical merchant — collapse ‘SQ BLUE BOTTLE COFFEE’, ‘BLUE BOTTLE PHX’, ‘BLUE BOTTLE #4 PHX’ to ‘Blue Bottle Coffee’), category (one of: dining, groceries, transportation, travel, lodging, entertainment, subscriptions, shopping, utilities, healthcare, fees, payment, other), amount (positive for charges, negative for payments and credits), transaction_type (one of: charge, payment, credit, fee, interest), card_issuer, last_four, and statement_period_end (ISO 8601).”

    Save the prompt as a preset called “Credit card → budget workbook.” Next month it’s one tap.

  5. Pick XLSX as the output format. One sheet, one row per transaction, with the card and period columns keeping each row attributable. Values arrive as clean text — your budget workbook’s column formats type them on paste.

  6. Hit Convert. ignitai reads the PDF on-device and sends only the recognized text to its private pipeline. A 2–4 page statement extracts in seconds.

  7. Save to Files. Drop into the iCloud Drive folder where the budget workbook lives. Three statements in a sitting means three XLSX files; merge them in Excel for iPad afterward, or have ignitai output to a single workbook by selecting all three PDFs at once via the share sheet’s multi-select.

The whole flow per statement, end to end, takes about thirty seconds. Three statements is ninety. Compare to the manual path — typing thirty merchant rows × three statements × at least ten seconds each — and the math is obvious.

Why XLSX (not CSV) for credit card statements

For bank statements going into QuickBooks the right output is CSV. For credit card statements going into a personal budget the right output is usually XLSX, for three reasons:

  1. One workbook, not loose files. A statement month lands as a sheet you append straight into the budget workbook you already keep, next to the pivots and formulas that live there. CSV is loose single-table files you re-import every month.
  2. Your workbook’s formatting does the typing. The category dropdown, the currency format on amount, the date format — set them once in the budget workbook and the appended rows inherit them. CSV round-trips strip that context every time.
  3. Pivot tables for the budget review. “How much did I spend on dining at Blue Bottle this quarter?” is a pivot table grouped by merchant_normalized × month filtered to category = dining. The workbook preserves the pivot between months; CSV is just numbers.

If your destination is YNAB, Monarch, Copilot, or another budgeting app’s CSV import, output CSV instead — same prompt, different format selector. For a spreadsheet-native budget, XLSX wins.

Method 2: Apple Card’s built-in CSV export (no install, via iPhone)

If you only have Apple Card and want a no-install path, skip PDF extraction entirely — Apple Card exports its transactions as CSV. The export lives in Wallet on the iPhone (there is no Wallet app on iPad, and card.apple.com shows statements and PDFs but no documented CSV export):

  1. On your iPhone, open Wallet → tap the Apple Card → tap Card Balance.
  2. Scroll to Statements and tap the month you want.
  3. Tap Export Transactions → choose CSV. Exports are one statement month at a time.
  4. AirDrop the CSV to the iPad (or Save to Files → iCloud Drive, and it’s already there).
  5. Open the CSV in Numbers on iPad. Date, merchant, category (Apple’s own categorization), amount, and type come through clean.
  6. Merchant strings still arrive as the raw network strings on some rows — merge variants by hand if you pivot by merchant.

This covers Apple Card only. Amex, Chase, and Citi don’t offer an equivalent CSV from their statements — their PDFs still need the extraction path. Single-card households on Apple Card alone can run this every month in a few minutes. Multi-card households can’t.

Method 3: web converters (and why not for credit cards)

A dozen “PDF to Excel” web tools exist. From the iPad they’re worse, not better, than the desktop versions, and for credit card statements specifically they’re the wrong posture:

  • Upload speed and reliability over LTE. A 2 MB credit card PDF over LTE on a train is a noticeable wait; on a flaky connection it just times out.
  • Privacy. A credit card statement is a complete merchant-by-merchant map of your spending — exactly the document type you don’t want passing through a free-tier converter whose terms say “we may use submissions to improve our service.” With ignitai the statement file never leaves the iPad — it’s read on-device, and only the recognized text goes to the private pipeline.
  • No category awareness. Web converters extract tables. None of them know that SQ *BLUE BOTTLE is a dining merchant. The categorization is yours to add after, which is the slow part — and it’s the part ignitai collapses into the original prompt.
  • Free-tier gating. Two to five files free per month, then a recurring fee. Three statements a month is right at the limit; year-end consolidation across twelve months puts you well over.

For a tutorial PDF with no real spending data, fine. For the actual merchant detail of your last month, no.

Method 4: Excel for iPad’s built-in capture

Excel for iPad has no “Get Data from PDF” — Power Query’s PDF import is Excel-for-Windows-only, and Excel’s mobile apps can’t ingest a PDF at all. The one built-in capture path is Insert Data from Picture: photograph a printed table (or pick a screenshot) and Excel OCRs it into cells, flagging low-confidence reads for manual review. Two reasons it’s not the right tool for credit card statements:

  1. It doesn’t take PDFs. A statement PDF would need screenshotting page by page, one table per capture.
  2. It captures a raw grid, not a statement. You get merchant_raw as the only merchant column — no categorization, no normalization, and the fees and interest bands either mixed in or missed. The post-capture cleanup undoes the time savings.

For a paper receipt you’re holding it’s a workable one-off. For statements that arrive as PDFs, ignitai takes the file as-is, keeps it on the iPad, and adds the categorization the budget actually needs.

The three reconciliation checks per statement

Once the XLSX is written and opened in Excel for iPad, three quick checks separate “I have a file” from “I have a row I can trust in my budget”:

  1. Statement total reconciliation. Sum the amount column for the statement. It should equal the statement’s new_balance minus the prior balance plus any payments, minus any credits — the same identity the issuer prints at the top. If the sum diverges, a transaction was missed or duplicated on extraction. Sort by transaction_date and scan for gaps in the date sequence.
  2. Payment sign sanity. Payments should be negative; charges should be positive. Filter transaction_type = payment and confirm all rows have negative amounts. A payment that landed positive will inflate the spending total when you pivot. A charge that landed negative will silently hide that month’s biggest purchase.
  3. Merchant normalization spot-check. Pivot the transactions sheet by merchant_normalized. Look for variants of the same merchant that should have merged: Blue Bottle and Blue Bottle Coffee as separate rows, Amazon and Amazon Marketplace split, Apple Inc. and APPLE.COM/BILL separate. Edit the column to consolidate, then update the saved prompt to make the consolidation persistent for next month.

Skip these three and the budget-review insight is wrong in subtle ways — your “dining” total is missing a quarter of the dining spend because Blue Bottle’s third variant landed under “other.”

A worked example: three cards, one budget workbook

Concretely: a household runs Amex Gold, Chase Sapphire Reserve, and Apple Card. Statements close on the 6th, 22nd, and last day of the month respectively. The end-to-end iPad flow at month’s end:

  1. Open Mail for the Amex and Chase statement PDFs; grab the Apple Card statement PDF from card.apple.com in Safari (or AirDrop it from Wallet on the iPhone). Open each PDF in turn.
  2. Share each into ignitai. Apply the “Credit card → budget workbook” preset for each.
  3. Pick XLSX. Hit Convert. Each runs in seconds.
  4. Save each XLSX into iCloud Drive/Budget/2026-04/.
  5. Open the household budget workbook in Excel for iPad. Append the new transactions rows from each of the three extractions. The categorization is already in place from the prompt; manual edits required only for ambiguous merchants.
  6. Run the three reconciliation checks per card. Statement totals reconcile, payment signs check out, two merchant variants need merging (Blue Bottle’s two spellings on the Amex, plus an Uber Eats vs Uber split on the Chase).
  7. Pivot the combined transactions sheet by category × month. The April dining total, transportation total, subscriptions total, etc., land in the budget review tab automatically.

Total time start to finish: about twenty minutes, most of it the reconciliation spot-checks. Compare to the manual transcription path: thirty merchant rows × three statements × ten seconds each is fifteen minutes just typing, plus categorization, plus the inevitable spelling-variant pivots later. The ignitai path also keeps the statement file on the iPad the way the manual path does; the web-converter path costs both time and privacy.

When this workflow isn’t the right fit

Honest edge cases:

  • Year-end consolidation across twelve statements. Don’t do that on iPad. Send the statement folder to your Mac (AirDrop or iCloud Drive) and use the Mac batch flow. Twelve share-sheet round trips on the iPad is fine, but the post-processing — twelve XLSX files to merge — wants the keyboard and the big screen.
  • Card issuers with CSV exports. Apple Card exports a transactions CSV from Wallet on the iPhone (Card Balance → Statements → Export Transactions); AirDrop it or save to iCloud Drive and it’s on the iPad. If the issuer offers a CSV export, take it — no extraction needed.
  • Reimbursable business charges mixed with personal. Tag the prompt to add a reimbursable column based on a merchant whitelist you maintain (“any charge at airport hotel chains, ride-share, or business-name merchants is reimbursable”). The categorization quality drops compared to pure personal/business separation, so for serious expense reporting use a dedicated tool.
  • Foreign-currency charges. Most issuers show the foreign-currency amount, the exchange rate, and the USD amount. Tell the prompt to capture all three columns. The budget pivot wants the USD amount; the audit trail wants the original.
  • Disputed charges or pending transactions. Pending charges shouldn’t go into the budget — they may reverse. Tell the prompt to skip rows marked “Pending” or in a pending section. For disputed charges, ask for a disputed true/false column so they stay flagged without contaminating the totals.

Bottom line

For a credit card statement PDF that arrived in Mail on iPad and needs to end up as merchant-categorized rows in your budget workbook: install ignitai, share the PDF into it, apply the saved preset, pick XLSX, hit Convert, run the three reconciliation checks. For Apple-Card-only households who want zero install, the iPhone Wallet CSV export — AirDropped to the iPad and opened in Numbers — covers the month with Apple’s own categorization. For year-end consolidation, switch to the Mac batch flow. For everything in between — the monthly multi-card review on the couch — the on-device iPad path is the shortest distance from statement PDF to a row you can trust in your spending pivot.

The bank-statement equivalent on iPad is in the iPad bank-statement guide; the Mac receipt batch path is in the Mac receipt guide; the iPhone single-statement path is the iPhone bank-statement Excel guide. Same app, presets sync via iCloud, so the prompt you write once on iPad shows up on iPhone for the next mid-month review.

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

FAQ

How do I convert a credit card statement PDF to Excel on iPad?

Open the statement in Mail or Files, share it into ignitai (or pick it with the in-app file picker), describe the columns you want in plain English, pick XLSX, and tap Convert. The statement is read on the iPad and never uploaded — only the recognized text goes to ignitai’s private hosted pipeline.

Can it normalize merchant names like SQ *COFFEE or AMZN MKTP?

Yes — tell the prompt to collapse variants to a canonical name (for example, collapse ‘SQ *BLUE BOTTLE’ and ‘BLUE BOTTLE #4’ to ‘Blue Bottle Coffee’) and the year-end pivot stops splitting one merchant into five rows.

Does converting statements on iPad require a subscription?

The download is free and your first conversion is free. After that it’s $19.99/month with a 3-day free trial — and the whole statement workflow stays inside the one app, with the XLSX saved to Files or iCloud Drive.