PracticeAUDFree practice exam

AUD · Assessing Risk and Developing a Planned Response · 6 practice questions

When to Identify Significant Audit Risk in Year-End Sales

When a late sale creates a significant revenue risk, revise the audit plan immediately rather than relying on clean interim testing. Follow Ridgeway's sale through risk identification and targeted year-end procedures.

The ruleIdentify the significant revenue risk when the year-end sales facts become known, not after detecting a misstatement. Revise the response immediately and perform targeted substantive procedures at or near year-end, including cutoff tests.

Try one first

During the Year 2 audit of Ridgeway Manufacturing (fiscal year end December 31, Year 2), revenue increased 45% from Year 1 after the company began shipping through a large new distributor. The auditor's control and substantive testing at an interim date (September 30, Year 2) indicated controls were operating effectively. On December 30, Year 2, management recorded $3.2 million of sales (more than 10% of total Year 2 revenue) to that distributor. Shipping terms are FOB shipping point, but the auditor learns the distributor is affiliated with the CEO and that return/price‑adjustment terms were not documented. Which timing or trigger best describes the auditor's appropriate response for revenue‑related substantive procedures?
Hint

Focus on whether the December 30 sale creates a "significant risk" for revenue recognition and whether interim testing substitutes for period‑end substantive evidence, also remember when evidence must be obtained relative to the report date.

Step by step

  1. Spot the late sales red flags

    Interim testing at Ridgeway found effective controls on September 30. On December 30, Ridgeway records a large FOB shipping point sale to a CEO-affiliated distributor with undocumented return and pricing terms.

  2. Identify the significant risk now

    The unusual related-party sale and missing terms create a significant revenue-recognition risk. Identify that risk when the facts become known, without waiting for a misstatement.

  3. Move substantive testing to year-end

    Revise the planned response to include substantive procedures at or near year-end. Effective September control testing does not establish whether this December sale occurred or belongs in the current year.

  4. Test the sale's cutoff

    Inspect the December 30 sale's invoice and shipping documents, including shipping records spanning December 31. Determine whether the evidence supports recording the sale in the year ended December 31.

  5. Test occurrence and confirm terms

    For occurrence, confirm the sale directly with the distributor and inspect supporting documents; also confirm return and pricing terms. FOB shipping point alone does not resolve those undocumented terms.

  6. Finish before issuing the report

    Do not replace these tests of details with analytics alone or defer them until after report issuance. Obtain sufficient appropriate evidence addressing the significant revenue risk before issuing the report.

Key points

  • Remember: Effective interim testing does not cover a new significant risk concentrated at year-end.
  • Risk assessment drives the testing plan; a detected misstatement is not the trigger.
  • Cutoff asks when to record the sale; occurrence asks whether the sale happened.

How the exam traps you

  • Wait until testing finds a misstatement before identifying a significant risk. Identify the risk when the unusual sale and undocumented terms become known.
  • Rely on effective interim controls and use only year-end analytics. Perform targeted period-end tests of details for the newly identified revenue risk.
  • Treat FOB shipping point as proof that revenue recognition is correct. Inspect shipping evidence and investigate undocumented return and pricing terms.

5 more, each from a different angle

0 of 5 answered · 0 correct

Question 2

During the Year 2 audit of Meridian Manufacturing, the auditor notes that Meridian ran a large year‑end sales promotion: about 35% of annual sales were recorded between December 28 and December 31, Year 2. Shipping terms are FOB shipping point. Management accelerated shipments to meet targets, but the client changed its shipping-recording process in Year 2 and those control changes have not been tested. The auditor is concerned about revenue cutoff (timing) risk. Which of the following is the most appropriate timing/trigger for the auditor's additional procedures to address this risk?
Hint

Identify where the misstatement risk is concentrated (which period and which assertion) and consider whether the evidence needed (e.g., shipment date) is best obtained at or near the period end rather than at interim or solely by analytics.

Question 3

