ZATCA e-Invoicing: A Practical Checklist for Saudi Workshops

ZATCA e-invoicing compliance can sound intimidating in regulatory language, but in practice it comes down to a handful of concrete requirements your shop management software needs to handle for you.

First, every invoice needs a QR code containing the seller's name, VAT registration number, timestamp, invoice total, and VAT amount — generated automatically at the point of invoicing, not added manually afterward.

Second, Phase 2 requires invoices to be generated in a structured XML format (UBL 2.1) and cryptographically signed before being cleared or reported to ZATCA's platform, depending on whether it is a standard or simplified invoice.

Third, simplified invoices — the kind most workshops issue to walk-in customers — must be reported to ZATCA within 24 hours of issuance. Standard invoices to VAT-registered businesses require clearance before they are issued to the customer at all.

Fourth, every invoice needs a tamper-evident hash linking it to the previous invoice in sequence, which means your software needs to maintain this chain automatically — manually re-creating it after the fact is not compliant.

The practical takeaway: this is not a feature you bolt onto your existing invoicing process, it is a requirement your core invoicing engine needs to be built around from day one. Verify with any software vendor whether ZATCA compliance is integrated into invoice generation itself, or sold as a separate add-on you will need to reconcile manually.