Under the us gaap accounting rules about software sfas 86, two milestones are used to determine the treatment of costs incurred in the development process of software. Appendix a of sop 972 104 response to comments received appendix b of sop 972 109 revenue recognition on software arrangements appendix c of sop 972 110 glossary from sop 972 1 appendix a multipleelement arrangements. Effective july 1, 1998, the company adopted statement of position 972, software revenue recognition. Gaap provides a definition of revenues and also describes when revenues should be reported, or recognised, in a companys financial statements. In accounting practices, vendorspecific objective evidence vsoe is a method of revenue. Sop 972 superseded sop 911, also entitled software revenue recognition that had served as the previous guidance on the topic.
The companys revenue recognition policies are in compliance with all applicable accounting regulations, including american institute of certified public accountants aicpa statement of position sop 97 2, software revenue recognition, and sop 989, modification of sop 97 2, with respect. Revenue are inflows or other enhancements of assets of an entity, or settlement of its liabilities from delivering or producing goods, rendering services, or other activities. Vsoe revenue recognition is commonly used by companies that sell software products. Vsoe, as defined in sop 972, software revenue recognition, is the best evidence of fair value.
Leased, or marketed sfas 86, august 1985 accounting for the costs of computer software to be sold, leased, or otherwise marketed asc 985605. Here you will find the issues identified and further discussion. Revenue recognition revenue is recognized when earned. It also highlights the most important provisions of gaap related to software revenue recognition. Revenue and expense recognition cases developed from the. Revenue recognition for software companies softrax. Thus, fasb seems to have been well aware of the potential for revenue fraud and abuse and to have deliberately avoided a model that would invite improper revenue recognition. Sop 989 amends sop 972 to require recognition of revenue in accordance with the residual method in limited circumstances. It should be applied by all entities that earn such revenue. The guidance of sop 97 2 is effective for software arrangements entered into in fiscal years beginning after december 15, 1997. Software revenue recognition under sop 972 the cpa journal. By clicking on the accept button, you confirm that you have read and understand the fasb website terms and conditions. Gaap before the codification sfas 86, august 1985, accounting for the costs of computer software to be sold, leased, or otherwise markete.
Paragraphs 2633 of sop 97 2 discuss how to apply the fixed or determinable fee criterion in software transactions. Turners letter addresses the question of whether websites, or information available on websites, should be deemed to be software and therefore be subject to the provisions of sfas 86, accounting for the costs of computer software to be sold, leased or otherwise marketed. New revenue recognition guidance and the potential for. Effective july 1, 1998, the company adopted statement of position 97 2, software revenue recognition. Arrangements involving multiple deliverables or a deliverables.
Software revenue recognition under sop 972 by carmichael. Additional guidance on allocating among elements may be found in sop 811, paragraphs 35 through 42. When no modifications are necessary, revenue can be recognized when a contract exists, it is delivered, price is determinable, and revenue is collectable. Multipledeliverable revenue arrangements a consensus of the fasb emerging issues task force, as further described below. We apply the provisions of statement of position 972, software revenue recognition, as amended by statement of position 989, modification of sop 972, software revenue recognition, with respect to certain transactions, to all transactions involving the sale of software. Sop 972 defines a fixed fee as a fee required to be paid at a set amount that is not subject to refund or adjustment. When producing roadmaps, vendors need to ensure that they are following the appropriate rules that govern revenue recognition for software companies or risk deferring all revenue until their commitments have been fulfilled. Accordingly, the company accounts for revenue in accordance with statement of position no. Issued by the accounting standards executive committee acsec, sop 972 provides guidance on applying revenue recognition principles to software transactions. This approach is intended to avoid accounting practices that might result in revenue being recognised too early. The financial accounting standards board issued the american institute of certified public accountants statement of position 989 sop 989, modification of sop 97 2, software revenue recognition. Software revenue recognition aicpa sop 972 software revenue recognition asc 35040.
Sop 972, software revenue recognition, provides guidance on when. More changes are also on the horizon with the joint fasb and iasb statement that is nearing completion. Guidance on applying statement 86 aicpa sop 972, software revenue recognition. Sop 972 uses the definition of probable from fasb statement no. The primary authority for software revenue recognition is aicpa statement of position sop no. Costs of software to be sold, leased, or marketed sfas 86, august 1985 accounting for the costs of computer software to be sold, leased, or otherwise marketed asc 985605. Acsec pointed out that this was consistent with fasb. The software entities revenue recognition task force has been created to address issues which may arise due to fasb s new revenue recognition standard. The financial accounting standards board issued the american institute of certified public accountants statement of position 989 sop 989, modification of sop 972, software revenue recognition. Improper revenue recognition is the recipe of choice for cooking the book sec enforcement divisions chief accountant walter schuetze companies try to boost earnings by manipulating the recognition of revenue. Revenue recognition for software companies softrax industry.
Diving into the history of revenue recognition in the software industry. Staff accounting bulletin 101, revenue recognition in financial statements, is the third in a series of sabs issued in response to sec chair arthur levitts concerns over financial reporting abuses and earnings management. Feb 12, 2014 we recognize revenue from licensing our software upon the installation and acceptance of the software by customers in accordance with statement of position 97 2, software revenue recognition. Sop 97 2 superseded sop 911, also entitled software revenue recognition that had served as the previous guidance on the topic. Deferral of the effective date of a provision of sop 972, software revenue recognition aicpa sop 989, modification of sop 972, software revenue recognition, with respect to certain transactions. Notes to consolidated financial statements annual report. Based on the boards decision, public organizations should apply the new revenue standard to annual reporting periods beginning after december 15, 2017. The companys revenue recognition policies are in compliance with all applicable accounting regulations, including american institute of certified public accountants aicpa statement of position sop 972, software revenue recognition, and sop 989, modification of sop 972, with respect. It provides registrants and their auditors with the staffs position on the. Revenue recognition issues for software and high technology companies eitf 0021 accounting for revenue arrangements with multiple.
Therefore, the unearned revenue accounts balance increased significantly after using the new recognition policy. Sfas 9, rescission of sfas 53, financial reporting by producers and distributors of motion picture films and amendments to sfas nos. We apply the provisions of statement of position 97 2, software revenue recognition, as amended by statement of position 989, modification of sop 97 2, software revenue recognition, with respect to certain transactions, to all transactions involving the sale of software. Revenue is one of the most important measures used by investors in assessing a companys performance and prospects. Internaluse software, asc 350 accounting questions and. Gaap codification of accounting standards guide by. The companys revenue recognition policies are in compliance with all applicable accounting regulations, including american institute of certified public accountants aicpa statement of position sop 972, software revenue recognition, and sop 989, modification of sop 972, with respect to certain transactions. I anticipate that the fasbs ongoing revenue recognition project will. A brief history of revenue recognition in the software. Gaap before the codification arb 45, october 1955, longterm constructiontype contracts sfas 48, june 1981, revenue recognition when right of return exists eitf 859, revenue recognition on options to purchase stock of another entity eitf 8710, revenue recognition by television barter syndicators. The guidance of sop 972 is effective for software arrangements entered into in fiscal years beginning after december 15, 1997. The fasb based the rules for revenue recognition on a document housed within the sec reporting guidelines. Paragraphs 2633 of sop 972 discuss how to apply the fixed or determinable fee criterion in software transactions.
Software revenue recognition aicpa sop 972 software revenue recognition accounting for the costs of software for internal use asc 35040 based on aicpa sop 981 three stages to develop software 1. Statement of position, 97 2, software revenue recognition sop 97 2 was issued in 1997 by the american institute of certified public accountants aicpa and amended by statements of position 984 and 989. The following summarizes the significant accounting policies. It applies to both public companies according to sab 104 and private enterprises. All of the methods of allocating revenue in those sops, including the residual method discussed in sop. The statement splits software sales into two different categories. Internaluse software, asc 350 accounting journal entries. The same is true for other substantial mixes that include intangible asset software and. Notes to condensed consolidated financial statements unaudited difference between net income and comprehensive income for the third quarter and nine months ended march 31, 1999. Out of the box software this is prepackaged software that is sold to customers without any modifications. Aicpa sop 981, accounting for the costs of computer software developed or obtained for internal.
The latest chapter in that history is statement of position sop 972, software revenue recognition, issued by the aicpas accounting standards executive committee acsec in october 1997. The amendments in this update do not affect software revenue arrangements that do not include tangible products. Software revenue recognition on the rise journal of accountancy. Overview of effects of vsoe of fair value on revenue recognition and measurement requirements 115. Key impacts of recent changes to revenue recognition standards.
Adjustments to sop 97 2 software revenue recognition. On august 12, 2015, the fasb issued an accounting standards update deferring the effective date of the new revenue recognition standard by one year. Costs of software to be sold, leased, or marketed accounting rules about software asc 98520. As a result, many public entities have now disclosed the impact of adopting asc 606 within their interim financial reports on form 10q. Instead, fasb adopted a fivestep model for revenue recognition that is compared to the fourcriteria model the sec staff presented in staff accounting bulletin sab 101. You wouldnt pop the cork on that bottle before it was ready. For example, the two software development companies examined in this paper, computer associates and microsoft, product sale as a percentage of revenue of 2000 is 94% and 88%, respectively. The underlying concept of recognition of revenue from software product sales at delivery remained constant.
Implementation guidance on statement of federal financial. As evidence that change is the only constant, sop 97 2 software revenue recognition has subsequently been modified again to adjust for changing business conditions. New standards update sop 972 software revenue recognition. Sop 972, software revenue recognition, provides guidance on when revenue should be recognized and in what amounts for licensing, selling, leasing or otherwise marketing computer software. Costs of software to be sold, leased, or marketed, asc 985. Revenue recognition topic 605 an amendment of the fasb accounting standards codificationtm no. Revenue recognition issues for software and high technology. However, previous revenue recognition guidance differs in generally accepted accounting principles gaap and international financial reporting standards ifrsand.
Effects of roadmaps on revenue recognition for software companies. Issued by the accounting standards executive committee acsec, sop 97 2 provides guidance on applying revenue recognition principles to software transactions. The fasb and the iasb are working on a converged model for customer contracts that will completely revamp the revenue recognition rules and replace much of the guidance currently in place. We recognize revenue from licensing our software upon the installation and acceptance of the software by customers in accordance with statement of position 972, software revenue recognition. Software revenue recognition, statement of position 972 am. A brief history of revenue recognition in the software industry. Sop 97 2 defines a fixed fee as a fee required to be paid at a set amount that is not subject to refund or adjustment. The accounting requirements within the standard have been modified by asu 2009 and asu 200914. Software revenue recognition 5 recognised, even if all other revenue recognition criteria have been met and the lack of signature is due solely to administrative formalities extraneous to the negotiations between the parties.
Revenue recognition rules for bundled sales in high technology. Banking, finance and accounting business accounting accounting software computer services industry standards computer software industry financial software information technology services industry software industry. Arrangements with multiple deliverables, fasb essentially expanded revenue. Revenue recognition on software arrangements appendix c of sop 972. The latest chapter in that history is statement of position sop 97 2, software revenue recognition, issued by the aicpas accounting standards executive committee acsec in october 1997. Sfas 86, august 1985 accounting for the costs of computer software to be sold, leased, or otherwise marketed asc 985605. Additionally, the company provides unspecified software upgrades and enhancements related to the equipment through its maintenance contracts for most of its products.
Internaluse software, asc 350 accounting questions and answers. A fixed fee includes amounts designated as minimum royalties. Revenue recognition software sop 972 wittsiepe consulting. 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. Revenue recognition rules leveling the playing field 1. The financial accounting standards boards fasb s new revenue recognition standard asc 606 was effective for annual reporting periods beginning after december 15, 2017, for public entities. The high proportionate elements of the revenue recognition highlights two conflicting purposes in revenue recognition from sale of software products. Sfas 48 may affect the amount of revenue recognized. Sop 989 amends sop 97 2 to require recognition of revenue in accordance with the residual method in limited circumstances. Costs of software to be sold, leased, or marketed sfas 86, august 1985 accounting for the costs of computer software to be sold, leased, or otherwise marketed. Ias 18 revenue recognition ifrs 15 archiv sfas 141r ifrs 3r business combinations archiv. Sfas 48, june 1981, revenue recognition when right of return exists eitf 859, revenue recognition on options to purchase stock of another entity.
409 297 18 321 1494 357 154 670 1188 760 525 49 1496 853 819 89 944 1088 597 495 63 540 51 1091 1392 707 204 402 542 485 355 997 1473 246