In recent months, companies with complex revenue recognition processes have been gearing up for a fundamental change in how they account for revenue derived from their contracts with customers. The new revenue recognition standard is known as ASC 606 in the United States, or IFRS 15 elsewhere around the world.
Companies across all industries have been asking us what ASC 606 compliance means for them, how it can benefit them, and what they need to know. To address these shared questions, we have partnered with Simplus’s CPQ implementation specialists to put together this multi-part blog series. In this blog post—the first of five—we will explore five essential things that every company with complex revenue recognition processes should understand to achieve ASC 606 compliance:
Revenue recognition is moving further up the sales pipeline: in traditional revenue operations, revenue recognition is driven by orders and invoicing schedules. However, this is actually relatively late in the sales pipeline, and ASC 606 is requiring that revenue be recognized much earlier, at the stage where agreements and quotes are generated for contracted pricing. This change in philosophical approach has significant ripple effects for how revenue recognition data is recorded on your accounting ledgers.
Goods and services need to be delivered to the customer before revenue can be recognized: A core principle of ASC 606 is that companies should not recognize revenue until goods and services have been delivered to the customer. This requires you to identify what exactly constitutes a contract. For example, it could be an explicit customer quote, or it could be a negotiated contracted document. Once you define what a contract is, you will be able to decide when the transfer of goods and services to your customers is actually occurring.
Recognized revenue must reflect the actual consideration to which your company is entitled: When you recognize revenue, ASC 606 requires you to do so in a way that reflects the total consideration you actually expect to receive from the delivery of goods and services. This recognition process can get very tricky very quickly, especially if your pricing is set through subscriptions, multi-year contracts, and recurring revenue relationships.
Legacy ways of structuring deals and discounts may not be compatible: The contracts you are accustomed to are not necessarily compatible with ASC 606 revenue recognition standards. Indeed, many companies have built their deals and structured their discounts in ways that do not allow the accounting department to readily recognize revenue derived from the transfer of goods and services to the customer—nor to do so in amounts that can be linked to the actual consideration to which the company is entitled.
Systems built for one-time sales transactions are unlikely to be helpful: As your Customer Relationship Management (CRM) needs have evolved, you have no doubt developed ad-hoc solutions that build upon and adapt the base systems you’ve had for years. In many cases, these base systems were built for one-time transactions; then, you customized the systems with workarounds to accommodate your changing business model. With the advent of ASC 606, systems originally built for one-time transactions are unlikely to be able to make the transition. You need a modern CPQ (configure, price, quote) system like Salesforce CPQ that can be easily configured to properly manage the treatment of revenue in compliance with ASC 606.
The new ASC 606 compliance standards will be challenging for many businesses, but they also can be advantageous. The changes you’ll be required to make under ASC 606 will force you to revisit and overhaul aspects of your sales cycle that may not be as efficient or as connected as it should. The key things to remember about achieving ASC 606 compliance are that revenue recognition is moving further up the sales pipeline, revenue recognition can only happen after goods and services are delivered to the customer, revenue recognition must reflect the actual consideration to which the company is entitled, legacy ways of structuring deals may not be compliant, and legacy systems originally built for one-time sales transactions may not be compatible.
To learn more about ASC 606 and how you can use the powerful capabilities of Salesforce to automate and streamline your ASC 606 compliance obligations, please visit https://www.salesforce.com/campaign/asc-606