Software license fee revenue recognition issues

Detailed rules on software license revenue recognition bi101. Licensing, selling, leasing, or otherwise marketing. Revenue recognition and saas accounting for subscription. Does anybody know how to treat up front revenue paid for a software license. Classifying settlement proceeds and ip licenses by noah webster 2018jan19 in the second part of this twopart series on the asc 606, litigation columnist noah webster delves into the considerations for recognizing revenue from settlement contracts, the two distinctions of ip licenses, and more. Many companies have been surprised at the length and complexity of the assessment and implementation phases for the new revenue. For example, an entity may license software, perform installation services, and provide unspecified. The standard has broad implications and may affect many parts of your organization. Revenue recognition is vital to correctly determine the financial health of your company, and you still need to recognize your revenue only when you earn it. Perpetual licenses and software license revenue recognition. Ninetyday warranties for software licenses seem to be accepted as routine. Revenue recognition is a critical piece of accounting for any business, and compliance with official standards is not optional. Will there be any changes to the timing of your revenue recognition. Sales or usagebased fees promised in exchange for a software license will typically not be subject to the general guidance on variable consideration.

That include software elements a consensus of the fasb emerging issues. The new standard presents a unique opportunity for taxpayers to revisit their tax methods for revenue recognition to not only ensure compliance with the tax rules, but also to take advantage of tax opportunities and planning around revenue recognition. Typically, the line items for revenue recognition in include licence fee which is broken. The revenue recognition transition resource group trg and the aicpas software revenue recognition task force have discussed various implementation issues impacting companies across many industries. Software licensing versus saas the revenue and cost recognition rules that different than the accounting rules that software licensing companies employ. Aug 02, 20 perpetual licenses and software license revenue recognition. Recurring revenue recognition issues in software companies determining the right accounting literatureto. Entities that license software to customers may need to determine whether they. Income earned by a company for allowing its ed or patented material to be used by another company.

In general, the portion of the arrangement fee allocated to pcs is recognized ratably. The sops basic principle in software revenue should be recognized at the time the software is delivered. Several revenue issues are topics of concern, as changes to these specific revenue areas could have a significant impact on a companys cash tax position and the timing of recognition. The new revenue standards asc 606 and ifrs 15, revenue from contracts with customers replace industryspecific. 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. Proper revenue recognition for subscription businesses for finance operations, one of the most menial and time consuming tasks is revenue recognition. Comapny financial year end is june 2011, the company raises an invoice in dec 2010 the licnese is paid in full in dec 10 also for a license agreement that runs from the 01012011 to the 31122011. This is not much of a change from what weve discussed above, but rather a much more clear stepbystep definition of rules for revenue recognition that can be easily applied across all businesses. While your customers may pay you a lump sum upfront for a years worth of usage, you wont be able to categorize that entire amount of cash as revenue right away. Accounting impact wide and potentially very significant effects on the timing and profile of revenue and profit recognition in comparison with current. In a software license agreement the license fee allocated to software cannot be.

Executive summary statement of position sop 972 provides guidance on applying gaap in recognizing revenue from software and software related transactions. Under this method, the full fair value, as indicated by vsoe, of the undelivered products and services is deferred. Softrax provides superior experience, knowledge, products, and services to address your companys asc 606 needs. Commencing the data conversion services prior to golive shifts the dates of revenue recognition but should not alter the method of revenue recognition. It applies to both public companies according to sab 104 and private enterprises. The high proportionate elements of the revenue recognition highlights two conflicting purposes in revenue recognition from sale of software products. Should the revenue from these fees be recognized upon contract. Software companies continue to analyze the impact of the new revenue standard on their contracts, accounting policies, and financial statements.

