
Separable components or elements of software transactions and vendor specific objective evidence of their fair value are among the most critical building blocks of software revenue recognition. However, most standards have been silent with respect to an operational and consistently applicable definition of separate elements or deliverables.
The tentative conclusions of the Emerging Issues Task Force (EITF ) Issue No. 00-21, Accounting for Revenue Arrangements with Multiple Deliverables, provide some insight into a potential resolution.
EITF 00-21 says that a deliverable should be segmented and accounted for separately if
Software companies may consistently include or exclude all deliverables in an arrangement from the revenue accounting (and recognize a liability) for the arrangement if all of the following conditions are met:
No allocation is permitted in the absence of verifiable fair value. Third-party evidence may not be a reliable indicator of VSOE if the product or service is unique to the vendor.
When objective and verifiable evidence of fair value is available for the undelivered item(s) but not for one or more delivered items in the arrangement, the residual method (SOP 98-9) can be used to allocate revenue if
Note: The residual method cannot be used to establish the fair value of an undelivered item.
Treatment of the Discount:
Risk Assessment
Our new checklist assesses the risk in your reporting processes. Start Now.
This Just In
Risk and Complexity in Revenue Reporting under US and International Standards
Most Popular
Laying the foundation for automating revenue accounting
SOP 97-2: Current Issues in VSOE Accounting
EITF 00-21: Revenue Arrangements with Multiple Deliverables
Webcasts
The Milestone Method: U.S. GAAP?
Sponsored by Softrax
The Essential Revenue Management Roadmap
Case Study
Automating Revenue Processes to Integrate Acquisitions
As a member you gain access to a host of valuable resources! Sign-up now, it's free!