Every Acumatica close, someone asks for "the trial balance" when what they actually need is the general ledger detail, or vice versa. The two reports answer different questions — one confirms the books balance, the other shows you why they don't — and knowing which to pull first saves a lot of back-and-forth during month-end.
What the Trial Balance report shows
The Trial Balance report lists every account (optionally by subaccount) with its beginning balance, period activity, and ending balance, summarized — no individual transaction lines. It exists to answer one question: do total debits equal total credits for the period, ledger, and branch you're looking at. It's the report an accountant runs first at month-end, before touching anything else, because if it doesn't balance nothing downstream will either.
You'll find it under Finance > General Ledger > Reports. It filters by ledger (useful if you run parallel ledgers for statutory vs. management reporting), by branch or consolidated across branches, by account class or a specific account range, and by period or date range. The output is deliberately flat — one line per account — so it's fast to scan and easy to tie to a set of financial statements.
What the General Ledger report shows
The General Ledger report (and the related GL transaction inquiry screens) is the drill-down version: every posted transaction line for the selected accounts, in date order, with the batch number, reference, description, and source document it came from. Where the Trial Balance tells you an account moved by a certain amount, the General Ledger report tells you which invoices, journal entries, or AP bills made up that movement.
This is the report you reach for once the Trial Balance flags something — an account that doesn't match expectations, a balance that moved more than it should have, or a variance an auditor is asking about. You filter it the same way (ledger, branch, subaccount, date range) but the output is transaction-level, so it's the tool for tracing a number back to its source document rather than confirming the books tie out overall.
| Trial Balance | General Ledger | |
|---|---|---|
| Level of detail | Summarized by account/subaccount | Individual posted transactions |
| Typical use | Confirm debits = credits before close | Investigate a specific balance or variance |
| Drill-down | No — links out to GL detail | Yes — links to source document |
| When to run it | First, at period-end | After the Trial Balance flags an issue |
Filtering by ledger, branch, and subaccount
Both reports share the same filter logic, and getting it wrong is the most common source of "the numbers don't match" confusion. If your tenant runs a statutory ledger alongside the actual ledger, running the Trial Balance against the wrong ledger will show a balance that looks wrong but isn't — it's just a different book. Same with branch filtering on multi-branch tenants: a consolidated Trial Balance and a single-branch Trial Balance will legitimately disagree, and subaccount segmentation (department, project, cost center) can make an account look unbalanced at the subaccount level when it's balanced at the account level.
When someone says the Trial Balance and General Ledger "don't agree," the first thing to check is whether both reports were run with identical ledger, branch, and date filters. Nine times out of ten that's the whole discrepancy.
Common reconciliation pitfalls
Unposted batches are the usual culprit when a Trial Balance looks off during close — a journal entry sitting in Balanced or On Hold status doesn't hit the ledger, so the Trial Balance won't reflect it while a source document elsewhere implies it should. Run the Batches screen filtered to unposted status before you trust any period-end Trial Balance.
The other pitfall is out-of-balance postings introduced by a customization — a PXGraphExtension that posts a GL batch with unbalanced debits and credits will normally be rejected by the posting engine, but a poorly written import or integration that writes directly to GL tables (rather than going through the standard posting graph) can bypass that check. If a Trial Balance won't tie out and there's no obvious unposted batch, that's the next place to look.
Wrapping up
Use the Trial Balance to confirm the period is in balance and the General Ledger report to find out why it isn't. Match your ledger, branch, and subaccount filters between the two before assuming there's a real discrepancy, and check for unposted batches before you chase a customization bug that isn't there.
Independent software engineer in Nairobi specialising in Acumatica customisations, Laravel backends, and tax fiscalisation integrations across East and Southern Africa.