to receive member fee.
Change is definitely coming. For those entities currently following industry-specific accounting guidance for revenue recognition, Topic 606 will be replacing this with a single model. For those in the technology sector that utilize Statement of Position 97-2, Software Revenue Recognition (SOP 97-2), adopting Topic 606 will most likely result in significant changes to when you recognize revenue, particularly with regard to contracts with multiple performance obligations. With the requirement to have vendor-specific objective evidence (VSOE) to support the allocation of transaction price going away under Topic 606, technology companies will also see major change in how they allocate transaction price, which will impact when they record revenue on these transactions.
With Topic 606's effective date right around the corner, now is the time to get the answers to your implementation questions. In this course, we'll explore Topic 606 from the perspective of entities that currently recognize revenue under SOP 97-2. We'll highlight the changes that Topic 606 makes to the guidance found in the SOP and focus on the impact that software entities should expect when implementing this new guidance.
Implementing Topic 606 will be a challenge for software entities, and this course will help you identity and resolve these issues so that you can complete your adoption strategy.
Accounting and auditing practitioners at all levels desiring to understand the challenges in applying Topic 606 for those in the software industry