Convert invoice PDF to Excel on iPhone

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 — invoices read on-device, never uploaded — 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 → ignitai is one tap. The share sheet on a PDF in Mail or Files exposes installed apps directly. ignitai shows up in the row, reads the invoice on-device — the PDF is never uploaded — and the result writes back to Files in seconds. No web-tool upload form, 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. ignitai reads the PDF on-device, so the file never leaves the phone; only the recognized text goes to its private pipeline.

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:

1. 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.
2. 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.
3. 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.
4. 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.

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

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:

1. Open the invoice in Mail. Tap the PDF attachment to preview it.

2. Tap the share button. Bottom-left of the preview view in Mail, or top-right in Files.

3. 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.

4. 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_number, vendor_name, description, quantity, unit price, line total, and tax rate. Repeat the invoice-level fields — issue_date (ISO 8601), due_date (ISO 8601), po_number, and grand_total — on each row.”

   Save it as a preset called “Invoice → AP workbook.” Next invoice it’s one tap.

5. Pick XLSX as the output format. One sheet, one row per line item, with the invoice-level fields repeated on each row — clean text your AP workbook’s column formats type on paste.

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

7. 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:

1. One sheet straight into the workbook. The extraction lands as rows you append into the AP workbook you already keep — line items with the invoice number and vendor repeated on each row, ready for vendor × month × tax_rate pivots. CSV means an import step first.
2. The workbook’s formats do the typing. Currency on amounts, percentage on tax rates, ISO dates on issue/due dates — set them once in the AP workbook and pasted rows inherit them. CSV round-trips make the receiving spreadsheet re-infer everything each time.
3. Formulas survive. A =SUMIFS in the workbook that reconciles line-item totals against printed grand totals is a one-time setup; each month’s appended rows flow straight into it.
4. 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:

1. Open the PDF in Mail.
2. 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.
3. Long-press the merchant name in the PDF preview, copy. Paste into a new Numbers row.
4. 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 capture

Excel for iOS has no Power Query and no “Get Data” menu — there is no way to hand it a PDF at all. What it does have is Insert Data from Picture: point the camera at a printed table (or pick a photo) and Excel OCRs it into cells, flagging low-confidence reads for manual review. Two reasons it’s not the right answer for inbound AP:

1. It doesn’t take PDFs. The input is the camera or a photo — an emailed invoice PDF would have to be screenshotted page by page first, one table per capture.
2. It captures a table, not an invoice. You get the grid of text it saw, with no line-item/totals structure and no understanding that the totals block is supposed to reconcile against the line-item sum. For AP, the review pass is yours, cell by cell.

For a paper invoice you’re physically holding, it’s a workable one-off. For PDF invoices arriving in Mail, the share-sheet extraction path is built for the actual input.

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”:

1. Line-total reconciliation. Sum the new invoice’s line_total rows — =SUMIF(invoice_number_range, "INV-2041", line_total_range) — and compare against the grand total printed on the invoice. Any divergence means a line was missed, duplicated, or misread on extraction.
2. 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.
3. 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: ‘Acme, Inc.’ and ‘Acme Inc’ are ‘Acme Inc.’” — 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:

1. Open the email in Mail. Tap the PDF.
2. Tap share → ignitai.
3. Apply the “Invoice → AP workbook” preset. (First time, write it; subsequent times, one tap.)
4. Pick XLSX. Hit Convert. Seconds later the rows are back.
5. Save the result into the Payables/2026-Q2/ folder in iCloud Drive.
6. Open the team workbook (also in iCloud Drive) in Excel for iOS. Copy the extracted line-item row into the payables sheet.
7. Run the three reconciliation checks. Line total matches subtotal — good. Vendor name matches the existing canonical entry — good.
8. 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 the invoice number on the row linking it back.

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.
• Older iPhones (pre-iOS 26). Apple’s newest table-aware document recognition isn’t available, so ignitai uses the classic on-device text recognition instead. The path works the same — the PDF still never leaves the phone; unusually dense line-item tables may just need one extra spot-check.

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 Convert, 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.

FAQ

Can I convert an invoice PDF to Excel on my iPhone?

Yes — share the PDF from Mail, Files, or Messages into ignitai, name the fields you want in one plain-English sentence, pick XLSX, and tap Convert. The line items come back one row each with amounts in their own columns, ready for the workbook.

What about scanned or photographed invoices?

Same flow — ignitai reads the page image the way it reads a born-digital PDF, so a contractor’s photographed invoice extracts like a clean download. If you’re capturing paper yourself, use the Notes or Files document scanner for the cleanest input.

Is the invoice uploaded during conversion?

No — the file is read on-device on every supported iOS version and never uploaded. Only the recognized text is sent to ignitai’s private hosted pipeline to build the spreadsheet.