Evaluate financial reporting processes, source systems, and internal controls that affect reliable reporting.
Reliable financial reporting depends on more than accounting knowledge. The entity must capture transactions completely, classify them correctly, preserve source documents, review estimates, reconcile accounts, and produce statements from systems that can be trusted.
In Core 1, reporting controls usually appear when the accounting conclusion depends on weak data. If source records are incomplete, duties are not segregated, reconciliations are not performed, or spreadsheets override the system without review, the right answer may be a control recommendation before a final accounting conclusion.
| Control issue | Reporting risk | Evidence to inspect |
|---|---|---|
| Source document weakness | Transactions may be incomplete, unsupported, or recorded in the wrong period. | Invoices, contracts, shipping documents, approvals, receiving reports, cash receipts. |
| System limitation | Reports may omit data, duplicate entries, or fail to preserve audit trail. | ERP settings, manual spreadsheets, access rights, interface failures, report logic. |
| Reconciliation failure | Accounts may contain timing errors, unreconciled balances, or unexplained differences. | Bank reconciliations, subledger-to-general-ledger reconciliations, inventory counts, AR aging. |
| Review weakness | Estimates and adjustments may be biased or unsupported. | Management review, approval evidence, board minutes, variance analysis, independent checks. |
| Segregation problem | One person can initiate, record, approve, and conceal errors. | Workflow, approval matrix, small-team compensating controls, access logs. |
| Closing process weakness | Statements may be late, inconsistent, or missing disclosures. | Close checklist, journal-entry review, disclosure checklist, subsequent-event review. |
The control point should be tied to a financial reporting consequence, not written as generic internal-control advice.
Sometimes the case asks for an accounting treatment, but the facts reveal that the data are unreliable. In that situation, state the provisional accounting implication and the process issue.
Example:
| Fact | Reporting response |
|---|---|
| Sales are recorded from unsigned orders and no one checks shipping dates. | Revenue cut-off is unreliable; confirm shipment or performance evidence before concluding revenue is earned. |
| Inventory is counted by warehouse staff with no independent review. | Inventory existence and valuation are at risk; recommend supervised counts and reconciliation before relying on the balance. |
| The CFO manually adjusts impairment assumptions without review. | Estimate bias risk exists; require documented assumptions and independent review before accepting the impairment model. |
| Bank reconciliations are six months behind. | Cash, debt, and cut-off may be misstated; complete reconciliations before final statements are issued. |
Do not overstate certainty when the records do not support it.
Distinguish a data problem from a policy problem.
| Problem type | Example | Correct response |
|---|---|---|
| Source data problem | Missing invoices, unapproved journal entries, unreliable inventory counts. | Improve records, reconcile, obtain support, and only then apply accounting treatment. |
| Accounting policy problem | Management uses an inappropriate revenue policy. | Evaluate the policy against the applicable framework and facts. |
| Estimate problem | Useful life, allowance, impairment, or provision assumptions lack support. | Assess assumptions, evidence, bias, sensitivity, and disclosure. |
| Presentation problem | Current and non-current amounts are not separated. | Reclassify and explain stakeholder effect. |
| Disclosure problem | Material uncertainty is not described. | Recommend disclosure and supporting analysis. |
This distinction matters because the recommendation differs. A missing invoice is not solved by a new policy; an inappropriate policy is not solved by filing documents neatly.
Estimates require controls because they involve judgment. Common Core 1 estimates include allowance for doubtful accounts, warranty provisions, impairment, useful lives, obsolete inventory, provisions, fair value inputs, and going concern assumptions.
Strong control recommendations include:
The answer should connect the control to the risk. For example, if a bonus depends on EBITDA, impairment and provisions may need stronger review because management has an incentive to understate expenses.
Core 1 reporting controls can include technology issues even when the case is not an IT case. Spreadsheets, interfaces, access permissions, and report logic can affect financial statement reliability.
Watch for:
The recommendation should be practical: restrict access, review formulas, reconcile reports, preserve audit trails, document report logic, or test migrated data.
CRA guidance on IFRS-related books and records emphasizes documentation, reconciliations, and system-change support for tax filing where IFRS is used. The same discipline is useful for financial reporting cases: accounting records should support the numbers, the reporting basis, and any tax or regulatory reconciliation.
Core 1 answers should mention records when:
Use this order for reporting control questions:
| Pitfall | Better approach |
|---|---|
| Giving generic control advice. | Tie each control to a specific reporting risk. |
| Ignoring data reliability before calculating. | Assess whether the records support the calculation. |
| Treating all problems as accounting policy problems. | Separate source-data, process, estimate, presentation, and disclosure issues. |
| Recommending segregation in a small entity without practicality. | Use owner review, independent reconciliation, access logs, or documented approval as compensating controls. |
| Forgetting system changes. | Consider migration, report logic, access rights, and reconciliations. |