CPA Core 1 — Financial Reporting Scenario Practice Guide

How to approach CPA Core 1 scenarios

The CPA Canada PEP Core 1 - Financial Accounting and Reporting exam expects more than recognition of accounting terms. A scenario may mention revenue, leases, impairment, related parties, contingencies, inventory, financial instruments, or disclosure, but the familiar term is only the starting point. Your task is to decide what the facts require and support the conclusion with relevant accounting reasoning.

A strong scenario approach helps you:

• Identify the reporting entity, users, and decision maker.
• Determine the applicable reporting framework or assumption.
• Separate financial reporting facts from background noise.
• Locate the actual issue: recognition, measurement, presentation, disclosure, or next action.
• Apply criteria in a logical order.
• Choose the answer that best fits all relevant facts, not just one clue.

This guide is independent exam-preparation guidance for candidates studying CPA Core 1. It does not replace CPA Canada materials or professional standards. Use it to build a repeatable reading method for financial accounting and reporting scenarios.

Start with the reporting context

Before you analyze the accounting issue, establish the setting. In Core 1, many wrong conclusions begin with answering the wrong question for the wrong entity or framework.

On your first read, identify:

• Entity type: private company, public company, not-for-profit, partnership, subsidiary, or another reporting entity.
• Reporting framework clue: ASPE, IFRS Accounting Standards, Accounting Standards for Not-for-Profit Organizations, or another stated basis.
• Users of the statements: lenders, investors, owners, grantors, regulators, board members, management, or buyers.
• Purpose of the financial statements: annual reporting, financing, covenant compliance, sale of business, tax planning support, internal decision-making, or assurance preparation.
• Period and timing: year-end date, interim date, transaction date, subsequent event timing, or deadline.
• Your role: preparer, controller, external accountant, advisor, auditor, analyst, or reviewer.

Do not assume the framework or objective if the scenario states it. A recognition conclusion under one framework may not be the best answer under another, and a management reporting issue may require a different response than external financial statement reporting.

Quick orientation questions

Ask these before you calculate or select an answer:

1. Who is reporting?
2. Who will rely on the information?
3. What reporting framework or basis is being used?
4. What date matters?
5. What decision is being requested?
6. What facts are relevant to that decision?

If you cannot answer those questions, reread the opening and closing lines of the scenario.

Find the actual decision point

Scenario questions often contain several accounting facts, but only one decision point. The decision point is the specific action you must take, such as:

• Recognize or do not recognize an asset, liability, revenue, expense, gain, or loss.
• Measure an item at cost, fair value, net realizable value, recoverable amount, amortized cost, or another required basis.
• Adjust the financial statements or disclose only.
• Classify an item as current or non-current, operating or financing, debt or equity, restricted or unrestricted, related-party or third-party.
• Correct an accounting treatment.
• Recommend additional documentation or analysis before finalizing.
• Identify the best presentation or note disclosure.
• Explain the impact on financial statements or ratios.

The last sentence of the scenario often reveals the decision point, but do not read it in isolation. It may ask, “What should the accountant recommend?” or “Which treatment is most appropriate?” Your answer must still follow the stated framework, dates, and facts.

Convert the question into a task

Turn the prompt into a short instruction:

• “Determine whether revenue should be recognized this year.”
• “Assess whether the equipment is impaired.”
• “Decide whether the lawsuit requires accrual or disclosure.”
• “Choose the correct treatment for a related-party transaction.”
• “Identify the best next step before issuing financial statements.”

This prevents you from drifting into issues that are interesting but not asked.

Separate relevant facts from distractors

A Core 1 scenario may include operational details, management opinions, deadlines, personal preferences, and numerical data. Some are essential. Others are context only.

Relevant facts usually affect one of these areas:

• Recognition: Does an asset, liability, revenue, expense, gain, or loss meet the criteria?
• Measurement: What amount should be recorded?
• Presentation: Where and how should the item appear in the financial statements?
• Disclosure: What must be explained for users to understand the issue?
• Timing: Which reporting period is affected?
• Evidence: What supports the accounting treatment?
• Materiality: Would the issue influence users’ decisions?
• Risk: Is there uncertainty, estimation risk, bias, or incentive pressure?
• Authority: Who approved the transaction or has the right or obligation?
• Substance: What is the economic reality beyond the legal form?

