Saudi Arabia·6 min read·2026-08-08

ZATCA E-Invoicing Phase 2: What KSA Accounting Teams Must Do Now

Phase 2 integration is no longer a future project — it is live across most taxpayer waves. Here is the accountant-side workflow, the reconciliation checkpoints, and the operational traps your team cannot afford to miss.

By the SuperAccountant Editorial Team

ZATCA E-Invoicing Phase 2: What KSA Accounting Teams Must Do Now · zatca e invoicing phase 2 changes — SuperAccountant Journal illustration

Your ERP is technically "Phase 2 compliant" — your VAT workpapers are not. That is the gap killing accounting teams right now. ZATCA's Fatoorah Phase 2 (Integration Phase) shifts the compliance burden squarely onto how your team reconciles cleared invoices, handles rejections, and ties e-invoice data back to VAT returns — and most published guidance stops at the IT layer.

What Phase 2 Actually Changed for the Accounting Function

Phase 2 is not a software upgrade you hand to IT and walk away from. Under ZATCA's E-Invoicing Implementing Regulations (Articles 53–60), every standard tax invoice and credit/debit note must now be cleared by ZATCA's platform (FATOORAH) in real time before it is delivered to the buyer. Simplified invoices require near-real-time reporting within 24 hours.

The operational consequence: your sales invoice workflow now has a mandatory third party in the middle. An invoice that your billing team generates at 10 a.m. does not legally exist until ZATCA returns a clearance stamp — and if clearance fails, the AR entry you posted at 10 a.m. is backed by a document that has no legal standing.

Wave onboarding has been rolling since January 2023 (Muharram 1444H) and, according to the official ZATCA portal, new waves continue to be announced. If your entity has not confirmed its wave letter, check the portal now — the penalty clock starts from your wave go-live date, not from when you discover the letter.

The Four Workflow Changes Your Team Needs to Own

1. Pre-clearance invoice hold Build a status field into your AR sub-ledger: Draft → Submitted → Cleared → Delivered. Do not allow GL posting until status = Cleared. If your Mu'tamad ERP posts on Submitted, you are carrying legally invalid receivables.

2. UUID and cryptographic stamp storage Every cleared invoice carries a UUID and a cryptographic stamp (QR for simplified, digital signature + UUID for standard). ZATCA Implementing Regulation Article 53 requires this data to be retained as part of the tax record. Your document management policy must archive the signed XML, not just the PDF. A printed invoice without the embedded stamp is not a valid tax document for audit purposes.

3. Rejection handling — the reconciliation gap nobody talks about ZATCA can return one of three statuses: Cleared, Cleared with warnings, or Rejected. Most teams handle Cleared smoothly. Warnings are where reconciliation breaks down.

A Cleared with warnings invoice is legally valid, but ZATCA has flagged a data inconsistency — for example, a mismatch between the VAT registration number in the invoice XML and the master data on ZATCA's portal. Your team must log every warning, investigate within the period, and correct master data before the next VAT return. Accumulating warnings without resolution is a red flag in a ZATCA field audit.

A Rejected invoice means the document never legally existed. Reverse the GL entry, fix the data error, reissue, and re-submit. Do not let the original sequence number sit open in your ERP — it creates a gap in the mandatory sequential numbering required under Article 53(2).

4. Credit and debit notes — the Phase 2 trap CDNs under Phase 2 must reference the UUID of the original cleared invoice, not merely the invoice number. If your credit note XML references only the human-readable invoice number, ZATCA will reject it. This trips up teams migrating from Phase 1 templates. Audit every CDN template in your ERP against Article 55 of the Implementing Regulations before your next monthly close.

Reconciliation Checkpoints at Month-End

Add these four checkpoints to your standard month-end close checklist:

CheckpointWhat to verifyConsequence of skipping
Clearance status reconciliationEvery standard invoice posted in GL has status = Cleared in FATOORAH logsInvalid receivables on balance sheet
Warning log clearanceZero unresolved warnings older than 30 daysAudit flag; potential penalty under Article 41
Sequential numbering integrityNo gaps in invoice sequence; rejected invoices voided and reissuedNon-compliance with Article 53(2)
VAT return tie-outCleared invoice totals (output VAT) agree to Box 1 of the VAT returnZATCA cross-match will surface any variance automatically

