By Hiran de Silva
One of the biggest misconceptions in modern business technology is the idea that ERP systems and Excel are rivals.
The ERP vendors tell us that spreadsheets are the problem.
The Excel replacement industry tells us that spreadsheets are holding businesses back.
Many ERP consultants imply that the answer is to move everything into the ERP platform.
Meanwhile, parts of the Excel community respond by defending Excel as if it is competing against ERP systems.
I believe both sides are looking at the problem incorrectly.
ERP systems and spreadsheets should not be competing.
They should be working together as one ecosystem.
What Is an ERP System?
One reason this misunderstanding persists is that many people don’t really understand what an ERP system is.
To most business users it appears to be a black box.
It is managed by the IT department.
It has governance.
It has controls.
It has procedures.
It has reports.
It is difficult to modify.
It is expensive to change.
But underneath all of that complexity lies something surprisingly simple.
Data.
An ERP system is fundamentally a collection of relational database tables and the business logic that operates around them.
When a sales order is entered, records are added or updated.
When a purchase invoice arrives, records are added or updated.
When payroll runs, records are added or updated.
When journals are posted, records are added or updated.
Everything ultimately revolves around data stored in relational tables.
The database is the heart of the ERP system.
The screens, forms, reports, workflows, security controls and business processes are layers built around that data.
The ERP system is essentially a client-server environment.
The server stores and manages the data.
The clients provide ways for the business to interact with that data.
Understanding this is important because it changes how we think about spreadsheets.
The Gap That Always Appears
Businesses evolve.
New requirements emerge.
New regulations arrive.
New management requests appear.
Someone asks for a new analysis.
Someone wants a new workflow.
Someone wants a new review process.
And suddenly the ERP system doesn’t quite do what the business needs.
This is not a failure of the ERP system.
No system can anticipate every future requirement.
Historically, businesses bridged these gaps using paper.
People created registers, forms, filing systems and manual procedures.
Today they open Excel.
Excel becomes the emergency toolkit.
Excel becomes the bridge between what the business needs and what the system currently provides.
In many cases that bridge becomes permanent.
The Mistake Most Organisations Make
Most organisations treat the ERP system and the spreadsheet environment as separate worlds.
The process usually looks something like this:
Export data from ERP.
Open Excel.
Import data.
Manipulate data.
Email spreadsheets.
Consolidate spreadsheets.
Chase versions.
Repeat.
This creates a second disconnected ecosystem.
The ERP system lives in one world.
The spreadsheets live in another.
The only connection between them is a file export.
This is where much of the inefficiency comes from.
Not because Excel is bad.
Not because the ERP system is bad.
But because they have been artificially separated.
The Missing Piece
The missing piece is recognising that spreadsheets can participate in the same ecosystem as the ERP system.
Not by replacing the ERP system.
Not by modifying the ERP system.
Not by creating risk.
But by connecting intelligently to the same data architecture.
Instead of thinking:
ERP System versus Excel
we should be thinking:
ERP System plus Excel.
When viewed this way, Excel becomes another client in a client-server architecture.
Exactly like the ERP screens themselves.
Exactly like reporting tools.
Exactly like web portals.
Exactly like mobile applications.
The spreadsheet becomes another way of interacting with business data.
The Budget Review Example
I often demonstrate this principle using my Budget Review model.
Imagine a business with:
- 400 budget holders
- 145 managers
- A finance team
- Thousands of account lines
The traditional process involves everyone downloading information individually.
Managers review their data locally.
Comments arrive through emails, meetings, phone calls and spreadsheets.
Finance attempts to consolidate all of this information.
The process becomes slow, fragmented and difficult to control.
Now consider a different approach.
At month end, a controlled extract of the General Ledger is copied into a separate relational database.
A clone.
Not the live ERP database.
Not a modification to the ERP system.
A working copy.
From that point onward, budget holders, managers and finance staff work collaboratively within a shared Excel-based environment.
Comments are captured centrally.
Adjustments are tracked centrally.
Status is tracked centrally.
Audit trails are maintained centrally.
Everyone is working from the same source of information.
When the review is complete, the resulting journals are uploaded back into the ERP system through its standard import mechanism or API.
The loop is complete.
The ERP system and the spreadsheet environment have worked together towards a single objective.
One ecosystem.
An Important Clarification
At this point some readers may think:
“That sounds like another IT project.”
No.
In fact, quite the opposite.
One of the most important principles behind this approach is that the business should be empowered to solve business problems.
The tools already exist.
Excel.
Relational databases.
Import mechanisms.
APIs.
Client-server architecture.
These are not exotic technologies.
They have been available to business users for decades.
The traditional mindset is that every new business requirement must be handed to IT.
The business submits a request.
The request enters a queue.
The queue enters a prioritisation process.
Months pass.
Budgets are discussed.
Consultants are hired.
The business waits.
This approach starts somewhere entirely different.
The business creates a proof of concept.
The business demonstrates the value.
The business proves that the requirement is real.
In many cases there may be little or no IT involvement at the beginning.
A finance team.
A planning team.
An operations team.
A business analyst.
Any of these groups can build and demonstrate a working solution.
Only after the value has been proven does IT involvement become necessary.
And even then, the discussion changes.
Instead of asking:
“Can IT build this for us?”
the business says:
“We have already demonstrated that this works. How can we operationalise it?”
That is a completely different conversation.
The business leads.
IT supports.
Both sides contribute their strengths.
Why This Matters
The irony is that this architecture mirrors the same client-server architecture used by the ERP system itself.
Yet it can often be prototyped in days by the business rather than waiting months for a formal development project.
ERP systems are excellent at transaction processing, governance and control.
Excel is excellent at agility, innovation and rapid problem solving.
Neither replaces the other.
Each does what it does best.
When organisations force them into separate camps, inefficiency follows.
When organisations allow them to work together, extraordinary things become possible.
The Real Future
The future is not ERP replacing Excel.
The future is not Excel replacing ERP.
The future is recognising that both belong within the same architecture.
One data ecosystem.
Multiple clients.
Shared objectives.
The ERP system does what it does best.
The spreadsheet ecosystem does what it does best.
And together they create something more powerful than either can achieve alone.
That is the lesson of the Budget Review model.
And I believe it is one of the most important lessons that modern business technology has yet to fully understand.
Add comment