{"id":3964,"date":"2016-04-12T15:43:12","date_gmt":"2016-04-12T13:43:12","guid":{"rendered":"https:\/\/chartmogul.com\/blog\/?p=3964"},"modified":"2023-08-09T21:02:38","modified_gmt":"2023-08-09T19:02:38","slug":"changes-to-revenue-recognition","status":"publish","type":"post","link":"https:\/\/chartmogul.com\/blog\/changes-to-revenue-recognition\/","title":{"rendered":"Ready or not, changes to revenue recognition are coming"},"content":{"rendered":"

Revenue recognition is changing. A new accounting standard is slowly, slowly, being implemented across all kinds of businesses \u2014 big and small, goods and services, on earth and in the cloud.<\/p>\n

Despite a flurry of discussion about it in the accounting world, most companies haven\u2019t paid the change much mind yet. The deadline is 2018 \u2014 and sure, technically you still have a year and a half to adopt it. But don\u2019t underestimate the impact of what seem like mere accounting details. As PwC<\/a> warns,<\/p>\n

\u201cThe impacts of the new standard extend far beyond technical accounting. Change to the way revenue is recognized will have broader impacts on other areas of the business, including go-to-market strategies, income taxes, compensation arrangements and debt covenants, among others.\u201d<\/p><\/blockquote>\n

Arm yourself with information now and the inevitable transition may not be so tricky. No time like the present, right?<\/p>\n

What is the new standard?<\/h1>\n

The new standard is called Revenue From Contracts With Customers<\/em>, or less affectionately, ASC 606. A joint endeavor by the Financial Accounting Standards Board (FASB) and International Accounting Standards Board (IASB), its aim is to smooth over how contracted revenue is recognized across industries and around the world. Uniform and simplify.<\/strong> It was originally set to go into effect in December 2016, but the adoption deadline has been revised to January 1, 2018.<\/p>\n

Why is it happening?<\/h1>\n

Thus far, revenue guidance has been either (a) generally lacking, or (b) highly sector-specific or even transaction-specific. For example there were all sorts of technicalities around whether, and when, your product would be considered \u201csoftware\u201d or a \u201cservice.\u201d This unnecessarily acute specificity led to different accounting methods for transactions that were actually economically similar. It led to varying revenue recognition patterns that didn\u2019t accurately reflect business\u00a0performance. Such discrepancies were a bit of a nightmare for the other side: auditors, investors, and anyone interested in acquiring a company.<\/p>\n

The new reporting framework applies to any<\/strong> situation where there is a contract for goods and services<\/strong>. It\u2019s principles-based, which means it\u2019s comprehensive yet leaves a lot of room for judgment on the actual execution. The model is also neatly sorted into five steps.<\/p>\n

The model<\/h1>\n

\"Revenue<\/p>\n

As you can see, each point gives the company a lot of agency. You identify, you determine, you allocate.<\/em><\/p>\n

The new standard leaves a lot more judgment to management. As a result, the new standard also requires a lot more explanation from management. I.e.- disclosures<\/strong>, justifying your judgment and disclosing how it impacts your financial line items. Considering this\u00a0it\u2019s imperative you understand your realm of influence when it comes to revenue \u2014 and how your decisions affect your financial reporting.<\/p>\n

What does each step mean for SaaS?<\/h1>\n

Though the new model may be simple, implementation can be anything but. Here’s a brief overview of the basics, laying out how you would apply the\u00a0model to each contract. However there are many more intricacies involved in full implementation which are better discussed with an accounting professional!<\/p>\n

Step 1: Identify the contract with a customer<\/h2>\n

Whether or not you use the word \u201ccontract\u201d in your SaaS business, here it simply means \u201can agreement between two or more parties that creates enforceable rights and obligations\u201d \u2014 the service agreement with your customer.<\/p>\n

Step 2: Identify the separate performance obligations in the contract<\/h2>\n

A \u201cperformance obligation\u201d is a distinct service included in the contract. A service is distinct if the customer can benefit from that specific element on its own, without corresponding service or software use. The subscription itself is a performance obligation, but there could be other items bundled, too. It\u2019s up to you to determine if whether\u00a0items are separate performance obligations or not.<\/p>\n

Example<\/h3>\n

There’s a\u00a0SaaS contract that’s a multiple-element arrangement of\u00a0\u201csubscription + consultation.\u201d If the consultation service provides measurable value to the customer apart from their use of the subscription software, then\u00a0the consulting element would be a distinct service with a distinct cost (see Step 4) and require a separate line in revenue accounting. However if the consultation was just teaching the customer how to use the software better<\/em>, then it is not a distinct service and not a separate performance obligation.<\/p>\n

Step 3: Determine the transaction price<\/h2>\n

Pretty straightforward. This is the actual cost you expect to be paid for delivering a service.<\/p>\n

Step 4: Allocate the transaction price to the separate performance obligations in the contract<\/h2>\n

Each performance obligation (remember: distinct service) needs its own transaction price. This could get hazy if your company doesn\u2019t already and clearly allocate value\/cost within a subscription, diced out for each element in the contract. Most don\u2019t. So it\u2019s largely an estimate. Allocating the transaction price is another place where your judgment comes in. Also, you must consider any discounts offered to the customer!<\/p>\n

Step 5: Recognize revenue as\u00a0the entity satisfies a performance obligation<\/h2>\n

With a subscription, you satisfy your performance obligation over time. So you recognize the revenue from the customer over time, usually month by month. Different revenue recognition schedules exist for other types of performance obligations.<\/p>\n

How to adopt it?<\/h1>\n

There are two options for transition to the new revenue recognition standard. Regardless of which method you choose, you will have to maintain two sets of accounting records and supporting processes for some period of time.<\/p>\n

Full retrospective transition<\/h2>\n

Wait until the deadline.<\/strong> The new standard is applied retrospectively to each prior reporting period presented with the cumulative effect of the change recorded in retained earnings as of January 1, 2016. Two years of dual GAAP reporting.<\/em><\/p>\n

Modified retrospective transition<\/h2>\n

Start now.<\/strong> The new standard is applied to all existing contracts as of the effective date and to all future contracts. While this allows companies to avoid restating prior periods, there is a still some extra work. The qualitative and quantitative impact of applying the new standard on all affected financial statement line items must be disclosed in the year of adoption. One\u00a0year of dual GAAP reporting.<\/em><\/p>\n

\"revenue
Source: PwC<\/figcaption><\/figure>\n

Final\u00a0Word<\/h1>\n

Stay engaged with your revenue recognition schedule and financial reporting. After all, revenue performance determines the valuation of your company, and your revenue recognition methods will be heavily scrutinized. You want to make sure your company is compliant with the new standards, and that your methods are aligned with those who are evaluating your business. Seeking help from a professional accountant is wise. Best of luck in the transition!<\/p>\n

Name:<\/strong> ASC 606, Revenue From Contracts With Customers
\nDeadline:<\/strong> U.S. GAAP public companies is January 1, 2018, U.S. GAAP non-public companies is January 1, 2019
\nResources:<\/strong>
\nExhaustive accounting and financial reporting guide<\/a>\u00a0on ASC 606 from PwC
\nOverview<\/a> of ASC 606 from Deloitte<\/p>\n\n

Share and follow!<\/h1>\n
\n

NEW on @ChartMogul<\/a>: Ready or not, changes to #revenue<\/a> recognition are coming https:\/\/t.co\/XMYeCAvXtd<\/a> #SaaS<\/a> #Startup<\/a> pic.twitter.com\/PKPTgbobUb<\/a><\/p>\n

\u2014 ChartMogul (@ChartMogul) April 12, 2016<\/a><\/p><\/blockquote>\n