Convert credit card statement PDF to Excel on iPhone (2026)

The Amex statement landed in Mail this morning. You’re on the train, or in a waiting room, or about to fall asleep, and the budget spreadsheet in Excel on iCloud has been waiting for last month’s numbers since the second of the month. The PDF is right there in Mail on your iPhone. The Mac is at home, the iPad is on the kitchen counter, and the only device on you is the one in your hand.

The instinct is to wait — to handle it on the Mac later. The reality is that “later” is the reason last quarter never got reconciled. The iPhone, in 2026, is enough for this specific job: read a forty-line statement PDF, write clean Excel rows, push the workbook back to iCloud, and have the budget pivot updated by the next stop.

This walkthrough covers the workflow that actually works on iPhone: extract a credit card statement PDF to Excel on iPhone — the statement file read on-device, never uploaded.

Why iPhone (not iPad, not Mac) for this specific task

The iPad credit card walkthrough is the right path for couch-side monthly review of three or four statements at once. The Mac batch path is the year-end consolidation across forty statements and four issuers. The iPhone is the capture device — the moment the statement arrives in Mail, before it gets lost in a thread of receipts, the conversion happens on the device that’s actually with you.

Three reasons the iPhone wins for the single-statement, in-the-moment job:

• The PDF is already there. The statement arrived in Mail or appeared in Wallet for Apple Card. No download, no AirDrop, no “let me handle it later on the Mac.” Share sheet → ignitai → done, all in under thirty seconds.
• The statement is read on the iPhone, not uploaded. ignitai runs document recognition on-device — the PDF never leaves the phone — and sends only the recognized text to its private pipeline. On iOS 26, Apple’s newest document recognition reads the charge tables natively for sharper columns.
• iCloud sync makes the iPhone capture round-trip back to Mac analysis. The XLSX lands in iCloud Drive; it’s sitting next to the budget workbook on the Mac next morning, ready to paste in. You handle the iPhone moment when it lands; the pivot lives where pivots live.

Why credit card statements aren’t just bank statements

The iPhone bank-statement Excel guide handles checking-account PDFs. A credit card statement looks similar — date, description, amount — but structurally it’s a different document with four extraction problems a generic bank-statement tool will get wrong:

1. Merchant strings as the network passed them. A checking-account statement shows payee names you set up yourself (“Verizon”, “Comcast”). A credit card statement shows merchant strings raw from the payment network: SQ *BLUE BOTTLE COFFEE, TST*PIZZA HOUSE PHX 0431, AMZN MKTP US*PB4XD8RC2, APL*ITUNES.COM/BILL. The same merchant visited three times can appear as three different strings. Without normalization, the year-end pivot splits one coffee shop into five rows.
2. Sign convention is the inverse of bank statements. On a checking statement, money out is negative. On a credit card statement, a new charge is on the debit side (you owe more) and a payment to the card is on the credit side (you owe less). Mixing both account types in one workbook needs an explicit transaction_type column to avoid silent inversions.
3. Issuer-specific table layouts. Amex puts fees and interest in a top summary, then transactions chronologically. Chase Sapphire Reserve splits transactions by spending category; Chase Freedom keeps them chronological. Citi puts the payment-due block above the transactions; Capital One puts it below. Apple Card’s Wallet-exported PDF has its own clean two-column layout. A naive extractor handles two layouts well and the rest badly.
4. Fees and interest in separate bands. Credit card statements isolate fees and interest into a “Fees Charged” and “Interest Charged” section that visually mimics the transactions table but isn’t part of it. A tool that mashes those into the main charge list inflates monthly spending; one that drops them silently hides actual costs.

Method 1: ignitai on iPhone (the no-upload way)

ignitai treats credit card extraction as a language task: you describe the rows you want in plain English, the model finds them on the page, and the output is one Excel workbook with the categorization and the normalization already baked in. The iPhone flow:

1. Open the statement PDF in Mail (or Wallet for Apple Card). Share sheet → ignitai. The PDF stays on the device — share-sheet hand-off uses iOS’s local file-coordination APIs, not a network round-trip.

