Convert invoice PDF to Excel on iPhone (2026 share-sheet flow)

The invoice landed in Mail twenty minutes ago. You’re in an Uber, the supplier wants the bill paid by Friday, and your accountant wants every line item in the shared Excel sheet that drives this month’s payables. The Mac is back at the office, the iPad is on the kitchen table, and the iPhone is the only thing in your hand. The choices, historically, have been: forward the email to yourself and forget; type the invoice into a Numbers row by hand at the next stoplight; or send the PDF to one of the web converters that returns an XLSX you then have to AirDrop to the Mac to actually use.

The iPhone is the device the invoice arrived on. The work — turning that PDF into a clean Excel row that lands in the team workbook — should happen there, in the time it takes the Uber to get to the next intersection.

This guide covers the workflow that actually works in 2026: convert invoice PDFs to Excel on iPhone, on-device on iOS 26+, straight from the Mail or Files share sheet, with line items, totals, and tax landing in the right columns the first time.

Why iPhone (not iPad, not Mac) for inbound invoices

The Mac invoice batch guide exists for the month-end stack of forty bills. The iPad walkthrough is the desk-style single-invoice flow when the iPad is the device you’re already holding. The iPhone is different: it’s the capture surface for the live inbox.

Three reasons the iPhone is genuinely the right tool for the in-the-moment invoice:

It’s where the email arrived. Suppliers email PDFs to the address you check on your phone. Most invoice processing happens within an hour of arrival, before the email becomes one of forty unread. Doing the conversion at the moment the email lands removes the “I’ll deal with it on the Mac later” failure mode that turns one invoice into a backlog.
Share sheet → on-device extraction is one-tap on iOS 26. The share sheet on a PDF in Mail or Files exposes installed apps directly. ignitai shows up in the row, the extraction runs locally on iPhone 15 Pro or newer, and the result writes back to Files in 6–10 seconds. There’s no upload, no wait for a web service round-trip, no AirDrop step.
Privacy surface matters for AP. A vendor invoice carries supplier names, bank details, your billing address, your purchase totals — exactly the document type you don’t want passing through a third-party server with a “we delete after 24 hours” promise. On-device extraction means the PDF never leaves the phone.

If the bill is one of forty arriving at month-end, batch on the Mac. If it’s a single bill from a contractor who emails sporadically, the iPhone is the shortest distance from inbox to spreadsheet.

Why invoice PDFs are harder than they look

“Invoice to Excel” sounds like one problem. It’s actually four, and most converters only handle the first:

Header metadata. Invoice number, issue date, due date, PO number, vendor name and address, your billing address. These are scattered across the top third of the page in boxes, not in a table. A generic table extractor skips them or smashes them into the line-item grid.
Line items. The actual table: description, quantity, unit price, line total, sometimes tax per line, sometimes a discount column. Templates vary wildly between vendors — even two invoices from the same supplier can diverge if they updated their billing software midway through the year.
Totals block. Subtotal, tax (often split across multiple rates — standard VAT, reduced VAT, zero-rated), shipping, discounts, grand total. Visually a small table; structurally a set of key-value pairs that need to land in specific columns alongside the line items.
Payment terms and footer. Bank details, payment reference, late-fee policy. Usually irrelevant for bookkeeping but sometimes the payment reference is the column that matters for AP matching.

A tool that grabs “all the tables” gives you a mess. A tool that understands an invoice as an invoice puts header metadata in normalized columns, line items in their own rows with an invoice_id foreign key, and totals in a reconciled summary. That’s what you want exported to Excel — even if it’s just one invoice today, because tomorrow’s row from a different vendor needs to land in the same columns to be useful.

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

Open the invoice in Mail. Tap the PDF attachment to preview it.
Tap the share button. Bottom-left of the preview view in Mail, or top-right in Files.
Pick ignitai from the share sheet. It’s in the row of installed apps. Long-press to pin it as a favorite if you’ll do this often.
Apply the saved invoice prompt. First time: write it once. The prompt that works for almost every standard US/EU vendor template:

“For each line item, return invoice_id (use the invoice number), description, quantity, unit price, line total, and tax rate. In a separate sheet, return invoice_id, invoice_number, issue_date (ISO 8601), due_date (ISO 8601), vendor_name, vendor_address, po_number, subtotal, total_tax, shipping, and grand_total.”

