This flow requires a party that has completed registration. The same workflow handles both models. Invopop picks clearance or reporting from the invoice itself.
| Flow | Invoices |
|---|---|
| Clearance | Standard tax invoices (B2B, B2G) |
| Reporting | Simplified tax invoices (B2C) |
Sending
The send workflow claims the next ICV, builds and hashes the UBL document, signs it and generates the QR (for simplified invoices), submits to ZATCA and then stores the final XML and QR back on the silo entry.How it works
Set State → processing
Moves the invoice into a visible “in progress” state for operator dashboards.
Send to ZATCA
Converts the GOBL invoice to UBL 2.1, adds the ICV and PIH chain values, hashes the document, and submits it to the clearance or reporting flows.
- Template
- Code
Saudi Arabia send invoice workflow
Clears standard invoices and reports simplified invoices to ZATCA.
Credit and debit notes
Issued invoices cannot be cancelled or edited once cleared or reported. Corrections are made with credit notes (reduction) or debit notes (increase) that reference the original invoice. A note flows through the same clearance or reporting model as the document it corrects, using the same send workflow.Example invoices
Every example pairs the minimal hand-authored GOBL input with the built version produced bygobl build. All carry the sa-zatca-v1 add-on. Standard invoices are cleared; simplified invoices are reported.
Standard tax invoices (clearance)
Standard invoice (B2B)
Standard invoice (B2B)
A standard tax invoice between two VAT-registered parties, billed at the 15% standard rate. This is the baseline document cleared with ZATCA before it is shared with the buyer.
Standard credit note
Standard credit note
A credit note that reduces a previously cleared standard invoice. The
preceding block links it to the original document.Standard debit note
Standard debit note
A debit note that increases the value of a previously cleared standard invoice, referencing the original in
preceding.Standard export invoice
Standard export invoice
An export to a customer outside the GCC, taxed at the zero rate. Exports carry an exemption reason and are reported with the export tag.
Standard nominal invoice
Standard nominal invoice
A nominal (deemed) supply — goods or services provided without a monetary charge but still subject to VAT.
Standard self-billed invoice
Standard self-billed invoice
A self-billed invoice, where the customer issues the document on the supplier’s behalf under a self-billing agreement.
Standard third-party invoice
Standard third-party invoice
An invoice issued by an authorised third party on behalf of the supplier.
Standard invoice in foreign currency (USD)
Standard invoice in foreign currency (USD)
An invoice issued in USD. The VAT amount must also be expressed in SAR, converted at the SAMA rate on the supply date.
Summary credit note
Summary credit note
A summary credit note that corrects one or more preceding invoices in a single document, tagged
summary.Simplified invoice (B2C)
Simplified invoice (B2C)
A simplified tax invoice for a consumer sale. It is signed and stamped locally with the Production CSID, delivered immediately, and reported to ZATCA within 24 hours.
Simplified credit note
Simplified credit note
A credit note reducing a previously reported simplified invoice.
Simplified debit note
Simplified debit note
A debit note increasing the value of a previously reported simplified invoice.
Simplified zero-rated invoice
Simplified zero-rated invoice
A simplified invoice on zero-rated supplies, carrying explanatory tax notes for the applied rate.
FAQ
How does Invopop decide between clearance and reporting?
How does Invopop decide between clearance and reporting?
From the GOBL invoice type. Simplified invoices (B2C) are reported to ZATCA; all standard invoices (B2B and B2G) are cleared.
When do I submit a standard invoice (clearance) to Invopop?
When do I submit a standard invoice (clearance) to Invopop?
Before you share it with the buyer. Standard invoices follow the clearance model: Invopop submits the invoice to ZATCA in real time, ZATCA validates it and applies its cryptographic stamp, and the cleared document is returned. Only that cleared version is legally valid and shareable — so the invoice must go through Invopop before you send it on to the buyer.
When do I submit a simplified invoice (reporting) to Invopop?
When do I submit a simplified invoice (reporting) to Invopop?
Within 24 hours of issuing it. Simplified invoices follow the reporting model, so you can give the invoice to the customer straight away at the point of sale — it does not need ZATCA validation first, and you can share it before it ever reaches Invopop. You then have up to 24 hours from issuance to submit it to Invopop, which forwards it to ZATCA immediately when the workflow runs.
Do I need to build the ICV/PIH chain myself?
Do I need to build the ICV/PIH chain myself?
No. Invopop calculates the Invoice Counter Value (ICV) and Previous Invoice Hash (PIH) internally on every submission. You only see them reflected in the generated invoice XML.
How is the invoice chain created?
How is the invoice chain created?
ZATCA requires every document a party issues to form a single, unbroken cryptographic chain. Invopop maintains one chain per party and environment (sandbox simulation/developer vs. production are separate sequences), so each registered CSID has its own continuous counter. Two values link it together:
- ICV starts at
1for the first document and increments by exactly1for every document that follows. - PIH of the first document is the hash of the value
0— the base case defined in ZATCA’s data dictionary. Every document after that sets its PIH to the hash of the immediately preceding document.
- Document type does not split the chain. Standard invoices, simplified invoices, credit notes, and debit notes all share one sequence.
- Rejected documents still occupy their slot. A document that ZATCA rejects keeps its ICV and hash; the next document chains off it, not off the last accepted one.
hash(invoice 2) as its PIH and ICV = 3:| Document | ICV | PIH points to | ZATCA result |
|---|---|---|---|
| Invoice 1 | 1 | hash of 0 (base case) | Accepted |
| Invoice 2 | 2 | hash(Invoice 1) | Rejected |
| Invoice 3 | 3 | hash(Invoice 2) | Accepted |
| Credit note 4 | 4 | hash(Invoice 3) | Accepted |
Where do I find the cleared invoice?
Where do I find the cleared invoice?
In the Files section of the silo entry. After a successful submission the final XML is attached as
invoice.xml — for standard invoices this is the ZATCA-cleared, stamped document. The QR code is also stamped onto the document.🇸🇦 Invopop resources for Saudi Arabia
🇸🇦 Invopop resources for Saudi Arabia
| Compliance |  Invoicing compliance in Saudi ArabiaCompliance timeline |
| Apps | Saudi Arabia |
| Guides | Registration Clearance & Reporting |
| FAQ | Saudi Arabia FAQ |
| GOBL |  Saudi Arabia Tax Regime ZATCA Addon |
| GitHub | gobl.sa.zatca |
Participate in our community
Ask and answer questions about invoicing in Saudi Arabia →