Every accounting software vendor in Saudi Arabia will tell you their system is ZATCA compliant. That is usually true, and it is also useless as a selection criterion, because compliance is now the floor that everyone clears. The question that actually separates these systems is a different one: what happens to your business twelve months after go-live?

We implement business systems, we do not sell accounting software. That means we see what happens after the sales demo ends: which systems grow with a company, and which turn into an obstacle you pay to escape two years later. What follows is the criteria we actually use.

First, separate a regulatory requirement from an operational one

The regulatory requirement is clear and bounded. The Zakat, Tax and Customs Authority (ZATCA) mandates e-invoicing for VAT-registered businesses in two phases: generation, then integration with the Fatoora platform. The second phase is the one that needs real attention, because it requires a direct technical connection to the platform, a cryptographic stamp, a unique identifier per invoice, a QR code, and a specific XML format.

Any product selling into the Saudi market today covers this. So do not make it your differentiator. Make it an entry condition: if it is missing, the vendor leaves the list, and that is the end of it.

The operational requirement is what decides the outcome. How many branches do you have? Do you sell wholesale and retail? Do you need stock tracked by batch or expiry date? Are your payroll figures tied to commission? These questions eliminate three quarters of the options.

The six criteria we apply

1. Does the system extend beyond accounting?

Most companies buy accounting software believing their problem is an accounting problem. Usually it is not. Invoices are late because the sales order never arrived. Stock figures are wrong because the warehouse records on paper. Collections are weak because nobody sees debtor ageing in real time.

Ask the vendor a direct question: if in a year I need inventory, or point of sale, or purchasing, or HR, do I add it inside this same system or buy a second one and integrate them? The answer changes your five-year cost more than any difference in monthly price.

2. True cost of ownership, not the subscription price

The advertised price is one part of four. Count:

  • Subscription or licence, multiplied by your realistic user count in two years, not today
  • Implementation and configuration, which frequently exceeds a full year of subscription
  • The cost of customisations specific to your business, and of reapplying them at every upgrade
  • The cost of leaving: can you export all your data in a usable format?

That last line is the one always forgotten, and it is the one that determines whether the decision is reversible.

3. Who implements it, and who is still there afterwards

The software rarely fails. The implementation fails. Ask for the delivery team by name, for comparable projects at your size and in your sector, and who answers the phone in month eight after the project closes.

A single vendor who sells, implements and supports looks convenient, but it also means your options narrow if the relationship sours. Separating the software from the implementer keeps an alternative open to you.

4. Arabic, properly

A translated interface is one thing. A system that works in Arabic is another. Check three specifics: does the invoice print in Arabic with correct right-to-left layout? Do fields carry Arabic customer names through into reports and exports? Are the financial reports themselves available in Arabic, or only the interface?

Ask for a real printed invoice and an exported financial report before you sign. That step reveals a great deal in five minutes.

5. Data: where it lives and who reaches it

Ask where your company data is stored geographically, what the backup policy is, and how long a restore takes. If your sector carries additional obligations for handling data, that is a question to ask before purchase rather than after.

6. Can you watch the system run on your own data?

A demo is always built on ideal data. Ask for a trial on a sample of your real data: your chart of accounts, a few of your customers, one sales cycle end to end. A confident vendor agrees. Hesitation here is signal enough.

When accounting software alone is the right answer

Not every company needs an integrated system. If your business is services, invoice volume is modest, there is no stock, and you run a single team, then simple cloud accounting software is the rational choice, and anything larger is complexity without return.

The dividing line usually appears at one of three points: real inventory arrives, a second branch opens, or selling has to connect to supply. At that point standalone accounting software starts generating manual work rather than saving it.

The practical step

Write down your operations first, before you watch a single demo. One page: where the order comes from, who approves it, how it becomes an invoice, where the goods leave from, and when the payment is recorded. Then put that page in front of every vendor and ask them to walk through how their system executes it.

That page separates these systems better than any feature comparison, because it measures the system against your business rather than against its own feature list.

If you want to talk through your operations before deciding, get in touch. We build systems around how a company works, not around one product we happen to sell.