ZATCA Compliance Updates
We stay current so you don't have to.
ZATCA changes. Your API doesn't.
ZATCA regularly updates requirements, error codes, validation rules, and sometimes input/output formats. If you integrate directly with Fatoora, every change can mean rework: updated XML schemas, new error handling, certificate flows, or reporting logic. That's a constant risk of going outdated and hitting production issues.
With Esnad, your contract stays the same. You send the same JSON; we return the same cleared invoice. When ZATCA rolls out a change, we update our integration, test it, and ship it. You get the benefit without touching your code. We take care of data, versioning, and compliance so you can focus on your product.
Why choose Esnad
- ✓Stable API. Same request/response shape. We absorb ZATCA changes on our side.
- ✓Always up to date. We track every ZATCA update and release compatibility as soon as it's live.
- ✓Data and versioning. Your invoice data and archives stay consistent. We handle schema and format evolution.
- ✓Complete solution. No need to juggle ZATCA docs, certificate renewal, and error codes. One API, one partner.
ZATCA updates we've tracked
A non-exhaustive list of ZATCA e-invoicing changes over the last few years. We monitor these and keep Esnad aligned so your integration stays compliant.
Esnad is compliant and stays current
We track every ZATCA change and update our integration as soon as it's live. Your API contract stays the same — no rework, no surprises. You get a complete, always-up-to-date solution.
- Stable API
- No rework
- One partner
Ongoing API and validation changes
ZATCA periodically updates validation rules, error codes, and response formats. Sandbox and production endpoints may receive minor breaking or behavioral changes. Esnad tracks these and updates our integration so your API contract stays stable.
Wave 24 announced (June 2026)
Wave 24 announced for taxpayers with revenue over SAR 375,000. Compliance window April–June 2026. Confirms Phase 2 expansion to smallest in-scope businesses.
Waves 13–22 and new deadlines
Multiple waves targeting mid-size and smaller businesses (revenue thresholds from SAR 15M down to SAR 1.25M). New integration deadlines and compliance windows. ZATCA portal and OTP flow updates.
Credit and debit note rules
Stricter rules on referencing original invoices and reason codes for credit/debit notes. Validation tightened on clearance and reporting endpoints.
QR and TLV specification updates
Refinements to simplified invoice QR code (TLV) encoding and character limits. Some new mandatory fields and namespace updates in the Saudi UBL profile.
Additional waves and revenue thresholds
ZATCA rolled out Phase 2 in waves by annual revenue. New thresholds and deadlines announced every few months. Error codes and clearance response formats clarified in developer documentation.
Phase 2 (Integration) Wave 1
First wave of real-time integration with Fatoora. Large enterprises required to clear B2B invoices and report B2C invoices. UBL 2.1 XML, QR codes, and CSID became mandatory.
Phase 1 (Generation) mandatory
ZATCA required all VAT-registered businesses to generate and store e-invoices electronically. Paper and unstructured PDFs no longer accepted for tax invoices.
The complete solution you need. No one else.
Stop worrying about ZATCA changes. Use one API, one dashboard, one partner. We handle compliance, certificates, and updates so you can run your business.