Saudi Arabia
E-invoicing in Saudi Arabia (FATOORA)
Each page here is a field, a rule or a concept, written from the authority’s own documents (checked on 4 November 2026) and the JooDax programs’ code, saying plainly what is built and what is not.
E-invoicing
BuiltPhase 1 of e-invoicing has applied to every resident taxpayer since 4 December 2021; Phase 2 (integration) arrives in waves, and wave 25 covers anyone whose VAT-taxable revenue passed SAR 187,500 in any year from 2022 to 2025, with a deadline of 1 February 2027. JooDax connects to ZATCA directly: UBL 2.1, an ECDSA (secp256k1) stamp, a hash chain with a counter, a TLV QR code and a CSID certificate; B2B invoices are cleared before they go out, and B2C invoices are reported within 24 hours. What is built is the simplified invoice and the credit note: a local test mode, onboarding with a one-time password and reporting in the background, accepted without warnings by ZATCA's developer environment on 27 October 2026. The standard B2B invoice and its clearance are planned, not built.
Sections
Concepts
- The e-invoice QR codeA square code printed on the invoice that carries its key data and stamp as base64-encoded TLV, so a buyer can check it with a phone.
- The invoice hash: how it is computedA SHA-256 fingerprint of the document after removing the stamp and QR blocks and canonicalizing it, written in base64; the stamp and the chain rest on it.
- The cryptographic stamp (digital signature)An ECDSA signature in XAdES form over the document hash and signing properties, made with a registered device key and a ZATCA-issued certificate.
- Onboarding a device and its CSIDHow an invoicing device obtains its stamping certificate from ZATCA: key, certificate request, OTP, compliance checks, then the production certificate.
- Clearance of standard invoicesSending a standard invoice or note to FATOORA before the buyer gets it; the platform returns it stamped with a QR code.
- Reporting simplified invoices within 24 hoursSending a simplified invoice or note, already stamped and handed to the buyer, to FATOORA within 24 hours of issue.
- The invoice counter (ICV)A number that goes up by one with every document a device issues, never reset or reused, so any gap in the chain shows.
- The previous invoice hash (PIH) and the document chainEach document carries the hash of the one before it from the same device, so documents form a chain in which any deletion or change shows.
- The UUID in an e-invoiceA 128-bit identifier the device generates for each document, making it globally unique in exchanges with FATOORA.
- Standard versus simplified tax invoicesStandard invoices are for businesses and cleared before hand-over; simplified ones are mostly for consumers, stamped locally and reported within 24 hours.
- Credit and debit notesDocuments that correct an issued invoice: a credit note when the invoiced VAT exceeds the right amount, a debit note when it falls short.
- Invoice type codes: 388, 381, 383, 386A document's type is a three-digit code plus a seven-position name attribute saying whether it is standard or simplified and which flags it carries.
- Phase 1 (generation) and phase 2 (integration)Phase 1, since 4 December 2021, requires issuing and keeping invoices electronically; phase 2, from 1 January 2023 in waves, adds XML, stamping and integration with FATOORA.
- Integration waves and deadlinesZATCA brings taxpayers into phase 2 in waves by VAT-subject revenue, from SAR 3 billion in wave 1 to SAR 187,500 in wave 25.
- Local test mode in the JooDax programsUntil the business onboards its device with ZATCA, the programs stamp documents with a self-signed certificate and print them with a QR code, sending nothing anywhere.
- The e-invoice generation unit (EGS)The device or software that issues invoices and holds their chain, key and certificate; each unit has one sequence and one certificate.
- XML canonicalization (C14N 1.1) before hashingTurning XML text into one standard form before hashing, so the same document gives the same fingerprint on every system.
- VAT exemption reason codes (VATEX)Sixteen codes ZATCA defines to explain why the standard rate is not charged: three for exempt, twelve for zero-rated, one for out of scope.
- Prohibited functions in e-invoicing solutionsFive things no invoicing solution may do from phase 1: uncontrolled access, tampering with invoices or logs, more than one sequence, exporting the stamping key, and changing the time.
Fields
- BT-23 · Business process type
- BT-1 · Invoice number
- KSA-1 · Unique invoice identifier (UUID)
- BT-2 · Invoice issue date
- KSA-25 · Invoice issue time
- BT-3 · Invoice type code
- KSA-2 · Invoice transaction code
- BT-5 · Invoice currency code
- BT-6 · Tax currency code
- BT-25 · Billing reference (original invoice number)
- KSA-16 · Invoice counter value (ICV)
- KSA-13 · Previous invoice hash (PIH)
- KSA-14 · QR code
- KSA-15 · Cryptographic stamp
- BT-29 · Seller identification (other seller ID)
- BT-35 · Seller street name
- KSA-17 · Seller building number
- KSA-3 · Seller district
- BT-37 · Seller city
- BT-38 · Seller postal code
- BT-40 · Seller country code
- BT-31 · Seller VAT registration number
- BT-27 · Seller name
- KSA-21 · Tax scheme identifier
- BT-44 · Buyer name
- BT-46 · Other buyer ID
- BT-48 · Buyer VAT registration number
- BT-50 · Buyer street name
- KSA-18 · Buyer building number
- BT-52 · Buyer city
- BT-53 · Buyer postal code
- KSA-4 · Buyer district
- BT-55 · Buyer country code
- KSA-5 · Supply date
- KSA-24 · Supply end date
- BT-81 · Payment means code
- KSA-10 · Reason for issuing a credit or debit note
- BT-106 · Sum of invoice line net amounts
- BT-109 · Invoice total amount without VAT
- BT-110 · Invoice total VAT amount
- BT-111 · Invoice total VAT amount in accounting currency
- BT-112 · Invoice total amount with VAT
- BT-113 · Prepaid amount
- BT-114 · Rounding amount
- BT-115 · Amount due for payment
- BT-116 · VAT category taxable amount
- BT-117 · VAT category tax amount
- BT-118 · VAT category code
- BT-119 · VAT category rate
- BT-121 · VAT exemption reason code
- BT-120 · VAT exemption reason text
- BT-126 · Invoice line identifier
- BT-129 · Invoiced quantity
- BT-130 · Unit of measure code
- BT-131 · Invoice line net amount
- KSA-11 · Line VAT amount
- KSA-12 · Line amount with VAT
- BT-153 · Item name
- BT-146 · Item net price
- BT-151 · Invoiced item VAT category code
- BT-152 · Invoiced item VAT rate
JooDax programs in Saudi Arabia
Sources
- Electronic Invoice XML Implementation Standard to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- Electronic Invoice Data Dictionary to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- Security Features Implementation Standards to the E-Invoicing resolution dated 2023-05-19 (v1.2) — ZATCA
- الضوابط والمتطلبات والمواصفات الفنية والقواعد الإجرائية اللازمة لتنفيذ أحكام لائحة الفوترة الإلكترونية (قرار المحافظ رقم 62738 وتاريخ 1443/11/23هـ) (vfile dated 20230519 (decision 62738)) — ZATCA
- Controls, Requirements, Technical Specifications and Procedural Rules for Implementing the Provisions of the E-Invoicing Regulation (Decision No. 62738 dated 23/11/1443H) (vfile dated 20230519 (decision 62738)) — ZATCA
- Detailed Guidelines for E-Invoicing (vVersion 2) — ZATCA
- الدليل الإرشادي التفصيلي للفوترة الإلكترونية (vالنسخة الثانية) — ZATCA
- E-invoicing Detailed Technical Guidelines (vVersion 2) — ZATCA
- Developer Portal Manual (vVersion 3) — ZATCA
- FATOORA Portal User Manual (vVersion 3) — ZATCA
- Integration Sandbox API pages (Swagger): reporting, clearance, compliance, production CSID, renewal (ve-Invoicing Sandbox Release 2.1.0 (page lists 2.1.1 as latest)) — ZATCA
- اللائحة التنفيذية لنظام ضريبة القيمة المضافة (vالنسخة العاشرة (آخر تعديل بقرار 24-06-01 في 2024-11-19)) — ZATCA
- Implementing Regulations of the Value Added Tax Law (unofficial translation) (vEighth Edition 04/04/1443H) — ZATCA
- Guideline for Tax Invoicing and Records under VAT Provisions (vVersion 3) — ZATCA
- تحمّل الدولة ضريبة القيمة المضافة المستحقة على الخدمات التعليمية الأهلية المقدمة إلى المواطنين (vالإصدار الثاني) — ZATCA
- E-Invoicing roll-out phases (vpage last updated 2026-09-01) — ZATCA
Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.