What Is a Ledger? The General Ledger, Explained

A ledger is the master record of a business organized by account: every cash movement in one place, every sale in another, every expense in its own account. The general ledger (GL) is the complete collection — the single source from which the trial balance and every financial statement are built. This guide covers the journal-vs-ledger distinction, what lives inside a ledger account, the chart of accounts, subledgers and control accounts, a worked posting example, and how month-end review actually uses the GL.

Journal vs ledger — the two views

The journal records transactions in date order, each with its debits and credits (the layout rules are in journal entry format). The ledger re-sorts those same entries by account. Same data, two lenses: the journal answers “what happened on March 5?”, the ledger answers “what has happened to Cash all year?” Posting is the transfer from one view to the other — instantaneous in modern software, but conceptually still the spine of every system.

Inside a ledger account

Each account carries: an identifying GL code from the chart of accounts, its opening balance, every debit and credit posted with dates and references back to source entries, and a running balance. The visual shorthand for one account is the T-account — two columns under a T — explored with a full example in T-accounts. The reference trail matters as much as the numbers: a clean GL lets anyone walk from a statement line back through the ledger to the original invoice, which is precisely what auditors do for a living.

The chart of accounts — the GL’s skeleton

The chart of accounts is the numbered list of every account the business uses, conventionally grouped: 1000s assets, 2000s liabilities, 3000s equity, 4000s revenue, 5000s+ expenses. Design choices here echo for years — too few accounts and analysis is impossible (“Miscellaneous expense: $400,000”); too many and posting becomes guesswork between near-duplicates. The working rule: create an account when someone will make a decision from its balance, not before.

Subledgers and control accounts — the detail beneath

High-volume areas keep their own subsidiary ledgers: accounts receivable (one record per customer), accounts payable (per vendor), inventory (per item), fixed assets (per asset). The GL then carries a single control account per subledger whose balance must always equal the subledger’s total:

Control account (GL)	Subledger detail
Accounts receivable — $84,000	217 customer balances summing to $84,000
Accounts payable — $31,500	64 vendor balances summing to $31,500
Inventory — $120,000	1,400 item records summing to $120,000

The equality is a built-in cross-check: when control and subledger disagree, a posting skipped one level, and reconciling the two is a standard month-end task.

Worked example — one transaction, full journey

March 5: invoice a client $5,000. Journal entry: debit Accounts receivable 5,000, credit Sales revenue 5,000. Posting hits two GL accounts (AR and Revenue) and the client’s record in the AR subledger. March 20: client pays. Debit Cash, credit AR — again GL and subledger together. At month end, the AR control shows every invoice and receipt netted; the subledger names exactly which clients still owe; and the trial balance pulls the AR balance into its debit column along with every other account. One transaction, three layers, all reconciled — that is the GL doing its job.

Month-end: how professionals actually read a GL

Nobody reads a ledger line by line. The working sequence: run the trial balance and scan for wrong-side balances and odd movements (the review workflow detailed in general ledger vs trial balance); drill into any suspicious account’s ledger detail; reconcile control accounts to subledgers; reconcile Cash to the bank statement; then book adjusting entries — accruals like accrued liabilities, consumed prepayments, depreciation. Only after the GL survives this gauntlet do the statements get built from it. A messy GL is not a bookkeeping inconvenience; it is the reason month-end takes three weeks in some companies and three days in others — and choosing machinery that fits your volume is the subject of accounting systems.

The three documents, side by side

	General journal	General ledger	Trial balance
Organized by	Date	Account	Account (balances only)
Contains	Every entry as recorded	Every entry, re-sorted	One line per account
Job	Capture	Master record	Verify & review

Common GL problems — and their cost

Miscoding (marketing spend landing in office supplies) corrupts every report downstream while keeping totals perfectly balanced. Unreconciled control accounts mean the GL and subledger have quietly diverged — receivables reports nobody can trust. Suspense-account graveyards collect entries nobody classified, aging into write-offs. Chart bloat — three near-identical expense accounts — splits the same cost across lines and hides trends. The common thread: a GL fails silently. Nothing crashes; the reports just slowly stop meaning anything, which is why disciplined monthly reconciliation is the habit that separates clean books from expensive archaeology.