Less relevant facts often include:

• Names of individuals unless they establish related-party status, authority, or conflict.
• Long business descriptions unless they explain revenue, inventory, impairment, or risk.
• Management’s preferred accounting answer unless it is evidence of bias or intent.
• Exact dates unless timing, cut-off, or subsequent-event treatment matters.
• Detailed contract language unless it affects control, performance, obligation, rights, or restrictions.

Do not ignore background facts automatically. Instead, ask, “Does this fact change recognition, measurement, presentation, disclosure, timing, or evidence?” If not, park it.

Use a financial reporting decision sequence

When you see an accounting issue, use a consistent sequence. This is faster than jumping between facts.

1. Identify the item

What is being accounted for?

Examples:

• A sale with uncertain collection.
• A customer deposit.
• A lease-like arrangement.
• A government grant or contribution.
• A lawsuit.
• Inventory with declining selling price.
• A related-party loan.
• A development cost.
• A subsequent event.
• A business combination or asset acquisition.
• A change in estimate or error correction.

Label the item before applying rules.

2. Determine the accounting question

Most financial reporting questions fit one of five categories:

• Recognition: Should anything be recorded?
• Derecognition: Should something be removed?
• Measurement: At what amount?
• Classification or presentation: How should it be shown?
• Disclosure: What should be explained?

If you are unsure, look for answer choices or prompt wording. An answer that gives a measurement amount may be irrelevant if the real issue is whether recognition is permitted at all.

3. Match the facts to criteria

Avoid quoting rules mechanically. Instead, connect each criterion to a scenario fact.

For example, in a revenue scenario, do not stop at “revenue is recognized when earned.” Ask:

• What was promised to the customer?
• Has the entity performed?
• Has control or benefit transferred, based on the framework and facts?
• Is the amount measurable?
• Are there return rights, warranties, bill-and-hold terms, consignment features, acceptance clauses, or collection uncertainty?
• Is any part of the consideration variable or contingent?
• Does the transaction include multiple deliverables or obligations?

The exact terminology may differ by framework, but the exam skill is the same: match the criteria to the facts.

4. Consider measurement after recognition

If the item should be recognized, determine the amount. Useful measurement questions include:

• What is the initial measurement basis?
• Are directly attributable costs included or expensed?
• Is there a fair value, cost, lower-of-cost-and-market, net realizable value, present value, or impairment concept involved?
• Are estimates supportable?
• Is the amount gross or net?
• Are there tax, financing, foreign exchange, or discounting effects?
• Is the amount material enough to change the recommendation?

If recognition is not supported, do not waste time calculating a precise recorded amount unless the question asks for disclosure or impact.

5. Decide presentation and disclosure

Even when no adjustment is recorded, disclosure may be required. Consider disclosure when facts include:

• Significant uncertainty.
• Related-party involvement.
• Commitments or contingencies.
• Restrictions on assets.
• Going concern concerns.
• Subsequent events.
• Significant accounting policies.
• Judgments and estimates.
• Unusual transactions.
• Financial statement user sensitivity.

A strong answer often distinguishes between “record an adjustment” and “disclose the matter.” That distinction is central to financial reporting judgment.

Identify the client, account, and authority

Finance and accounting scenarios often involve people with different roles. The same transaction can be interpreted differently depending on who has authority and who bears the obligation.

Client and role clues

Watch for:

• Owner-manager: may have incentives to improve earnings, reduce taxes, meet loan covenants, or sell the business.
• Controller or CFO: may be responsible for reporting but influenced by management pressure.
• Board or audit committee: may require balanced, user-focused reporting.
• Lender or investor: may focus on covenants, liquidity, and comparability.
• Related party: may affect measurement, disclosure, and substance.
• Customer or supplier: may affect collectability, performance obligations, warranties, or return rights.
• External accountant or advisor: may need to recommend documentation, adjustment, disclosure, or further analysis.

