Convert Brokerage Statement PDF to Excel on iPhone

The brokerage statement is already on your iPhone. Fidelity, Schwab, Vanguard, Morgan Stanley, or whoever holds the account emailed the monthly PDF, or you downloaded it from their app, and now you want it in Excel — the holdings with their cost basis and market value, the dividend and trade activity, the realized gains — so you can track the portfolio in your own sheet instead of squinting at a statement designed to be filed and forgotten. And Excel, on the iPhone exactly as everywhere else, has no “import PDF” button. The Excel app opens .xlsx and .csv; it will not open a brokerage statement PDF. So the job is never “open the statement in Excel” — it is “turn the statement’s tables into Excel rows, with the numbers intact and the columns where they belong.”

A brokerage statement is one of the harder PDFs to do this with, and one of the more sensitive. Hard, because a single statement is not one table — it is a stack of them: an account summary, a holdings table, a realized-gains section, a transaction ledger, sometimes a dividend schedule, often spread across a dozen pages and laid out in dense, multi-column blocks. Sensitive, because it carries your full account number, your positions, and your balances. Emailing that to a desktop later to run through a web converter ships exactly that data to a stranger’s server — the one document you least want sitting on infrastructure you do not control. There is a path that stays on the iPhone the file already lives on.

This guide is how to convert a brokerage statement PDF to Excel on iPhone in 2026: pull the table you actually want out of the multi-section statement, on-device on iOS 26+, and land it in Excel with the numbers ready to sum.

Why a brokerage statement fights every simple tool

Copy a holdings table out of a brokerage PDF in the Files app and paste it into Excel on the iPhone, and you get a single mangled column — ticker, description, quantity, price, and market value all crushed together, with the multi-line position descriptions wrapping into rows that do not align with anything. The reason is the same one behind every PDF table: the grid you see is a visual arrangement of characters at fixed coordinates on a page built to be printed, not parsed. There are no cells underneath, no column delimiters. Excel receives a stream of text and cannot tell where “market value” ended and “unrealized gain” began.

Brokerage statements make this worse than a typical PDF in three specific ways:

Many tables, one document. The summary, the holdings, the activity, and the gains sections all look like tables but mean different things. A naive extractor either grabs the first one it finds or stacks them all together, and you spend longer untangling the result than you would have retyping it.
Numbers that must stay numbers. Cost basis, market value, and gain/loss are the whole point. If a parser drops a comma in “1,240.50” or fuses a parenthesized loss “(312.40)” to the next field, every downstream SUM is wrong and you will not notice until the totals do not tie.
Multi-line descriptions. A single holding’s description often spans two or three printed lines. A coordinate-based parser treats each line as its own row, and your 40-position portfolio becomes 110 rows of fragments.

The fix is an extractor that reads the rendered page the way you do — seeing the holdings table as one table with one row per position — instead of guessing column edges from pixel gaps.

Method 1: ignitai on iPhone (the on-device way)

ignitai reads the statement page as a person would and writes the result straight to an Excel file. The full iPhone flow:

Send the statement to ignitai. From Mail, Files, or your broker’s app, tap Share and pick ignitai — or open ignitai first and import the PDF from the Files browser. Several monthly statements at once are fine; more on batches below.
Name the table you want, in plain English. A brokerage statement has several, so this is where you point at the one you need rather than getting all of them:

“Extract the holdings table only: symbol, description, quantity, price, market_value, cost_basis, unrealized_gain. One row per position. Ignore the account summary and the activity section.”

Or, if it is the activity you are after:

“Extract the transaction activity: date, type, symbol, quantity, amount. One row per transaction. Skip the holdings table.”
Choose Excel (.xlsx) as the output format. ignitai sets the column types during extraction — quantities and prices become numbers, the market value column becomes currency — so the sheet opens ready to compute instead of as text you reformat by hand on a small screen.
Tap Extract. On an iPhone running iOS 26 or later, the extraction runs on-device. This is the part that matters for a brokerage statement specifically: the account number, the positions, and the balances are read locally and never uploaded.
Open in Excel. Tap the result and it opens in the Excel app, columns aligned, numbers as numbers. Drop a SUM under market_value and you have a portfolio total you can track month over month.

The reason the output-format choice earns its keep here: if you export CSV and import it, every column lands as text and you re-type the currency and number formats by hand — on a phone, which is the worst place for fiddly formatting. Exporting Excel directly decides the types during extraction, where the model already knows market value is money and quantity is a number.

Method 2: the CSV-then-Excel fallback

