How to choose an ERP for your business in Saudi Arabia: criteria and questions
To choose an ERP in Saudi Arabia, start with what cannot be traded away: a real Arabic, right-to-left interface, ZATCA Phase 2 e-invoicing and the VAT return. Then measure the system against how your business works: branches and cost centers, point of sale, permissions and separation of duties, data ownership and backups, and support after go-live. The best fit is not the one with the most features but the one that runs your daily cycle with no workarounds outside it.
Why is choosing an ERP different in Saudi Arabia?
An ERP brings accounting, sales, purchasing, inventory and people onto one database, so each event is entered once and shows everywhere it matters. The idea is global, but the Saudi market adds requirements an imported system does not always carry: e-invoicing linked to ZATCA's Fatoora platform, 15% VAT with a periodic return, national address data, and Arabic that staff, managers and auditors read.
Many Saudi businesses also run several branches or parallel projects and need each branch's profit and each employee kept to their branch. A system that misses this pushes the business back to side spreadsheets, the very problem it bought the system to solve.
So before any demo, write your real cycle on one page: how you sell, who collects, how you buy and receive, who approves, and which reports management asks for each week. That page is the yardstick for every system, and it keeps you from being dazzled by features you do not need while missing a daily step the system does not cover.
Arabic and right-to-left: how do you really test it?
Many systems say they support Arabic, sometimes meaning a partial translation of menus over an interface designed for English. Test it yourself in the demo: does every screen run right to left, tables, reports and pop-ups included? Are the terms sound accounting Arabic a Saudi accountant understands, or literal translation? Do the printed invoice and the account statement come out in tidy Arabic?
Ask about search, too: does it find a name whatever the spelling of hamza or taa marbuta? Small in a demo, these details decide whether staff use the system with ease or work around it.
E-invoicing and VAT: what is the minimum?
Today's minimum is full ZATCA Phase 2: onboarding and certificates, clearing standard invoices and reporting simplified ones, credit and debit notes, and following up rejections. Do not settle for 'ZATCA compliant'; ask to see an invoice sent and the platform's answer.
The VAT return should come out of the system itself, from the invoices, notes and entries recorded there, not from a hand-filled sheet. Ask: does it read journal entries carrying VAT, imports and returns? Can it be shown for one branch to review before totalling?
Branches, cost centers and projects: does the system see your business as it is?
If you have branches or projects, the question is not 'does it support cost centers?', since every system says so, but: are cost centers enforced on documents so they are never left out? Are the warehouse, cash box and payment methods tied to the branch? Is an employee kept to their branch? Do the income statement and trial balance come out per branch at a click?
Telling the structure (a branch or project with cost centers under it) apart from an execution project (a customer contract with its own revenue and costs) matters for contracting and installation firms especially; a system that merges the two muddles the reports.
Point of sale and inventory: what to test at the counter itself
If you sell retail or run a restaurant, test the till in real conditions: speed on an average connection, barcodes and different units (piece, carton), prices that differ by branch, a return from an earlier invoice, credit sales for named customers only. Then test the end of the day: the cashier's closing, the blind count, matching cash and card, and the supervisor's approval.
On inventory, ask about transfers between warehouses, stock counts, item cost, low-stock alerts, and whether every stock move reaches the accounts as it is approved.
Permissions and separation of duties: who enters and who approves?
Internal control starts in the system. Ask to see how an employee is stopped from approving what they entered, how one screen is given to one person without changing their whole role, and how changes are logged by who and when. Ask whether a document can be sent back to its maker with a note, and whether entries are reviewed before posting.
Flexible need not mean complicated: best is ready roles (accountant, accounts manager, reviewer, cashier) tuned per person when needed.
Ask to see the audit trail too: if an item's price is changed or a document line removed, does it show who, when and the old value? External auditors and ZATCA may ask, and a system that keeps no trail leaves the business with no answer.
Data ownership, cloud, backups and support
Your accounting data is yours, so ask before signing: how do I take all my data out if I leave, and in what format? Is my database my own or shared with others? Systems built on open-source platforms reduce lock-in to one vendor because the data format is known.
In the cloud, ask about backups: how often, where kept, whether encrypted, for how long, and when a restore was last tried. Then support after go-live: who answers when the closing breaks on a Thursday evening, and do updates apply without breaking what was set up for you?
Ask about speed from your actual branch locations, not the vendor's office: a till that waits two seconds on each invoice builds a queue at peak hour. A good system keeps the cashier working while sales save in the background.
Questions to ask an ERP vendor
Use these questions in every demo and ask for the answer shown on screen, not described. Keep the answers in one table to compare vendors on the same footing:
Finally, ask for a trial on data close to yours and involve the cashier and the accountant, not only the manager; they are the ones who will live with it every day.
- Show me a standard invoice cleared by Fatoora, and a credit note on it.
- Show me the VAT return produced for one branch, then for the whole company.
- How do I keep an employee to their branch and stop them approving their own entries?
- Show me a till closing with a blind count, and a drawer shared by two cashiers.
- How do I export all my data? Where are backups kept and when was a restore tried?
- What does the subscription include, and what is billed apart: training, customisation, support?
- Are the interface, reports and prints all in Arabic and right to left?
How does Arkan meet these criteria?
Arkan is a cloud ERP built on ERPNext with Arabic as its first language: screens, reports and prints run right to left, in the accounting terms a Saudi accountant reads. It includes ZATCA Phase 2 e-invoicing and a VAT return read from the system's own data, which can be shown for one cost center or project.
In Arkan a company is laid out as projects with cost centers under them; each cost center has its warehouses, cash boxes and payment methods, and each user is kept to theirs. It has retail and restaurant tills with blind closings and shared drawers, permissions per person and per screen, a rule that whoever enters does not approve, and a review and posting cycle for entries. Each workspace has its own database, with nightly encrypted backups in cloud storage apart from the server.
Till sales save in the background, so the cashier never waits on the server, and a project's accounting head is told of each document made or approved on the project. Each company is given only the systems it needs, such as commissions, archive or review, so screens are not crowded with what goes unused.
Common questions
What is the difference between accounting software and an ERP?
Accounting software records entries and invoices. An ERP adds sales, purchasing, inventory, tills and people on one database, so the accounts come from the operations themselves instead of being entered twice.
Is a cloud system safe for my financial data?
It depends on the vendor, not the cloud itself. Ask about a separate database, encrypted backups, two-step sign-in for admins, and a change log.
Do I need an ERP if my business is small?
With stock, a second branch or a till, usually yes: linking sales, stock, accounts and e-invoicing saves daily work and errors. Start with only the modules you need.
How long does an ERP take to go live?
It depends on size and how ready your data is. What delays go-live most is cleaning the chart of accounts, items and customers, not configuring the system, so start there early.
What is the single most important question for a vendor?
'Show me on screen.' Any feature the vendor cannot show you in the demo should not weigh in your decision.