ACCT20007 Chap.10 General Ledger and Reporting Controls
General Ledger and Reporting Controls
The reporting cycle combines special journals, subsidiary ledgers, journal vouchers and budget data in the general ledger before producing authorised reports. This chapter focuses on interface totals, control account reconciliation, supported adjusting journals, suspense ageing and report change control.
Balancing is necessary, but it cannot prove population completeness or query integrity.
Budget estimates should be authorised before the period so later variance reports compare actual performance with a genuine baseline. Late or undocumented changes can move the target after results are known.
Version history, approval and effective dates preserve accountability without preventing justified revision.
High-volume transactions often reach the ledger through special journals and subsidiary systems. Unique batches, record counts, monetary totals, rejected-item queues and control-account reconciliation test whether the population arrived completely.
Suspense can hold unresolved differences temporarily, but plugs do not explain them and should never become a substitute for investigation.
Manual and adjusting journals need documented purpose, calculation, source, accounts, period, preparer, independent approver, posting result and reversal rule. Restrict posting rights and review late, round-value or unusual combinations.
Where recurring entries arise from an upstream interface or estimate problem, correct the source rather than tightening only the close deadline.
Final report logic is also controlled code. A query can omit blank classifications or stale data while the ledger remains balanced. Govern changes, test edge cases, reconcile important outputs to the ledger and preserve versions.
Use negative tests to confirm that unusual records remain visible or enter an explicit exception population.
Close calendars assign deadlines and owners, but should not encourage unsupported plugs. Escalation is preferable to apparent agreement when a difference remains unexplained.
Reconciliation evidence includes the populations compared, date, preparer, reviewer, identified differences and resolution.
A tick mark without the underlying comparison does not demonstrate completeness.
Report distribution also needs control. Authorised recipients, version labels and protected output reduce the risk that an obsolete or altered report becomes the basis for decisions.
Interpret trends by cause and value.
A rise in rejected journals may show stronger detection, while repeated post-close corrections can reveal weak estimates or upstream interfaces needing redesign.
Materiality affects review depth but does not authorise unsupported entries. Small recurring differences can reveal a systematic interface or classification problem and deserve trend analysis.
Reversal logic matters for accruals.
Define whether an entry reverses automatically, how the next-period invoice clears it and who reviews residual balances to prevent duplication.
For revision, trace one reporting amount from source population through interface, ledger posting, adjustment and final query. At each stage, specify totals, identifiers, approval and exception evidence.
Test an omitted record, rejected item, unsupported journal and blank classification. A complete answer explains why balance alone is insufficient and who resolves each difference before the report is authorised.
What this chapter covers
- 01
Budget estimates
- 02
Special journals
- 03
Subsidiary ledgers
- 04
General ledger
- 05
Adjusting journals
- 06
Reconciliations
- 07
Report change control
Worked example · free
Govern a late adjusting journal
- 1Preparation and approval are not independent.
- 1The purpose, calculation and source evidence are not governed.
- 2Require a standard voucher, independent approval and linked support before posting.
- 2Review late and unusual entries and reconcile the report result.
Key terms
- Control Account
- A control account summarises a subsidiary ledger balance in the general ledger.
- Journal Voucher
- A journal voucher documents the purpose, accounts, amount, support and approval for a journal.
- Suspense Account
- A suspense account temporarily holds unresolved differences that require investigation and clearance.
General Ledger and Reporting Controls FAQ
Why are control-account reconciliations important?
They compare the general ledger summary with the detailed subsidiary population. Differences can reveal missing, duplicate, misclassified or failed interface entries. A plug to suspense hides the defect; the reconciliation should identify, correct and document the underlying transactions.
What evidence should an adjusting journal contain?
Record the business purpose, calculation, source documents, accounts, period, preparer, independent approver, posting result and reversal rule under one journal identifier. Restrict rights and review late, round-value and unusual-account combinations after posting.
Can a balanced ledger produce an incomplete report?
Yes. A report query can omit transactions, use stale data or change classifications while the ledger remains balanced. Govern query changes, test edge cases, retain versions and reconcile material report totals to the ledger population before authorised distribution.
Exam move
Practise following one transaction population from special journal or voucher through ledger and report. Recompute control totals, explain reconciliation differences and design a complete journal packet. Always distinguish a balanced trial balance from a complete, accurate and properly classified report.
Working through General Ledger and Reporting Controls in ACCT20007? Sia is AskSia’s AI Accounting tutor — ask any ACCT20007 General Ledger and Reporting Controls question and get a clear, step-by-step explanation grounded in how ACCT20007 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
