Cloud ERP
ERP implementation challenges rarely come from the software alone. In the projects we see in Saudi Arabia, the delays usually trace back to decisions nobody made early enough. Which processes change, who owns the data, how opening balances will be proved, and who signs off that the system is ready all matter more than any single feature.
This article goes through the main challenges in ERP implementation in the order they tend to appear, from selection to the months after go-live, with a worked check of migrated opening balances and what each challenge needs from the finance team.
Challenges before the project starts

The first challenge is agreeing what the project is for. “Replace the old system” is not a goal. “Close the month in five working days”, “stop re-keying sales invoices into accounts” or “issue e-invoices from every branch” are goals that can be tested at the end. Without them, every department adds its own wish list and scope grows.
The second is selection. Comparing vendors on long feature lists tells you little. A better test is to give each shortlisted vendor three or four of your own scenarios, for example a purchase with landed cost, a project progress invoice with retention or a payroll run with GOSI deductions, and watch them done on screen. Guidance on choosing is in how to choose an ERP system in Saudi Arabia.
The third is sponsorship. An ERP project needs one senior person who can settle disagreements between departments within days, not weeks. When approvals wait for a monthly management meeting, the plan slips a month at a time.
Process design and scope control
Every company has habits built around its old system, such as spreadsheets that fill gaps, manual approvals by email and reports rebuilt in Excel each month. Implementation means deciding which of these become system steps, which disappear and which stay outside. Each decision should be written down with the department head’s agreement, because “we always did it this way” will be raised again during testing.
Scope then has to be defended. New requests during the project are normal. The discipline is to log each one, estimate its effect on time and cost, and decide whether it goes into the first phase or a later one. In our experience, much of the overrun on ERP budgets comes from scope added after the plan was set rather than from the original estimate.
Data migration and cleanup
Data is where finance teams spend the most effort. Master data, meaning customers, suppliers, items and the chart of accounts, needs cleaning before it moves. Duplicate customers under slightly different names, suppliers without VAT numbers, items with three units of measure and no conversion, and accounts that nobody has posted to in years are all common.
Open transactions follow, such as unpaid customer and supplier invoices, open purchase and sales orders, stock by warehouse with its cost and fixed assets with their accumulated depreciation. Each balance must agree with the closing figures in the old system. Decide early how much history to bring. Many companies migrate only balances and open items, and keep the old system available for reference, since VAT records must be kept for at least six years from the end of the tax period.
A worked check of migrated opening balances
The figures are hypothetical. A distributor migrates on 31 December and compares the legacy trial balance with the balances loaded into the new system.
| Account | Legacy trial balance (SAR) | Loaded in new ERP (SAR) | Difference (SAR) |
|---|---|---|---|
| Accounts receivable | 1,248,100.00 | 1,245,600.00 | 2,500.00 |
| Inventory | 2,310,000.00 | 2,296,400.00 | 13,600.00 |
| Accounts payable | 976,300.00 | 976,300.00 | 0.00 |
Receivables are loaded invoice by invoice, so the 2,500 difference means the legacy control account holds something the customer ledgers do not. In practice it is often an unapplied receipt or a manual journal posted straight to the control account. Inventory is loaded item by item with quantity and cost, and the 13,600 gap usually comes from items with negative stock or zero cost in the old system.
Both differences must be explained and corrected before go-live, not carried into the new system through a suspense account. The common mistake is to load the totals as one balancing journal so the trial balance agrees on day one, and then spend months trying to find which customer the difference belongs to.
Change management and training
People resist a new system when it adds work for them without explaining why. A storekeeper asked to scan every receipt, or a salesperson who can no longer change a price, will find workarounds unless they understand what the control protects. Training is more effective when it uses the company’s own items, customers and approval rules, and when each role practises the five or six tasks it does every day.
Key users in each department help most. They take part in design, test their own processes and become the first point of contact after go-live. Their time has to be released from daily work during the project, which is a cost many plans forget.
Testing, go-live and the months after
Testing should follow whole processes from start to finish, for example a request to purchase order, goods receipt, supplier invoice and payment, checking the accounting entries at each step. A parallel month-end close on test data shows whether reports, VAT figures and approvals work before real money depends on them. In Saudi Arabia, e-invoicing must also be tested, including onboarding each branch with ZATCA and issuing a credit note against a cleared invoice.
After go-live, expect a period of corrections, new reports and small changes in setup. Plan a review after the first quarter-end to check which processes are followed, which workarounds have appeared and what the second phase should include. Longer-term causes of failure are covered in ERP implementation failure reasons.
How Tranquil handles setup and migration
Tranquil ERP takes data in through Excel templates for items, opening stock, customers, suppliers, price lists, document-wise opening balances, the chart of accounts and assets. Each uploaded row shows whether it was accepted or failed, with a remark, which makes the opening balance check above easier to run. Approval steps are set per document type, and company settings switch features such as batch-wise stock, landed cost and cost centres on or off without custom code. For e-invoicing, each branch onboards with ZATCA in sandbox, simulation or production mode.
The steps of a rollout are covered in ERP implementation, and the accounting system page covers the finance side. If you want to see an opening balance upload and its error remarks, request a demo.
Frequently asked questions
What are the biggest challenges in ERP implementation?
Unclear goals, scope that keeps growing, poor-quality master data, opening balances that do not reconcile, resistance from users and too little time from key users. Most of them come from decisions and people rather than from the software itself.
How long does an ERP implementation take?
It depends on the number of modules, branches and integrations and on how clean the data is. A single-company rollout of finance, sales, purchasing and inventory takes months rather than weeks. Projects with manufacturing, projects and payroll take longer, and are often phased.
Should we migrate all historical transactions?
Usually not. Most companies migrate opening balances and open items, such as unpaid invoices, open orders and stock, and keep the old system available for reference. VAT records must be kept for at least six years, so plan how that history stays accessible.
How do we keep an ERP project within budget?
Set measurable goals, log every change request with its cost before approving it, release key users from part of their daily work, and keep a contingency for data cleanup and training. Review scope at each phase rather than adding items mid-phase.


