The honest answer: for most SMEs, the software matters less than the process around it. Clean books in a simple system beat a powerful ERP full of rubbish.
Choose on three questions: does it handle compliant e-invoicing natively, can your team actually run it daily, and will it still fit when you add a branch or a warehouse?
Upgrade triggers are concrete: inventory you can’t trust, more than one location, or invoicing volume your current tool fumbles. Until then, invest in process, not licences.
Start with the non-negotiable
In Saudi Arabia, one requirement outranks every feature comparison: the system has to handle ZATCA e-invoicing properly, in your wave, with the right invoice format, QR code, UUID, hash and reporting or clearance behaviour.
Ask vendors a direct question and expect a direct answer: is the solution compliant today, and can you show it working with a live ZATCA connection? "Compliance ready" and "on the roadmap" are not answers.
Everything else on your requirements list is worth less than this. A system that cannot issue a compliant invoice is not a candidate, however good the reporting looks.
Then Arabic, properly
Not a translated menu — Arabic on the documents your customers and ZATCA see. Bilingual invoices, correct right-to-left rendering, Arabic company and item names that do not break in the PDF.
Ask to see a real bilingual invoice generated by the system. Screenshots in a deck are not the same thing.
The questions that actually differentiate
Once compliance and Arabic are settled, the useful questions are boring.
Can it produce a VAT return that ties to the ledger without manual rework? Does it handle multi-currency if you import? Can it run project or job costing if you are a contractor? Does it support the specific approval flow you already use, or will you change your process to suit it?
And the one people skip: can you get your data out? A CSV export of the full transaction history, not a formatted report. Systems you cannot leave become expensive over time.
Cost is not the licence fee
Budget for implementation, chart of accounts design, data migration from your current system, training, and the first VAT cycle where two systems run in parallel.
For most SMEs the licence is a minority of first-year cost. A cheap system implemented badly costs more than a mid-priced one implemented properly, because you pay for the mistakes in cleanup and filings.
ERP versus accounting software
Accounting software records what happened. An ERP runs the operation — inventory, purchasing, projects, payroll, sales — and the accounting falls out of it.
If your pain is producing accounts, you need accounting software. If your pain is that stock, purchasing and invoicing live in different spreadsheets that disagree, no accounting package will fix that, and you are looking at an ERP conversation.
Be honest about which problem you have. Buying an ERP to solve a bookkeeping problem is a long and expensive way to get a trial balance.
Before you sign
Get a demo using your own data — your chart of accounts, your invoice format, your VAT scenarios. Generic demos always work. Ask who does the implementation and whether they have done it for a business your size in Saudi Arabia. Ask what support looks like during your first ZATCA filing.
Key points
- ZATCA e-invoicing compliance outranks every other feature
- Demand a live demonstration, not "compliance ready"
- Arabic must work on the documents, not just the menus
- Check you can export your full transaction history
- Licence fee is usually a minority of first-year cost
- An ERP does not fix a bookkeeping problem
Practical checklist
- Confirm live ZATCA compliance for your wave
- See a real bilingual invoice from the system
- Test that the VAT return ties to the ledger
- Confirm full data export in an open format
- Budget implementation, migration, training and parallel running
- Decide honestly between accounting software and an ERP
- Insist on a demo with your own chart of accounts



