Skip to content

Clix and ZATCA compliance

This page is for reviewers at ZATCA and Monsha'at, and for business owners who want to check Clix before they rely on it. Each row below names one ZATCA Phase 2 requirement, links the page of ZATCA's own document that states it, and says what Clix does to meet it.

ZATCA's texts call an invoicing system that meets these rules a compliant solution (Implementation Resolution, Clause Third (1)–(2), p. 3). Terms on this page are defined in the Glossary.

ZATCA's Solution Providers Directory

ZATCA publishes a Solution Providers Directory on zatca.gov.sa. On 30 September 2026 it listed Clix as follows:

English page Arabic page
Directory Solution Providers Directory قائمة مزودي الحلول
Name shown Clix شركة التجربة الشاملة لتقنية المعلومات
Phase shown Phase Two المرحلة الثانية
Link on the entry getclix.azmx.sa getclix.azmx.sa

ZATCA describes a Phase Two entry this way: "Phase 2 qualified Solution Providers who have met the specific criteria that apply to Phase 2 (Integration Phase) compliance requirements; and hence, also met the specific criteria applicable to Phase 1 (Generation Phase) compliance requirements too."

ZATCA also states what the directory is not. It is "a guiding list (non-legally binding to taxpayers)", and "This list is not considered as an approval by ZATCA of the e-solutions provided by the solution providers." A taxpayer who meets the requirements is compliant whether or not its provider is listed. The rows below show how Clix meets each requirement.

Requirements and what Clix does

ZATCA requirement ZATCA source What Clix does
Listing in ZATCA's directory. Not a legal requirement; ZATCA publishes the directory to help taxpayers find providers. Solution Providers Directory (checked 30 September 2026) Listed as Clix, Phase Two. See above.
Register each unit and hold its CSID. Register each unit that generates invoices with ZATCA through the Fatoora portal. Keep its cryptographic stamp identifier (CSID) and key safe from copying and misuse. Implementation Resolution, Clause Seventh (7)–(8), p. 7; E-Invoicing Detailed Guidelines §2.8 and §2.10, p. 10; §4.1.2(a), p. 15 Each ZATCA connection in Clix is one unit. Clix registers it with the one-time code from the Fatoora portal. It sends ZATCA a signing request, receives a compliance CSID, passes ZATCA's compliance check with sample invoices, and then receives the production CSID. Clix stores the certificate and its private key; no user handles either. Clix emails the organisation's Admins when a certificate is within 30 days of expiry. See Devices, certificates and branches.
UBL 2.1 XML. Generate each invoice and note in XML to ZATCA's specification, and send ZATCA the XML. Implementation Resolution, Clause Third (2)(D)(1), p. 5; Annex 1, p. 11; XML Implementation Standard §4, p. 5 Clix builds every tax invoice, simplified tax invoice, credit note and debit note as UBL 2.1 XML, and sends that XML to ZATCA.
Cryptographic stamp and QR code. The solution stamps each simplified invoice and its notes. ZATCA stamps a standard invoice when it clears it. Every invoice and note carries a QR code with the fields ZATCA lists. Implementation Resolution, Clause Third (2)(C)(4) and (6), p. 4–5; Annex 1, p. 12–13; E-Invoicing Detailed Guidelines §4.1.2(b), p. 15 Clix signs each document's XML with the connection's certificate. It builds the QR code from the seller's name and VAT number, the time stamp, the totals, the XML hash and the signature. For a standard invoice, Clix stores the cleared XML that ZATCA returns with its stamp.
UUID, invoice counter and previous invoice hash. Give each document a UUID. Keep a counter that cannot be reset and that rises with each document. Put each document's hash into the next one, so a deletion or replacement shows. Implementation Resolution, Clause Third (2)(C)(3), (5) and (7), p. 4–5; Clause Third (2)(E)(2), p. 5; Annex 1, p. 12 Clix writes a UUID, the connection's counter value (ICV) and the previous document's hash (PIH) into the XML of every invoice and note. Each connection keeps one chain.
Clearance of standard invoices. A standard (B2B) invoice and its notes go to ZATCA before they are shared with the buyer. ZATCA stamps only those that pass its checks. Implementation Resolution, Clause Second (3)(A), p. 2–3; E-Invoicing Detailed Guidelines §4.1.2(b), p. 15 Clix sends each standard invoice and note to ZATCA's clearance service when you issue it. The document shows Cleared only after ZATCA accepts it. A refused one shows Not cleared and is not a valid invoice. See Clearance and reporting.
Reporting of simplified invoices within 24 hours. A simplified (B2C) invoice and its notes go to ZATCA within 24 hours of being generated. Implementation Resolution, Clause Second (3)(B), p. 3; E-Invoicing Detailed Guidelines §4.2.2(c), p. 18 Clix reports each simplified invoice and note to ZATCA's reporting service straight after issue. If ZATCA cannot be reached, Clix retries, and the document shows as pending until ZATCA answers.
No editing or deleting; corrections by note. The solution must protect issued invoices and notes from alteration or deletion. An invoice cannot be cancelled; it is corrected with a credit or debit note. Implementation Resolution, Clause Third (2)(C)(2), p. 4; Annex 1, Prohibited Functionalities, p. 14; E-Invoicing Detailed Guidelines, FAQ, p. 63 An issued invoice cannot be edited or deleted, by a user or by Clix support. The API refuses a request to delete one. You correct an invoice with a credit or debit note that references it, and both documents stay on record.
Arabic. Invoice data must be in Arabic. Other languages may appear beside it. E-Invoicing Detailed Guidelines, FAQ, p. 60 and p. 63 The invoice PDF labels every field in Arabic and English. Each item has an Arabic name, which is required and printed on the invoice. The Company Profile and each client have an Arabic name field, printed beside the English name.
Records in the Kingdom, and retention. Keep records electronically in the Kingdom; a resident taxpayer's server must be in the Kingdom. Keep invoices for at least six years from the end of the tax period, and 15 years for real estate. Guideline for Tax Invoicing and Records §8.3.1, p. 41; §8.3.3, p. 42; VAT Implementing Regulations Art. 66, p. 66; Implementation Resolution, Clause Fifth, p. 6 Clix runs on Oracle Cloud Infrastructure in the Jeddah region, and invoice data stays in Saudi Arabia. Issued invoices cannot be deleted, and a downgrade or a lapsed plan deletes nothing. Keeping records for the required period remains the taxpayer's duty. See Your data.
PDF/A-3 with the XML embedded. XML is the format sent to ZATCA. A PDF/A-3 with the XML embedded is the format for sharing an invoice with the buyer as a PDF. Implementation Resolution, Clause Third (2)(A)(1), p. 3; Annex 1, p. 11; E-Invoicing Detailed Guidelines §4.1.2(c), p. 15; FAQ, p. 63 Download PDF on an issued invoice gives a PDF of the invoice with the invoice's XML embedded in the file. See Download the PDF.

