Apply assurance standards, materiality, and planning judgment to Core 1 financial reporting situations.
Engagement planning decides whether the work is appropriate, what standards apply, what risks matter, and how much evidence is needed. In Core 1, the planning issue usually appears because a user wants assurance over financial information, management has weak records, or a reporting issue changes the nature of the work.
The answer should identify the engagement objective, user need, reporting basis, planning risk, and effect on materiality or procedures.
| Planning issue | What to decide | Evidence to inspect |
|---|---|---|
| Engagement type | Is the work an audit, review, compilation, agreed-upon procedure, or other assurance-related service? | User request, report expectation, required level of assurance, engagement letter. |
| Acceptance or continuance | Can the practitioner accept or continue the work with the available conditions? | Independence, competence, management integrity, records, deadlines, scope limitations. |
| Reporting basis | What framework or special-purpose basis will be used? | Financial statement purpose, lender requirement, tax basis, ASPE, IFRS, not-for-profit, public sector. |
| Materiality | What level of misstatement would influence the user? | Users, covenant thresholds, profit, assets, revenue, sensitive disclosures. |
| Risk areas | Which balances, transactions, or disclosures require more attention? | Prior issues, new systems, estimates, controls, unusual transactions. |
| Timing and staffing | When and by whom should procedures be performed? | Deadlines, inventory count dates, expertise needs, locations, system access. |
Core 1 does not require a full engagement plan. It requires the planning implication that follows from the facts.
A planning answer starts with what the user expects. Different services provide different levels of work and communication.
| User expectation | Planning implication |
|---|---|
| High confidence over financial statements. | An audit may be required, with risk assessment, evidence gathering, and an auditor’s report. |
| Limited assurance over statements. | A review engagement may be more appropriate if the user accepts limited assurance. |
| Prepared financial information without assurance. | A compilation may be relevant, but it does not provide assurance. |
| Procedures over specific items. | An agreed-upon procedure may fit if users specify procedures and accept factual findings. |
| Internal control or process advice. | Advisory or consulting work may be separate from assurance reporting. |
Do not recommend an engagement type only because it is cheaper or faster. Match the work to the user need and required level of confidence.
Before planning detailed procedures, identify conditions that may prevent or complicate the engagement.
Common Core 1 facts include:
If the issue affects acceptance or continuance, state it separately from the accounting treatment. A correct reporting answer does not solve an independence or scope problem.
Materiality depends on users and decisions, not only a formula. A small amount may be material if it affects a covenant, changes profit to loss, affects compliance, or involves fraud, related parties, or sensitive disclosure.
| User or context | Materiality focus |
|---|---|
| Lender | Debt classification, covenant compliance, cash flow, and liquidity. |
| Owner-manager | Profit, tax, distributions, related-party balances, and operating trends. |
| Investor or buyer | Earnings quality, normalized results, commitments, contingencies, and valuation. |
| Donor or funder | Restricted funds, eligible spending, and stewardship reporting. |
| Regulator | Prescribed basis, disclosure, filing deadlines, and compliance. |
A strong response explains why a matter is material to the user, not only that it is “large.”
Financial reporting issues shape assurance planning.
| Reporting issue | Planning response |
|---|---|
| Complex revenue terms | Focus on contracts, performance, cut-off, collectability, and fraud risk. |
| Weak inventory controls | Plan count observation, reconciliation, valuation testing, or alternate evidence. |
| New accounting system | Understand data flow, access, report logic, and conversion controls. |
| Significant estimates | Evaluate assumptions, methods, data, bias, and sensitivity. |
| Debt covenant pressure | Focus on classification, waiver evidence, going concern, and lender communication. |
| Related parties | Identify relationships, terms, approvals, balances, and disclosure. |
The procedure should respond to the risk. Generic “perform more testing” is not enough.
Use this order for engagement-planning questions:
This structure keeps planning tied to the case instead of becoming a generic standards summary.
| Pitfall | Better approach |
|---|---|
| Treating every request as an audit. | Match the engagement type to user need and expected assurance. |
| Ignoring acceptance issues. | Address independence, competence, scope, records, and management integrity before procedures. |
| Applying materiality mechanically. | Consider qualitative factors and user decisions. |
| Recommending generic testing. | Link procedures to the identified reporting risk. |
| Confusing advisory work with assurance. | Separate recommendations to management from assurance conclusions. |