Oct 08, 2015 basic differences between saas, subscription and traditional perpetual licenses published on october 8, 2015 october 8, 2015 168 likes 28 comments report this post. Basic differences between saas, subscription and traditional perpetual licenses published on october 8, 2015 october 8, 2015 168 likes 28 comments. According to sab 104 and software license revenue recognition rules, revenue for both perpetual and time based licenses can be recognized when the licenses are delivered as long as a firm has satisfied the following rules. If a license is deemed to not be distinct during this analysis, the license is combined with the other goods or services and the combined performance obligation is accounted for using the general revenue recognition model. Under existing revenue recognition rules, software companies are already required to estimate the fair value of each.
Saas asc 606 revenue recognition summary bterrell group. What is the correct revenue recognition accounting by a reseller who resells e. Software vendors increasingly rely on a recurring revenue license model and other pricing strategies to create steadier revenue streams. Valuing software companies in the changing gaap environment. Perpetual license transaction accounting under eitf 081. For example, online connectivity between the customers onpremise software and the vendor not only makes the perpetual license relationship look more like a subscription relationship, but such a feature also provides activity and availability monitoring, diagnostic feedback and upsellupgrade opportunities. Revenue recognition is an issue that arises when delivering solutions to the marketplace using term subscriptions or perpetual licenses. Investor perspectives on asc 606 for software and saas.
You pay for your software licence upfront and have the right to use it indefinitely. Under this interpretation, enforceable rights and obligations for the initial software license transfer to the customer at the beginning of the contract and do not change during the contract term even when converting to a saas model. As youre well aware, software providers typically sell their products through either perpetual or term licenses. In this paper, the pricewaterhousecoopers pwc global software practice examined certain situations in which adopting ifrs may require a reconsideration of revenue recognition policies and practices that were driven by us gaap compliance.
For many companies, a timebased license is a preferred alternative to selling an unlimited software license without a time restriction known as a perpetual license. The new revenue standards asc 606 and ifrs 15, revenue from contracts with customers replace industryspecific guidance with a single revenue recognition model. Estimating standalone selling prices in perpetual license contracts. Interestingly enough, this post actually was inspired by the amusing ad below from autodesk. Good revenue recognition software can therefore be a changemanagement tool to transform traditional independent software vendors isvs from the perpetual license business to the cloud business, he said. Every year, the buyer has to pay the annual fee again, but constantly gets updates and support. Under the new revenue recognition guidelines, company a would likely decide to recognize revenue attributed to the term license at the point in time when the software is transferred to the customer, while the revenue associated with the updates would be recognized over time. Detailed rules on software license revenue recognition bi101. Ninetyday warranties for software licenses seem to be accepted as routine.
A perpetual licence is the traditional model used to purchase software. Revenue recognition within the software industry has historically been highly complex with much industryspecific guidance. Under todays gaap, revenues from perpetual software licenses may be recognized upon delivery, provided the license can be unbundled from other deliverables in the arrangement, such as pcs. Identifying performance obligations and licensing, which was issued on april 14, addresses questions pertaining to licensing and identifying performance obligations that were brought up to and discussed by the fasbiasb joint transition resource. Perpetual software licenses perpetual licenses are considered the traditional model when purchasing software for a business. As you are probably aware, current accounting under us gaap often requires deferral of upfront license revenue.
The term perpetual license is one method of selling software, that is sort of the opposite of the subscription model. Software companies continue to analyze the impact of the new revenue standard on their contracts, accounting policies, and financial statements. Mar 08, 2018 software license arrangements can be organized as a hosting arrangement, saas, a hybrid of both hosting and saas, or direct delivery to the customerall of which have different implications for the application of each of the five steps of the new revenue recognition model. While the new revenue recognition standard has and will affect entities differently depending on their facts and circumstances, we have briefly summarized for corporate executives cxos some of the common significant themes associated with its application by entities in the software and softwareasaservice saas sectors, using insights and perspectives learned in the past year as public. Software companies are often tasked with deconstructing the typical. Revenue recognition accounting for software as a service. The following was a question posed by a cfo during a recent revenue recognition webinar. Basic differences between saas, subscription and traditional. Revenue recognition software could also boost companies profitability, according to reports published around the time of the fasb changes. This throws off traditional expense ratios and typically makes the ratio appear higher than in onpremises software. Major considerations when moving from perpetual licenses to saas.
On top of the licence fee, you will have the option to pay for oneoff implementation services and a support contract, which is renewed annually. If a perpetual license contract achieves vsoe then the license portion of the revenue is recognized upfront if vsoe is not achieved and thus it is not clear that the license is separate from the ongoing services, both the license revenue and the ongoing services revenue are typically recognized over time. They are categorised into termbased vs capacitybased or perpetual license. Implement a recurring revenue license model license. Applying the new accounting for revenue recognition. Companies selling perpetual licenses must also consider additional factors before recognizing revenue. The financial accounting standards board fasb recently issued final guidance on accounting for licenses of intellectual property and identifying performance obligations in its new revenue recognition standard accounting standards update asu no.
Saas businesses must get revenue recognition right every time. Software license revenue attributable to distinct software licenses is recognized at the point in time the customer obtains control of the license, which no longer. January 2015 the new revenue recognition standard software and cloud services 5 1. Revenue recognition, cloud revenue recognition intacct.
The core principle of the standard is that an entity will recognise revenue at an amount that reflects the. Software license arrangements can be organized as a hosting arrangement, saas, a hybrid of both hosting and saas, or direct delivery to the customerall of which have different implications for the application of each of the five steps of the new revenue recognition model. As such, revenue recognized for the software license will remain unchanged and revenue is not recognized during the saas period unless additional fees are charged. If it is a software sale, then it is recognized following the rules outlined within asu 2009 regarding revenue recognition in multiple element arrangements. That said, here are a few extremely important revenue recognition bullets. Software license revenue attributable to distinct software licenses is recognized at the point in time the customer obtains control of the license, which no longer rests solely on when the software is delivered to the customer. Software companies are often tasked with deconstructing the typical bundles of product and services, and then determining the separate selling price of each of those elements. The complete guide to saas revenue recognition with asc 606. Consistent with asc 606s approach to revenue recognition, revenue from licenses of ip should faithfully reflect the transfer of utility to the customer. It applies to both public companies according to sab 104 and private enterprises. A term license is the right to software for only a fixed term, in most cases a one or two year timeframe.
Also, our onpremise perpetual software licenses are only sold bundled with our maintenance support and services. Under todays gaap, revenues from perpetual software licenses may be recognized upon delivery, provided the license can be unbundled from other. Revenue recognition is a critical piece of accounting for any business, and compliance with official standards is not optional. As for the capacitybased or perpetual license, the revenue is recognized. Those companies with software license revenue will be most affected, while there is likely a lesser impact on the recognition of softwareasa. Jul 28, 20 we have some transactions that are sold on a perpetual basis and some that are sold on a subscription term basis. Financial guide for converting perpetual software licenses.
Will your companys revenue disappear into a black hole. Perpetual vs subscription software license youtube. It is recommended that all companies with term subscriptions, private or public, understand the important concepts and adopt a process for financial reporting based on revenue recognition as early as practical. Software revenue recognition rules for subscription services. Major considerations when moving from perpetual licenses. Technology entities often sell updates to licensed software that are. Subscription replaces the capital outlay of buying software licenses with ongoing subscription payments making software more affordable. Revenue recognition on software arrangements appendix c of sop 972. Reviewing different parameters while comparing between perpetual and subscription software. The license will have no value if the team were to stop playing. We have some transactions that are sold on a perpetual basis and some that are sold on a subscription term basis. The reseller essentially purchase the service agreement from the supplier, and resell it at a markup to the end customer.
The updated standard uses a different process to allocate the contract value and related discounts with the contract by eliminating the need to establish vendorspecific objective evidence vsoe, which may produce more aggressive revenue recognition. With current revenue recognition policies, subscription licenses in software are recognized ratably over the length of the contract. Revenue recognition for software companies softrax industry. For example, a sports team licenses its name to a manufacturer. The rate for private companies is even more astonishing. In software, broadly licenses are recognised on delivery. Mar 22, 2016 regulations new revenue recognition standard means big changes for software companies. The change from perpetual to subscription based software. For a discussion of the key considerations for technology entities that do not currently apply software guidance, refer to our applying ifrs, the new revenue recognition standard technology january 2015 technology. Aug 02, 20 according to sab 104 and software license revenue recognition rules, revenue for both perpetual and time based licenses can be recognized when the licenses are delivered as long as a firm has satisfied the following rules.
Revenue recognition by reseller var for service contract. Revenue recognition software helps tech vendors meet. Under todays gaap, revenues from perpetual software licenses are recognized upon delivery of the software, while revenues associated with term licenses are often recognized proportionately over the license term. But, if your organization is purchasing perpetual license, subscription or cloud software, these seemingly arcane bodies may have plenty of influence on your decision. While the new revenue recognition standard has and will affect entities differently depending on their facts and circumstances, we have briefly summarized for corporate executives cxos some of the common significant themes associated with its application by entities in the software and software asaservice saas sectors, using insights and. For more predictable revenues, consider a recurring revenue license model. These strategies result in smoother and more predictable revenue growth which makes financial planning easier and increases business efficiency, maximizing value to. Revenue recognition for saas businesses is inherently complex, and depends on your specific revenue model. A sale of ip is not a license under asc 606, so the general revenue recognition model applies. A perpetual software license is a type of software license that authorizes an individual to use a program indefinitely. May 27, 2014 a term license is the right to software for only a fixed term, in most cases a one or two year timeframe. This publication reflects implementation developments since issuance of the standards and highlights considerations relevant in evaluating the impact of the new standard to revenue arrangements common.
Accounting for the sales of software licenses with. Fortunately for most businesses, asc 606 brings a level of consistency and clarity that did not exist before in saas accounting the wild west is being tamed, and thats a good thing for all of us. Aug 19, 2014 for software vendors who want to keep their customers for more than 3 years the subscription model will generate more revenue than a perpetual model. Although the pcs looks like subscription revenue, it would be wrong to categorize it as saas. Revenue for software and saas financial reporting view. If the providers warranty for the software is not shortterm and routine, that fact can jeopardize the providers ability to recognize all the license revenue immediately. The primary authority for software revenue recognition is aicpa statement of position sop no. The shift from perpetual to subscription software licenses. The shift from licensed software to saas has resulted in significant saas accounting. Heres a primer with some important facts to consider. As for the capacitybased or perpetual license, the revenue is recognized upfront, when the license in delivered.
Revenues from term perpetual software licenses may be recognized upon delivery, provided the license can be unbundled from other deliverables in the arrangement, such as pcs. Recognize revenue as performance obligations are satisfied. Revenue recognition accounting for software as a service saas an executive webcast with jeffrey werner 1. Identifying performance obligations and licensing, which was issued on april 14. Cfos react to asc 606 impact on the subscription model. For a perpetual license to symbolic ip, the licensee recognizes the revenue over the economic life of the ip, which needs to be estimated. New revenue guidance implementation in the software industry. Here, ifrs 15 provides the specific guidance for the licenses, but only if the license is. Maintenance and support revenue requires significant labor, which reduces the scalability of this revenue. Accounting for the sales of software licenses with subsequent. Generally, outside of termination, a perpetual software license allows the holder to use a specific version of a given software program continually with payment of a single fee. However, if the software is actually sold as a service, or saas model, then revenue recognition needs to.
The standard has changed the timing of revenue recognition for many technology. Summary of the new standard ifrs 15 specifies the requirements an entity must apply to recognise and measure revenue and the related cash flow s. Yet, to a prospect that breathes cad, youre adding so much unnecessary complexity to a sale. Cfos react to asc 606 impact on the subscription model zuora. For termbased license, the revenue is accounted over the term of the license. Revenue management can quickly get complex when you consider multiple entities, subscriptions, licenses, services, etc. Regulations new revenue recognition standard means big changes for software companies. For software vendors who want to keep their customers for more than 3 years the subscription model will generate more revenue than a perpetual model. The software license is paid for upfront and can be used indefinitely. For a saas or subscription business, revenue recognition can be complex, mainly because of the serviceoriented nature of the product. Accounting for conversion from onpremise to cloud for. Software the primary authority for software revenue recognition is aicpa statement of position sop no. New revenue recognition standard means big changes for. If a customer license via perpetual or subscription license includes any software modification or customization, revenue recognition will be impacted.
Under todays gaap, revenues from perpetual software licenses are recognized upon delivery of the software, while revenues associated with term licenses are. When the license is required for a customer to benefit from a related service e. For both types, an entity may not recognize any revenue from a license before the ip is actually available to the customer, and the licensing period during which the customer is able to utilize the license has begun. Perpetual licensing mini and pc era license fees support fees implementation fees. Do note an important point regarding perpetual licenses with separate revenue line items for software licenses and pcs. When purchasing the license, there is an option to pay for oneoff implementation services along with a support contract that renews annually. Perpetual licenses and software license revenue recognition according to sab 104 and software license revenue recognition rules, revenue for both perpetual and time based licenses can be recognized when the licenses are delivered as long as a firm has satisfied the following rules.
Revenue recognition for software companies softrax. Dod esi financial guide for converting perpetual software licenses to software as a service saas 4 i. Software licensed on a perpetual basis is often, but not necessarily, hosted by the customer on its own servers and may require a higher level of customization and integration in order to interoperate with the customers other systems and meet the customers specific needs. Sure, to software folks like you and me we understand the nuances of a perpetual license versus a saas one. However, when implementing asc 606 to licenses of ip, revenue cannot be recognized before both 1 the licensor makes the ip available to the customer and 2 the license period begins asc 606105558c.
Typically a term license is priced to be equal to a perpetual license over three years. Fasb issues guidance on licensing and performance obligations. Under a perpetual license, you pay a onetime fee, and then have the right to use the software forever. Valuation of your company is impacted by, if not solely determined by, your historic revenue performance. The shift towards subscription has been fuelled by the adoption of cloud computing and software as a service saas solutions. Revenue recognition considerations for software and technology companies sep 08, 2017 published by rachel polson the new accounting standards update 201409 topic 606, revenue from contracts with customers creates a unified, principlebased standard on accounting for revenue from customers and replaces hundreds of pages of rules. With perpetual licenses, vendors can achieve vendor specific objective evidence vsoe, which demonstrates that the purchase of the upfront license is independent of any ongoing services. Forget the industryspecific guidance youve used before and prepare to make. It also would account for the nonsoftware deliverables per general revenue recognition criteria asc subtopic 60510, revenue recognition overall and multipleelement guidance asc subtopic 60525, revenue recognition multipleelement arrangements and account for the amount allocated to the software deliverables software and pcs as a group per the software revenue recognition guidance in asc subtopic 985605, software. Revenue recognition for timebased licenses is no exception. In contrast, revenues associated with timebased licenses are often recognized ratably over the license term because the current rules make it very difficult to establish vsoe for pcs bundled with a term license.
479 1082 1139 19 1326 1109 1008 1528 21 32 523 468 434 1605 929 670 1370 1252 657 1175 736 441 1587 219 1260 723 747 1355 60 283 600 530 88 676 524 311 179 564 1345