ZATCA Phase 2 Accounting Software Comparison for KSA
Evaluating ZATCA-approved accounting systems in 2025? Here's the practical framework KSA accountants need — covering integration depth, Arabic support, implementation effort, and accountant handoff workflows that most comparison guides ignore.
By the SuperAccountant Editorial Team
ZATCA Phase 2 Accounting Software Comparison for KSA Accountants
Your client just asked which accounting system to migrate to before ZATCA's Phase 2 integration deadline hits their wave. You can find the approved-vendor list on zatca.gov.sa in under two minutes — but that list tells you nothing about which system will cause the least pain during onboarding, which one your team can actually operate, or what breaks at month-end close. This guide fills that gap.
What Phase 2 Actually Demands from Your Software
Phase 2 (Integration Phase) under the ZATCA E-Invoicing Implementing Regulations moves beyond the PDF-and-QR-code requirements of Phase 1. Under Article 53 of the ZATCA E-Invoicing Implementing Regulations, every taxpayer in scope must integrate their ERP or POS directly with the Fatoorah portal via API, transmitting cleared or reported e-invoices in real time (standard invoices) or within 24 hours (simplified invoices).
That means your software must:
- Generate UBL 2.1 XML — not a PDF equivalent. The XML must embed the cryptographic stamp (CSID) issued after ZATCA onboarding.
- Call the Clearance or Reporting API and handle rejection responses without dropping the transaction.
- Store compliant invoice archives for a minimum of six years per ZATCA regulations, with retrieval capability.
- Support Arabic mandatory fields — buyer/seller names, line-item descriptions, and the QR code all carry Arabic content requirements that many non-localised ERPs fumble.
If your current system can't do all four, a patch-and-pray middleware approach may clear the compliance checkbox but it will create reconciliation nightmares at VAT return time.
The Approved List vs. the Mu'tamad Reality
ZATCA's Fatoorah portal publishes a list of solutions that have passed conformance testing. Being on that list confirms the software can generate a compliant XML and receive a CSID. It does not confirm:
- How the integration behaves under high invoice volume (>10,000 invoices/day)
- Whether the Arabic chart of accounts is SOCPA-endorsed out of the box
- What version of the software passed testing (older builds are sometimes listed)
- Whether local support exists in KSA for implementation and hypercare
Cross-reference the vendor's listing date against their current product version. A system that passed conformance in 1444H on version 4.x is not automatically compliant if you deploy version 5.x without re-certification.
Decision Criteria That Actually Matter
Most comparison articles stop at "it's on the approved list." Here is the framework your evaluation committee should run every shortlisted vendor through:
| Criterion | What to Verify | Red Flag |
|---|---|---|
| API reliability | Uptime SLA for Fatoorah integration; error-handling logic for ZATCA timeouts | No documented retry/fallback mechanism |
| Arabic UI depth | Full AR interface, not just AR invoice templates | Menu navigation still in English only |
| SOCPA chart of accounts | Pre-built COA aligned with SOCPA-endorsed IFRS | Generic IFRS COA requiring manual localisation |
| VAT return auto-population | Box-by-box mapping to VAT return (Form VAT-01) | Manual export/import to file the return |
| Implementation timeline | Reference clients in your revenue/volume band | Quoted timeline under 4 weeks for mid-market |
| Accountant handoff workflow | Audit trail, journal entry lock dates, preparer-reviewer roles | Single-admin model, no role segregation |
| Zakat module | Zakat base calculation, notional capital adjustments | Zakat handled entirely outside the system |
| Upgrade cadence | How quickly ZATCA regulatory changes are patched | Patches require paid professional services |
The accountant handoff workflow criterion deserves special attention. When a client's finance team posts an entry and your firm reviews it, you need locked periods, clear preparer/reviewer segregation, and an immutable audit log. Systems that let any user amend posted transactions without a reversal trail will cost you hours of forensic reconciliation during fieldwork.
Implementation Effort: The Number Nobody Quotes Upfront
Vendors quote go-live timelines in weeks. The honest number includes:
- Data migration — opening balances, customer/vendor master, item master with HS codes for VAT classification
- ZATCA onboarding — generating the CSR, submitting to the Fatoorah portal, receiving and storing the CSID (allow 3–5 business days per ZATCA's published SLA)
- Parallel run — running the old and new system simultaneously for at least one full VAT period (one calendar month minimum)
- Staff training — accounts payable clerks operating the Arabic interface, not just the ERP consultant
A realistic mid-market implementation (SAR 50M–500M annual revenue, ~500 invoices/month) runs 10–16 weeks from contract signature to Phase 2 live. Any vendor quoting four weeks for that profile is either scoping discovery and data migration out of the timeline or has never done it in KSA.
For larger entities (>SAR 500M), budget six months and assign a dedicated internal project manager. The Mu'tamad ERP programmes that ZATCA references for large taxpayers carry additional configuration requirements that compress your testing window.
Arabic Support: The Differentiator Most Comparisons Skip
This is where locally-implemented systems consistently outperform globally-deployed cloud ERPs. Arabic support has three layers:
- Right-to-left (RTL) UI rendering — the entire interface, not just the invoice print template
- Arabic mandatory fields in XML — the UBL 2.1 schema requires Arabic seller name (
cac:PartyNamein Arabic), and ZATCA validation will reject invoices where the Arabic field is blank or populated with transliterated Latin characters - Arabic helpdesk and training materials — when your client's AP clerk calls support at 11pm on the 15th of the month because the batch upload is failing, English-only tier-1 support is a business risk
Test this during the demo: ask the vendor to navigate the full invoice-posting workflow in Arabic. If they switch to English to complete any step, that is a gap you will own post-go-live.
Connecting Software Choice to Your VAT and Zakat Workflows
Your software selection decision does not live in isolation. It directly affects:
VAT reconciliation — The system's VAT ledger must reconcile to the Fatoorah portal's reported invoice totals before you submit Form VAT-01. Any system that holds VAT in a single GL account without output/input split by tax code will require manual reclassification every period.
Zakat base computation — Under ZATCA/GAZT rules, Zakat is levied on the Saudi-resident shareholder's proportionate share of the Zakat base (equity plus certain additions, less specific deductions). A system with no Zakat module forces your team to export a trial balance into a separate spreadsheet model every year — workable, but error-prone when the trial balance structure changes post-migration.
Withholding tax (WHT) — Article 68 of the Income Tax Law imposes WHT on payments to non-residents. Your system needs to flag WHT-applicable vendor categories and generate the GAZT WHT return data automatically, not via manual lookup.
If you are currently assessing which skill gaps your team has around these workflows, the SuperAccountant quiz benchmarks your ZATCA and VAT knowledge against practising peers in KSA — worth running before you sit across the table from a vendor.
The Migration Decision: Greenfield vs. Upgrade vs. Middleware
Three paths exist for entities not yet Phase 2 compliant:
Greenfield ERP replacement — highest effort, lowest long-term technical debt. Justified when the existing system is more than eight years old, lacks Arabic support, or cannot expose an API layer. Budget 12–20 weeks.
ERP upgrade — if your current vendor is on the approved list and your version is behind, an in-place upgrade is often the fastest path. Confirm the upgraded version has been re-certified on the Fatoorah portal, not just that the vendor is listed.
Middleware/connector layer — a ZATCA-certified middleware sits between your existing ERP and the Fatoorah API, translating transactions into compliant UBL XML. Lower implementation risk, but you now have two systems to maintain, two SLAs to manage, and a reconciliation point between them. Suitable as a bridge for entities in ZATCA's near-term compliance waves who cannot complete a full migration in time.
The middleware route is not a permanent answer. Plan your full migration within 18–24 months or the technical debt compounds.
Evaluating Phase 2 systems is one of the highest-leverage decisions a KSA finance team will make this year. Get the criteria right, pressure-test the vendor demo against real workflows, and your post-go-live life will be measurably easier.
Sharpen your edge with SuperAccountant's next live cohort — small batches, real client workpapers, taught by partners. Details and seats at https://app.superaccountant.in/en/cohort?utm_source=blog&utm_medium=cta&utm_campaign=accountants.