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

The audit engagement starts the same way every year: the client sends the year-end trial balance. Not a QuickBooks backup, not an export — a PDF, because that’s what the bookkeeper’s report screen prints. Two hundred accounts across nine pages, account numbers and names on the left, debits and credits in their own columns, section subtotals interleaved, a grand total on the last page that foots to the penny. Every workpaper in the file — the lead schedules, the mapping to the firm’s groupings, the comparative against last year — starts from those two hundred rows. And right now they’re a print layout.

Every accountant who works with client-side books meets a version of this. The auditor whose client runs QuickBooks Desktop and sends whatever File → Print produces. The tax preparer who inherits an engagement and gets the predecessor’s final trial balance as a scanned page in the permanent file. The fractional controller consolidating four entities whose bookkeepers each use a different system — Sage here, Xero there, something legacy at the entity nobody talks about — and every one of them delivers a PDF. The reviewer building a three-year comparative from PDFs in the prior-year files. The numbers are all there; the numbers are all trapped.

This guide is the Mac workflow: convert trial balance PDFs to Excel on Mac — read on-device, only the text sent to ignitai’s servers — with one row per account, debits and credits in their own columns, footing to the printed total, ready for mapping and the workpapers.

In this guide10 sections

Why trial balances defeat table extractors

A trial balance is the most table-shaped document in accounting, which makes it deceptive — grid-based extractors still mangle it, for four reasons:

1. The debit/credit columns are mostly blank. Every account has an amount in exactly one of the two columns. Grid detectors routinely collapse the empty column, shift credits left into the debit column, and hand you a sheet where cash and accounts payable look like the same kind of number. Once the sign convention is lost, it can’t be reconstructed from the amounts alone.
2. Subtotals print like accounts. Section subtotals — total assets, total liabilities, total income — and the grand-total line print in the same font and columns as account rows. Import them as data and the sheet double-counts; the foot check fails and you spend an hour hunting a phantom difference.
3. Multi-page layouts repeat headers and split rows. A nine-page trial balance repeats its column headers on every page, sometimes with a “balance carried forward” line. Grid tools import each page as its own fragment, headers included, and long account names wrap onto a second line that becomes a spurious row.
4. The prior years are scans. The predecessor’s final trial balance, the permanent-file copy, the entity that still faxes — those exist as paper or rasterized images. A layout parser needs a text layer; a scan has none. It has to be read, not parsed.

The fix is an extractor that understands the document — that “48,201.77” sits in the credit column of the accumulated-depreciation row, whichever system printed it and whichever page it landed on. 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 QuickBooks, Sage, Xero, and the legacy system in the same folder:

1. Drag the PDFs in — or use the file picker, or right-click → Open With from Finder. The born-digital reports and the scanned predecessor pages work the same way; the scanned-PDF walkthrough covers capture-quality details for the paper ones.

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 account: account_number, account_name, debit, credit. An account has an amount in exactly one of debit or credit — leave the other blank. Skip section subtotals, page totals, carried-forward lines, and the grand total. Bare amounts, no currency symbols or thousands separators.”

   Save it as a preset — it syncs to your other devices via iCloud — and every client’s year-end PDF is one click from being workpaper-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 the dense multi-page layouts; the same flow works back to macOS 14.4. A nine-page trial balance is usually ready in under a minute.

4. Open the result in Excel or Numbers. One worksheet, one row per account — bare amounts, blanks where the document was blank — and the amounts are real numbers in the Excel file, so the foot check runs the moment it opens. ignitai also totals the debit and credit columns on screen, with the original page a click away; edits happen in the spreadsheet.

The comparative, one batch. Select this year’s and the prior two years’ trial balances in Finder and drag them in together with the prompt extended by one clause: “add as_of_date from the report header.” Filenames never leave your Mac, so there’s no filename column — identity has to come from the document itself, and every trial balance prints its as-of date (and company name, if you’re consolidating entities) in the header. Three years land in one sheet, one row per account per year, and the comparative pivot is account × as_of_date. Scanned prior 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 grain. One row per account is the workpaper grain. If a client’s system prints a trial balance with beginning balance, activity, and ending balance columns, that’s still one run — name the five columns in the prompt. But the general-ledger detail behind an account is a different document and a different run, not extra sheets in the same workbook.

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 trial balance trips the grid detector’s weak spots: the mostly-blank debit/credit pair collapses into one ambiguous amount column, subtotal rows arrive embedded in the data, and each page imports as a separate table you then stitch and de-header by hand. Against the scanned prior years it returns nothing at all.

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

