Loading
Loading
Issue 03 · 2026
Many ERP programmes fail not because the platform is weak, but because the organization bought a system before deciding who owns the process, who closes the month, and which record is the single source. This report sets a practical maturity list and states what must be settled before a contract is signed.
Start the checkExecutive brief
01
A system does not fix ownership chaos. If no owner is named for each process before implementation, the system will reproduce the same spreadsheets in a prettier form.
02
Readiness is measured on twelve items. Data, period close, integration, and permissions matter more than a module catalogue.
03
If month-end close depends on one person and a private spreadsheet, the organization is not ready to go live.
04
Integration with payroll, social insurance, and inventory is an operating decision before it is a technical one.
05
Early customization freezes chaos inside code. Delay it until the standard process is stable.
06
A ninety-day path is enough to diagnose readiness: a systems inventory, process owners, and a first-phase scope.
07
Sometimes the right decision is a three-month delay to settle the chart of accounts and the purchase cycle.
08
After signing, programmes fail when scope changes weekly and no committee can say “this is out of phase one”.
01
Organizations buy an ERP looking for one system that ends the scatter of finance, inventory, projects, and human resources. That ambition is sound. The problem is that the purchase is usually made from a module demo, not from an operating diagnosis.
This report does not compare platforms and does not recommend a vendor. It asks an earlier question: is the organization ready for one system to live as the source of truth? If the answer is no, delay is cheaper than a second implementation.
Readiness is not management approval of a budget. Readiness is the ability to close a month with figures that finance and operations accept on the same day.
02
If three of these symptoms are stable, do not go live.
The month does not close unless one employee is present with a file nobody else can read. That is not efficiency. It is operating risk.
“Revenue” in sales is not “revenue” in finance. “Active employee” in HR is not what is filed on government platforms.
After every official system a parallel sheet remains “because the system does not understand our reality”. The parallel sheet is the real system.
Request, approval, receipt, invoice, payment: if these steps live in speech or WhatsApp, the system will turn chaos into mandatory fields that everyone hates.
03
Score each item simply: in place and working, on paper only, or absent. Do not dress the result. An organization that scores “on paper only” on more than four items is not ready for a full go-live.
| Item | The question that must be settled | A sign of readiness |
|---|---|---|
| Chart of accounts | Does the chart reflect the activity, or is it an imported copy? | A trial close of one month on the proposed chart. |
| Process owner | Who may change the sales or payment cycle? | One named owner per process, not a general committee. |
| Master data | Customers, suppliers, items, cost centres: where is the correct copy? | One agreed file before migration. |
| Month-end close | How many days after month-end until figures are approved? | A written close calendar known to finance and operations. |
| Permissions | Who approves, who executes, who reviews? | Segregation of duties on paper before system setup. |
| Inventory | Does the count match the records, or is it reconciled at year-end? | A trial count of a critical item before go-live. |
| Projects | Is a project a cost centre, a contract, or an initiative? | One definition used by finance and the project manager. |
| Human resources | Does the employee file feed payroll and government platforms from one source? | A sample match between HR and social insurance. |
| Integration | What stays outside the system in year one? | A signed exception list, not later promises. |
| Reporting | Which management report must come from the system in month one? | Three reports that will not be accepted from outside the system. |
| Internal support | Who answers the user after the implementer withdraws? | An internal system owner, even part-time. |
| Phase scope | What goes live on day one, and what is deferred? | A scope paper that blocks a mid-stream module add. |
04
Draw the cycle as it happens today, not as it should happen. Then ask: which step exists because the old system forced it, and which exists because the risk is real? The first is deleted. The second is fixed in the new system.
Do not start with customization. Start with one standard month: invoice, payment, journal, report. If the team cannot complete that path in a trial environment, the problem is not the screen.
05
In a Saudi organization an ERP does not live alone. Around it sit payroll, wage protection, social insurance, and customs or point of sale depending on the activity. The useful question is not “does the system connect?” but “who owns the figure if the two sources disagree?”
Owns the close, the chart, and statutory reporting. Management figures are not debated if finance will not approve them from the system.
Owns the employee file and employment status. Any link to government platforms starts from this file, not from a parallel sheet.
Owns quantities, dates, and project delivery. If operations do not enter data on time, finance will keep correcting at month-end.
06
The contract is signed, the celebration ends, and then three failure patterns repeat in the local market as they do elsewhere.
Every department discovers that “its chance” is now. Without a committee that can refuse, the programme becomes a rebuild of the whole organization in nine months.
Applied exampleAn HR module is added in week six because the original deck mentioned it on the last slide.
Migration reveals duplicate customer names and opening balances that do not tie. Go-live slips a week at a time.
The implementer leaves, and the user returns to Excel because nobody inside owns configuration decisions.
07
Three months are enough for an honest readiness report, not for a full implementation.
Inventory systems and files, interview process owners, and draw the close and purchase cycles as they are.
Score the twelve items, name the critical gaps, and propose what to fix before any purchase or what to include in phase one.
A written scope, an internal owner, and a decision: implement, delay with a cleanup plan, or a narrow phase (finance and inventory only, for example).
08
Delay is a mature management decision if the chart of accounts is being rebuilt, the organization is in a merger, or the nominated system owner will leave within a quarter. Buying the system at that moment locks a temporary disturbance into a long contract.
If the decision is to proceed, make phase one smaller than the demo. A narrow go-live that closes a month from the system is stronger than a wide platform used in fragments.
09
The report draws on established ERP implementation practice (lifecycle, scope control, segregation of duties, master-data quality) and on how Saudi organizations actually operate, where internal systems meet government platforms for payroll and insurance. It is a diagnostic frame, not a market study or a product comparison.
The report does not offer market-size figures and does not guarantee an implementation outcome. The final decision stays with the organization’s management after examining its own file, not after a general reading.
NIRROV works with organizations that want strategy, operations, and digital delivery to move as one system.