ZATCA Clearance vs. Reporting Explained: B2B Standard vs. B2C Simplified Invoices
In ZATCA Phase 2, Saudi Arabia enforces two distinct API transmission models depending on the transaction type: real-time synchronous Clearance for Standard Tax Invoices (B2B/B2G) and asynchronous Reporting within 24 hours for Simplified Tax Invoices (B2C). Understanding the validation rules for each workflow is essential for ERP configuration.
1. Side-by-Side Comparison: Clearance API vs. Reporting API
ZATCA distinguishes between Standard Tax Invoices (Type Code `388` with subtype `0100000`, typically B2B or B2G) and Simplified Tax Invoices (Type Code `388` with subtype `0200000`, typically B2C retail or point-of-sale).
| Dimension | Standard Tax Invoice (Clearance) | Simplified Tax Invoice (Reporting) |
|---|---|---|
| Primary Use Case | B2B & B2G transactions | B2C retail, POS, and walk-in transactions |
| XML Subtype Code | 0100000 | 0200000 |
| API Transmission Timing | Real-time synchronous prior to sharing with buyer | Asynchronous within 24 hours of issuance |
| Who Applies Final Stamp & QR? | ZATCA FATOORA clears XML, embeds stamp & returns QR | Taxpayer EGS signs XML & generates 9-tag QR locally before printing |
| Legal Validity Condition | Valid only after receiving CLEARED status from ZATCA | Issued immediately to customer with EGS cryptographic stamp |
2. Mandatory Buyer Fields: VAT Number & Client Address (B2B vs. B2C)
One of the most frequent causes of ZATCA rejection errors (`BR-10`, `BR-KSA-09`, `BR-KSA-81`, `BR-KSA-46`) is misconfigured buyer master data validation in the source ERP.
For Standard Tax Invoices (`0100000`), the buyer’s full structured address (`cac:AccountingCustomerParty/cac:Party/cac:PostalAddress`) is strictly mandatory under `BR-10`. Additionally, if the buyer is a VAT-registered corporate business in KSA, their 15-digit VAT Registration Number (`BT-48`, starting and ending with `3`) is mandatory under `BR-KSA-81`. If a corporate buyer is not VAT-registered (or is a foreign buyer), an alternative Buyer Other ID (`BT-46`, such as Commercial Registration `CRN` or `MOM` license) must be supplied.
For Simplified Tax Invoices (`0200000` — B2C individual/walk-in customers), neither the Buyer VAT Registration Number nor the Buyer Address is mandatory in the UBL 2.1 XML.
| Field | B2B (VAT-Registered) | Corporate (Non-VAT Registered) | B2C (Individual / Walk-in) |
|---|---|---|---|
| Invoice Workflow | Standard (0100000 — Clearance) | Standard (0100000 — Clearance) | Simplified (0200000 — Reporting) |
| Buyer 15-Digit VAT Number | Mandatory (BR-KSA-81) | Not Applicable (Supply CRN / Other ID in BT-46) | Optional / Not Required |
| Buyer National Address | Mandatory (Street, Building, District, City, 5-Digit Zip, SA) | Mandatory (BR-10) | Optional / Not Required |
3. Handling ZATCA API Statuses: CLEARED, REPORTED, WARNING & REJECTED
Both the Clearance and Reporting APIs return structured validation results. A status of `CLEARED` (HTTP 200) or `REPORTED` (HTTP 200) may also include non-blocking `WARNING` messages (HTTP 202), which indicate minor specification advisories that should be remediated in your ERP mapping.
A `REJECTED` status (HTTP 400) means the invoice failed a mandatory XSD or Schematron `ERROR` rule and was not accepted by ZATCA. Arejected invoice must be corrected and resubmitted rather than distributed to a B2B customer.
Official ZATCA Regulatory References
- ZATCA Electronic Invoice XML Implementation Standard & Data Dictionary— Zakat, Tax and Customs Authority (ZATCA)