ZATCA Compliant Workshop Software: What Phase 2 Actually Requires (and a 4-Vendor Comparison)

Most ZATCA compliant workshop software in Saudi Arabia falls into one of two categories: Phase 1-only tools dressed in compliance language, or enterprise ERP systems built for retailers rather than auto repair workshops. The difference is not cosmetic. Phase 1 software generates a locally compliant invoice — but it has no live connection to the Fatoora portal, which means every invoice it produces fails Phase 2 requirements. This article defines four technical criteria that separate genuine Phase 2 compliance from Phase 1-only claims, then applies those criteria to four software options marketed to Saudi workshops — so you can evaluate any vendor before you sign. For readers arriving from broader software research, see our guide to garage management software Saudi Arabia.

What Does ZATCA Phase 2 Compliance Actually Require?

Phase 1 (Generation) vs Phase 2 (Integration) — The Critical Distinction

Phase 1 — the Generation Phase — requires your software to produce invoices in UBL 2.1 XML format with a QR code. The invoice is generated and stored locally. ZATCA never receives it automatically. Phase 2 — the Integration Phase — is a different compliance regime entirely: your software must connect to the Fatoora portal via API. Standard B2B invoices are submitted to ZATCA for clearance before the customer receives any copy. Simplified B2C invoices are reported to the portal within 24 hours of issuance. The majority of software sold to Saudi small businesses and workshops as "ZATCA compliant" is Phase 1 only. For a full technical breakdown, see our ZATCA Phase 2 compliance guide.

The Four Non-Negotiables for Phase 2

A genuine Phase 2 ZATCA e-invoicing system must deliver all four of the following — not three, not a partial combination depending on configuration:

• UBL 2.1 XML format — not a PDF with a QR code attached
• Cryptographic stamp (CSID) — a digital signature applied to each invoice before submission, device-specific and issued via the Fatoora portal
• QR code to ZATCA TLV specification — embedded on both digital and printed invoice copies, structurally different from Phase 1 QR codes
• Active Fatoora API connection — real-time clearance for standard B2B invoices; automated 24-hour reporting for simplified B2C invoices

Workshop Invoices Have Two ZATCA Paths — and Most Software Only Covers One

ZATCA compliant workshop software must handle two distinct invoice types, because a Saudi auto workshop serves two distinct customer categories. Most generic POS and accounting software defaults to one — and picks the wrong one for half your transactions.

Standard Invoices — Fleet Accounts and B2B Customers

A ZATCA standard invoice is triggered when the customer is VAT-registered: a fleet company, government department, rental agency, or any commercial buyer. The invoice must carry the customer's VAT registration number. Under Phase 2, the invoice must be submitted to the Fatoora portal and cleared before it is issued to the customer. ZATCA reviews it in real time. An invoice issued without this clearance is not a legally valid tax document — your fleet customer cannot claim input VAT on it, making your workshop commercially unattractive to every corporate account you serve.

Simplified Invoices — Walk-In B2C Customers

A ZATCA simplified invoice is triggered when the customer is an individual — a walk-in car owner with no VAT registration. This covers the majority of transactions in most auto workshops. Simplified invoices must carry a ZATCA-specification QR code and are reported to the Fatoora portal within 24 hours of issuance, not cleared before issue. If your software applies standard invoice logic to B2C customers, the XML structure is wrong for simplified invoices and the submission will fail Fatoora validation.

The Parts and Labour VAT Split — the Hidden Compliance Risk in Workshop Billing

Workshop invoices combine two economically distinct categories: physical goods (spare parts, tyres, oil) and services (labour hours, diagnostic fees, alignment checks). ZATCA requires each to appear as a separate line item in the UBL 2.1 XML schema. Both categories attract 15% VAT in Saudi Arabia — but they must be individually itemised in the schema. They cannot be merged into a single "repair job" total, however convenient that may be for your workflow.

If your software produces a single combined line for parts and labour, the XML fails Fatoora portal validation. The invoice is rejected, the job is held, and resubmission requires correcting the underlying data record — not simply resending the file. Generic accounting and POS software built for retail almost always fails this test. Retail invoices sell individual SKUs; there is no concept of "labour" as a separate billable category in a retail schema. Workshop management software that natively tracks parts inventory separately from labour time is structurally positioned to produce correct UBL 2.1 XML from the start.