The revenue recognition principle is a cornerstone of accrual accounting together with the. For example, a company receives an annual software license fee paid out by a customer upfront on the january 1. Saas companies frequently encounter challenges in applying the new guidance, including. In a subscription model, all these are bundled into a subscription fee. Revenue recognition for software companies softrax industry. More than 80% of the companies also invoiced at the point of recognition of the revenue. 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. 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. Revenue recognition software helps tech vendors meet. All that is required is for the delivery to take place. Nine areas impacted by revenue recognition for software and saas. Jul 25, 2017 software companies continue to analyze the impact of the new revenue standard on their contracts, accounting policies, and financial statements. 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. While your customers may pay you a lump sum upfront for a years worth of usage, you wont be able to categorize that.

Therefore, assuming all other revenue recognition criteria have been met, it would be recognized on august 31. For accounting purposes, saas subscription revenues should be considered nonrefundable upfront fees. New guidelines for software revenue recognition practical. This is because according to the gaap software revenue recognition rules, revenue can only be recognized upon delivery if fair value has been established for each element within a contract. The complete guide to saas revenue recognition with asc 606. The list will be updated as the task force continues it discussions. 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 perspectives learned in the past year as public. Update on revenue recognition issues affecting software. Those companies with software license revenue will be most affected, while.

Introduction overview in october 1997, the american institute of certified public accountants aicpa adopted a new set of guidelines for revenue recognition in software. 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. Fasb issues guidance on licensing and performance obligations. An entity shall recognize revenue when or as the entity satisfies a performance obligation by transferring a promised good or service that is, an asset to a customer.

Software licensing is generally treated for accounting purposes as a sale or licensing of a product. Fasb updated revenue recognition guidelines for the amount and. Some examples of things that may be licensed include songs, sports. Abstract the accounting standards committee of the american institute of certified public accountants issued a paper to the financial accounting standards board on the recognition of revenue on the sale and licensing of computer software. The sop provides instruction on recognition for licensing, selling, leasing or otherwise marketing software. This is doubly so in subscriptionbased businesses where the financial accounting standards board fasb currently doesnt have any specific standards for saas. These include advance payments, percentage of completion, licenses of intangible property, and sales of inventory. Typically, the line items for revenue recognition in include licence fee which is broken down further to initial license fee or a capacity license fee, implementation and customization fee, annual maintenance support fee. As technology becomes further entrenched in consumer and enterprise products, companies outside of the traditional software. The new revenue recognition guidelines dont contain severe penalties for committing to specified features in future product releases. The timing of revenue recognition for unspecified software updates or upgradesenhancements and professional services will be similar to today.

New revenue guidance implementation in the software industry. 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 perspectives learned in the past year. Is it complete or does it require constant updates. 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. Historically, xlog issues around 12 software upgrades per year, but the. Greg fairbanks is a tax managing director with grant thornton llp in washington. Revenue recognition software could also boost companies profitability, according to reports published around the time of the fasb changes. Mar 22, 2016 regulations new revenue recognition standard means big changes for software companies.

Technology spotlight the future of revenue recognition deloitte. 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. No problem, you have the contract and you quote your selling price clearly. Practical applications of asc 606 for saas companies fei. Software revenue recognition rules and postcontract support. The challenges can arise from the sales process, the volume complexity of the sales transactions, the number of inputs required in the revenue process, or from the appropriate accounting standards that apply to your business. How to account for the sales of software licenses with. Revenue recognition within the software industry has historically been highly complex with much industryspecific guidance. Assuming that after the revenue allocation is performed according to sop 972 where vendorspecific objective evidence vsoe.

