Outsource bookkeeping

Accounting Software in Saudi Arabia: A ZATCA-Ready Selection Checklist and Scorecard

By ·

Team applauding a colleague who presents colourful bar charts on a wall screen, illustrating a review of accounting software reports

Accounting Software in Saudi Arabia: A ZATCA-Ready Selection Checklist and Scorecard

Choosing accounting software in Saudi Arabia is no longer only a question of features and price. Every VAT-registered business must issue compliant electronic invoices, and once a business enters Phase 2 of ZATCA's e-invoicing programme, its system has to connect directly to the Fatoora platform. A tool that looks attractive in a demo can still leave you with rejected invoices, VAT returns built by hand in spreadsheets, or data you cannot easily move later.

This article is a vendor-neutral selection guide for owners and finance leads who are buying their first system or replacing one that no longer fits. It sets out what a ZATCA compliant accounting software must do, the wider criteria that matter in daily use, a weighted scorecard you can fill in, and a 60-day selection and migration plan. If you want background on how cloud systems work first, read our explainer on cloud accounting and financial software for Saudi businesses; for help with the decision itself, see our accounting software services in Saudi Arabia.

Table of Contents

Start with ZATCA e-invoicing Phase 2 software requirements

E-invoicing is the one area where a weak choice creates a direct compliance problem, so test it first. ZATCA's E-Invoicing Detailed Guidelines describe what a compliant solution must do and what it must not do. ZATCA rolls Phase 2 (integration) out in waves by taxpayer group and states that it notifies taxpayers of their wave at least six months in advance; the ZATCA roll-out phases page is the place to confirm where your business stands. In plain terms, ask every vendor to show you, not just tell you, how their system handles the following:

  • Generation. Standard tax invoices (usually B2B) and simplified tax invoices (usually B2C), plus credit and debit notes, produced as XML or as PDF/A-3 with the XML embedded.
  • Clearance and reporting. Standard tax invoices are sent to Fatoora for clearance before they go to the buyer. Simplified invoices are given to the customer and reported to Fatoora in XML within 24 hours of generation.
  • QR code and cryptographic stamp. Phase 2 simplified invoices carry a compliant QR code, and documents are stamped using a Cryptographic Stamp Identifier (CSID) issued by ZATCA.
  • Onboarding. Each invoicing unit is registered through the Fatoora portal, which is also where onboarded solutions can be viewed and renewed or revoked. Ask how the vendor handles onboarding for several branches, sales channels or point-of-sale devices.
  • Anti-tampering controls. No reset of the invoice counter, no user access to the system date, no deletion or editing of issued invoices (corrections go through a credit note and a new invoice), unique logins with no default passwords, tamper-proof activity logs, and a stamping key that cannot be exported.
  • Arabic output. The human-readable invoice must be in Arabic, and other languages may appear alongside it.

A clean answer to each point is the minimum. Ask also how the vendor reports a rejected invoice to your team and how quickly that can be fixed and resubmitted. For the regulatory background, see our FATOORAH Phase 2 compliance guide.

VAT return reporting and records

A VAT report accounting system should produce the return from posted transactions, not from a separate spreadsheet. ZATCA's guideline on imports and exports under VAT confirms that the return is the taxpayer's self-assessment for each monthly or quarterly period, that monthly filing applies above SAR 40,000,000 in annual revenue, and that the return and payment are due by the last day of the month after the period ends. When you test a system, check that it can:

  • Map each tax code to the return. Standard-rated, zero-rated, exempt and out-of-scope sales and purchases, exports, imports and services received under the reverse charge mechanism should each land in the right return field without manual reclassification.
  • Handle VAT on imports. Businesses approved to account for import VAT through the return need the system to treat it differently from VAT paid at customs.
  • Drill down. Every return figure should trace back to the invoices behind it, which saves time when ZATCA asks questions.
  • Support record retention. The same guideline sets a basic retention period of 6 years, extended to 11 years for records on movable capital assets and 15 years for non-movable capital assets. Confirm the system, or your archive, can keep and export records for that long.

Core accounting criteria beyond compliance

Compliance gets a system onto the shortlist. Daily usability decides whether your team keeps it. Score each product on:

  • Arabic and English. Bilingual invoices are the baseline; check whether reports, the chart of accounts, customer names and the user interface work in both languages, and whether Arabic text prints and exports correctly.
  • Chart of accounts and multi-entity. Can you build a chart of accounts that fits your auditors and Zakat or tax filings? If you run several companies or branches, check intercompany entries, consolidation and separate VAT numbers.
  • User roles and audit trail. Separate rights for entering, approving and posting. A full audit trail of who changed what supports both ZATCA's logging rules and your own internal controls.
  • Bank integration. Bank statement import or feeds and reconciliation rules reduce month-end effort. Ask which Saudi banks are supported and in what format.
  • Payroll and WPS. If payroll runs in the same system, check that it can produce the salary file your wage protection process needs and post payroll journals by cost centre. Our guide on Qiwa, GOSI and wage protection explains the employer side.
  • E-commerce and point of sale. If you sell online or in stores, confirm the integration posts sales, fees and refunds as compliant simplified invoices, not just summary totals.

Data hosting, PDPL, backups and support

Where your data lives matters for two different rule sets. ZATCA's e-invoicing guideline allows invoices to be stored on premises in the Kingdom or in the cloud in line with VAT rules, provided cloud data is accessible to ZATCA through a direct link, and notes that other regulations, such as National Cybersecurity Authority requirements, may also apply. Separately, customer and employee records are personal data. SDAIA's laws and regulations page publishes the Personal Data Protection Law (PDPL), its Implementing Regulation and a Regulation on Personal Data Transfer Outside the Kingdom, with supporting guidance on transfer risk assessments and breach incidents. Ask each vendor:

  • Which country and data centre host your data, and can you choose a Saudi region?
  • Do support staff outside the Kingdom have access to your records, and under what contract terms?
  • How often are backups taken, where are they kept, and how fast can a restore be completed?
  • Can you export all data, including e-invoice XML files, in a usable format if you leave?
  • Is support available during Saudi working hours, in Arabic and English, and what response times are written into the contract?