2. Reuse last month’s prompt from Previous Prompts (or write it once on the first run). The prompt that handles almost every US/EU issuer’s layout:

   *“Return one row per transaction with: transaction_date (ISO 8601), post_date (ISO 8601, if shown separately), merchant_raw (the merchant string as printed on the statement), merchant_normalized (the canonical name — collapse ‘SQ BLUE BOTTLE COFFEE’, ‘BLUE BOTTLE PHX’, ‘BLUE BOTTLE #4’ to ‘Blue Bottle Coffee’; collapse all Uber Eats variants to ‘Uber Eats’; collapse Amazon Marketplace variants to ‘Amazon’), 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 (Amex, Chase, Citi, Capital One, Apple Card, etc.), card_last_four, statement_period_start (ISO 8601), and statement_period_end (ISO 8601). If a transaction is a foreign-currency charge, return foreign_amount and foreign_currency.”

   ignitai keeps it in Previous Prompts — next month it’s one tap to reuse.

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

4. Hit Convert. A fifteen-page statement extracts in seconds, with live progress as the pages are read.

5. Save to Files → iCloud Drive → Budget/, or to whichever iCloud folder the budget workbook on Mac lives in. The new month’s XLSX lands next to the budget workbook; next time it’s open on the Mac, pasting the month’s rows into the running transactions sheet takes seconds.

6. Spot-check three rows. Tap into the file in ignitai’s preview pane. Three quick checks (described below) take ninety seconds.

End to end from “statement arrives in Mail” to “rows are in the iCloud budget workbook”: about three minutes, most of which is the spot-check.

Method 2: Apple Wallet’s built-in transactions (Apple Card only)

For Apple Card specifically, Wallet on iPhone has a built-in transactions view that already exposes structured rows. You don’t need PDF extraction at all:

1. Open Wallet → tap the Apple Card.
2. Tap the month you want.
3. Scroll to Export Transactions. Save as CSV or OFX.

The CSV is already clean — date, merchant, category (Apple’s own categorization), amount, type. Open in Excel for iPhone via Files, save as XLSX, append to the budget workbook. If your entire credit-card universe is Apple Card, this is the right path; skip the extraction step.

It does not extend to Amex, Chase, Citi, Capital One, Discover, or any other issuer. Those issuers offer PDFs in Mail or downloads from their websites — extraction is what gets you to the same place across issuers.

Method 3: web converters and why not on iPhone

Smallpdf, iLovePDF, PDFTables, and the rest of the web-converter category have iOS apps or mobile-web flows that, technically, work on iPhone. For a credit card statement specifically they’re the wrong posture for three concrete reasons:

• You’re uploading the file. Every web converter routes the PDF through a server you don’t control. The privacy policy on most free tiers reserves the right to process submissions for “service improvement.” A credit card statement contains your full card number’s last four, your merchant pattern for the month, and your spending profile. The economics of leaking that data are bad even when nothing goes wrong.
• Free-tier file caps gate at one to three uploads. Past that, watermarks, paywalls, or download caps. Even for a single statement, the conversion frequency hits the cap by month three.
• Merchant normalization is yours to add after the fact. Generic table extractors return the raw merchant string. The work of collapsing SQ *BLUE BOTTLE and BLUE BOTTLE PHX to one row is a manual edit on every transaction. ignitai does that work in the same pass.

For a tutorial PDF with no real data, web converters are fine. For your actual statement, no.

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

Excel for iPhone has no Power Query and no Get Data menu — it cannot ingest a PDF at all. Its one built-in capture path is Insert Data from Picture: photograph a printed table and Excel OCRs it into cells, flagging uncertain reads for review. For a credit card statement that arrives as a PDF, that means screenshotting pages one at a time and reviewing cell by cell — and the output is a raw grid: merchant_raw and nothing else, no categorization, no normalization, fees and interest mixed in or missed. For personal credit card data where the statement file should stay on the phone, ignitai’s read-on-device path takes the PDF as-is and adds the categorization in the same pass.

The three reconciliation checks, on iPhone

Once the XLSX is in iCloud Drive, three quick checks in the ignitai preview pane or in Excel for iPhone separate “I have a file” from “I have a row I can trust on next month’s budget review”:

1. Statement total match. Sum the amount column for this statement’s rows. The sum, minus any payments, should equal the new balance minus the previous balance printed at the top of the statement. A divergence means a transaction got missed or duplicated during extraction. On iPhone, this is a one-formula check; open the source PDF to spot the missing row.
2. Payment sign sanity. Filter transaction_type = payment. Every row should have a negative amount. A payment that landed positive will inflate next month’s “Total charged” pivot by twice the payment amount — once for the inverted sign and once for the missing offset. Fix the row, then update the saved prompt for next month so the inversion doesn’t recur.
3. Merchant normalization spot-check. Scroll the merchant_normalized column for the top fifteen rows by count. Look for variants of the same merchant that didn’t merge — Trader Joes vs Trader Joe's, a coffee shop appearing under two different street locations, a delivery app split across UBER EATS and UBER*EATS. Edit the column in place. After two or three monthly iterations, the prompt is reusable across the year.

Skip these three and the monthly spending picture is wrong in subtle ways — the dining total under-counts because two coffee-shop variants stayed split, the travel total over-counts because a refund landed positive, the subscription category is missing one streaming service because it was categorized as “entertainment” instead.

A worked example: monthly review on a commute

Tuesday morning, the Chase Sapphire Reserve statement landed at 6:02 AM. By 7:15 AM you’re on the train. The flow:

1. Open Mail → tap the Chase email → tap the PDF. The statement opens in iOS’s PDF previewer.
2. Share → ignitai. Three taps.
3. Reuse the monthly credit card prompt from Previous Prompts. Tap Convert. Seconds later the rows are back.
4. Preview the output. Twenty-eight transaction rows.
5. Spot-check: statement total reconciles, no positive payments, one merchant cleanup needed (“STARBUCKS #4831” → “Starbucks”) — note it for the paste. Forty seconds.
6. Save → Files → iCloud Drive → Budget/. Next time the budget workbook is open, paste the month’s rows into the transactions sheet of 2026-credit-cards.xlsx and make that one merchant edit there.
7. Get back to whatever you were doing on the train.

Total time: under four minutes. Compare to “wait until I’m at the Mac tonight, by which time the PDF is buried under fourteen Mail messages, and now it’s Saturday and the month is over.”

When the iPhone path isn’t the right tool

Honest edge cases:

• Year-end consolidation across multiple issuers. Switch to the Mac batch path. iPhone is for the single statement; Mac is for the forty-statement annual rollup.
• Three or four statements landing in the same week. Use the iPad path. The bigger screen makes the multi-statement spot-check faster than swapping views on iPhone.
• Apple-Card-only households. Use Wallet’s built-in transactions export. ignitai handles Apple Card PDFs fine, but if Wallet already gives you structured rows, the extraction step is unnecessary work.
• Disputed or pending transactions. Pending charges shouldn’t go into the budget workbook — they may reverse before posting. Add to the prompt: “Skip any row marked ‘Pending’ or in a pending-transactions section.” For disputed charges, ask for a disputed true/false column so they stay flagged without contaminating the totals.
• Scanned statements (rare for credit cards). Almost all credit-card statements are text PDFs by 2026. If you’ve scanned a paper statement from an archive, the extraction still works because ignitai routes scans through the OCR-then-extract pipeline; spot-check more carefully because OCR adds a small accuracy hit.

Bottom line

For an iPhone user who wants the monthly credit card statement in Excel without waiting to be at the Mac: share the PDF from Mail to ignitai, reuse the monthly prompt from Previous Prompts, pick XLSX, run the three reconciliation checks, save to iCloud Drive. The PDF never leaves the device. The month’s XLSX is waiting in iCloud next to the budget workbook the next time you’re at the Mac.

The same app handles the iPad monthly review for three-or-four-statement weeks, the Mac annual consolidation for year-end rollups, and the iPhone bank-statement Excel flow for the checking-account version of the same job. Presets sync across all three via iCloud — write the monthly prompt once on iPhone and the Mac batch next December picks up the same normalization rules automatically.

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

FAQ

Can I convert a credit card statement to Excel right on my iPhone?

Yes — open the PDF in Mail, share it to ignitai, describe the rows once, pick XLSX, and tap Convert. A fifteen-page statement extracts in seconds and the workbook saves straight to iCloud Drive.

Is my credit card statement uploaded anywhere?

No. The PDF is read on-device on every supported iOS version — only the recognized text is sent to ignitai’s private hosted pipeline. On iOS 26, Apple’s newest on-device document recognition reads the charge tables natively for sharper columns.

How do charges and payments get the right signs?

Ask for it explicitly in the prompt — amounts positive for charges, negative for payments and credits, plus a transaction_type column. That keeps card activity from silently inverting when you mix it with checking-account rows in one workbook.