Last reviewed: July 2026.
The nominal ledger is the traditional name for the general ledger: the central record containing financial-statement accounts. In modern computerised systems, sales, purchases, payroll, inventory, fixed assets and bank processes feed the general ledger through integrated postings and controlled journals.
Automation improves speed, but reliable reporting still depends on configuration, access, reconciliations and review.
Role of the general ledger
| Function | Example | Control objective |
|---|---|---|
| Classify transactions | Revenue, wages, inventory and tax accounts | Use the correct account and dimension |
| Aggregate subledger postings | Customer and supplier control totals | Complete and accurate interfaces |
| Record adjustments | Accruals, depreciation and provisions | Supported and approved journals |
| Produce trial balance | Debit and credit balances | Complete close and reconciliation |
| Support reporting | Financial statements and management reports | Accurate mapping and disclosure data |
Chart of accounts
The chart of accounts defines account codes, names, types and reporting relationships. A good design supports statutory reporting and management analysis without creating duplicate or ambiguous accounts.
Use dimensions such as department, product, project and location instead of creating unnecessary ledger accounts.
Integrated transaction posting
When a sales invoice is raised, an integrated system can debit trade receivables and credit revenue while updating the individual customer account. Purchase invoices similarly update supplier detail and the trade payables control balance.
Review the sales ledger guide and purchase ledger guide.
Subledgers and control accounts
Customer, supplier, inventory and fixed-asset subledgers contain detailed records. Their totals must reconcile with corresponding general-ledger accounts.
Integration reduces manual posting but does not remove interface, mapping or master-data risk.
Manual journals
Manual journals remain necessary for non-routine transactions and adjustments. Each should include a clear explanation, supporting calculation, preparer, approver and period.
Restrict posting rights and require stronger approval for unusual, late or senior-management journals.
Recurring journals
Recurring journals can automate rent, insurance, depreciation and allocations. Review templates, start and end dates, account mapping and amounts regularly.
Outdated recurring journals can continue posting after the underlying transaction ends.
Accruals and reversals
Accrual journals often reverse automatically in the following period. The reversal date should match the expected invoice or settlement process.
A reversal does not remove the need to investigate unmatched or repeated accruals.
Posting periods and locks
Open periods should be limited to authorised users and dates. After the close, lock the period and control any reopening with approval and audit trails.
Backdated postings can change previously reported results and reconciliations.
Trial balance
The trial balance lists general-ledger balances and confirms that total debits equal total credits. Balanced totals do not prove that accounts are correctly classified or complete.
See the ledger accounts guide.
Month-end close
- complete interfaces and resolve rejected transactions;
- reconcile subledgers, bank and control accounts;
- record accruals, depreciation and estimates;
- review unusual balances and journal entries;
- prepare an adjusted trial balance;
- map accounts to statements and notes;
- lock the period after approval.
The accounting process guide explains the full close cycle.
Account reconciliations
Every material balance-sheet account should have a reconciliation linking the ledger to independent evidence or detailed schedules. Reconciling items need owners, dates and resolution plans.
Suspense and clearing accounts
Clearing accounts can support interfaces and temporary allocation, but balances should be investigated and cleared promptly. Suspense should not become a permanent storage area for unexplained differences.
Interface controls
- control record counts and monetary totals;
- identify duplicate or missing batches;
- review rejected transactions;
- protect mapping tables;
- reconcile source-system totals to the ledger;
- monitor timing differences.
User access and segregation
Separate account creation, transaction processing, journal approval, payment release and reconciliation where practical. Use role-based access and review privileged accounts.
Audit trail
The system should retain the user, date, time, source, original entry and every authorised change. Direct database edits should be prohibited or tightly controlled and independently reviewed.
Master data governance
General-ledger reliability depends on controlled customer, supplier, tax, currency, product and chart-of-account master data. Changes should require approval, effective dates and audit trails.
Duplicate or incorrect master records can create errors across every integrated module.
Foreign currency and consolidation feeds
Multi-currency systems should retain transaction currency, functional-currency amounts and exchange rates. Group reporting also requires controlled entity mappings, intercompany identifiers and consolidation adjustments.
Journal documentation standard
A journal policy should define required support, naming, preparer, approver, evidence, reversal method and retention. Automated journals should be documented as carefully as manual entries.
General ledger analytics
Useful exception reports include round-value journals, weekend postings, dormant accounts, unusual sign balances, duplicate descriptions, postings to closed periods and entries just below approval limits.
Cloud and integration risk
Cloud systems add vendor, availability, data-location, interface and cybersecurity considerations. Backups, recovery testing and exit arrangements remain important.
Use the accounting software risks and controls guide.
Common mistakes
- assuming integrated postings require no reconciliation;
- allowing unrestricted manual journals;
- creating duplicate accounts instead of using dimensions;
- leaving clearing accounts unresolved;
- reopening closed periods without control;
- mapping accounts to the wrong statement line;
- relying on software without understanding double entry.
Key takeaway
The computerised nominal ledger is the core of financial reporting. Integration, controlled journals, reconciliations, access security and disciplined close procedures turn transaction data into reliable accounts.
Official learning references: ACCA computerised accounting systems, ACCA computerised accounting and the auditor, and ACCA general ledger role.