Convert balance sheet PDF to Excel on Mac (2026 guide)

The credit renewal lands in the analyst’s queue with the borrower’s financials attached: audited statements, thirty-one pages, PDF. The spreading model wants twelve numbers from the balance sheet — cash, receivables, inventory, total current assets, fixed assets net of depreciation, and down the right side to total equity — for each of two years. The numbers are on page four, printed in a two-column comparative with parentheses around the accumulated depreciation. And the way most of them get into the model, still, in 2026, is someone reading page four and typing.

Every finance role that consumes other people’s statements meets a version of this. The lender spreading a borrower’s financials into the bank’s template. The M&A associate rebuilding a target’s balance sheet from the data-room PDFs. The fractional CFO consolidating three entities whose bookkeepers each print statements from a different system. The small-business owner whose bank wants three years of balance sheets in the bank’s own Excel workbook, when what exists is three years of accountant-prepared PDFs. The tax preparer inheriting an engagement whose permanent file holds the prior firm’s final statements as scans. The numbers are all there; the numbers are all trapped in a print layout.

This guide is the Mac workflow: convert balance sheet PDFs to Excel on Mac — read on-device, only the text sent to ignitai’s servers — with one row per line item, comparative years in their own columns, and the accounting equation as your proof the extraction is complete.

In this guide10 sections

Why balance sheets defeat table extractors

A balance sheet looks like the easiest table in the financial package — two columns of numbers, tidy labels — and grid-based extractors still mangle it, for four reasons:

1. The structure lives in indentation, not gridlines. Cash is a line item; Total current assets is a subtotal; Total assets is a total — and all three print in the same font and columns, distinguished only by indent depth and typography. A grid detector reads them as three equal rows, and the sheet double-counts the moment you sum a column.
2. Parentheses mean negative. Accumulated depreciation, treasury stock, an accumulated deficit — balance sheets print credits-against-the-section in parentheses. Grid tools pass (48,201) through as text, and every formula downstream breaks or, worse, silently treats it as positive.
3. The comparative columns aren’t always adjacent. Audited statements put the note references between the labels and the numbers; some layouts print assets on the left half of the page and liabilities and equity on the right, side by side. Grid detection splits these into fragments that don’t reassemble.
4. The prior years are scans. The predecessor accountant’s final statements, the permanent-file copy, the borrower who prints, signs, and scans — a layout parser needs a text layer, and a scan has none. It has to be read, not parsed.

The fix is an extractor that understands the document — that (48,201) is a negative amount on the accumulated-depreciation row, and that Total current assets is arithmetic, not data. That’s what a prompt-driven extractor does that a grid tool can’t.

Method 1: ignitai on Mac (the read-on-device way)

ignitai extracts by description, not by layout template, so one prompt covers the QuickBooks print, the audited package, and the scanned prior years alike:

1. Drag the PDFs in — or use the file picker, or right-click → Open With from Finder. Born-digital statements and scanned ones go through the same flow; the scanned-PDF walkthrough covers capture quality for the paper years.

2. Describe the output shape in plain English. A prompt is required — the Convert button stays disabled without one. Start from the Table starter or write your own, one clause per failure mode above:

   “One row per line item: line_item, section (assets / liabilities / equity), current_year, prior_year. Skip subtotal and total rows. Amounts in parentheses are negative — output a leading minus. Bare amounts, no currency symbols or thousands separators. Ignore the note-reference column.”

   Save it as a preset — it syncs to your other devices via iCloud — and every statement package that crosses your desk is one click from being model-ready.

3. Pick Excel, hit Convert. Each PDF is read on your Mac — never uploaded — and only the recognized text goes to ignitai’s servers to build the sheet. On macOS 26, Apple’s native on-device table recognition sharpens extraction from dense statement layouts; the same flow works back to macOS 14.4. A statement package is usually ready in under a minute.

4. Open the result in Excel or Numbers. One worksheet, one row per line item — bare amounts, minus signs where the document printed parentheses — and because the Excel file holds real numbers, the equation check runs the moment it opens. Check it in ignitai first: numbered rows, on-screen totals for the amount columns, and the original page a click away for comparison; edits happen in the spreadsheet.

Three years, one batch. Select the three annual packages in Finder and drag them in together, with the prompt extended by one clause: “add as_of_date from the statement header.” Filenames never leave your Mac, so there’s no filename column — identity comes from the document itself, and every balance sheet prints its as-of date (and company name, if you’re consolidating entities) at the top. Three years land in one sheet, and the comparative is a pivot on line_item × as_of_date. Three annual packages can outrun the plan’s 80 pages a week, so check the page count ignitai shows first and add extra pages or convert one year per week. Scanned years photographed as images run as their own batch: a drop mixing PDFs and images imports only the PDFs.

One table per run — pick the statement. The balance sheet is one run. The P&L stapled two pages ahead of it is a different statement with different columns and its own Mac flow — a second run with a second prompt, not extra sheets in the same workbook. Same for the cash-flow statement. Three statements, three runs, three clean sheets.

Method 2: Excel for Mac’s Get Data (no PDF connector)

Excel for Mac ships Power Query under Data → Get Data, but the Mac connector list — Text/CSV, XLSX, XML, JSON, SharePoint, SQL Server, OData — has no From PDF option; that connector is Excel-for-Windows-only. Even on Windows, a balance sheet trips the grid detector’s weak spots: indentation flattens, so subtotals arrive as data rows; parenthesized negatives import as text; a side-by-side assets/liabilities layout splits into fragments you stitch by hand. Against the scanned prior years it returns nothing at all.

Method 3: a pdfplumber script (for one issuer, forever)