The fourth checkpoint is critical. ZATCA now holds a complete, real-time mirror of your output VAT from cleared invoices. When you file your VAT return via the ZATCA portal, the system can cross-reference your declared Box 1 figure against the sum of cleared invoice VAT. A material variance triggers a query — or an automatic assessment under VAT Implementing Regulation Article 68.

Input VAT: The Buyer-Side Obligation Nobody Reads

Phase 2 compliance is not only a seller problem. As a buyer, your right to deduct input VAT under VAT Implementing Regulation Article 48 requires that the underlying invoice is a valid tax document. That means:

  • The supplier's invoice must carry a valid ZATCA clearance stamp (for standard invoices above the simplified threshold).
  • Your AP team must verify QR code validity on simplified invoices — ZATCA provides a free verification API.
  • An invoice that was rejected on the supplier's side and never reissued gives you zero input VAT entitlement, even if you have a PDF copy.

Build a supplier communication protocol: if a supplier sends a PDF without an embedded stamp or a mismatched QR, hold the payment and request the cleared XML. This is not over-engineering — it is protecting your input VAT claim.

Common Operational Pitfalls in Phase 2 for KSA Teams

Teams currently live on Phase 2 are reporting these recurring issues:

  • ERP timestamp vs. ZATCA timestamp mismatch: Your ERP records the invoice date as the generation time; ZATCA stamps it at clearance time. If the two differ across a month boundary (e.g., generated 31 March, cleared 1 April), the invoice falls in the wrong VAT period. Implement a rule: invoice date in the ERP is locked to the ZATCA clearance date, not the generation date.

  • Multi-branch setups: Each branch operating as a separate billing point needs its own ZATCA device (solution unit). Centralising invoicing through head office without registering branch devices is a non-compliance. Article 7 of the E-Invoicing Regulations defines the obligation at the level of the taxable person's billing system, not the legal entity.

  • Year-end accruals: Accrued revenue at 31 December (31 Jumada Al-Thani 1446H) where the invoice has not yet been cleared cannot be treated as a VAT event. Do not accrue output VAT on uncleared invoices — recognise the VAT liability only on clearance.

  • Testing environment discipline: Changes to invoice templates or ERP configurations must be tested in ZATCA's Simulation Environment before pushing to production. A template change that breaks the digital signature will cause bulk rejections. Teams that skip simulation are the ones calling ZATCA support at midnight before month-end close.

If you want to benchmark your current Phase 2 readiness against real scenarios, the SuperAccountant skills quiz includes a KSA e-invoicing module built around live compliance cases.

Preparing for the 2026 Enforcement Tightening

According to announcements on the ZATCA portal, 2026 (1447H) brings expanded audit activity targeting Phase 2 compliance specifically — focusing on data integrity between cleared invoices and VAT returns. ZATCA's enforcement powers under VAT Law Article 41 include penalties of up to SAR 50,000 for violations related to tax invoice issuance.

The practical preparation steps for your team before the next VAT return:

  1. Pull a full export of FATOORAH clearance logs for the last six months.
  2. Reconcile against your GL invoice register — identify any gaps or status mismatches.
  3. Review all CDN templates for UUID referencing compliance.
  4. Confirm your document retention policy covers signed XML files, not PDFs only.
  5. Schedule a tabletop walkthrough of your rejection-handling procedure with both finance and IT — the first time you run it should not be during an audit.

The accounting teams that come through the next ZATCA audit cycle cleanly will be those who treated Phase 2 as an accounting workflow problem, not a technology project.


Sharpen your edge with SuperAccountant's next live cohort — small batches, real client workpapers, taught by partners. Details and seats at https://app.superaccountant.in/en/cohort?utm_source=blog&utm_medium=cta&utm_campaign=accountants.