During planning of the Year 1 audit of Rho Co., a nonissuer, the auditor notes the following: recurring operating losses in Years -1 through 1; negative operating cash flows in Year 1; a debt covenant violation at 12/31/Year 1 that made the line of credit callable; on 2/20/Year 2 the lender granted only a temporary waiver through 6/30/Year 2; and on 3/1/Year 2 a customer representing 28% of Year 1 sales notified Rho it will not renew a contract expiring 8/31/Year 2. Management expects the Year 1 financial statements to be available to be issued on 4/15/Year 2 and says it is confident it can raise replacement capital, but as of the auditor's report date only nonbinding discussions exist. Assume no definitive refinancing or capital agreement has been executed unless stated. Under U.S. GAAS, which conclusion is most appropriate about the trigger and timing of the auditor's going-concern evaluation?
Hint

Separate two issues: what facts are enough to require a going-concern evaluation, and what date starts the one-year look-forward period under current U.S. GAAS.

Question 4

Company X's financial statements are for the year ended December 31, Year 1. After the balance sheet date but before issuance, the auditor became aware of the following events: Event 1 (Jan 10, Year 2): A major customer that owed a material receivable at Dec 31 filed for bankruptcy on Jan 5, Year 2. Prior to year‑end, Company X had experienced missed payments from that customer and had received a formal collection notice in November Year 1; the receivable was not written down at year‑end. Event 2 (Feb 15, Year 2): A tornado destroyed one of Company X's manufacturing plants. The plant was intact on Dec 31, Year 1 and there were no indications of damage or loss before year‑end. Which of the following best describes whether management should adjust the Year 1 financial statements for these events?
Hint

For each event, ask: does the information provide evidence about a condition that existed at Dec 31 (adjusting) or did the condition arise after Dec 31 (nonadjusting)?

Question 5

During the audit of Rylan Co., the auditor identifies recurring operating losses and a violation of a loan covenant. Management says its plans to refinance debt and cut discretionary spending remove any going-concern doubt. Assume the auditor has already determined that conditions exist that raise substantial doubt. Under U.S. auditing standards, the auditor may conclude that management's plans alleviate that substantial doubt only if which condition is met?
Hint

Focus on what must be true before management's plans can actually reduce a going-concern problem, not just what management says or hopes will happen.

Question 6

During the Year 2 audit of Meridian Manufacturing (fiscal year ended December 31, Year 2), the auditor noted these facts: (a) Meridian had net losses and negative operating cash flow in Year 1 and Year 2 and a December 31, Year 2 current ratio of 0.6; (b) Meridian breached a material bank loan covenant in November Year 2 and, as of the audit report date, has only a verbal assurance from the bank that it will not demand immediate repayment (no written waiver or commitment exists); and (c) on December 28, Year 2 Meridian recorded a $1.5 million sale of inventory to Novus LLC, a company formed in October Year 2 and wholly owned by the CEO's sibling; the sale was recorded as revenue at a price below Meridian's cost and payment terms were extended to 180 days, and no formal sales contract or independent evidence of Novus's ability to pay was in the file. Considering these facts, which specific areas of engagement risk are indicated and what is the most appropriate auditor response?
Hint

Identify whether the facts point to more than one distinct risk (e.g., financial‑distress indicators versus characteristics of an unusual related‑party sale) and think about what specific evidence each risk requires.

Drill all 93 Specific Areas of Engagement Risk questionsMixed across every rule in the topic, so you have to spot which one applies. That is how the exam does it.

Common questions

When should an auditor identify a significant revenue risk?

When the facts supporting that assessment become known. Ridgeway's unusual late sale and undocumented terms require action without waiting for a detected misstatement.

Can effective interim controls replace year-end cutoff testing?

Not for Ridgeway's newly identified year-end risk. The auditor must revise the response and perform targeted period-end substantive procedures.

Does FOB shipping point prove a year-end sale is valid?

No. Shipping terms help assess cutoff, but the auditor must also verify the sale and evaluate return and pricing terms.

Watch it solved

A full CPA AUD task-based simulation on Specific Areas of Engagement Risk, worked step by step.

Revenue Fraud Risk & Audit Procedures | CPA AUD Simulation (TBS) on YouTube

Practice AUD like the real exam

The free ChatCPA simulator: real exam layout, timed testlets, starting with a question on this topic. No account needed to start.

Open the free simulator →

More on Specific Areas of Engagement Risk

All Specific Areas of Engagement Risk practice →

Questions from the ChatCPA bank of 17,658 CPA exam questions, each with a written reason for every wrong answer. ChatCPA is built by Nicholas Miller, CPA (Oregon #14907). How these pages are made. Spot an error? Tell us.