Invocie

MENA

ZATCA Phase 2 a Saudiyya: Jagorar Filin Masu Sayarwa

Phase 2 ba batun gobe ba ne — kowane mai sayarwa da ke da rajistar VAT yanzu yana buƙatar clearance na invoices ta hanyar Fatoora kafin fitar da su. Ga jagorar aiki.

Invocie Team · 22 Maris, 2026 · 5 min karatu

ZATCA's Phase-2 (Integration Phase) replaced Phase-1 (Generation Phase) for the first wave of taxpayers in January 2023. Three years and twenty-four waves later, every VAT-registered business in the Kingdom is in scope. If you're issuing invoices in SAR, you're issuing them through Fatoora.

What the rules actually require

  • Standard tax invoices (B2B) must be cleared in real time — submitted to ZATCA, validated, stamped with a UUID, and only then sent to the buyer.
  • Simplified tax invoices (B2C) follow a reporting model — issued first with a TLV-encoded QR code, reported to ZATCA within 24 hours.
  • Every invoice must include a chained cryptographic hash linking it to the previous invoice, plus a digital signature using a CSID (Cryptographic Stamp Identifier) issued by Fatoora.
  • The XML must conform to UBL 2.1 with the ZATCA-specific extensions defined in the Phase-2 implementation specification.

The ZATCA TLV QR

The Phase-1 QR survives in Phase-2 as a TLV (Tag-Length-Value) base64 string. Five mandatory tags: seller name, VAT number, ISO 8601 timestamp, total with VAT, and VAT amount. Phase-2 adds three more — the XML hash, the digital signature, and the public key. ZATCA's mobile app validates these, so any field encoded incorrectly causes the QR to fail verification at the buyer's end even after the invoice is cleared.

Top operational gotchas

  1. Time drift. Invoices stamped more than 30 seconds out of sync with ZATCA's reference clock get rejected. Use NTP, not your laptop.
  2. Hash-chain breaks. If you issue an invoice and forget to include the previous invoice's hash, the chain is broken and the entire device must be re-onboarded with a fresh CSID.
  3. Cross-tax handling. Goods at 15% mixed with zero-rated exports in one invoice need separate <cac:TaxSubtotal> blocks per rate; collapsing them into a single subtotal is a top-3 rejection cause.

Invocie's MENAStrategy implements all of this — UUID generation, chain hashing, TLV QR, UBL 2.1 with ZATCA extensions — so you focus on issuing invoices, not parsing the implementation spec.

Karatu masu alaƙa

FTA UAE E-Invoicing: VAT 5%, TRN, da Abin da Yake Zuwa a 2027

UAE tana motsi daga post-audit zuwa cikakken interoperable. Ga abin da ke canzawa ga masu sayarwa — kuma me yasa TRN ɗinku yake da muhimmanci fiye da kowane lokaci.

Manyan Dalilai 7 da ZATCA ke ƙin Invoices (da yadda za a gyara su)

Daga drift na agogo zuwa lambobin VAT marasa kyau, waɗannan su ne ƙin amincewa da muka fi gani a samarwa — tare da gyara ga kowannensu.

UAE PINT and the 5-Corner Model: How UAE E-Invoicing Actually Works

The UAE's e-invoicing system runs on a 5-corner model — Peppol's 4 corners plus a fifth for the Federal Tax Authority. Here's how UAE PINT, Accredited Service Providers, and the DCTCE framework fit together, explained without the jargon.

Aika invoice masu bin doka a kowace kasuwa

ZATCA, FTA, Peppol da post-audit na duniya — API ɗaya.

Yi magana da ƙungiyarmu