What stays with the taxpayer

Clix builds, signs, submits and stores each document. Three duties stay with the business that issues it:

  • The content. Clix signs and submits exactly what you enter: the buyer's VAT number and address, the VAT category on each line, the amounts. ZATCA checks the format and its business rules, not whether the sale happened as described.
  • Registering each place that issues invoices. Every device that issues invoices under your VAT number must be registered (E-Invoicing Detailed Guidelines, FAQ, p. 59). In Clix, that means one ZATCA connection for each.
  • Keeping records for the required period. See the retention row above.

ZATCA sources

All are ZATCA's official publications. Where the English and Arabic texts differ, ZATCA says the Arabic prevails.

  • Solution Providers Directory — English · Arabic. Checked 30 September 2026.
  • Implementation Resolution (Controls, Requirements, Technical Specifications and Procedural Rules), 2023 — English · Arabic. Cited: Clause Second (p. 2–3), Clause Third (p. 3–5), Clause Fifth (p. 6), Clause Seventh (p. 7), Annex 1 (p. 11–14).
  • E-Invoicing Detailed Guidelines, version 2, May 2023 — English · Arabic. Cited: §2.8 and §2.10 (p. 10), §4.1.2 (p. 15), §4.2.2 (p. 18), FAQ (p. 59, 60, 63).
  • Electronic Invoice XML Implementation Standard, version 1.2, May 2023 — PDF. Cited: §4 (p. 5).
  • Guideline for Tax Invoicing and Records under VAT Provisions, version 3, May 2026 — English · Arabic. Cited: §8.3.1 (p. 41), §8.3.3 (p. 42).
  • VAT Implementing Regulations — English, 2021 edition · Arabic, current. Cited: Article 66 (English p. 66).