Our article on PDPL compliance covers the data protection side in more detail.

Cloud accounting vs ERP vs local products

Most options in the market fall into three broad categories. None is right for every business, and the categories overlap.

  • Cloud accounting tools. Subscription software focused on invoicing, purchases, banking and reporting. Generally quick to start and suited to service businesses and smaller traders. Check how far they go on inventory, multi-entity and approval workflows.
  • ERP modules. Accounting as one part of a wider system covering sales, purchasing, inventory, manufacturing, HR and projects. Suited to businesses whose operations need to feed accounting automatically. Implementation takes more planning. Odoo is one example; our Odoo ERP guide for Saudi businesses and Odoo ZATCA e-invoicing integration guide explain how it approaches Saudi requirements.
  • Locally developed products. Software built for the Saudi market, often with strong Arabic support and local implementation teams. Check reporting depth and integrations.

The question to answer is not which category is best, but which one covers your next three to five years of growth without forcing another migration.

A weighted scorecard for accounting software in Saudi Arabia

Give each criterion a weight that reflects your business, score each product from 1 (poor) to 5 (strong) after a scripted demo, then multiply. The weights below are an illustration only; adjust them so they total 100.

CriterionExample weightProduct A score (1-5)Product B score (1-5)Product C score (1-5)
ZATCA Phase 2 e-invoicing (generation, clearance, reporting, QR, onboarding)20
VAT return mapping and drill-down12
Arabic and English across invoices, reports and interface8
Chart of accounts, multi-entity and consolidation8
User roles, approvals and audit trail8
Bank, payroll and WPS integration8
E-commerce and point-of-sale integration6
Data hosting, PDPL and exit/export options10
Backups, security and support in Saudi hours8
Total cost of ownership over 3-5 years12
Weighted total (weight × score)100

For total cost of ownership, add licences or subscriptions per user, implementation, data migration, integrations, training, e-invoicing onboarding effort, annual support and the internal staff time needed to run the system.

A 60-day selection and migration plan, and mistakes to avoid

A realistic plan for a small or mid-sized business, assuming a decision-maker and finance lead who can commit time each week:

  • Days 1-10: requirements. List entities, branches, invoice volumes, sales channels and integrations. Confirm your e-invoicing status with ZATCA. Agree the scorecard weights.
  • Days 11-25: shortlist and demos. Run scripted demos with your own sample transactions: a B2B invoice, a B2C sale, a credit note, an import and a reverse charge service. Score each product and check references.
  • Days 26-40: data cleanup and setup. Clean customer and supplier master data (VAT numbers, national addresses, Arabic names), close open items, finalise the chart of accounts and configure taxes. Onboard e-invoicing in the vendor's test or simulation environment first.
  • Days 41-55: parallel run. Process a sample of real transactions in both systems and compare invoices, VAT and trial balances. Train users on their roles.
  • Days 56-60: cut-over at period end. Switch at the start of a VAT period or month, load closing balances, move to production onboarding and lock the old system for read-only access and archive.

Typical mistakes

  • Choosing on price before testing clearance and reporting with real invoices.
  • Migrating dirty master data, which turns into rejected invoices.
  • Cutting over mid-period, which splits a VAT return across two systems.
  • Forgetting the archive: old invoices and records must stay accessible for the full retention period.
  • No exit plan: not checking that data and e-invoice XML can be exported.

Rules on e-invoicing, VAT and data protection can change, so confirm the current requirements with ZATCA, SDAIA or a qualified adviser before you sign. If you prefer to hand over the day-to-day work after go-live, our accounting management services and guide to outsourced bookkeeping for startups and SMEs explain how that can work.

Frequently Asked Questions

What makes accounting software ZATCA compliant?

For Phase 2, the software must generate tax and simplified invoices and notes in the required XML or PDF/A-3 format, clear standard tax invoices with Fatoora before they reach the buyer, report simplified invoices within 24 hours, add the QR code and cryptographic stamp, be onboarded through the Fatoora portal, and block prohibited functions such as editing issued invoices, resetting counters or changing the system date.

Is cloud accounting software allowed for e-invoicing in Saudi Arabia?

Yes. ZATCA's e-invoicing guidelines allow invoices to be stored on premises in the Kingdom or in the cloud in line with VAT rules, provided cloud-hosted data can be made available to ZATCA through a direct link. Other rules may still apply, including cybersecurity requirements and the PDPL for personal data, so check where the vendor hosts data and who can access it.

Should a small business choose cloud accounting or an ERP?

It depends on operations, not size alone. A trading or service business with simple processes is often well served by a cloud accounting tool. A business with inventory, manufacturing, several branches or projects may benefit from an ERP where operations post to accounting automatically. Score both types against the same weighted criteria and include three to five years of total cost of ownership.

When is the best time to switch accounting systems?

Switch at the start of a VAT period or financial month, ideally after a parallel run. This keeps each VAT return within one system, makes opening balances easier to verify and reduces the risk of duplicated or missing invoices. Keep the old system or its exported records accessible for the VAT retention period.

Need help choosing or migrating to ZATCA-ready accounting software? Contact Sokrab Saudi Arabia today.

Category

Latest articles

Get in Touch

Book a Meeting

WhatsApp

Book a Meeting