The video of the May 4th Bramasol and SAP presentation to ASUG on SAP RAR is now available for viewing online.
The video of Bramasol's latest Revenue Recognition Webinar, "SAP RAR - Using Fiori to Improve Usability and Efficiency", is now available for viewing online.
There are many reasons to participate in a Proof of Concept, but one of the most common is to get the process moving and to focus on the solution. The implementation of a solution will involve many different departments…it is not just an IT initiative.
On March 22, 2016 at the 12th Annual Life Sciences Accounting and Reporting Congress in Philadelphia, Pennsylvania, James V. Schnurr, Chief Accountant of the Securities and Exchange Commission gave an update on the new revenue recognition guidelines and the process of implementing them. The following is a summary of his speech.
Mr. Schnurr began his speech by talking about the importance of revenue as a financial measure used by investors globally in assessing a company’s performance and prospects. He also addressed the inconsistencies between IASB and FASB and the importance of a standards convergence. The movement toward a converged standard culminated in May 2014 when the FASB and IASB issued the new standard on recognizing revenue (ASC 606 and IFRS 15 respectively). The new standard is designed to improve consistency by eliminating industry-specific guidance, providing a more robust framework for addressing revenue issues, and requiring additional disclosures to users of financial statements. Mr. Schnurr went on to say:
I consider the new converged revenue standard to be an important step forward in financial reporting for preparers and investors, both domestic and foreign. These changes will impact all companies and all industries, but the extent of the impact will differ from industry to industry.
Bramasol is proud to be presenting a special session on Revenue Recognition at SAPPHIRE NOW and ASUG Annual Conference in Orlando, FL.
The video recording of our latest webinar "SAP RAR 1.1 - A Dive into New Scenarios" is now available for viewing online.
Per ASU 2014-09, a performance obligation is a promise in a contract with a customer to transfer a good or service to the customer. If an entity promises in a contract to transfer more than one good or service to the customer, the entity should account for each promised good or service as a performance obligation only if it is (1) distinct or (2) a series of distinct goods or services that are substantially the same and have the same pattern of transfer.
