Model a Range of Different RevRec Scenarios.
RevRec Ready - Hot-Tip #5 Model a Range of Scenarios
Aug 25, 2015
Aug 19, 2015
Aug 12, 2015
Aug 12, 2015
Aug 4, 2015
Jul 29, 2015
Jul 28, 2015
Jul 22, 2015
Tue, Aug 25, 2015 @ 03:55 PM / by Bramasol RevRec Team posted in Revenue Recognition, SAP Revenue Accounting and Reporting, revrec hot-tips
Model a Range of Different RevRec Scenarios.
Wed, Aug 19, 2015 @ 06:26 AM / by Bramasol RevRec Team posted in Revenue Recognition, SAP Revenue Accounting and Reporting, revrec hot-tips
Revenue recognition projects only succeed if they follow a solidly structured approach.
Wed, Aug 12, 2015 @ 03:57 PM / by Bramasol RevRec Team posted in Revenue Recognition, SAP Revenue Accounting and Reporting
The RevRec Summit held in Dallas, TX on August 12th by SAP, EY and Bramasol was a great success, with more than 30 attendees from companies spanning a variety of industries.
Tue, Aug 11, 2015 @ 06:10 PM / by Bramasol RevRec Team posted in Revenue Recognition, SAP Revenue Accounting and Reporting, revrec hot-tips
You need to consider the needs of people beyond just your in-house users; especially the auditors.
External auditors, who themselves in many cases are uncertain how to interpret the new rules, will have to sign off on the changes. So you need to make it easy for external auditors to understand your process and decisions.Tue, Aug 4, 2015 @ 07:28 AM / by Bramasol RevRec Team posted in Revenue Recognition, SAP Revenue Accounting and Reporting, revrec hot-tips
The first step to success is revenue accounting.
Wed, Jul 29, 2015 @ 11:30 AM / by Hans Christian Metz posted in Revenue Recognition, SAP Revenue Accounting and Reporting
It’s a joint effort – Part 3 - Using a Structured and Phased Approach
Revenue recognition projects will only succeed if they follow a solidly structured approach. At Bramasol, we have found that one of the aspects causing confusion – in addition to the already complex subject matter – is lack of understanding how to best introduce the SAP Revenue Accounting and Reporting module to an organization, how to prepare good decisions, and when to take those decisions.
Both for consultants, as well as for customers, it is necessary to develop, coordinate, and manage expectations to the benefit of the project.
Tue, Jul 28, 2015 @ 02:07 PM / by Chris Ritterhern posted in SAP Revenue Accounting and Reporting
Tue, Jul 28, 2015 @ 12:08 PM / by Larry McKinney posted in Revenue Recognition, SAP Revenue Accounting and Reporting
On July 21st, 2015, my colleague and I were in Walldorf at SAP’s World Headquarters for the announcement of version 1.1 of the Revenue Accounting and Reporting (RAR) solution.
Wed, Jul 22, 2015 @ 08:47 AM / by Hans Christian Metz posted in Revenue Recognition, SAP Revenue Accounting and Reporting
It’s a joint effort – Part 2 - Stakeholders
Part 1 of this blog series outlined the key elements for success with the new SAP Revenue Accounting and Reporting Application. This post focuses on the importance of bringing together all of the stakeholders.
The multitude of projects our consultants at Bramasol have been working on in the area of SAP revenue recognition have made it very clear to us that projects run only well if all major stakeholders are engaged and work together.
The new guidelines are mandatory for all entities reporting under them – so they are all facing the same deadline. Still, we have discussions with customers where it becomes obvious that in some cases, only a single interested party in an organization seems to really drive the project - with others abstaining or worse yet, impeding progress.
We also have discussions where it is clear that the whole organization has realized the importance of close coordination between all stakeholders – these projects sometimes bring together managers and specialists for the first time, but they pull together as one. The difference is not whether a project will be completed – it has to, there is no alternative -, the difference lies in how painful the process will be, what time and effort it will have cost to complete.