If every trial balance you’ll ever touch comes from one accounting system, one report format, born-digital, a Python script — pdfplumber to pull words by position, pandas to assemble rows — is a defensible build, and the fixed column positions of a single system’s report make it easier than most documents. The costs arrive on schedule anyway: the debit/credit split needs positional logic, subtotal rows need exclusion rules keyed to label text, the system’s next report-format update silently shifts your coordinates, and the second client on a different system doubles the script. The scanned years it can’t touch at all. For a practice whose clients run four different systems, the maintenance never amortizes.

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

Generic web PDF-to-Excel tools share Power Query’s blindness to the blank-column convention — and on this document the quality question is beside the point. A trial balance is the client’s entire financial position on a page: every account, every balance, cash to retained earnings. Uploading it to a free converter you don’t control is a confidentiality decision made on the client’s behalf, and for an accountant it’s the kind of decision 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

Trial balances don’t always arrive at the desk:

• iPhone — the predecessor accountant hands over the permanent file at a lunch meeting: capture the final trial balance with the in-app camera scan, apply the saved preset, and the opening balances are rows before you’re back at the office. 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 at the client’s office: collect the PDFs they AirDrop you in Files, multi-select them 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 workpapers live.

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

The foot check: the strongest extraction test in accounting

Before anything else, foot the sheet: sum the debit column, sum the credit column. A trial balance balances by construction — debits equal credits, always — so the two sums must match each other and the grand total printed on the document’s last page. If they do, every amount made it across intact: a missed account, a shifted column, or an imported subtotal would each break the equality. No other document type hands you a built-in, zero-effort extraction check this strong — use it every time, on every file, before the mapping starts.

Then the sheet goes to work:

1. Map to the firm’s groupings. Add a grouping column, VLOOKUP against the firm’s standard chart-of-accounts map, and the lead schedules populate from a pivot. This is the task that has no manual shortcut — two hundred accounts retyped is an afternoon, and one transposed digit surfaces at review as a difference nobody can find.
2. Build the comparative. With as_of_date in the batch output, pivot account × year and the analytical review’s flux analysis is a column of formulas instead of a week of retyping prior-year PDFs.
3. Consolidate the entities. Four entities, four systems, one prompt, one batch — with company name from each header as a column, the consolidation worksheet’s eliminations start from one sheet instead of four formats.
4. Tie the payroll accounts. Wages, payroll-tax liabilities, and accrued payroll on the trial balance should tie to the year’s registers — the payroll register Mac flow extracts that side of the check.
5. Tie cash. The cash accounts should reconcile to the bank — the bank-statement-to-Excel guide turns the statements into the transaction detail behind the balance.

When not to use this

• You have system access. QuickBooks, Xero, Sage, and NetSuite all export a trial balance to XLSX or CSV directly from the report screen. If you can log in — or can get the client to click Export instead of Print — take the export; extracting from a print layout of data the system will hand you structured is a workflow built backwards. The PDF path is for closed engagements, predecessor records, entities you don’t control, and the scanned years.
• You need the adjusting entries. The trial balance records where the books stand; the adjusting, reclassifying, and eliminating entries are judgment work that happens downstream in the workpapers. Extraction gets the starting column right — it doesn’t propose the entries.

Bottom line

For trial balance PDFs that need to become workpapers on a Mac: gather the folder — every entity, every year, the scanned predecessor pages, all of it — drag the stack into ignitai, write the one-paragraph prompt (one row per account, debit and credit in their own columns, skip the subtotals, as-of date from the header), pick Excel, Convert, then foot it against the printed total before anything else. Use a pdfplumber script only for a single-system born-digital feed you want to own; keep client trial balances away from web converters entirely. The engagement’s hours belong on the mapping and the flux analysis — not the retyping — and the on-device read means the client’s books 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 trial balance PDF to Excel on a Mac?

Drag the trial balance PDF into ignitai, describe the rows in one sentence — account number, account name, debit, credit, blank means zero, skip the subtotal and total 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 account, ready to foot and map.

How do I check the extraction didn’t miss an account?

Foot it. Sum the debit column, sum the credit column, and compare both to the totals printed on the trial balance’s last page. A trial balance balances by construction, so if your extracted debits equal your extracted credits and both match the printed total, every amount made it across. No other document type hands you a built-in extraction check this strong.

Can I convert twelve monthly trial balances into one sheet?

Yes — select all twelve PDFs and run them as one batch with one prompt. Add the as-of date from each report’s header as a column, since filenames never leave your Mac and there is no filename column in the output. One sheet, one row per account per month, ready for the comparative pivot.