GL
The General Ledger (GL) is the master accounting record that holds every financial transaction of an organisation, organised by account from the Chart of Accounts. It sits at the top of the finance stack, receiving summary postings from sub-ledgers such as accounts receivable, accounts payable, inventory, payroll and fixed assets, and is the source of the trial balance and statutory financial statements.
The General Ledger, almost always shortened to GL, is the master accounting record of an organisation. Every euro that moves through the business eventually lands here, posted to an account defined in the Chart of Accounts. If a sub-ledger answers the question which customer owes us what, the GL answers the broader question what is the financial state of the company right now.
In the finance stack, the GL sits at the top. Beneath it are the operational sub-ledgers: accounts receivable holds invoice-level customer detail, accounts payable holds vendor invoice detail, the inventory sub-ledger tracks stock movements, payroll tracks employee pay runs, and the fixed-asset register tracks property, plant and equipment. Each of these systems generates summary postings that flow into the GL. The GL then feeds the trial balance, which in turn feeds the balance sheet, profit and loss statement and cash flow statement that auditors, investors and regulators ultimately read.
Because of this position, the integrity of the GL determines the integrity of every downstream financial number. If the GL is wrong, the statutory accounts are wrong.
The GL is organised into accounts, and each account belongs to one of five categories drawn from the Chart of Accounts:
Every posting to the GL is a journal entry that follows double-entry bookkeeping rules: total debits must equal total credits. A sale on credit, for example, debits accounts receivable and credits revenue. A customer payment debits cash and credits accounts receivable.
The trial balance is the periodic snapshot that lists every GL account and its balance. The sum of all debit balances must equal the sum of all credit balances. If it does not, something is wrong, either in a journal entry, a sub-ledger feed, or a manual adjustment. The trial balance is the first artefact controllers review before closing a period.
One of the most important concepts for anyone touching the books is the control account relationship between the GL and the sub-ledgers.
Take accounts receivable. The AR sub-ledger contains every open and closed invoice for every customer: invoice numbers, due dates, partial payments, credit memos, disputes. It can run to hundreds of thousands of line items. The GL, in contrast, holds a single AR control account whose balance equals the sum of all open AR invoices at any point in time.
So if the AR sub-ledger shows total open receivables of 4.2 million euros across 18,000 invoices, the AR control account in the GL must also show 4.2 million euros. If those two numbers do not match, there is a reconciliation problem that has to be investigated before the books can be closed.
The same pattern applies to AP, inventory, payroll and fixed assets. Sub-ledger queries answer transaction-level questions: show me every overdue invoice for customer X. GL queries answer position-level questions: what is our total receivables exposure on the balance sheet. Both views are essential, and they must always tie.
The GL is the engine that drives the financial close. Whether the close is monthly, quarterly or annual, the sequence is broadly the same.
First, sub-ledgers are closed. AR posts the final cash receipts and credit memos for the period, AP posts vendor invoices and accruals, payroll runs are finalised, inventory counts are reconciled, and depreciation is calculated on fixed assets. Each sub-ledger then rolls its summary into the GL.
Next, GL accounts are reconciled. Control accounts are tied back to sub-ledger balances, bank accounts are reconciled to bank statements, and intercompany balances are matched between entities. Any variance becomes a reconciling item that must be cleared or explained.
Then adjusting journal entries are booked: accruals for expenses incurred but not yet invoiced, deferrals for revenue collected but not yet earned, provisions for bad debt, reclassifications between accounts. Once adjustments are complete, the trial balance is reviewed, the period is locked, and financial statements are produced.
For most mid-market and enterprise finance teams, this cycle still takes 5 to 10 working days. The GL is both the bottleneck and the gatekeeper.
The GL lives inside the ERP. The most widely deployed platforms among mid-market and enterprise finance teams include SAP S/4HANA, Oracle Cloud ERP, Microsoft Dynamics 365 Finance, NetSuite and Workday Financials. Smaller organisations often run on Sage, Xero or QuickBooks. The mechanics of the GL are the same across all of them: accounts, journal entries, control accounts, trial balance, close.
What is changing is the cadence. Three trends are reshaping how the GL is operated:
AI is now actively used to support GL operations in three concrete ways.
The first is anomaly detection in GL postings. Models trained on historical journal patterns flag entries that look unusual for the account, period or user, catching errors and potential fraud before they corrupt the trial balance.
The second is auto-reconciliation between sub-ledger and GL. Instead of controllers manually tying AR, AP or bank balances back to control accounts, AI matches transactions, identifies variances and proposes clearing entries, leaving humans to approve exceptions rather than chase every line.
The third is predictive close. By learning from prior periods, models estimate accruals, forecast close-cycle bottlenecks and flag accounts likely to require manual adjustment, so the team can pre-empt issues rather than discover them on day 7 of close. For AR and O2C leaders specifically, this means the AR control account is no longer a black box that gets reconciled once a month, but a live signal that ties customer-level collections activity directly to the balance sheet.
The General Ledger holds summary balances organised by account, while sub-ledgers hold the underlying transaction detail. For example, the AR sub-ledger contains every open invoice for every customer, but the GL only holds a single AR control account whose balance equals the sum of those invoices. Sub-ledger queries answer questions about specific transactions or customers; GL queries answer questions about the overall financial position. Both must always reconcile to each other.
Because the AR control account in the GL is, by definition, the summary of all open receivables in the AR sub-ledger. If the two do not match, either a posting was missed, a journal entry was booked incorrectly, or a sub-ledger transaction did not flow through. An unreconciled control account means the balance sheet is misstated, so controllers will not close the period until AR, AP, inventory and other control accounts tie back to their respective sub-ledgers.
A trial balance is a list of every account in the General Ledger along with its debit or credit balance at a point in time. The sum of debit balances must equal the sum of credit balances; if they do not, there is a bookkeeping error somewhere. The trial balance is the first checkpoint of the close process and the foundation for producing the balance sheet, profit and loss statement and cash flow statement.
The close cycle runs in a strict sequence: sub-ledgers close first and roll their summary balances into the GL, then GL control accounts are reconciled to those sub-ledgers, then adjusting journal entries are booked for accruals, deferrals and provisions, then the trial balance is reviewed and locked. Only once the GL is closed can financial statements be issued. The GL is therefore both the bottleneck and the gatekeeper of the close.
Most mid-market and enterprise finance teams run their GL inside an ERP such as SAP S/4HANA, Oracle Cloud ERP, Microsoft Dynamics 365 Finance, NetSuite or Workday Financials. Smaller organisations often use Sage, Xero or QuickBooks. The underlying mechanics, namely accounts, journal entries, control accounts and the trial balance, are the same across all of them; what varies is the user experience, the depth of automation and how easily the GL integrates with surrounding finance systems.
AI supports the GL in three practical ways. Anomaly detection models flag journal entries that look unusual for the account, period or user, catching errors and potential fraud early. Auto-reconciliation engines match sub-ledger transactions to GL control account balances and propose clearing entries for any variance, so controllers approve exceptions instead of chasing every line. Predictive close models forecast accruals and highlight accounts likely to need manual adjustment, shrinking the close window and reducing surprises on the final days of the period.
