Resources

Compliance is not a state you attain once but a chain of controls per invoice: where it fails, how to build a provable cycle, and four explicit controls.

Deleting an issued invoice is barred from Phase 1. Cancel with a credit note within the deadline, and use a pro forma before payment to avoid cancelling.

Your buyer needs a priced document to approve payment? Issue a pro forma instead of a tax invoice, then turn it into the invoice when they pay.

A customer orders for the season and calls off in parts? Record a sales order, invoice from it as goods go, and always know what is left on each line.

Goods leave on several trucks? Record each delivery on a signed note, invoice only what was delivered, and never miss an uninvoiced delivery.

A customer takes several deliveries on different orders and wants one invoice? Combine the delivery notes on one invoice, each line traced to its order.

Billing by percentage done while the client holds 10% until handover? Issue a completion certificate and its invoice, and track retention until release.

A late-delivery penalty, a volume discount, a delivery charge or a fee your customer charges you: where each goes on the invoice, with worked figures.

Standard invoices for B2B, simplified for point of sale. How the fields, the QR code and Phase 2 submission to ZATCA differ between the two.

E-invoicing in short: what it is, who is covered in Saudi Arabia, how it differs from paper or PDF invoices, and what the two phases mean for your business.

The main e-invoicing violations as ZATCA publishes them, from a missing QR code to deleted invoices, how enforcement is graduated, and how to avoid them.

An issued invoice is never edited or deleted. Credit notes reduce, debit notes increase: when to use each, and what it must cite from the original.

From clearance and reporting to CSID, ICV and PIH: Saudi e-invoicing terms defined practically, one by one — in plain language.

Input VAT is deducted on the strength of a valid tax invoice in your name. What makes an invoice deductible, and how e-invoicing protects that right.

A counter sale is invoiced at once, but when do you invoice a contract, an advance or a monthly subscription? The timing rule, and why invoices carry two dates.

Seven steps to wire an ERP to ZATCA: field inventory, the mapping layer, validation before signing, certificates, status back to the ERP, failure testing.

The certificate is a governed cryptographic identity: from CSR and OTP to the production CSID, where the private key stays, and when to replace it.

The whole document cycle, not just the submit call: one JSON shape, mandatory idempotency, scoped permissions, and a status your system can read.

AI does not replace compliance rules: where it adds real value, what must not be automated without controls, and separating reads from production writes.

Connecting an assistant to invoicing services without a direct route to production: reads vs writes, permission scope, and approval for high-impact actions.

Correcting a rejected ZATCA invoice: read the reason, fix the field at its source, know when to retry or reissue, and stop the error repeating.

The QR on a Saudi invoice is not a link but TLV-encoded data: its base fields, the cryptographic fields Phase 2 added, and how the ZATCA app verifies it.

Behind the printed layout: the UBL-based XML, the UUID, the invoice counter (ICV) and the previous-invoice hash (PIH), and why they make it tamper-evident.

The validation rules invoices actually fail on: VAT number, national address, transaction type code, dates and amounts, each with its rule code and fix.