Software Revenue Recognition Policy (SOP 97-2)
Software Revenue Recognition Policy (SOP 97-2)
________________________________________________________________
SUMMARY
This policy provides guidance related to software revenue recognition. Software revenue recognition issues can be very complex and the body of technical literature covering this topic is constantly expanding.
SOP 97-2, Software Revenue Recognition provides guidance on when revenue should be recognized and in what amounts for licensing, selling, leasing, or otherwise marketing computer software. It does not apply, however, to revenue earned on products or services containing software that is incidental to the products or services as a whole.1
Software sale arrangements may involve several deliverables such as software product licenses, upgrades/enhancements, postcontract customer support (“PCS”), installation and other services. The revenue for these multiple elements should be recognized when the following four criteria are met:
Persuasive evidence of an arrangement exists
Delivery has occurred
The fee is fixed or determinable
Collectibility is probable.
For multiple element arrangements, the total fee received from a sale should be allocated to the various elements based on vendor-specific objective evidence (“VSOE”) of fair value, regardless of any separate prices stated within the contract for each element. The allocated fee for each element is then recognized as revenue based on the nature of the specific item.
When sufficient VSOE does not exist, all revenue from the arrangement is deferred until the earlier of the point at which (a) such VSOE does exist, or (b) all elements of the arrangement have been delivered. Use of the “residual method” in situations where VSOE exists for all undelivered elements but does not exist for one or more of the delivered elements is permitted. Under the residual method, the undiscounted VSOE of fair value of the undelivered elements is deferred, and the difference (residual) between the total fee and the amount deferred for the undelivered elements is recognized as revenue for the delivered elements.
1 SOP 97-2 par .02
policy in circumstances where reasonably dependable estimates (of the extent ...Instead, AICPA SOP 97-2 (Software Revenue Recognition) has significant ...
1997 年 10 月,美国会计师协会 AICPA 颁 布的 SOP 97-2 (Statement of Position No. 97-2:Software Revenue Recognition ),对软件收入 3 上海立信会计学院...
software (SOP 81-1 deliverables) and the operation of the equipment using ...Disclosure Requirements t t The accounting policy for revenue recognition in ...
已讨论过有关销售影片附带软件产品时的会计处理, EITF 指出软件镶嵌在某些产品 销售组合时,必须依 SFAS 86 及 SOP 97-2 Software Revenue Recognition(电脑软件...
98-9, Modification of SOP 97-2, Software Revenue Recognition, With Respect...If a registrant’s historical accounting policy for the recognition of ...
精益生产-标准化作业(SOP)_工程科技_专业资料。Lean production - SOPGPS(丰田生产方式) 标准化作业 2009年3月 0 标准作业概述 1 标准作业: ① 以最少浪费...
SOP 体系 行政部管理制度和程序 Job Description 岗位责任制岗位名称 行政部经理 直接上司 行政总监 级别___编 辑人 ___ _ 管理对象__总经理秘书、车队、员工...
Big Bath Charges Creative Acquisition Accounting Revenue Recognition Cookie Jar...确认销售收入的实现 违反SOP97-2要求,在软件许可当期提前收入 与关联方进行交易...
(GMP认证资料)标准操作规范(SOP)03-物料管理标准操作规程(SOP-RM)_医药卫生_专业资料。中药材灭虫标准操作规程颁发部 门 总经理 办公室 题目 新订:√ 中药材...
采购作业流程 (SOP)_生产/经营管理_经管营销_专业资料。编页 号次 P2-001 1/3 采购作业程序 Purchasing Procedure 编页 号次 P2-001 1/3 1.目的: 建立...
热门文档