On an older iPhone where ignitai exports CSV rather than a native Excel file, the path is one step longer but still entirely on-device:

Extract to CSV in ignitai using the same plain-English prompt naming the holdings or activity table.
Save the CSV to Files (it usually lands there automatically).
Open the Excel app, create a new workbook, and use Insert → Import (or open the CSV from Files and pick “Open in Excel”) to bring the CSV in. Excel splits the columns on the commas.
Format the market-value and cost-basis columns as currency once. Done.

This is the same data, with you doing by hand the formatting the direct-Excel export would have handled. If your endpoint is a budgeting tool rather than Excel, the bank-statement-to-CSV flow on iPhone covers the CSV path for the cash side of your accounts.

A worked example: tracking a portfolio month over month

Say you want a running sheet of your holdings so you can see how the portfolio moves each month:

In Mail, tap this month’s statement PDF, Share, pick ignitai.
Prompt: “Holdings table only: symbol, quantity, price, market_value, cost_basis. One row per position.”
Output format: Excel. Tap Extract.
Open the result in Excel. Under market_value, add =SUM() and confirm it matches the “Total market value” printed on the statement’s summary page.
If it ties, paste the rows into a master workbook with a month column. Next month, repeat — and a simple SUMIF by month gives you the portfolio’s trajectory without you retyping a single position.

The check in step 4 is the one that catches everything: if the extracted market_value total matches the printed total, the table came across clean. If it does not, sort by market value and find the row that is off — it is almost always a multi-line description that split or a parenthesized loss that lost its sign, and it takes under a minute to spot.

Which statements convert cleanly, and which need a precise prompt

How much prompt you write depends on the statement:

A single-broker monthly statement with a clear holdings table converts with a one-line prompt naming that table. This is the common case and the fastest path.
A consolidated statement — multiple accounts, or a broker that bundles holdings, activity, and gains into one long PDF — is where the prompt does real work. Name the exact section (“the holdings for account ending 4417, not the activity”) and ignitai ignores the rest. Without that sentence you would get every table from every account stacked together.
A scanned or photographed statement — a paper statement you snapped with the iPhone camera — has no text layer, so copy-paste and naive parsers have nothing to read. ignitai reads the rendered image the same way it reads a downloaded PDF, so a photographed statement converts as cleanly as a digital one. The same on-device reading is what powers the scan-receipts-to-spreadsheet flow on iPhone.

The rule mirrors every other document type: one table you want all of, a short prompt; several tables and you want one, name it precisely. Either way the output stays Excel and either way it runs on-device on iOS 26+.

Batches: a year of statements into one workbook

The real work is rarely one statement — it is twelve, when you sit down to review the year or hand a tidy spreadsheet to an accountant. Select a folder of monthly statements in the Files browser, send them to ignitai, apply one prompt, and every statement’s activity flows into the same Excel sheet, one row per transaction, each tagged with its source filename so you can pivot by month. A year of trade and dividend activity becomes a single workbook without you opening any statement individually. The per-file progress shows which finished, and any that fail — a password-protected PDF, a corrupt download — are listed separately so you re-run only those. The mechanics of batching are the same as the batch PDF-to-CSV workflow.

A note on privacy

A brokerage statement is the single most sensitive PDF most people own — full account number, every position, every balance, in one file. A web converter requires you to upload exactly that to a server you do not control to get it back as something Excel can read. Extracting on-device with ignitai on iOS 26+ inverts the trade: the statement is read on the iPhone, the Excel file is written on the iPhone, and nothing leaves the device. The data is not uploaded, does not sit on a converter’s server, and does not appear in an email you have to remember to delete. If your iPhone predates on-device support, ignitai falls back to a hosted pipeline with documented zero retention — the file is not training anyone’s model either way. The deeper explanation of how the on-device reading works is in the AI PDF-to-CSV walkthrough, and the same approach applies to a bank statement to Excel on iPhone.

Bottom line

A brokerage statement is a stack of tables wrapped in one PDF, carrying the most sensitive data you own, and Excel cannot open it — but your iPhone can turn it into a clean Excel sheet without the data ever leaving the phone. Share the statement to ignitai, name the holdings or activity table in one plain-English sentence, choose Excel as the output, and tap Extract; on iOS 26+ it runs on-device and lands an .xlsx with the numbers as numbers. A single SUM against the printed total tells you in under a minute whether it is clean, and a month column turns a folder of statements into a portfolio you can actually track. For the same job on a bigger screen, see convert brokerage statement PDF to Excel on Mac.

Get ignitai on the App Store and convert your first brokerage statement to Excel on iPhone today.