Skip to content

Contact Info

Saudi Arabia

Getting a Saudi ERP project back under control

When does a Saudi company need an ERP rescue consultant?

A Saudi company needs ERP rescue when the rollout is stuck, costing far more than planned, or live but disrupting invoicing and the books. I protect the ability to issue valid invoices first, then establish what was promised, built and still missing, agree a new plan with the partner or organize a handover, steady VAT and month-end with your accountant, and advise on keeping, narrowing or replacing the platform, all remotely.

Last reviewed by Vikas Saroj

In Saudi Arabia an ERP failure is felt quickly, because the system is tied to how invoices reach the tax authority. If documents are rejected, delayed or issued from the wrong place, customers query them, collections slow down and finance spends its days on corrections instead of the close.

I act as an independent rescue consultant for the buyer, working remotely with your leadership, finance and operations staff and with the implementation partner. I start by securing day-to-day invoicing and filing, then build a factual view of the project and a plan everyone can work to.

Because I am not selling software, configuration days or a replacement platform, I can recommend the least disruptive route back to a stable system, even when that route is less work for everyone, including me.

ERPNext desk showing the Profit and Loss Statement report with income, expense and net profit totals and a quarterly trend chart
  • Invoicing continuity first
  • Fact base on scope and delivery
  • Partner reset or orderly handover
  • VAT and close stabilization
  • Arabic retesting with your staff
  • Clear continue or change decision
What I Do

Recovery services for Saudi implementations

Each service can stand alone, but most rescues use several in sequence.

Invoicing Continuity Triage

An immediate review of invoices that failed, were flagged or were issued outside the new system, with your advisor and vendor agreeing how to correct them and how to issue new ones safely.

Project Fact Base

A documented comparison of the proposal, statement of work and change requests with what is configured and tested, so both sides argue from the same evidence.

Recovery Plan and Governance

A revised plan with named business owners, a risk and issue log reviewed every week, a gate for new requests and short status reports that tell leadership plainly what is off track.

Close and VAT Support

Working beside your accountant to get receivables, payables, bank and VAT accounts reconciled so the next return and the next management accounts can be produced with confidence.

Arabic Retest Cycle

Focused retesting of invoices, credit notes, statements and reports with Arabic-reading staff, using scripts I prepare and your own staff execute, repeated until every output is accepted.

Contract Fact Pack

A neutral summary of scope, deliverables, acceptance and change history prepared for your legal counsel, so any commercial discussion with the partner rests on facts.

How I Work

Three steps from disruption to stability

Contain

Protect invoicing, payroll and filing

01
Request an Assessment
  • Review failed invoice queue
  • Agree interim invoicing route
  • Confirm payroll can run
  • Fix critical posting errors

Diagnose

Find out what really happened

02
Discuss Your Project
  • Talk to each party alone
  • Read contract and change history
  • Test core processes end to end
  • Map gaps by business impact

Rebuild

Agree and run the way forward

03
Talk About Next Steps
  • Decide continue or change
  • Reset scope and acceptance
  • Retest with Arabic outputs
  • Exit hypercare on criteria

How Saudi ERP projects end up needing rescue

Saudi ERP projects share a pattern that makes them vulnerable. A deadline set by e-invoicing obligations fixes the go-live date before the scope is properly understood. Partners can be stretched around those deadlines, so senior consultants may be spread thin. Data from older local accounting packages turns out to be less clean than expected, and Arabic print templates and acceptance testing are squeezed into the final days.

The result can be a go-live that technically happened but left the business struggling:

  • Invoices sit in an error queue or are issued from a temporary tool while the ERP is fixed.
  • Branches or companies in the group are still on the old system with no firm date to move.
  • Receivables and customer balances do not agree with the old system after migration.
  • Payroll and end-of-service balances were moved in summary form and nobody can trace them.
  • The partner and your finance team disagree about what was in scope.

None of this is unusual or shameful. It is the predictable result of deadline-led delivery, and it can be recovered with a clear sequence. The general approach is described on the fixing a failed ERP implementation page; the rest of this page covers how it applies in Saudi Arabia.

Triage when invoices are rejected or delayed

When the system that issues tax invoices is unreliable, everything else waits. The first days of a Saudi rescue focus on one question: can the business keep invoicing customers correctly while the ERP is repaired?

I work through it with your finance lead, your tax advisor and the vendor or connector provider:

  • List every invoice that failed, was flagged or was issued outside the new system, with dates and amounts.
  • Group the failures by cause, such as missing customer VAT numbers, address fields, wrong invoice type or a connector error.
  • Fix master data causes first, because they are usually the fastest and affect the most documents.
  • Agree with your advisor and vendor how already-issued documents should be corrected, rather than improvising credit notes.
  • Put one person in charge of the error queue each day, with a simple log of what was resolved.

I do not interpret ZATCA rules or tell you which corrections are acceptable; those decisions belong to your advisor and the vendor. What I bring is order: a single list, clear owners and a daily rhythm, so the problem shrinks instead of growing. Once invoicing is steady, the wider diagnosis can begin without customers feeling the disruption.

Getting VAT filing and month-end back on track

After a difficult go-live, the next VAT return is the deadline that concentrates minds. Your accountant needs figures they can stand behind, and the new ERP may not be ready to produce them alone. Stabilizing the close is joint work between your finance team, your accountant and the partner, and I coordinate it remotely.

