ERP Core ConceptsGlossary

What Is General Ledger?

Also known as: GL, nominal ledger

Definition

The general ledger is the central accounting record of a business, where every financial transaction posts as balanced debits and credits against accounts in the chart of accounts, producing the trial balance behind all financial statements.

General Ledger Explained

The general ledger enforces double-entry bookkeeping: every journal entry must balance, with total debits equal to total credits. Entries carry an account, an amount, a posting date that determines the fiscal period, a reference to the source transaction, and usually dimensional segments such as site, department, or project. Because the ledger is the aggregation point, the balances in it summarize potentially millions of subledger transactions into a few thousand account balances that produce the balance sheet and income statement.

In an integrated ERP, the vast majority of general ledger entries are generated automatically by operational transactions rather than typed by accountants. Receiving material debits inventory and credits a received-not-invoiced account. Shipping debits cost of goods sold and credits inventory. Reporting labor to a work order debits work in process and credits a labor absorption account. This automation is the payoff of ERP integration, and it is also why an operational configuration error, such as a wrong product line account assignment, shows up as a mysterious ledger imbalance rather than an obvious operational problem.

Subledgers detail what the ledger summarizes. Accounts receivable, accounts payable, inventory, and fixed assets each maintain transaction-level records that must reconcile to their control account in the general ledger. Reconciliation between subledger and control account is a core period close activity, and an unexplained difference almost always means either a direct journal entry was posted to a control account or a subledger transaction failed to post. Most ERPs can lock control accounts against manual entry precisely to prevent the first case.

Dimensional structure determines what the ledger can answer. A ledger segmented only by account can produce a company income statement but cannot answer profitability by site, product line, or contract without extracting to a separate reporting tool. Government contractors often need indirect cost pool and base structures embedded in the ledger to support incurred cost submissions, and retrofitting that structure after go-live is one of the more painful ERP remediation projects.

Why It Matters

  • The general ledger is the audited system of record, so its accuracy determines whether financial statements can be relied on or signed.
  • Because ERP posts to it automatically, operational configuration errors surface as financial misstatements rather than obvious defects.
  • Subledger to control account reconciliation is the standard mechanism for detecting broken integrations and unposted transactions.
  • Ledger dimensional design sets the limit on what management reporting is possible without external data warehousing.

In Practice

Common gotcha: someone posts a manual journal entry directly to the inventory control account to force a balance sheet number to agree. The general ledger now balances but no longer reconciles to the inventory subledger, and the difference compounds every month. Lock all control accounts against manual entry and require corrections to be made through the originating subledger.

Frequently Asked Questions

What is the difference between the general ledger and a subledger?

A subledger holds transaction-level detail for one area, such as every open customer invoice in accounts receivable. The general ledger holds the summarized balance for that area in a control account. Subledgers answer which customer owes what; the ledger answers total receivables. They must reconcile, and any unexplained gap indicates a posting or integration failure.

Can you post directly to the general ledger in ERP?

Technically yes through manual journal entries, and that capability is needed for accruals, reclassifications, and adjustments. But control accounts fed by subledgers should be locked against direct entry, because a manual post there breaks reconciliation permanently. Good practice is to restrict manual journals to non-control accounts and require documented approval and support for each one.

Working with General Ledger in a live environment? Our engineers do this every day - and our AI agents automate most of it.