The general ledger is the master record of every transaction posted to every account, organized by account rather than by date. Every invoice, bill, payment, deposit, and journal entry posts to the GL — making it the most-referenced entry in this glossary. The GL is what every other accounting report (trial balance, balance sheet, income statement) pulls from.
A transaction in modern accounting software hits multiple places: the customer record, the vendor record, the bank account, the relevant subledgers. But underneath all of those views, the GL is the single canonical record. If a transaction isn't in the GL, it doesn't exist for accounting purposes.
In QBO, the GL is generated automatically from every Invoice, Bill, Expense, Sales Receipt, and Journal Entry you create. You don't usually post to the GL directly; the source documents do it for you. But the GL is what every report ultimately reads.
The journal lists transactions in date order: March 1, March 2, March 3. The GL lists transactions in account order: every transaction that hit Cash, then every transaction that hit AR, then every transaction that hit Sales Revenue. Within each account, transactions are listed by date.
That account-first organization is what lets you ask "what happened in Cash this month?" and get a clean answer. The journal can't answer that question quickly because it groups by date instead.
Every accounting system (paper, Excel, QBO, NetSuite, SAP) has a GL because the GL is the only structure that supports double-entry validation. If debits don't equal credits across all GL accounts, the system has an error. Without a GL, there's no place to run that check.
The general ledger is the master account-by-account record of every transaction in your books. It groups every debit and credit by the account they hit, with running balances. Every financial report (trial balance, P&L, balance sheet) derives from the GL. It's the spine of the double-entry method.
Three related reports show up in every accounting system:
The GL is the middle layer. It's more detailed than the trial balance and more useful than the journal for most bookkeeper work.
T-accounts are how the GL gets taught in accounting class. They show up almost nowhere in actual day-to-day work, but understanding them helps you read GL reports correctly.
A T-account is literally a T drawn on paper. The account name is at the top. The vertical line splits the account into left and right halves. Debits go on the left. Credits go on the right. The balance is the difference between the two columns.
For Cash:
The ending balance is total debits minus total credits.
Every account has a "normal balance", the side it usually carries. Asset accounts (Cash, AR, Inventory) carry debit balances. Liability accounts (AP, Loans, Credit Cards) carry credit balances. Equity accounts (Owner's Equity, Retained Earnings) carry credit balances. Revenue carries credit balances. Expense accounts carry debit balances.
A negative number on the "wrong" side is usually an error: a negative cash balance, a negative AR balance with no offsetting deposit, a debit balance in revenue. Most QBO files have a few of these in nooks of the chart of accounts; cleaning them up is part of any year-end close.
Bookkeepers don't draw T-accounts in real life. They run GL reports out of QBO instead. The T-account exists as a teaching aid because it makes debits and credits visual. Once the rules are internalized, the T-account stops being useful and the GL report takes over.
Cash account, March 1 starting balance $25,000:
Ending balance: $25,000 + $15,000 - $12,500 = $27,500.
That same information in QBO comes out as a Transaction Detail report on the Cash account. Same data, different presentation.
T-accounts are slow. A bookkeeper running a 30-client book in QBO has hundreds of accounts and thousands of transactions per month. The GL report (sortable, filterable, exportable) replaces the T-account in the actual workflow.
T-accounts still come up when explaining a complex journal entry to a client or walking a junior bookkeeper through a posting. As a workflow tool, they don't survive the move from textbook to QBO.
In a paper accounting system, posting was a mechanical step: copy each line of each journal entry into the relevant GL account. Modern systems do this automatically, but the underlying mechanic still matters.
A journal entry is a list of debits and credits with at least two lines. Posting means taking each line of the entry and adding it to the relevant GL account's running record. For an invoice that creates a journal entry of "debit AR $3,500, credit Service Revenue $3,500," posting means adding $3,500 to the debit side of the AR ledger and $3,500 to the credit side of the Service Revenue ledger.
In a paper system, this was hours of work per month. In QBO, it happens the instant you save the invoice.
When you save an Invoice, Bill, Expense, or other source document in QBO, the system writes the journal entry behind the scenes and posts it to the GL in real time. The bookkeeper doesn't see the posting step. They just see the source documents and the resulting reports.
That's why "running the GL" in QBO is just running the GL report. There's no posting to do because it already happened.
Some entries don't have a source document. Year-end accruals, depreciation, deferred revenue, and reclassifications are typically posted as manual journal entries via "+ New → Journal Entry." The bookkeeper enters the debits and credits directly. QBO validates that debits equal credits and posts to the GL the same way.
These manual entries are where most GL errors originate: a debit-only entry that QBO rejects, or a posting to the wrong account.
Year-end depreciation entry:
GL impact: Depreciation Expense ledger gains $4,800 on the debit side (its normal balance). Accumulated Depreciation ledger gains $4,800 on the credit side (it's a contra-asset, so credits build the balance). The balance sheet net book value of fixed assets drops by $4,800. The P&L net income drops by $4,800.
One journal entry, four account impacts, all flowing through the GL.
Some accruals get reversed at the start of the next period. A December 31 accrual of $2,000 in Accrued Liabilities for a December rent or utilities bill that arrives January 8 gets reversed January 1: debit Accrued Liabilities $2,000, credit Utilities Expense $2,000. When the actual bill is entered January 8, it posts the expense correctly without double-counting.
The reversal is a journal entry that posts to the GL like any other.
The GL is the master, but several specialized subledgers feed it.
The AP subledger tracks every vendor's open balance. The total of every vendor balance equals the AP control account in the GL. If they don't match, there's a posting error somewhere, typically a journal entry that hit AP without selecting a vendor.
The AP subledger is what produces the aging report. The GL control account is what the balance sheet shows. They must tie.
Same structure on the receivables side. Every customer's open balance is tracked in the AR subledger; the sum equals the AR control account in the GL. Mismatches here often indicate journal entries posted to AR without a customer attached.
Fixed assets are tracked at the individual asset level (each piece of equipment, each vehicle, each significant improvement) with its own depreciation schedule. The total of all asset balances and accumulated depreciation balances ties to the GL control accounts.
In smaller QBO files, the fixed asset subledger is often kept in Excel rather than QBO directly. Either way, the spreadsheet total has to tie to the GL.
For businesses with inventory, every SKU has its own quantity-on-hand and value record. The total inventory value across all SKUs equals the Inventory control account in the GL. Discrepancies (physical count vs book) get reconciled monthly or quarterly.
Imagine if every vendor invoice and every customer payment posted directly to the GL without subledgers. The GL would have hundreds of thousands of lines, none of them grouped by vendor or customer. Reports would be unusable.
Subledgers solve that by grouping the detail externally and posting only summary entries to the GL. The detail stays in the subledger; the totals tie to the GL control accounts.
Monthly close includes subledger-to-GL reconciliation: AP subledger total to AP control account, AR subledger total to AR control account, and so on. A mismatch is a control failure that needs investigation. Most are caused by journal entries posted directly to the control account without going through the subledger workflow (a manual JE to AR without selecting a customer, for example).
The fix is to delete the rogue JE and re-post via the proper source document, or post a correcting JE that matches what the subledger would have done.
The GL is the input. The financial statements are the output. Here's the chain.
The trial balance is a single snapshot per account: debit total, credit total, ending balance. It's generated by summarizing every line of every account in the GL. The trial balance proves debits equal credits across the entire GL. See the month-end trial balance primer for the troubleshooting framework when it doesn't.
The balance sheet pulls every asset, liability, and equity account from the trial balance. The income statement pulls every revenue and expense account. Closing entries at year-end zero the income statement accounts and roll the net into Retained Earnings on the balance sheet.
Two reports, both derived from the trial balance, both ultimately derived from the GL.
In QBO, you don't run "the GL" and then "the trial balance" and then "the balance sheet" as sequential steps. You just run the report you want. QBO calculates the trial balance and the financial statements on demand from the underlying GL data.
The chain still exists structurally (the data flows GL → TB → Statements), but the bookkeeper interacts with whichever report they need.
When the balance sheet looks off, the diagnostic flow is: check the trial balance for unusual balances (negative cash, debit balances in revenue), then drill into the GL for the specific account showing the problem, then identify the offending transaction. Without understanding the chain, the bookkeeper has nowhere to start.
QBO's GL reports are accessed through the Reports center.
The path is "Reports → For My Accountant → General Ledger." The default view shows every transaction in every account for the current period. Filter to a specific account, date range, or transaction type to narrow it down.
The most useful filters:
For diagnostic work, filter by account and run the full year. You can see every transaction that hit the account, with running balance, in one report.
Export to Excel for any review where you need to filter, sort, or annotate. The export includes transaction date, type, number, name, account, debit, credit, and balance: everything a tax preparer or auditor would need.
Send the trial balance for a quick "are debits balanced" check. Send the full GL when the preparer needs transaction-level detail (year-end review, audit prep, accounts payable cleanup verification). The full GL is large but the most useful single export for serious review.
Three patterns account for most GL problems.
Misclassifying a transaction at entry time creates a GL error that propagates to every report. A loan payment booked as an expense (instead of split between principal-reducing-loan-balance and interest-expense) inflates expense and hides debt. A capital expenditure booked as repair expense inflates current period expense and skips the asset.
These errors are caught by reading the GL for unusual balances during monthly close. Cleanup is a reclassification journal entry.
QBO won't save an unbalanced JE; the system enforces debits-equal-credits at save time. Legacy data imported from other systems can have unbalanced entries that silently break the trial balance. The fix is to find the offending JE and add the missing line.
When the AP subledger total doesn't match the AP control account, somewhere a journal entry posted to AP without going through the vendor record. Find it via the GL detail report on the AP account, looking for entries with no vendor name. The fix is to either add the vendor or post a correcting entry.
A clean monthly close includes subledger-to-GL ties for AP, AR, fixed assets, inventory, and any other subledger the business uses. Doing it quarterly is a minimum; monthly is best. The longer subledger and GL drift apart, the harder the cleanup gets.
Growthy is bookkeeping software, not a CPA firm. This content is educational, not professional advice. Full disclaimer.
Related: Accounting & Bookkeeping Glossary, Double-Entry Bookkeeping: How Debits & Credits Actually Work, Trial Balance: What It Is, How to Read It, and What to Do When It's Off, Accounts Payable (AP): What It Is & How It Works
Free during alpha. Read-only access. You review every sync.
CPA firm partner who got tired of watching bookkeepers click categorize 500 times a day. Built Growthy to fix it.
View all articles →Growthy is dedicated to helping businesses of all sizes make informed decisions. We adhere to strict editorial guidelines to ensure that our content meets and maintains our high standards.
The trial balance lists every GL account with its debit or credit balance, proving total debits equal total credits. Here's how to read it, and the troubleshooting framework for when it doesn't balance.
Undeposited Funds is the QBO holding account where customer payments sit between receipt and bank deposit. It exists so a single bank statement deposit can match multiple customer payments. Here's how to use it correctly and clear stuck balances.
Uncategorized Expense is QuickBooks Online's catchall for transactions imported but never assigned to a real category. A clean book has $0 in this account. Here's how to recategorize what's there and prevent new ones from landing.