One recurring learnings from our work across organisations, is the importance of finance data architecture and data collection. This includes the processes and policies for collecting data and analysis codes.
As partners providing enterprise resource planning solutions, we often have conversations with finance teams at the point when they have decided that their system is no longer working.
While it often is the case that there are better systems for them, we have also noticed a trend. Too often, the system is blamed for a problem that actually starts much further upstream. The problem, in fact, usually begins with the data collection, segments/dimensions/analysis codes.
The Challenge of Data Collection and segments/dimensions/analysis codes
Data is complex in the commercial context.
Very often, an organisation needs to tie Accounts Payable to Account Receivables together. This particularly arises in the context of project accounting and separate sales CRM data and Finance.
This often leads to a complex range of different data held in different systems particularly between CRM, order/project management and finance systems sometimes spread out across various locations around the globe.
By the time the problem makes it to us, we hear that there are different numbers on different reports or even that your organisation’s data is too complex to run reports on.
However, if you don’t focus on the data architecture first, this problem will only duplicate itself in whatever system you choose next.
The Challenge of Customisations
Most organisations try to manage this maze of data architecture through customisations. Sometimes this means configuring existing ERPs – and reconfiguring, and reconfiguring again. Other times, that means creating highly specific, new reports to reconcile all the different data fields.
After going down this road for a little while, the customisations can even feel comforting or necessary for your organisation. Your team works hard to deliver for your organisations mission, and the configurations you have come up with function to a certain extent, so why take the time and energy to fix what isn’t completely and horribly broken?
The Solution: Single Source of Truth Data
The truth is that shaky data architecture and complex workarounds cost your organisation. Endless configurations to your ERP turn your finance experts into a pseudo-IT team. Custom report upon custom report upon custom report mean that when someone is out on holiday, you can’t pull up the data you need to make the decisions to empower your organisation.
That is why – even beyond choosing a new ERP – it is so crucial to move to the Single Source of Truth (SSOT) data model. You’ll set up one single data source where all your data lives. Then, every other part of your financial planning and reporting integrates into that data source with the SSOT data model.
Time Savings: Adopt, Not Adapt
When stuck with multiple data sources, your team has had no choice but to adapt, adapt, and keep adapting as needs changed. It can be tempting to look at any new system for data architecture and see all the ways your team would configure it to meet each of your specific needs.
Instead, consider the “Adopt, Not Adapt” strategy. Work with your ERP to discover the established data best practices for charities across the platform, and implement those best practices for your team. From there, you can adapt if necessary. However, starting with this strategy allows your organisation to restart your data architecture according to industry best practices, instead of carrying over the problem from your old system into your new one.
Our goal is to unleash the potential of an organisation. That means identifying the problem where it begins, instead of assuming the problem is the existing system. After helping many organisations transform the financial planning systems, we have seen how important it is to commit to creating a sturdy data architecture to ensure the success of your team.
Cloud Doing Good is an Oracle-NetSuite’s specialist partner, working exclusively with the ‘Suite Success Adopt not Adapt’ methodology. Here is a 2.5 minute video on who we are.