Why ERP Selection Deserves a Method
An ERP system is not software you install and forget. Your company will live with it for years. Every riyal in and out passes through it, every invoice cleared by ZATCA leaves from it, and every payroll file uploaded to Mudad is built in it. A poor choice costs far more than the subscription: months of stalled implementation, frustrated staff, reports nobody trusts, and sometimes a second selection exercise two years later.
Yet many companies still choose on the strength of a polished demo, a friend's recommendation or the lowest line in a quick price comparison. This guide sets out a seven-step method used by careful buyers, with a weighted scorecard, a five-year cost model and the Saudi-specific requirements that should never be treated as optional.
Step 1: Document Your Requirements Before Meeting Vendors
If you walk into the first vendor meeting without written requirements, the vendor will write them for you, and you will end up comparing systems on criteria that suit the vendor rather than your business. Form a small selection team with someone from finance, sales, inventory and HR: people who touch the data every day.
Questions the team should answer
- Core processes: which cycles must the system cover? Quote to cash, procure to pay, inventory, payroll, projects, manufacturing.
- Current pain points: what exactly are you trying to fix? Note each problem with a rough impact in hours or riyals.
- Size and growth: how many users today and in three years? How many branches, warehouses and legal entities?
- Integrations: banks, e-commerce, POS, attendance devices, government platforms.
- History: how many years of data will you migrate, and how clean is it?
Map the process before you buy software for it
Spend one session on each core cycle and map it as it really runs, not as the policy manual says it should. In procurement, for example: who requests, who approves, how suppliers are chosen, who receives the goods, and how the invoice is matched to the PO and the receipt before payment. You will almost always find duplicated steps and approvals nobody can explain. Some of these problems are fixed by changing the procedure, not by buying a system. The new ERP should be configured around the improved process, not used to automate the current mess.
The maps pay off twice: once when you write demo scripts for vendors, and again during implementation, because the partner starts from a clear document instead of discovering your operation from scratch.
Classify every requirement
Sort requirements into must have (a system without it is out), should have (affects the score) and nice to have (a tie-breaker). This list is your main tool for everything that follows, and it protects you from falling for an attractive feature you do not need.
Step 2: The Saudi Non-Negotiables
E-invoicing Phase 2
Phase 2 (integration) has been rolled out in waves since 1 January 2023. Standard tax invoices (B2B and B2G) are cleared by ZATCA in real time before they reach the buyer; simplified (B2C) invoices are reported within 24 hours. Ask the vendor to walk you through onboarding: each invoicing unit (EGS) generates a key pair and CSR, an OTP is generated in the Fatoora portal, a compliance CSID is issued for testing, and after passing compliance checks a production CSID is used for live invoices. Each invoice carries the previous invoice's hash and a per-unit counter. A vendor who cannot explain this plainly has probably not done it many times.
There is no officially announced "Phase 3". If a vendor markets Phase 3 compliance, ask for the official reference.
VAT in all its forms
The standard rate is 15%, but the system must also handle zero-rated, exempt and out-of-scope supplies, credit and debit notes, and advance payments, which become taxable when received. VAT return data, monthly or quarterly, should come straight out of the ledger.
Arabic and the Hijri calendar
Test the interface, reports, invoices and search in Arabic yourself. Superficial translation shows up as a report with the wrong text direction or a field that rejects Arabic names. If contracts or payroll reference Hijri dates, check dual-calendar support.
Payroll and labour compliance
GOSI contributions for Saudis under the legacy system and for new entrants from 3 July 2024; the WPS file, due within 30 days since March 2025; end-of-service awards under Articles 84 and 85 of the Labour Law; and leave rules as amended in February 2025.
Data protection and hosting
The PDPL has been in force since September 2023 and allows cross-border transfers only under conditions and safeguards. If you hold government data through public-sector contracts, the cloud computing framework does not allow it to leave the Kingdom. Ask where your data will be hosted, which security controls apply and how incidents are reported.
Step 3: A Weighted Scorecard
Impression-based comparisons tend to favour whoever gave the best presentation. A weighted scorecard turns impressions into numbers the team can argue about. These weights are a starting point; adjust them to your priorities.
| Criterion | Suggested weight | How to measure it |
|---|---|---|
| Saudi compliance | 25% | Live demo of a cleared invoice, a VAT return and a WPS file |
| Functional fit | 25% | Share of must-have and should-have items covered without custom development |
| Usability | 15% | Your own staff complete real tasks in a trial session |
| Local support and implementation | 15% | Local team, support language, written response times |
| Five-year total cost | 10% | All cost lines, not just the subscription |
| Scalability | 10% | Adding a branch, entity, module or users |
A hypothetical scoring example
Suppose a distributor scores three shortlisted systems from 1 to 5:
| Criterion (weight) | System A | System B | System C |
|---|---|---|---|
| Compliance (25%) | 5 | 3 | 4 |
| Functional fit (25%) | 4 | 5 | 4 |
| Usability (15%) | 4 | 2 | 5 |
| Local support (15%) | 4 | 2 | 3 |
| Cost (10%) | 3 | 2 | 5 |
| Scalability (10%) | 4 | 5 | 3 |
| Weighted score | 4.15 | 3.30 | 4.00 |
System B has the broadest functionality but loses on support and usability. A and C are close, which is exactly when a hands-on trial decides. The real value of the scorecard is not the final number; it forces the team to justify every score.
Step 4: Scripted Demos, Then a Real Trial
A generic demo shows the system at its best with prepared data. Instead, send each vendor a written script a week ahead, for example:
- A customer asks for a quote on three items, one of which is short on stock.
- The quote becomes a sales order, then a partial delivery, then a ZATCA-cleared invoice.
- The customer returns part of the goods; a credit note is issued.
- A partial bank transfer arrives and is matched.
- Show customer profitability after all of the above.
After the demo, ask for a short trial on your own data with three to five real users. What your accountant and storekeeper say after a week of use is more reliable than any presentation.
Reference calls that actually tell you something
Vendors naturally offer their happiest customers as references, so ask pointed questions rather than "are you satisfied?":
- How long did implementation take compared with the original plan, and why?
- What was the first serious issue after go-live, and how long did it take to resolve?
- What do you wish you had known before signing?
- Do you still use Excel alongside the system, and for what?
- How did the vendor handle the latest e-invoicing changes?
The fourth question is the revealing one. If core reports are still built in Excel a year after go-live, either the system does not fit or the implementation was never finished.
Step 5: Model Five-Year Total Cost
The subscription is only the visible part. Here is a hypothetical model for 30 users; the figures are illustrative and are not any vendor's prices.
| Cost line (SAR) | Year 1 | Years 2 to 5 | Total |
|---|---|---|---|
| Subscription | 120,000 | 480,000 | 600,000 |
| Configuration and customisation | 90,000 | 40,000 | 130,000 |
| Data migration | 30,000 | 0 | 30,000 |
| Training | 25,000 | 20,000 | 45,000 |
| Internal team time during rollout | 60,000 | 0 | 60,000 |
| Integrations and extra reports | 20,000 | 30,000 | 50,000 |
| Total | 345,000 | 570,000 | 915,000 |
The subscription is about two thirds of the total; the rest is what buyers forget. Ask every vendor about renewal price increases, since a small annual uplift compounds over five years. Our guide to total cost of ownership goes deeper.
Check your own data readiness
Before comparing migration plans, look at your data. Duplicate items under different names, customers without VAT numbers, suppliers inactive for years, opening balances that do not reconcile. A company with 6,000 items may find that 1,500 are duplicates or obsolete. Cleaning that is internal work no vendor can do for you, so give it time and an owner in your plan.
Step 6: Evaluate the Implementation Partner
A strong system implemented badly produces a bad experience; a good system implemented by an experienced team can produce an excellent one. Ask about:
- Sector experience: how many projects in a business like yours, with customers you can call?
- The actual team: who will work on your project, and what have they done? Senior names on the proposal are not enough.
- Method: defined phases with measurable outputs and checkpoints before moving on.
- After go-live: a written SLA with response times by severity.
For a fuller list, see our article on questions to ask before an ERP implementation.
Step 7: Read the Contract
- Scope: modules, integrations and reports listed by name, not in general terms.
- Data ownership and exit: your right to export all data in a usable format at the end of the contract, and how long you have to do it.
- Pricing: the price of additional users or modules and a cap on renewal increases.
- Service levels: availability, response and resolution times, and remedies if they are missed.
- Regulatory updates: are e-invoicing and tax changes included in the subscription?
A Suggested Selection Timeline
| Weeks | Activity | Output |
|---|---|---|
| 1 to 2 | Process mapping and requirements | Classified requirements list |
| 3 | Market scan and request for information | Long list of five to seven systems |
| 4 to 5 | Check responses against must-haves | Shortlist of three |
| 6 | Scripted demos | First-pass scorecard |
| 7 to 8 | Trial on real data and reference calls | Final scorecard and recommendation |
| 9 to 10 | Negotiation and contract review | Signed contract and outline plan |
Record each stage decision in writing. It stops a system that was eliminated for clear reasons from reappearing in the last week because of a tempting discount.
Test Industry Depth
| Sector | What you should see in the trial |
|---|---|
| Manufacturing | Multi-level BOM, material planning, production scheduling, quality checks |
| Trading and distribution | Multiple units of measure, customer-specific pricing, multi-warehouse stock |
| Contracting | Project budgets, progress billing, work in progress, site materials |
| Retail | POS connected to inventory and accounting in real time |
| Real estate | Units, tenants, contracts and collections |
If you are still working out the basic categories of ERP, start with our overview of different types of ERP systems.
Common Selection Mistakes
- Buying on price: the cheapest subscription can be the most expensive five-year cost.
- Leaving users out: a decision made only by management usually meets resistance on the floor.
- Skipping the trial: two weeks of real testing is cheaper than a year with the wrong system.
- Going live with everything at once: phased rollout lowers risk and lets the team learn.
- No success measures: agree before signing how you will judge the project, such as close time or stock accuracy. Our article on ERP implementation KPIs has examples.
Where Tranquil Fits
Tranquil is a cloud ERP covering financial accounting; ZATCA e-invoicing for Phase 1 and Phase 2 with real-time integration, deadline alerts and automatic validation; inventory; sales and distribution; purchasing; HR and payroll with Muqeem integration and direct bank salary transfer; projects; contracting; asset and property management; and POS. Customisation of screens, reports, multi-level approvals and API integrations is available, along with certified training and 30 days of post-training support. Review Tranquil's solutions against your own scorecard.
Frequently Asked Questions
How long should a structured ERP selection take?
For a mid-sized company, six to ten weeks from requirements to signature is typical. Rushing this stage saves weeks and costs months later.
How many systems should we compare?
Start with five to seven, cut to three against your must-haves, and run scripted demos and trials only on those three.
Is cloud always better than on-premise?
Not always. Cloud suits most SMEs because of lower upfront cost and easier updates, while organisations with special requirements or government data may need specific hosting arrangements.
What should we ask about e-invoicing specifically?
Ask for a live standard invoice cleared by ZATCA, a reported simplified invoice and a credit note, and ask how invoicing units are onboarded and production CSIDs obtained.
How do we start with Tranquil?
Send your requirements list to receive a quote within 24 hours and a demo built around your scenarios. You can contact the Tranquil team directly.