Key Points
- The general ledger is the single source from which all primary financial statements are derived; errors in it flow directly to the reported figures.
- Auditors obtain a complete GL extract early in fieldwork because it underpins both journal entry testing under ISA 240.32–33 and substantive analytical procedures.
- Entities with more than 50,000 journal entries per year increasingly use automated posting rules, which shifts the audit focus from individual entries to IT general controls.
- A GL that does not reconcile to the trial balance is a red flag for unrecorded transactions or posting errors that affect every financial statement line.
What is General Ledger?
The general ledger holds every posted transaction of the entity, grouped by account code according to the chart of accounts. Each entry records a debit, a credit, a date, a narrative, and a source reference. Sub-ledgers (accounts receivable, accounts payable, fixed assets) feed into the GL through periodic or real-time posting, and the GL totals must reconcile to those sub-ledgers at every reporting date.
From an audit perspective, ISA 500.A1 identifies the accounting records (including the general ledger) as a primary source of audit evidence. The auditor does not audit the GL in isolation. Instead, the GL provides the population from which samples are drawn for substantive testing and the dataset on which journal entry testing under ISA 240.32(a) operates. ISA 240.33 requires the auditor to test the appropriateness of journal entries recorded in the general ledger, with particular attention to entries made at or near the end of the reporting period. When the entity uses an ERP system, the GL is typically an extraction point for data analytics, and the auditor's reliance on IT general controls under ISA 315.26 determines how much trust can be placed in the completeness of that extraction.
Worked example: Rossi Alimentari S.p.A.
Client: Italian food production company, FY2025, revenue €67M, IFRS reporter. The engagement team is performing journal entry testing as part of the fraud risk response under ISA 240.
Step 1 — Obtain the complete GL extract
The team requests a full download of the FY2025 general ledger from Rossi's SAP system, covering 1 January to 31 December 2025. The extract contains 74,200 journal entries with a total debit value of €412M (reflecting gross transaction flow). The team reconciles the GL extract totals to the trial balance provided by management. Debits and credits both agree to €412M. No reconciling differences.
Step 2 — Identify the population for journal entry testing
ISA 240.32(a) requires the auditor to test journal entries for evidence of management override of controls. The team applies risk-based filters to the 74,200 entries: entries posted by senior management (CFO, controller), entries posted on weekends or public holidays, entries with round-number amounts above €100,000, entries posted to unusual account combinations (revenue debited to a non-revenue account), and entries with blank or generic descriptions.
Step 3 — Test selected entries
The team examines supporting documentation for 186 flagged entries. One entry of €245,000, posted by the financial controller on 30 December 2025, reclassifies an amount from trade payables to other operating income. The narrative reads "year-end correction." The team requests the supporting invoice and finds a credit note from a supplier for a volume rebate earned during Q4. The reclassification is appropriate, but the generic narrative warranted investigation.
Step 4 — Evaluate completeness of the GL
The team compares the GL account listing against the chart of accounts to confirm that no accounts have been deleted or deactivated during FY2025 without explanation. Two dormant accounts (a legacy intercompany receivable and an unused provisions sub-account) were deactivated in March 2025 with appropriate authorisation from the controller.
Conclusion: the GL extract of 74,200 entries reconciles to the trial balance, the journal entry testing covered 186 risk-filtered entries with no unexplained items, and the completeness check identified no unauthorised account deletions. The work is defensible under ISA 240.32–33.
Why it matters in practice
Teams frequently accept the GL extract from management without reconciling it to the trial balance first. If the extract is incomplete (filtered by date, module, or posting status), every sample drawn from it is compromised. ISA 500.9 requires the auditor to evaluate whether the evidence is sufficient and appropriate, and an unreconciled GL extract fails that test before any journal entry testing begins.
The FRC's 2022/23 Audit Quality Inspection Report noted that journal entry testing often lacked documented rationale for the selection criteria applied to the GL population. ISA 240.33(a) requires the auditor to make inquiries of individuals involved in the financial reporting process about inappropriate or unusual activity. When firms apply automated filters to the GL but do not document why those specific filters address the identified fraud risks, the link between risk assessment and the testing response is missing.
General ledger vs. trial balance
| Dimension | General ledger | Trial balance |
|---|---|---|
| Content | Every individual posted transaction with date, accounts, amounts, and narrative | Aggregated closing balances (debit or credit) for each account |
| Level of detail | Line-level; shows each debit and credit entry | Account-level; one row per account |
| Primary audit use | Population for journal entry testing (ISA 240.32) and data analytics | Starting point for substantive testing, lead schedule preparation, and analytical procedures |
| Frequency | Continuously updated as transactions are posted | Typically extracted at period end (or monthly for interim procedures) |
| Reconciliation | Must agree in total to the trial balance; if it does not, the extraction is incomplete or entries are unposted | Must agree to the GL totals and to the financial statements |
The general ledger contains the transaction-level detail that sits behind the trial balance. Auditors need both: the trial balance to set the scope of substantive procedures, and the GL to test whether the entries that produced those balances are legitimate.
Related terms
Frequently asked questions
How do I document journal entry testing from the general ledger?
Record the complete population (total entries, total value, extraction source), the selection criteria with their ISA 240.33 basis, the number of entries selected, and the results of testing each selected entry. ISA 230.8 requires documentation sufficient for an experienced auditor to understand the nature, timing, and extent of procedures performed. Include the reconciliation of the GL to the trial balance as the first working paper in the sequence.
What is the difference between a general ledger and a sub-ledger?
The general ledger holds summarised or posted totals for every account, while a sub-ledger holds individual transaction detail for a specific account category (such as trade receivables or fixed assets). Sub-ledger balances must reconcile to their corresponding GL control accounts. ISA 500.A1 treats both as part of the accounting records that constitute audit evidence. When the sub-ledger does not agree to the GL, the auditor investigates before relying on either.
Does the auditor need to obtain the full general ledger or just a summary?
For journal entry testing under ISA 240.32, the auditor needs the complete, line-level GL (not a summarised trial balance). The full GL provides the population from which to select entries for inspection. A summary masks the individual postings that journal entry testing is designed to examine. ISA 240.A45 notes that the nature and complexity of the entity's journal entry process affect how the auditor obtains the data.