4 Criteria to Evaluate Any ZATCA Compliance Claim

Before you sign with any software vendor, apply these four criteria to their compliance claim. Each one maps to a specific Phase 2 requirement that determines whether your invoices are legally valid under the current ZATCA framework:

1. Phase 2 certified, not Phase 1 only. Ask the vendor for their ZATCA Phase 2 certification reference. ZATCA certified workshop software must show a Phase 2 integration certificate — Phase 1 approval is a lower-level accreditation and does not meet the current standard. Verify against the ZATCA Solution Providers Directory at zatca.gov.sa if unsure.
2. Fatoora API integration, not manual upload. Phase 2 requires automated API connectivity. Manual portal uploads are not Phase 2 compliant for a workshop processing more than a handful of invoices daily. Ask specifically whether the software connects to the Fatoora API automatically — or whether you must manually export and upload files.
3. Both standard and simplified invoice types supported. A workshop billing both fleet accounts and walk-in customers must handle both Fatoora submission paths. Confirm the software switches automatically based on whether a customer VAT number is entered — not a manual mode setting you must remember to change per transaction.
4. Parts and labour as separate UBL 2.1 line items. Ask the vendor for a sample XML output from the software. Parts and labour must appear on separate lines, each with an individual VAT amount. If the vendor cannot produce a sample XML, treat the compliance claim as unverified.

For the full implementation requirements, see our ZATCA e-invoicing requirements checklist.

ZATCA Compliant Workshop Software Compared: 4 Vendors

We applied the four criteria above to software options marketed to Saudi auto workshops. The table below scores each on Phase 2 certification, Fatoora API integration, invoice type coverage, parts/labour line-item separation, and native workshop job card support.

Two observations from the data: First, the only software on this list that combines Phase 2 certification with a native workshop job card module is StartPOS Workshop. Every other Phase 2-capable option is either POS-centric (no job card, no labour tracking) or depends on middleware that introduces a second system into your billing workflow. Second, middleware-based compliance introduces an additional integration layer. For a workshop without an existing ERP, this means a two-system dependency for every invoice — your workshop management system must talk to the middleware, which must talk to the Fatoora portal. Every additional hop is a potential point of failure, and a potential compliance gap when something breaks.

How StartPOS Workshop Handles ZATCA Phase 2 End-to-End

ZATCA Phase 2 certified from day one — Gulf Union Ozone handles device registration, CSID issuance, and Fatoora sandbox testing as part of onboarding. Here is how the compliance chain works inside the software:

• Signed XML UBL 2.1 generated automatically from the completed job card — technician labour lines and parts used appear as separate XML line items, meeting ZATCA schema requirements without any manual data entry or re-formatting
• Cryptographic stamp (CSID) applied to each invoice before submission — the digital signature ZATCA uses to detect tampering or backdating; device-specific and renewed automatically
• QR code generated to ZATCA specification and embedded on the printed invoice for B2C simplified invoices, TLV-encoded with all required seller and invoice data
• Fatoora API real-time clearance for standard B2B invoices — the portal approves the invoice before it is issued to the fleet customer; clearance confirmation stored against the job record
• Reporting submission for simplified B2C invoices within the required 24-hour window, with automatic retry on connectivity failure
• Bilingual output: Arabic and English on the same invoice, as required for Saudi businesses — no second invoice run, no dual-format configuration

The complete workflow: job card (vehicle in, diagnostics, parts used, labour recorded) → one-click review → signed XML generated → Fatoora API clearance → tax invoice issued to customer. No intermediate export, no manual portal upload, no separate compliance step. For a broader evaluation of workshop software options, see our best auto workshop software in Saudi Arabia comparison.

Pricing: SAR 7,500 one-time license (Starter) / SAR 10,000 (Professional) / SAR 15,000 (AI Pro, includes AI analytics). Annual hosting at SAR 1,200/year. No per-invoice fee, no monthly subscription, 0% invoice rejection rate on the Fatoora portal.

Frequently Asked Questions