ERP Project Recovery
Your team is still working in Excel even though you have an ERP: why it happens and how to fix it
Your ERP is live, but the close still runs on spreadsheets. Why it happens, what it costs your company and how to fix it.
· 5 min read
The ERP went live months ago and the project was declared closed. Even so, the month-end close still ends in a spreadsheet: someone exports, adjusts by hand and emails the version that is actually used to make decisions. Nobody reports it as a failure, because operations keep running.
It is an ERP that is only partly used. And it is almost never a people problem: whoever rebuilds a report in Excel is solving something the system did not solve for them. Fixing it starts with finding out what that was.
The warning signs
Part of the work that should happen in the system is happening off to the side:
- Export and rebuild: every close starts with an export and ends in a file adjusted by hand.
- Parallel reports: two versions of the same report, the one from the ERP and the one that is actually presented.
- Double entry: the same data lives in the system and in a separate file, and the file is the one people consult.
- Reconciliations outside the system: every month, as routine rather than as the exception.
- Numbers that don't match: finance and operations arrive at the same meeting with different figures for the same month.
- Files with an owner: a file that only one person understands and that the close depends on.
A single sign is an isolated case. If they repeat every month and in more than one department, part of the operation has already moved outside the system. And every parallel file takes away from the ERP what justified its investment: a single source of information for the whole company.
Why it happens
The team goes back to the spreadsheet because it finds there what the system doesn't give it. These are the three causes we see most at CETERiS when an ERP never quite gets adopted.
The design doesn't match how the business operates
The system was configured for the process as it was described during the project, not as work actually gets done on a close day. Exceptions were left unmodeled, approvals follow a different path in practice, and master data doesn't reflect how the business is analyzed. Where the system can't handle the real case, the spreadsheet can.
Training covered the screens, but not where the numbers come from
People learned where to enter data and which button comes next. What often gets left out is where each number in a report comes from and how to verify it is correct. Without that trail, a careful person checks in their own file. That is reasonable behavior, not resistance to change.
Habits inherited from the previous system
Manual steps that existed because of the old system's limitations moved to the new one without anyone questioning them. The ERP ended up layered on top of the habit instead of replacing it.
Two accelerators act on those causes. The first is trust: it takes just one figure that doesn't reconcile for the team to use the system only for data entry. Trust is lost all at once and recovered slowly. The second is the report the system doesn't deliver in the format leadership or the tax authority requires. It gets exported, assembled and sent, and over time that file becomes the official report.
What it costs the company
It doesn't show up in the budget, but it is paid for in four places:
- Control: the system's approvals, permissions and audit logs don't reach what happens inside a file, where a formula can change without leaving a trace.
- Audit: if the final figure comes from a file, in every review you have to demonstrate how you got from the transaction to that number.
- Close time: it lasts as long as the slowest manual step and depends on whoever performs it.
- Decisions: when two departments arrive with different figures, the meeting is spent arguing over which one is right.
And every month the parallel file stays alive, more processes lean on it and the return that justified the project drifts further away.
How to fix it
1. Measure where the operation leaves the system
The starting point is an inventory of the files that accompany the ERP: who uses them, what they pull from the system, what they add by hand and who they are handed to. Then you trace the figure that reaches leadership, from the final report back to the transaction that originated it. The result is a map of where and why the operation leaves the system. Without it, you fix things by gut feel.
2. Work out what is missing
It may be configuration: the system can do it, but it isn't tuned to the operation. It may be training: the system already does it and the team doesn't know where or how to verify it. Or it may be a report: the data exists, but not the view. That gets built on the system itself, or with Oracle APEX on the same data when the ERP can't do it natively, so the source remains a single one.
3. Fix by priority
First what touches the close, controls and what is delivered to leadership or the tax authority; then what saves daily time. One process at a time. Before retiring a parallel file, you run a close with both and compare the figures. When they match, it is retired explicitly: as long as it exists, it will remain the reference.
4. Know when to ask for help
Your internal team can handle it when the problem is limited to one or two processes and someone has the time and authority to decide. An assessment makes sense when the problem spans several departments or nobody can say with certainty what is missing. And a formal recovery makes sense when the cause is a deeper design or data issue, and the fix is already a project with a scope and a date.
To prevent a relapse, new needs have to have somewhere to go. Whoever doesn't find an answer opens another spreadsheet. That is ongoing support, and at CETERiS we offer it through CETERiS Care.
Where to start
This week, ask each department head for the list of files they use to close the month and reconcile. It is a one-line instruction and it is the start of the map. To see where your implementation stands, take the self-assessment at www.ceteris.mx/autodiagnostico-erp/.
If the map shows the problem runs deep, CETERiS has worked with Oracle since 2008, with Oracle Fusion Cloud ERP, Oracle NetSuite and Oracle E-Business Suite, and we offer assessments, ERP project recovery and ongoing support with CETERiS Care.
How we can help
Facing something similar?
Tell us which system you run and what it can't do for you today. The first conversation is about understanding your situation.
Request an assessment
Free guide · 24 pages · In Spanish
From Excel to ERP: how to tell if it's time
What we'd tell you in a first assessment meeting, in writing: how to know whether you need an ERP, what it costs in estimated ranges and how to migrate without disrupting operations. Currently available in Spanish; English edition coming soon.
- The 7 signs you've outgrown spreadsheets
- What an ERP costs and what drives the price
- The 5 most expensive mistakes
- A checklist to decide whether it's time