Question 250
A controller reviews a change for this problem: A prepaid annual software contract should recognize revenue monthly rather than all on the invoice date. Which limitation should the implementation team not overlook?
Explanation
Correct Answer
This caution follows from the actual financial-control issue: A prepaid annual software contract should recognize revenue monthly rather than all on the invoice date. The risk is that cash receipt timing alone does not determine revenue recognition period. The consultant should first inspect revenue deferral setup, coverage dates and recognition schedule. and then apply supported revenue deferral and periodic recognition rules to the contract..
Incorrect Answers
The alternative deals with “A proposed shortcut is under review because a subscription price should increase on its annual anniversary without rewriting previous invoices”. The consultant should first review billing schedule price update dates, recurrence and past invoice history. The current question instead selects “Cash receipt timing alone does not determine revenue recognition period”.
The warning belongs to a nearby but different scenario: A subscription renews monthly but the seller creates all future invoices on the contract start date. The risk specific to this situation—a prepaid annual software contract should recognize revenue monthly rather than all on the invoice date.—is instead that cash receipt timing alone does not determine revenue recognition period.
The distinct use case for this response is “an annual service fee invoiced upfront should be expensed across twelve service months”. The consultant should first review expense deferral setup, date range and the applicable posting accounts. The present case instead calls for “Cash receipt timing alone does not determine revenue recognition period”.