Revenue recognition challenges in the software industry. For functional intellectual property software, biological compounds or drug formulas, and completed media content, such as films, tv shows, or music, the nature of the entitys promise is to provide a right to use the entitys intellectual property as that intellectual property exists at the point in time the license is granted unless the entity is expected to undertake activities. If fair value has not been established on each element, then all revenue needs to be deferred until the contract is complete. The sec expects registrants to consider these discussions in applying the new guidance as they may provide helpful insight. Revenue recognition for software licenses accountingweb. If the proposal is finalized, the revenue recognition standard will take effect in 2018 for. May 03, 2016 recognize revenue when or as the reporting organization satisfies a performance obligation. 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. Revenue recognition for software companies softrax. What does the new revenue recognition standard mean for tax.

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 to software companies. Under current guidance, firm a would allocate a contract including deliverables within and outside the scope of software revenue recognition between software and nonsoftware components using the relative selling price method based on the multipleelement arrangement guidance in asc subparagraph 60525153a. In short, revenues related to these contracts were previously recognized ratably over the length of the contract but now may be accelerated under asc 606. Software the primary authority for software revenue recognition is aicpa statement of position sop no. The accounting literature on revenue recognition includes both broad conceptual discussions as well as certain industryspecific guidance. The timing of revenue recognition for unspecified software updates or upgradesenhancements and professional services will be similar to today sales or usagebased fees promised in exchange for a software license will typically not be subject to. New revenue recognition standard means big changes for.

Revenue recognition accounting for software as a service. For a saas or subscription business, revenue recognition can be complex, mainly because of the serviceoriented nature of the product. 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. Its almost twice as long as the first edition, with more examples and discussion of the areas that companies have found most complex, as well as the latest iasb and fasb developments. Revenue recognition for saas andor term subscription businesses. In january 2018, the new revenue recognition standard update no. Revenue recognition is a generally accepted accounting principle gaap and a fundamental aspect of the accrual basis of saas accounting. 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. It should be applied by all entities that earn such revenue. Revenue recognition issues are looked at on an arrangement basis rather.

The software is deliverablenothing needs to be done to complete or modify it before delivery. Companies who sell their software by subscription software asaservice or saas need to be particularly careful to ensure they are revising their policies appropriately for the new guidance. Revenue recognition, commonly referred to as rev rec or revenue rec, is an accounting principle and a process for reporting revenues by recognizing the monetary value of a transaction or contract over a period of time as the revenue is earned. Software revenue recognition journal of accountancy. 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 subsequent. Revenue recognition accounting for software as a service saas an executive webcast with jeffrey werner 1.

Often revenues will be recognized upon transferring control of initial goods or services to a customer, with some portion of the arrangement fee deferred until the new feature is released. Aug 26, 2016 regulations update on revenue recognition issues affecting software companies. Saas is viewed as the sale of a service that is provided over a period of time. Software companies are often tasked with deconstructing the typical. When the license is required for a customer to benefit from a related service e.

New guidelines for software revenue recognition practical pointers in providing guidance to clients part 1 i. Under current guidance, license renewals are generally recognized when the parties agree to the renewal and the fee is received or collection of the amount is probable. The fasb asked the aicpa to pursue the revenue side of the project after the aicpa published an issues paper on software revenue recognition in april 1987. Applying the new accounting for revenue recognition.

Asc 606 is a revenue recognition standard that will impact the software industry, particularly companies that offer onpremise subscription licenses over a finite, multiyear period. 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. Improve comparability of revenue recognition practices across entities. Below is a list of potential revenue recognition implementation issues identified by the software entities revenue recognition task force. Introduction the focus of part 2 of this article is on the practical steps that a lawyer should consider taking in preparing software agreements and the related policies and procedures to be considered by a software company in view of the new software revenue recognition guidelines, sop 972 the new sop. Fundamentals in software revenue recognition grant thornton lynne triplett, accounting principles partner. Recognizing revenue can be particularly challenging in the software industry. There are accounting software that are trying to solve the problem of. The impact of the new revenue recognition guidance on cloud. Implementing the new revenue guidance in the technology industry. The collectibility of the licensing fee is assumed to be reasonably assured.

264 849 1290 483 949 1168 495 782 246 1472 256 1203 1224 332 764 194 652 175 489 753 567 329 1421 793 619 1480 105 559 374 607 672 440 1361 820 951 1459 898 759 1120 1470 225 353 1474 406