The steps follow the money:

  • Opening position: agree the trial balance, receivables, payables and bank balances loaded at cutover against the old system, and document every difference.
  • VAT accounts: reconcile output and input VAT for the periods already in the new system, separating configuration errors from one-off posting mistakes.
  • Interim procedures: where the ERP cannot yet do something correctly, write a short controlled procedure with an owner and a reviewer, and set a date to retire it once fixed.
  • Year-end awareness: if the financial year closes during the recovery, flag early what the auditor and zakat advisor will need and which reports must be ready.

Your accountant and tax advisor decide what is filed and how adjustments are treated. My role is to make the ERP side predictable, keep a clear record of every correction, and stop temporary workarounds from becoming permanent. The go-live support page describes the close checks in more detail.

Resetting with the partner or arranging a handover

Most Saudi rescues can be completed with the partner already engaged. They hold the configuration knowledge, and a new partner would need time to learn it. What usually has to change is the way the project is run: a revised scope, explicit acceptance criteria, named decision-makers on your side and a plan matched to the people the partner can actually assign.

I prepare a reset workshop with a shared list of open items, each tagged as essential for stable operations, deferrable, no longer needed or disputed. The partner sees the list before the session, so the conversation is about solutions rather than surprises. Disputed items are resolved from the signed scope and the operational impact.

If the relationship has broken down, the goal becomes an orderly handover. Before any notice is given, I help you secure:

  • Administrator access to the ERP, the e-invoicing connector and any hosting account.
  • Configuration documentation, custom code and integration credentials.
  • Migration files, mapping sheets and reconciliation workpapers.

Contracts in the Kingdom may exist in Arabic and English versions, and payment or termination terms can be complex. Your legal counsel reviews the contract and advises on notice and commercial steps; I supply the factual record of scope and delivery they need. For background on how partner proposals are compared, see the Saudi ERP selection page.

Deciding whether to continue, re-scope or move platform

With invoicing steady and the facts on the table, leadership can make the strategic call without panic. I set out the options against the same criteria: fit with essential Saudi requirements, quality of what has been built, partner capacity, cost of further disruption and the risk to invoicing during any change.

Continue fits when the platform handles your core processes and e-invoicing reliably and the problems are specific and fixable. Re-scope fits when the first release tried to cover too many companies, branches or modules at once; a smaller stable core goes first, and the rest follows in planned waves. Re-platform fits only when essential requirements cannot be met without fragile custom work, or when the product's e-invoicing approach cannot be made dependable for your volumes and invoice types.

Changing platform in Saudi Arabia carries extra weight, because a second cutover may mean repeating e-invoicing onboarding steps and migrating open documents again. That cost has to be justified by evidence, not frustration. When it is, the next step is a focused selection rather than a fresh open search. The underlying service is ERP recovery. If your system is live and working but underperforming, an ERP audit in Saudi Arabia is the lighter option. More context is on the Saudi Arabia overview.

Not sure where to start?

Tell me about your business and current systems. I’ll suggest the most sensible first step.

Book a Consultation
Related

Related Services

  • ERP Recovery
  • Fix Failed ERP Implementation
  • ERP Go-Live Support
  • ERP Testing & UAT
  • Independent ERP Second Opinion
  • Fractional ERP Lead
Saudi Arabia

More for Saudi Arabia Businesses

  • Saudi Arabia overview
  • ERP Consultant
  • Freelance ERP Consultant
  • ERP Business Analyst
  • ERP Requirements Consultant
  • ERP Selection Consultant
  • ERP Implementation Consultant
  • ERP Audit Consultant
  • CRM Consultant
  • System Integration Consultant
Other Markets

ERP Rescue Consultant Elsewhere

  • USA
  • UK
  • UAE
  • Qatar
  • Oman
  • Kuwait
  • Bahrain
  • Canada

Not sure which ERP you need?

Do not choose software first.

Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.

  • Independent ERP advice before you invest - I do not resell software
  • Work directly with Vikas - no account managers or junior handoffs
  • Business analysis before software implementation
  • One consultant who understands both your business and the technology
FAQ

Questions About ERP Rescue Saudi Arabia

I do not build or repair the connector myself. I organize the response: a single list of failed documents grouped by cause, owners for each fix and a daily review with your vendor or connector provider. Your tax advisor confirms how issued documents should be corrected. The structure is meant to shrink the backlog steadily rather than chase single errors.

Sometimes a temporary fallback is the safest option, but it has e-invoicing and data consequences that must be checked with your advisor and vendor first. I set out what a fallback would involve, how data would be brought back into the new ERP later and what it would cost in effort, so leadership can decide with full information.

If a change is the right decision, I help secure a clean handover, define the remaining scope and compare proposals from replacement partners. I do not take referral fees, so the choice is based on capacity and fit. Notice and termination steps are agreed with your legal counsel before anything is communicated.

The engagement runs in English. I write test scripts for invoices, credit notes, statements and key reports, including edge cases, and your Arabic-reading staff run them and record results. Failures go into the same issue log as everything else, with an owner and a retest date, until the outputs are accepted.

Still have questions? Let’s talk them through.

Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.

Book a Consultation
Vikas Saroj seated at a meeting table with a laptop and notebook
Working Model Remote · Worldwide
Email Address hello@vikassaroj.com
Book a Consultation

Let’s Discuss Your ERP Rescue Saudi Arabia Project

Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.

Chat on WhatsApp