Save it as a preset called “Invoice → AP workbook.” Next invoice it’s one tap.
Pick XLSX as the output format. Two-sheet workbook: line_items and invoices, joined by invoice_id. Currency formatting auto-applied to amount columns, percentage formatting to tax rates.
Hit Extract. ignitai runs the PDF through the on-device model on iPhone 15 Pro or newer. A 1–3 page invoice extracts in 6–10 seconds. Older iPhones fall back to a hosted pipeline with documented zero retention.
Save to Files. Drop into the iCloud Drive folder where the team workbook lives, or share back into Mail to forward to your accountant. If the team workbook is the destination, open it in Excel for iOS afterward and append the new rows.

The whole flow — from receiving the email to having the rows in the workbook — takes under a minute on a recent iPhone.

Why XLSX (not CSV) for invoices

For bank statements the right output is often CSV — the destination is QuickBooks or Xero’s bank-import flow. Invoices are different. The destination is usually the spreadsheet itself: a workbook your accountant or AP system uses to track payables, run pivot tables on vendor × month × tax_rate, and reconcile against POs. XLSX is the right format because:

Multi-sheet structure. An invoice export wants two sheets: one for line items (one row per line, many rows per invoice) and one for header/totals (one row per invoice). CSV is single-table; jamming both in one CSV means denormalized rows.
Number formatting per column. Currency on amounts, percentage on tax rates, ISO dates on issue/due dates. XLSX preserves these; CSV is plain text and the receiving spreadsheet has to re-infer types.
Formulas survive the round trip. A =SUMIF(line_items.invoice_id, A2) in the header sheet that reconciles line-item totals against printed grand totals is a one-time setup in XLSX. In a flat CSV, you’d re-derive it every time you reopened.
Excel and Numbers both open it cleanly. Excel for iOS or Numbers for iPhone — either works. No encoding question, no quoted-string surprises.

For invoices destined for bookkeeping review, XLSX is what you want. CSV is fine if you’re piping into a script.

Method 2: Mail → Apple Notes → manual Numbers

If you only have one invoice and don’t want to install anything new:

Open the PDF in Mail.
Long-press the file → Save to Files, then open in Apple Notes if you want OCR’d selectable text on a scanned PDF; otherwise the PDF is already text-searchable.
Long-press the merchant name in the PDF preview, copy. Paste into a new Numbers row.
Repeat for invoice number, date, total. Type line items by hand or skip them.

This works for one invoice if you only need the header total. It does not handle line items in any sane time, and missing line items means your AP tooling can’t reconcile against POs. For one urgent invoice that’s a header-only entry, fine. For a sole proprietor doing real bookkeeping, the manual path stops scaling at the second invoice of the day.

Method 3: web converters (and why not for AP from a phone)

A dozen “PDF invoice to Excel” web tools exist. From the iPhone they’re worse, not better, than the desktop versions:

Upload speed on cellular. A 12 MB scanned-invoice PDF over LTE is a noticeable wait; on the worst connections it just times out. The on-device path doesn’t care about connectivity.
The output is XLSX delivered as a download URL. You then need to save it back into Files, which means popping out of the web view, navigating to Downloads, and moving it into the right folder — three steps that the share-sheet flow collapses into none.
Privacy. Vendor invoices include supplier bank details, billing addresses, line-item pricing. Uploading to a free-tier web converter that explicitly says “we may use submissions to improve our service” is the wrong posture for AP work.
Free-tier gating. Two to five files free per month, then a recurring fee. The math gets worse the more invoices you handle, and worse still on iPhone where the per-file friction is higher than on a desktop browser.

For one tutorial PDF with no real data, fine. For your actual supplier list, no.

Method 4: Excel for iOS’s built-in import

Excel for iOS has a “From PDF” data-import option (Insert → Get Data → From PDF on the most recent versions). It uses Microsoft’s cloud Power Query backend. Two reasons it’s not the right answer for inbound AP:

It uploads. The PDF goes to Microsoft’s servers for the table-extraction pass. Same privacy concern as the web converters.
It treats the PDF as a tables document, not as an invoice. You get the line-item table extracted as a generic data table, with header metadata as a separate detected table you may or may not want, and no understanding that the totals block is supposed to reconcile against the line-item sum. For AP, the post-import cleanup undoes the time savings.

If your IT team has already approved Microsoft 365 for AP work and the privacy posture is settled, it’s a workable path. For a freelancer or small operator, the on-device alternative is faster and keeps the data local.