Authority and documentation questions

Ask:

• Who approved the transaction?
• Is there a signed contract, board approval, invoice, shipment record, grant agreement, lease agreement, or legal correspondence?
• Are rights and obligations enforceable?
• Is management intent enough, or is external evidence needed?
• Has the event occurred before or after the reporting date?
• Is the evidence reliable and current?

If the scenario lacks key evidence, the best answer may be to obtain more information before finalizing the accounting treatment. However, do not choose “get more information” as a reflex. Choose it only when the missing fact is necessary to decide recognition, measurement, presentation, or disclosure.

Read numbers with purpose

Core 1 financial reporting scenarios may include amounts, percentages, dates, useful lives, fair values, selling prices, costs, probabilities, or covenant ratios. Do not calculate until you know why the number matters.

What numbers usually signal

• Large amounts: materiality, financial statement impact, covenant sensitivity.
• Dates: cut-off, subsequent events, depreciation period, obligation timing.
• Percentages: ownership, probability, collectability, impairment decline, interest, useful life.
• Fair value estimates: measurement, impairment, related-party transactions, asset exchanges.
• Cash received: deposits, deferred revenue, financing, collectability.
• Costs incurred: inventory, property, plant and equipment, development costs, repairs, borrowing costs.
• Sales price versus carrying amount: impairment, net realizable value, onerous arrangements, gain or loss.

Use materiality as a reasoning tool

Materiality is not just a calculation. It links the accounting issue to users. A small error may still be important if it affects a covenant, bonus, trend, compliance requirement, or sensitive disclosure. A large amount may be less decisive if the framework clearly prohibits recognition.

Use materiality to decide:

• Whether an issue needs discussion.
• Whether an adjustment is necessary.
• Whether disclosure is important.
• How much precision is required.
• How to prioritize issues in a case response.

Look for suitability and disclosure clues in accounting form

In finance, “suitability” often refers to whether a recommendation fits a client’s objectives, risk tolerance, and constraints. In Core 1 financial reporting, the parallel skill is asking whether the accounting treatment fits the entity’s reporting objective, framework, facts, and users.

A defensible treatment should fit:

• The applicable framework.
• The economic substance of the transaction.
• The reporting date.
• The evidence available.
• User needs.
• Materiality.
• Consistency with policy, unless a change is justified.
• Required presentation and disclosure.

If an answer is technically possible but ignores a major constraint, it is usually not the best answer.

Disclosure clues to mark

Disclosure becomes more likely when the scenario includes words such as:

• Uncertain
• Possible
• Pending
• Related party
• Significant
• Material
• Restricted
• Contingent
• Subsequent
• Management estimates
• Covenant
• Going concern
• Unusual
• Non-arm’s length
• Not yet finalized

These words do not automatically determine the answer, but they tell you to consider whether users need explanatory information beyond the recorded amount.

Work from the full scenario, not the first familiar term

A scenario may mention “lease,” “inventory,” “revenue,” or “contingency,” but the key issue may be narrower.

Example: revenue term is not enough

Suppose a company ships goods before year-end, but the customer can return them if resale does not occur. The word “shipped” may tempt you to recognize revenue. The return right changes the analysis. Relevant facts include transfer of risks and benefits or control, return estimates, customer acceptance, collectability, and whether the amount can be measured reliably under the applicable framework.

The best answer is not “recognize because shipped” or “defer because return possible” automatically. The best answer connects the return right, evidence, estimates, and framework to the appropriate recognition, measurement, and disclosure.

Example: lawsuit does not always mean liability

A claim against the entity may require accrual, disclosure, or no recognition, depending on likelihood, ability to estimate, timing, and materiality. Legal correspondence, management assessment, and subsequent developments may be more important than the fact that a lawsuit exists.

Example: related party does not answer measurement by itself

A related-party transaction may affect disclosure and measurement, but you still need to know the nature of the relationship, transaction terms, exchange amount, carrying values, commercial substance, and framework requirements. “Related party” is a flag, not a conclusion.

