ZATCA Phase 2 e-invoicing in Saudi Arabia: what it actually requires
Clearance, reporting, the hash chain and the six compliance invoices — a plain-English walkthrough of what the Zakat, Tax and Customs Authority requires from a business connecting to Phase 2, and what usually goes wrong.
Connecting your own system to ZATCA: what a direct integration really involves
A full accounting of what it takes to talk to the Fatoora platform yourself — CSR, compliance CSID, the compliance documents, UBL 2.1, XAdES signing, the ICV counter and PIH chain, clearance versus reporting, and certificate renewal forever — and an honest comparison with sending JSON to an API instead.
Our company is outside Saudi Arabia. Does ZATCA e-invoicing apply to us?
The rules attach to a VAT-registered taxpayer in the Kingdom, not to a head office address. Which entity issues the invoice decides almost everything — and this is what changes for a foreign-built system once that entity is in scope.
Standard vs simplified tax invoice in Saudi Arabia: which one you must issue
A standard tax invoice must be cleared by the Authority before you hand it over and must carry the buyer VAT number; a simplified one is given to the buyer immediately and reported within 24 hours. Getting it backwards costs your customer their input VAT deduction.
Your invoice was rejected by ZATCA: how to read the error code
Where the code sits in the Authority response, why "accepted with warnings" is accepted, why a rejection is fixed by resending the same invoice rather than issuing a credit note, and the handful of codes behind most rejections and most warnings.