If every balance sheet you’ll ever touch comes from one system, one report format, born-digital — say you spread statements your own firm prints — a Python script (pdfplumber for words-by-position, pandas to assemble rows) is a defensible build. The costs arrive on schedule anyway: subtotal exclusion needs rules keyed to label text, the parentheses convention needs its own handling, indent depth needs positional thresholds that shift with the issuer’s next template update, and the second issuer’s format doubles the script. The scans it can’t touch at all. For an analyst whose statements come from a hundred different borrowers’ accountants, there is no “one format” — the maintenance never amortizes.

Method 4: web converters (the never-upload line)

Generic web PDF-to-Excel tools share Power Query’s blindness to indentation and parentheses — and on this document the quality question is beside the point. A balance sheet is a company’s entire financial position on one page: cash balances, debt schedule, retained earnings. For a lender or an accountant, uploading a client’s statements to a free converter you don’t control is a confidentiality decision made on someone else’s behalf — the kind engagement letters and professional-conduct rules have opinions about. With ignitai the PDF stays on your Mac and only the recognized text goes to ignitai’s servers, where the AI builds the sheet; the finished file is kept in your ignitai account until you delete it. That is a smaller exposure than handing the whole PDF to a free converter, not a zero one — check it against your own confidentiality terms before running someone else’s documents.

On iPhone and iPad

Statements don’t always arrive at the desk:

• iPhone — the borrower hands over a signed statement package at the branch: capture the balance sheet page with the in-app camera scan, apply the saved preset, and the numbers are rows before the meeting ends. A Live Activity shows conversion progress from the lock screen. A PDF in Mail goes in through the share sheet the same way.
• iPad — fieldwork or a board meeting: collect the PDFs AirDropped into Files, multi-select from the picker or share sheet (there’s no external drag-and-drop into the app on iPad), convert with the synced preset, and iCloud puts the XLSX on the Mac where the model lives.

One subscription covers iPhone, iPad, Mac, and Vision Pro, so the preset travels with the engagement.

The equation check: proof in one formula

Before the numbers go anywhere, run the accounting equation on the extracted sheet: sum the asset rows, sum the liability rows plus the equity rows, and compare both to the total assets figure printed on the statement — once per year column. A balance sheet balances by construction, so if your extracted sides agree with each other and with the printed total, every amount made it across: a missed line, a dropped minus sign, or an imported subtotal would each break the equality. It’s the same zero-effort completeness test the trial balance’s foot check gives you one level deeper in the books.

Then the sheet goes to work:

1. Map to the spreading template. Add a template_line column, VLOOKUP against the bank’s or the firm’s standard line map, and the model populates from a pivot instead of an afternoon of keying. This is where the transposed-digit risk dies.
2. Run the ratios. Current ratio, quick ratio, debt-to-equity, working capital — a column of formulas against typed rows, per year, in minutes.
3. Build the common-size. Divide every row by total assets and the two-year comparative turns into the percent-of-assets view that makes drift visible.
4. Consolidate the entities. Three entities, three accountants, one prompt, one batch — with company name from each header as a column, the eliminations worksheet starts from one sheet instead of three formats.
5. Tie it to the books. The statement’s lines should roll up from the trial balance, and the cash line should reconcile to the bank statements — both have their own Mac flows when those documents are also PDFs.

When not to use this

• You have system access. QuickBooks, Xero, Sage, and NetSuite all export a balance sheet to XLSX directly from the report screen. If you can log in — or can get the client to click Export instead of Print — take the export. The PDF path is for statements you receive rather than produce: borrowers, targets, predecessors, and the scanned years.
• You need the footnotes. Audited financials are a package, and the balance sheet’s story is half-told without the notes on debt covenants, leases, and contingencies. Extract the table by all means — then read the footnotes yourself. They’re prose, not a table job, and that’s where the bodies are buried.

Bottom line

For balance sheet PDFs that need to become a model on a Mac: gather the folder — every year, every entity, the scanned predecessor statements, all of it — drag the stack into ignitai, write the one-paragraph prompt (one row per line item, sections labeled, parentheses to minus signs, skip the subtotals, as-of date from the header), pick Excel, Convert, then prove it with assets = liabilities + equity before anything else. Use a pdfplumber script only for a single-issuer born-digital feed you want to own; keep client statements away from web converters entirely. The hours belong in the analysis — the ratios, the trend, the credit decision — not the retyping, and the on-device read means the statements never left your Mac to get there.

Get ignitai on the App Store — free download; your first document (up to 4 pages) converts free with Sign in with Apple, and one subscription covers iPhone, iPad, Mac, and Vision Pro.

FAQ

How do I convert a balance sheet PDF to Excel on a Mac?

Drag the PDF into ignitai, describe the rows in one sentence — line item, section, current year, prior year, parentheses mean negative, skip the subtotal rows — pick Excel, and hit Convert. The PDF is read on your Mac, and only its text goes to ignitai’s servers; the result is one sheet with one row per line item, ready to check against assets = liabilities + equity.

How do I verify the extraction got every number right?

Run the accounting equation. Sum the asset rows, sum the liability and equity rows, and compare both to the total assets figure printed on the statement — for each year column. A balance sheet balances by construction, so if your extracted sides agree with each other and with the printed total, the amounts made it across intact.

Can I convert three years of balance sheets into one spreadsheet?

Yes — select the three PDFs and run them as one batch with one prompt, adding the as-of date from each statement’s header as a column. Filenames never leave your Mac, so identity has to come from the printed header, and every balance sheet carries its date there. The result is one sheet ready to pivot into a three-year comparative.