ERP Rescue Consultant, Oman

Signs an Omani ERP project needs outside help

Small and mid-sized Omani companies rarely have a dedicated ERP project manager. The role falls to the finance manager, an IT generalist or the owner, alongside everything else. When the project runs into trouble, the warning signs are easy to miss because the people who would notice them are already overloaded.

Signals worth acting on:

• The partner's status updates have become irregular, or every meeting starts with the same open issues.
• Your accountant is keeping the old system running in parallel with no end date.
• Migrated balances show small unexplained differences, often in baisa, that nobody has had time to chase.
• VAT reports from the new ERP are not yet trusted for filing.
• The WPS salary file or bank payment file still comes from the old tool.
• Users have stopped reporting problems because nothing seems to happen when they do.
• Change requests arrive for things your staff thought were in the original price.

Two or three of these together mean the project needs a reset, and that reset is hard to lead from inside a small team. An independent view can name the problems neutrally and take on the coordination needed to fix them. The general method appears on the ERP recovery page, and an initial outside view is described under independent ERP second opinion.

Triage without overloading a small finance team

The first risk in an Omani rescue is that the recovery itself adds more work to the people already stretched. So the triage is designed to take load off them. I do most of the evidence gathering from read-only access, exports and short, focused conversations, and I run the issue log myself so your staff do not have to.

Every open item is classified with the business owner:

• Blocks daily trading or filing: sales invoicing, purchasing, payments, VAT reporting or payroll cannot work correctly without it.
• Important but deferrable: it matters, but the business can operate safely while it waits for a later release.
• No longer needed: requested early in the project but overtaken by events or workarounds people prefer.
• Disputed: your team and the partner disagree on whether it was in scope.

The first group becomes the recovery's immediate focus, with a named owner on each side and a test that proves it is fixed. Everything else waits. This keeps the partner's effort on what actually unblocks the business and gives your team a short list they can follow, rather than a long issue log that nobody reads. Meetings are kept brief and scheduled away from the month-end close.

Reconciling migrated balances and rounding differences

Data migration can derail any rollout, and in Oman the rial's three decimals add a particular twist. Balances that were correct in the old system can arrive in the new one with small differences, because amounts were exported with two decimals, recalculated during import or summarized at a different level. Once those differences are in the opening position, every later reconciliation inherits them.

I reconcile the opening position area by area with your finance team:

• Trial balance by account against the old system at the cutover date.
• Open customer invoices and credits, with the aged listing agreed to the control account.
• Open supplier bills, agreed the same way.
• Bank balances and unreconciled items.
• Stock quantities and values by location, compared with the last count and the ledger.
• VAT control accounts at cutover, so the first return from the new system starts from a known point.

Each difference is explained and classified: a rounding or precision issue, a missing document, a duplicated record or a mapping error. Corrections are posted as documented adjustments approved by finance. Where the cause is a precision setting, I make sure it is fixed in the configuration as well, so new transactions stop creating fresh differences.

Keeping VAT returns and payroll on track during recovery

A rescue must never put a filing or a salary payment at risk. Before any redesign starts, I agree with your accountant how the next VAT return will be prepared and from which system, and which checks will confirm the figures. If the new ERP is not yet reliable for every area, a short documented procedure covers the gap, with an owner, a reviewer and a date by which it should no longer be needed.

Your tax advisor remains responsible for treatment and filing decisions. Where the recovery uncovers a past posting error that may affect earlier returns, it is reported to them with the evidence, and they decide what to do. My job is to make sure the ERP side is predictable and every adjustment is traceable.

Payroll gets the same care. I check that employee records, allowances and bank details are complete in whichever system will run the next salary, that the WPS file can be produced and checked before upload, and that the payroll journal posts correctly to the ledger. If e-invoicing obligations begin to apply to your business while the recovery is underway, the plan is adjusted with your advisor and vendor, so the rescue does not collide with a new requirement.

Partner, replacement partner or a different platform

Some Omani businesses are served by partners based in Oman, others by teams working from neighboring Gulf countries or further afield. Either can deliver well. In a rescue, the question is not where the partner sits but whether they can commit the right people to a revised plan.

If the current partner stays, I lead a reset: open items are agreed, acceptance tests are defined, people are named and a realistic timeline is set. If the relationship has ended, I help you secure administrator access, configuration notes, custom work, migration files and the issue history, and then support the choice of a replacement. Any notice or payment question is reviewed by your lawyer before it reaches the partner.

The larger question is whether the platform should stay. I compare three options in writing:

• Continue on the current scope once specific gaps are closed.
• Re-scope to a smaller stable core, such as finance, sales, purchasing and stock, with other modules later.
• Re-platform when the product cannot meet essential needs, including three-decimal accuracy and VAT reporting, without fragile workarounds.

Where the ERP is already running and the concern is how well it performs, an ERP audit in Oman is the better start. For steady oversight after recovery, see the Oman implementation consultant page or the Oman overview.