General Ledger Template

In plain language: Names the account, assigns its unique account code, and categorizes it as an asset, liability, equity, revenue, or expense account.

Common mistake: Assigning the wrong account type to an account. Classifying a liability as an expense, for example, distorts the balance sheet and creates mismatches that surface only at audit time.

In plain language: Records the exact calendar date the transaction occurred — the economic event date, not the date it was entered into the system.

Common mistake: Using the entry date instead of the transaction date. This misaligns revenue and expense recognition with the correct accounting period, creating period-cutoff errors that distort financial statements.

In plain language: A cross-reference to the originating journal entry, invoice, receipt, or payment document that supports the ledger entry.

Common mistake: Leaving the reference field blank or using a generic note like 'misc.' Without a traceable reference, locating the source document during an audit or dispute requires a full manual search.

In plain language: A brief narrative explaining what the transaction represents — vendor name, service rendered, or nature of the payment.

Common mistake: Writing one-word descriptions like 'payment' or 'expense.' Vague descriptions make reconciliation and audit preparation significantly slower and increase the risk of duplicate entries going undetected.

In plain language: Records the amount debited to this account in the transaction, increasing asset and expense accounts or decreasing liability and equity accounts.

Common mistake: Entering a debit amount in the credit column — or vice versa — because the bookkeeper confused the normal balance direction. This creates an out-of-balance trial balance that can take hours to locate and correct.

In plain language: Records the amount credited to this account in the transaction, increasing liability, equity, and revenue accounts or decreasing asset and expense accounts.

Common mistake: Omitting the corresponding credit entry entirely when posting. A one-sided entry throws the entire ledger out of balance and triggers an immediate trial balance discrepancy.

In plain language: The account's cumulative balance after each transaction is posted, updated continuously so the current balance is always visible without a separate calculation.

Common mistake: Calculating the running balance only at period-end rather than after every entry. Without a continuous balance, errors accumulate silently and are far harder to isolate when discovered.

In plain language: The total debits and total credits posted to the account within a defined accounting period — month, quarter, or year — used to prepare trial balance and financial statements.

Common mistake: Mixing transactions from two accounting periods in a single subtotal block. Period-cutoff errors misstate revenue or expenses in both affected periods and require adjusting entries to correct.

In plain language: Flags entries that are adjustments — accruals, deferrals, depreciation, or corrections — rather than original cash transactions, so they can be traced back to the underlying calculation.

Common mistake: Posting adjusting entries without labeling them as such or documenting the underlying basis. Unmarked adjustments look like errors during audit review and require time-consuming explanations.

In plain language: Records who prepared the ledger entries, who reviewed them, and who approved the period close — establishing an auditable authorization trail.

Common mistake: Allowing a single person to both prepare and approve ledger entries without a second reviewer. Single-person authorization is the primary internal control gap that enables bookkeeping fraud to go undetected.

A general ledger is the master financial record of a business that captures every debit and credit transaction across all accounts — assets, liabilities, equity, revenue, and expenses — in date order. It is the central source of truth from which all financial statements (income statement, balance sheet, and cash flow statement) are derived. Every other accounting record — journals, subsidiary ledgers, bank reconciliations — feeds into or is verified against the general ledger.

A journal is the first point of entry for a transaction — it records what happened, when, in which accounts, and for how much. The general ledger is where those journal entries are posted by account, accumulating a running balance for each. The journal is the chronological record; the ledger is the account-by-account record. Both are required for a complete double-entry bookkeeping system.

All five account categories appear: assets (cash, accounts receivable, inventory, property), liabilities (accounts payable, loans, accrued expenses), equity (common stock, retained earnings, owner's draws), revenue (sales, service income, interest income), and expenses (rent, payroll, utilities, depreciation). Each account has its own dedicated ledger section with a running balance.

No single law universally mandates the term 'general ledger,' but tax authorities in the US, Canada, the UK, and the EU all require businesses to maintain accurate, organized financial records sufficient to support tax returns and withstand audit. In practice, a general ledger — or its equivalent in accounting software — is the standard method of meeting that requirement. Failure to maintain adequate records can result in penalties, estimated assessments, and in some cases criminal liability for tax evasion.

The IRS requires businesses to retain records supporting tax returns for a minimum of 3 years from the filing date, but 6–7 years is the recommended standard to cover the statute of limitations for substantial understatements of income. Canada's CRA requires 6 years from the end of the tax year. HMRC in the UK requires 5 years for self-assessment taxpayers and 6 years for VAT records. EU member states range from 5 to 10 years depending on the country and record type.

Yes — a well-structured spreadsheet covering account codes, transaction dates, reference numbers, debit and credit columns, and running balances satisfies the record-keeping requirements in most jurisdictions for small businesses. The risks are formula errors, version-control issues, and the absence of an audit trail for changes. Accounting software automates posting, enforces double-entry rules, and maintains a change log — making it preferable as transaction volume grows beyond roughly 50 entries per month.

The general ledger contains every individual transaction posted to every account, in detail. A trial balance is a summary report extracted from the general ledger that lists each account's closing balance in a single row, verifying that total debits equal total credits. The trial balance is prepared from the ledger — it does not replace it. The ledger is the source; the trial balance is a check on that source before financial statements are prepared.

An out-of-balance trial balance means at least one posting error exists — a one-sided entry, a transposition, a debit posted to the wrong account, or an arithmetic error in a running balance. Start by checking for transpositions (differences divisible by 9 often indicate swapped digits), then verify that every journal entry has an equal debit and credit posted. Do not close the period or prepare financial statements until the trial balance balances to zero difference.

Yes — each legal entity must maintain its own general ledger. Commingling transactions from multiple entities in a single ledger makes it impossible to produce accurate financial statements for each entity, creates tax filing errors, and can pierce the liability protection of corporate structures. If you operate multiple entities, use entity-specific account codes and separate ledger files, with intercompany transactions recorded in both entities' ledgers as elimination entries.