The three reconciliation checks, on iPhone

Once the XLSX is written and opened in Excel for iOS, three quick checks separate “I have a file” from “I have an audit-ready row”:

Line-total reconciliation. In the header sheet for the new invoice, add (or apply the existing) =SUMIF(line_items.invoice_id, A2, line_items.line_total). It should equal the extracted subtotal for that invoice. Any divergence means a line was missed, duplicated, or misread on extraction.
Tax-rate sanity. If the invoice has multi-rate tax (standard VAT and reduced VAT, say), each tax rate’s line items summed and multiplied by the rate should equal the tax broken out for that rate in the totals block. This catches a line that landed under the wrong rate.
Vendor-name normalization. If the vendor name on this invoice doesn’t match the canonical form already used in the workbook (“Acme Inc.” vs “Acme, Inc.” vs “Acme Inc”), edit it now to match. Otherwise the pivot tables grouped by vendor split a single supplier into three. Pushing the rule into the saved prompt — “normalize vendor names to the spelling used in column A of the invoices sheet of the existing workbook” — fixes it for next time, but only after you’ve established the canonical spelling somewhere.

Skip these three and the AP error surfaces during reconciliation, when one invoice is paid twice and you’re hunting through the workbook for the duplicate.

A worked example: contractor sends a bill at 4:47 PM Friday

Concretely: a freelance designer emails an invoice for the month’s work as a PDF. You’re at the airport. The Mac is in checked baggage. The end-to-end iPhone flow:

Open the email in Mail. Tap the PDF.
Tap share → ignitai.
Apply the “Invoice → AP workbook” preset. (First time, write it; subsequent times, one tap.)
Pick XLSX. Hit Extract. 8 seconds.
Save the result into the Payables/2026-Q2/ folder in iCloud Drive.
Open the team workbook (also in iCloud Drive) in Excel for iOS. Copy the two extracted rows (one header, one line item) into the appropriate sheets.
Run the three reconciliation checks. Line total matches subtotal — good. Vendor name matches the existing canonical entry — good.
Forward the original email to the AP folder. Done.

Total elapsed time: about ninety seconds. Net effect: an invoice processed before boarding, an accountant who has the row before Monday, a clean audit trail with the original PDF still in Mail and a source_file column linking the row back to it.

When this workflow doesn’t fit

Honest edge cases:

A folder of forty month-end invoices. Don’t do that on iPhone. Send the folder to your Mac (AirDrop or iCloud Drive) and use the Mac batch flow. Forty share-sheet round trips on a phone is a workflow built backwards.
Multi-page invoices with a continuation table. The on-device extraction handles them, but tighten the prompt: “line items continue across pages until the totals block; do not treat each page as a separate invoice.” Save the preset.
Subscription receipts (Stripe, AWS, Apple Developer, Google Workspace). Those vendors all expose CSV exports under their billing portals. Use the CSV. Extracting from a hundred Stripe receipt PDFs when Stripe will hand you one CSV is the wrong tool.
Invoices in EDI / XML formats (UBL, PEPPOL, EDIFACT). The accounting tool’s e-invoicing connector parses those directly. PDF extraction is for the PDF-only suppliers, which in 2026 is most small vendors but rarely large ones.
Old iPhones (pre-iPhone 15 Pro). The on-device model isn’t available; ignitai falls back to a hosted pipeline. The path still works; the privacy posture is “documented zero retention” rather than “never leaves the device.” For most personal-business AP that’s still acceptable, but flag it explicitly if your business demands strict locality.

Bottom line

For an invoice PDF that arrives in Mail on iPhone and needs to end up as a row in your team’s Excel AP workbook: install ignitai, share the PDF into it, apply the saved preset, pick XLSX, hit Extract, run the three reconciliation checks. For a single header-only entry on one urgent bill, manual transcription works in a pinch. For batches of forty, switch devices to the Mac. For everything else — the day-to-day inbound bills from twenty different suppliers — the on-device share-sheet flow is the shortest distance from email to spreadsheet, and the only one that keeps your supplier data on the phone.

The bank-statement equivalent on iPhone is in the iPhone bank-statement guide; the receipt-capture flow on iPhone is the iPhone receipts guide; the desk-style single-invoice flow on iPad is the iPad invoice guide. Same app, presets sync via iCloud, so the prompt you write once on iPhone shows up on iPad and Mac for the next batch.

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