January 15, 2020
ASC 606 & The Urgency of Finance Transformation for Software Companies
The deadline for private companies to file annual financial statements under the new revenue recognition standards (ASC 606) is fast approaching. ASC 606 is the biggest development in accounting since The Sarbanes-Oxley Act, and perhaps the biggest change in standards in the last 100 years. It’s been quite a roller coaster for organizations of all sizes.
For private companies who have lagged behind, 2019 year-end financials are the last chance to attain ASC 606 compliance under the wire. Many emerging software companies fall into this category — and may already be experiencing a painful start to the year. Non-compliance or errors on those year-end statements will require time-intensive restatements. Issues like these can create additional pressure both internally and externally, with some of the most severe consequences stemming from non-compliance with GAAP.
It’s time for a long hard look at your progress with adopting the new ASC 606 standards and implementing them into your ERP solution. It might also be time to call for help.
KEY PAIN POINTS FOR SOFTWARE COMPANIES STRUGGLING WITH ASC 606 ADOPTION
- ASC 606 changes affect all aspects of the business. The Financial Accounting Standards Board (FASB) has redefined everything from revenue allocation to cost deferral. That means everyone in finance, accounting, sales, delivery, product management, and marketing has to change the way they think about revenue recognition — and how they work as a result.
- ASC 606 may force accounting decisions that have ripple effects across the business. For example, when a firm shifts its accounting policy to recognize licensing revenue upfront, financial statements become choppy. This makes it difficult to compare statements year over year, forecast revenue and plan strategically. As a result, moving to a subscription model may become more attractive and organizations may accelerate those plans.
- Implementing ASC 606 can get very complicated, very quickly. Organizations may have additional records to configure within their enterprise resource planning (ERP) system. Software transaction models that are highly variable may require extensive adaptations. Mergers and acquisitions can also increase the complications, as the different entities might have different policies and configurations that must be aligned.
All of this can quickly bog down the revenue team. Meanwhile, the clock keeps ticking.
YOUR ERP ASC 606 IMPLEMENTATION: WHAT IT REALLY TAKES
PREPARE THE ENTIRE ORGANIZATION FOR CHANGE
Sales, marketing and product teams must have a deeper understanding of your products, how you sell and discount them, and when and how they are delivered. They also need to understand how their practices may change under ASC 606. For example, one of Bridgepoint’s clients is a leading mainframe software provider. When we helped this client implement NetSuite in accordance with the new ASC 606 standards, the organization had to reassess its software delivery model — especially around end-of-year sales.
If the sales teams don’t fully grasp a company’s policies under ASC 606, they might close deals that simply don’t fit the parameters configured in ERP. This creates frustrating additional work for the revenue team and poses the risk of error-prone manual recognition.
With our mainframe software client, Bridgepoint engaged many stakeholders to help them understand how the business will recognize revenue going forward and how financial statements will change. Decision-makers must be brought up to speed, as well as all members of any departments that rely upon revenue numbers for budget, commissions and performance metrics.
REVIEW ALL CONTRACTS TO DETERMINE THE ACCOUNTING POLICY YOU’LL FOLLOW UNDER ASC 606
Before you can move forward, you have to understand what you’ve got. All existing sales revenue contracts need to be reviewed by qualified individuals to understand the details of each agreement. This can be especially challenging for growing organizations that may have started out with non-standardized sales practices and acquired other companies over time. You may have hundreds of contracts, each with a unique set of terms and agreements that must be assessed and addressed. This review may also reveal additional needs, such as fair value pricing studies, that must be completed to attain compliance. The information gathered in the contract review will help your revenue team, accounting and auditors settle on which ASC 606 rev rec methods to adopt in your implementation.
PLAN YOUR IMPLEMENTATION ROADMAP
In many ways, implementing ASC 606 within your ERP translates to the internal migration of all of your contracts to the new method. Start by conducting an analysis and modeling to identify the necessary configuration and customization work. For example, with NetSuite’s Advanced Revenue Module (ARM), the following records may require additions, changes, and updates:
- Item Revenue Categories
- Revenue Recognition Rules
- Forecast Revenue Recognition Rules
- Fair Value Formulas
- Fair Value Price Lists
You may also need to make modifications to the item master configuration, transaction dimensions, and any standard or custom fields; as well as any scripts and settings that assist with automation. With a clear sense of scope, you can then outline a strategic plan that makes the most effective use of the time and resources at hand.
EXECUTE YOUR IMPLEMENTATION PLAN
In addition to the ERP configuration and customizations, you may have to make adjustments to other systems. Be sure to identify and address any necessary work within your Customer Relationship Management (CRM) platform, Configure Price Quote (CPQ) software, Services Resource Planning (SRP) solution, etc.
Looking for NetSuite expertise?
Visit our NetSuite Services Page
CONTINUE MAINTAINING YOUR CONFIGURATION AND IMPROVING PRACTICES
As your organization grows and changes, your ERP configuration will have to be tweaked and adjusted. Any shift in your product mix, customer base or sales model may require configuration maintenance. New acquisitions may not be fully ASC 606 compliant, or they may have approached their ERP configuration differently.
The reality is, the still-developing impact of ASC 606 and the rapid evolution of the software industry both point towards a need for regular NetSuite maintenance from here on out.
BRINGING IT ALL TOGETHER
Whether or not your organization has fully adopted ASC 606 yet, there will still be plenty of work to do within your ERP for the foreseeable future. As the deadline for filing financial statements looms, now’s the time to redouble (or triple) your ASC 606 compliance efforts. It may even be time to sound the alarm for help. Engaging an experienced partner that can guide you — or even handle the work for you — can ease the pressure, so you can focus on running the business.
HOW BRIDGEPOINT CAN HELP
Bridgepoint has helped numerous public and private companies through their ASC 606 transitions. We also have deep experience working with software companies on a wide range of technical, operations and finance initiatives. If you’re feeling overwhelmed or even panicked at the thought of year-end close and reporting, please get in touch. Our expert team can manage the entire transition on your behalf — or handle discrete tasks like contract review, systems analysis or configuration assessments. We’re also here to help with merger and acquisition issues related to ASC 606, such as merging divergent revenue recognition practices and systems. Intrigued? Learn more about Bridgepoint’s ASC 606 transition services.
Top 10 Highlights: NetSuite 2019.2 Release
How Software Companies Can Get Ahead of ASC 606
3 Keys to a Successful ERP Implementation