Moving accountants to system analysts

11 October 2012

Mark Chalfen

Mark Chalfen

Former SAP S/4HANA Global Lead

There has been a real shift of power within finance organisations. Due to process and system efficiencies, the role of the Accountant has evolved. Historically the Accountant was there to record and reconcile financial data. These (low value - high volume tasks) have slowly been automated, removing the need for large armies of qualified Accountants to crunch figures. At the same time the size of organisations has grown, and with it, so has the volume of data.

What is expected of the "system analyst"?

I believe the new role requires three specific flavours which are:

  1. Spot trends
  2. Measure performance
  3. Identify risks

Spot trends

You have probably read this a hundred times already but business sentiment is moving at a pace like never before. As I write this today, the IMF has down-graded global growth again. These statistics seem to move dramatically every quarter. The same can be seen for organisations. Spotting trends, such as growth, hot products, poorly performing customer groups need to be performed frequently.

A simple example relates to a manufacturing client. Generally they will have hundreds of different products and will need future sales information to assist with the production forecasting of products. If the data is wrong the client will either be left with too much stock which will impact cash flow, or not enough stock which will impact sales and ultimately profit. The use of analytical tools enables these trends to be identified in a consistent manner.

Measure performance

Organisations are now aligned more to KPI's. By having a number of KPI's the success or measurement of them will provide a health check on the organisation. Setting a benchmark and measuring performance against the benchmark will provide early visibility as to the performance of the organisation and its future performance. Again this links in well to trends, as measuring performance allows remedial steps to resolve issues that could occur in the future.

Further to this, comparisons of business units, or product types, enables top performing units or products to be identified and invested in further. On the other end of the scale, units or products that do not perform as well can be analysed to resolve any potential issues. Using KPI's to measure the performance of business units or products will allow strong performing areas to coach the weaker areas to strengthen the organisation as a whole. The use of dashboard tools provides the system analysts a simple tool to track the performance based on a set of measures.

Identify risks

Where "actuals" and "budgets" align the need for further analysis is limited. Where a significant variance occurs between an actual and a budget further analysis is required. Some variances maybe positive, so having a higher revenue actual than the budgeted revenue normally is a good indicator. However there will be a risk associated to this. This could be due to the ability to meet future orders or the impact the extra revenue growth would have on the cash flow.

The ability to accurately tie up actual against budgets will improve the visibility of the performance of an organisation. As mentioned previously, business sentiment moves at a fast pace. In turn this leads to the requirement to have an Agile approach to budgeting and forecasting as the rationale used to create figures that are 6 months old may no longer be valid.

Summary

Where I am sitting this new type of role for the finance community is much more rewarding and value adding. Whilst ERP systems are important to record transactions, the real value for a finance department is found analysing data outside of ERP. Without ERP there would be no data to analyse, but once you have a stable platform the focus should change. There will always be a requirement to tidy up data within the system of record and to enhance the processes but the finance community can now start to add value by spotting trends, measuring performance and identify risks for the organisation.

View comments

Comments

Blog post currently doesn't have any comments.

About the author

Mark Chalfen

Former SAP S/4HANA Global Lead

Mark tells it straight - as an ex-boxer, what else would you expect?  Both his knowledge and experience of SAP products allow him to cut to the chase dispelling myths and hearsay.

As a result of working closely with various SAP Finance Product Management teams on product development, Mark understands these products inside out. This depth of understanding has led to him become a ‘thought leader’ in his field; after all, it is not often SAP consultants have helped shape and develop the very product they are selling.

Having such a strong relationship with SAP alongside being an SAP Mentor and Moderator means that Mark has an extensive network within SAP. For clients, this relationship proves to be a huge advantage and leads to configuration issues being resolved rapidly.

Mark has worked on short proof of concepts through to year-long multi-million pound global roll-outs. However, no matter how large or small the project, the true value Mark brings to his work is in the guidance he provides to senior stakeholders. In essence, he assists them to implement more effective processes and drive better behaviours within their finance teams.

Helping organisations transform their business with SAP S/4HANA is Mark’s current focus. The benefits of S/4HANA are numerous, including the simplification of tasks, embedded analytics and improved user engagement. Whilst the eventual move from SAP Business Suite into S/4HANA is inevitable, the journey to it is not always clear. Mark’s ability to understand an organisation’s needs coupled with his deep understanding of S/4HANA provides clarity and eases their transition.