Drop in any trial-balance PDF — QuickBooks, NetSuite, Sage Intacct, Xero, Microsoft Dynamics, or a printed PDF from a legacy ERP — and get a clean Excel file with account number, account name, debit, credit, and net balance. Adjusted, unadjusted, and post-closing trial balances all extract with the same workflow.
Auditors request the trial balance as the entry point into ledger testing. Tax preparers rebuild the books off a year-end TB. Controllers reconcile pre- and post-adjusting TBs as part of close. Most ERPs print TBs to PDF cleanly but Excel exports break account hierarchy, drop subtotals, or split sub-account roll-ups across rows.
Generic PDF tools either flatten the account column into one cell or lose the debit-credit pairing. The structure that makes a TB useful — account number ordering, debit-credit columns separate, subtotal rows with totals tied — is exactly what generic tools mishandle.
PDFExcel reads trial balances by account. Account number + account name extract as separate columns. Debit and credit columns stay paired. Net balance computes (or extracts the printed value if shown). Subtotal rows for asset / liability / equity / revenue / expense show up with a clear marker so they don't get mixed with detail rows. Adjusted, unadjusted, and post-closing TBs all extract with the same workflow.
Drop the Excel into your audit workpaper, tax-prep working trial balance, or close-reconciliation sheet. Pair with general ledger extraction for cross-checking summary against detail. Pair with balance sheet and income statement for full-suite financial reconstruction.
Trained on QuickBooks, NetSuite, Sage Intacct, Sage 50, Xero, Microsoft Dynamics 365, Oracle Financials, and SAP TB exports. Account ordering preserved, debit-credit math ties, subtotals tagged.
Trial balance work happens almost entirely in Excel. The bottleneck is getting the TB out of PDF without breaking structure.
Account-ordered rows with debits and credits in separate columns. Subtotal rows tagged for filtering. The math ties — sum of debits equals sum of credits across the full TB.
| # | Account # | Account Name | Debit | Credit | Net |
|---|---|---|---|---|---|
| 1 | 1010 | Cash — Operating | $182,420.40 | $182,420.40 | |
| 2 | 1100 | Accounts Receivable | $94,820.18 | $94,820.18 | |
| 3 | 2010 | Accounts Payable | $48,210.66 | -$48,210.66 | |
| 4 | 3010 | Common Stock | $50,000.00 | -$50,000.00 | |
| 5 | 4010 | Service Revenue | $612,480.00 | -$612,480.00 | |
| 6 | 6010 | Rent Expense | $38,400.00 | $38,400.00 |
Audit associates entering ledger testing, tax preparers building working trial balances, controllers reconciling pre/post-adjusting TBs at close.
Client TB delivered as PDF. Pull as Excel via PDFExcel, build the working trial balance with adjustment columns, run lead-schedule reconciliation. Saves the half-day manual rebuild.
Client provides year-end TB PDF (no ERP access). Pull into Excel, map to tax COA, build M-1 adjustments. Tax-prep TB ready in minutes vs hours retyping.
Pre- and post-adjusting TB comparison drives the close review. Pull both as Excel, side-by-side compare, flag account-level changes for journal-entry review.
Yes. Subtotal rows (asset / liability / equity / revenue / expense subtotals) are tagged in a flag column so you can filter them out for detail-only views or keep them for grouped views. Grand-total row preserved.
Yes — all three TB variants extract with the same workflow. The adjustment-flag column lets you tag which TB you uploaded for side-by-side reconciliation.
Yes — sum of debits should equal sum of credits across the full TB. We preserve the printed values; the SUM checks on the Excel side.
10 documents per month, free, forever. A typical engagement TB pull is 1-3 PDFs (interim TB + year-end TB + post-closing TB) — fits the free tier comfortably.
Yes. Multi-period comparative TBs extract with separate Net columns per period (e.g., Net-2024 / Net-2025) so the period-over-period comparison reads naturally in Excel.