Build a concise case note while reading

For longer scenarios, make a small working note. It should help you think, not copy the case.

Use this structure:

• Entity and framework: Who is reporting and under what basis?
• Users and objective: Why does the reporting matter?
• Issue: What accounting question is being asked?
• Facts for: Facts supporting recognition, adjustment, or disclosure.
• Facts against: Facts limiting or contradicting recognition, measurement, or classification.
• Conclusion: Most defensible treatment.
• Impact: Financial statement effect and disclosure.

A compact note for a revenue issue might look like:

• Entity: private company, year-end statements for lender.
• Issue: recognize sale before year-end?
• For: goods delivered before year-end, invoice issued.
• Against: customer acceptance after year-end, right of return, collection uncertain.
• Conclusion: consider deferral or recognition only if criteria are met and uncertainty can be measured.
• Impact: revenue, receivable, inventory or cost of sales, disclosure if material.

The goal is not to write a full memo for every question. The goal is to discipline your thinking.

Choose the most defensible answer

In scenario-based questions, more than one answer may contain a true statement. The best answer is the one most directly supported by the full fact pattern and the exam task.

Before selecting, test each option against four filters.

Filter 1: Does it answer the question asked?

Reject answers that discuss a real accounting issue but not the requested decision. If the prompt asks for the best treatment of a customer deposit, an answer about general revenue policy may be too broad.

Filter 2: Does it fit the framework and facts?

An answer can sound technically sophisticated but fail because it assumes a different framework, ignores the reporting date, or adds facts not given.

Filter 3: Does it handle both recognition and disclosure when needed?

Some answers record an amount but ignore necessary disclosure. Others disclose when recognition is required. The best answer distinguishes the two.

Filter 4: Is it proportionate and practical?

A good recommendation is implementable. It may include an adjustment, note disclosure, additional evidence, or revised policy. It should not overreact to immaterial facts or understate material uncertainty.

Use the answer choices as evidence, not as a shortcut

If you are working through multiple-choice or objective-style practice, read the scenario first, then predict the issue before comparing options. Answer choices can help you confirm the decision point, but they can also pull you toward a familiar phrase.

When reviewing options:

• Cross out choices inconsistent with the reporting framework.
• Cross out choices that ignore a key date or cut-off fact.
• Cross out choices that recognize an item before criteria are met.
• Cross out choices that defer or disclose only when the facts support recognition.
• Be cautious with absolute wording if the scenario includes uncertainty.
• Prefer answers that explain the accounting treatment and the reason.

For calculation-based options, estimate the expected direction first. Should assets increase or decrease? Should revenue be deferred? Should an impairment reduce carrying amount? This helps you catch options that are numerically plausible but conceptually wrong.

Apply the method to common Core 1 issue types

The same scenario-reading method works across topics. Adapt your focus to the accounting area.

Revenue and receivables

Focus on:

• What was promised.
• When performance occurred.
• Whether control, risks and benefits, or service completion supports recognition.
• Whether collectability is uncertain.
• Whether amounts are variable, refundable, or contingent.
• Whether multiple elements exist.
• Whether a receivable, contract asset, or deferred revenue is more appropriate.
• Whether allowance or impairment of receivables is needed.

Decision sequence:

1. Identify the transaction and customer rights.
2. Determine whether recognition criteria are met.
3. Measure revenue and related receivable or liability.
4. Consider returns, warranties, discounts, and collectability.
5. Consider disclosure if material or uncertain.

Inventory

Focus on:

• Costs included in inventory.
• Cut-off and ownership.
• Obsolescence, damage, or declining selling price.
• Net realizable value or lower-of-cost-and-market concepts, as applicable.
• Consignment or bill-and-hold features.
• Allocation between inventory and cost of sales.

Decision sequence:

1. Decide whether the entity owns or controls the inventory at year-end.
2. Determine cost.
3. Compare carrying amount to recoverable or realizable amount under the applicable framework.
4. Record write-downs if supported.
5. Disclose significant policies or unusual issues if material.

Property, plant and equipment and intangibles

Focus on:

• Capital versus repair or maintenance.
• Directly attributable costs.
• Componentization if relevant.
• Useful life, residual value, and depreciation method.
• Impairment indicators.
• Development versus research-type activities, if applicable.
• Derecognition on sale or disposal.

Decision sequence:

1. Identify whether the expenditure creates or enhances a resource.
2. Determine whether recognition criteria are met.
3. Measure initial cost.
4. Determine depreciation or amortization.
5. Assess impairment or disposal if facts indicate a decline in value.

Liabilities, provisions, and contingencies

Focus on:

• Present obligation.
• Past event.
• Likelihood of outflow.
• Ability to estimate.
• Legal versus constructive obligation.
• Timing of the event relative to year-end.
• Disclosure for uncertainty.

Decision sequence:

1. Identify the obligating event.
2. Determine whether a liability should be recognized.
3. Measure the best estimate if recognition is appropriate.
4. Decide whether disclosure is required.
5. Consider subsequent information that provides evidence about year-end conditions.

Financial instruments and debt

Focus on:

• Nature of the instrument.
• Classification as liability or equity.
• Interest terms and effective cost.
• Covenants, defaults, waivers, and maturity.
• Related-party loans.
• Measurement basis.
• Disclosure of risk, terms, or restrictions.

Decision sequence:

1. Identify rights and obligations.
2. Classify the instrument.
3. Measure initial and subsequent amounts.
4. Consider current versus non-current presentation.
5. Disclose significant terms or risks if relevant.

Related parties

Focus on:

• Relationship between parties.
• Whether terms are arm’s length.
• Measurement basis under the applicable framework.
• Economic substance.
• Disclosure of relationship, transaction, balances, commitments, or terms.
• Management bias or conflict.

Decision sequence:

1. Confirm related-party status from facts.
2. Identify the transaction and amounts.
3. Determine appropriate measurement.
4. Consider whether the transaction has commercial substance.
5. Assess disclosure needs.

Subsequent events

Focus on:

• Reporting date.
• Date the event occurred.
• Whether the event provides evidence of conditions existing at year-end.
• Whether it indicates a new condition after year-end.
• Materiality and disclosure.
• Going concern implications.

Decision sequence:

1. Place the event on a timeline.
2. Decide whether it adjusts year-end amounts or requires disclosure only.
3. Consider whether the event affects going concern or user decisions.
4. Recommend adjustment or disclosure based on the facts.

Final review checklist for scenario practice

Use this checklist during practice until it becomes automatic:

• Have I identified the reporting entity and framework?
• Do I know the user and purpose of the financial statements?
• Have I stated the exact decision point?
• Have I separated recognition, measurement, presentation, and disclosure?
• Which facts are essential to the conclusion?
• Which facts are background only?
• Have I considered timing and cut-off?
• Have I considered authority, contract terms, and documentation?
• Have I assessed materiality and user impact?
• Does my answer fit all relevant facts, not just one phrase?
• If more information is needed, is it truly necessary to decide the issue?
• Can I explain the conclusion in one or two professional sentences?

How to practise efficiently

For each CPA Core 1 practice scenario, avoid immediately checking the solution. First, write a short issue-based conclusion:

1. Issue: What accounting question is being asked?
2. Criteria: What must be true for the treatment to be appropriate?
3. Facts: Which scenario facts support or weaken the treatment?
4. Conclusion: What is the most defensible accounting answer?
5. Impact: What changes in the financial statements or disclosure?

Then compare your reasoning to the solution. Mark whether your error was in the framework, issue identification, fact selection, accounting criteria, calculation, or communication. This turns each question into targeted review rather than passive repetition.

Practical next step

Choose one Core 1 financial reporting topic, such as revenue, contingencies, inventory, or related parties. Complete a small set of scenario practice questions using the decision sequence above, then review only the facts that changed the conclusion. After that, move into mixed topic drills or a timed mock exam to practise identifying the issue under exam conditions.