ZATCA API & Validation GuideLast reviewed: November 1, 20268 min read

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.

Validation Reminder: Configure your ERP validations separately for B2B (VAT-registered buyers), B2C (Individual/Walk-in customers), and non-VAT-registered corporate buyers to align with ZATCA rules BR-10 and BR-KSA-81.

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).

ZATCA Phase 2 Clearance vs. Reporting Workflow Comparison
DimensionStandard Tax Invoice (Clearance)Simplified Tax Invoice (Reporting)
Primary Use CaseB2B & B2G transactionsB2C retail, POS, and walk-in transactions
XML Subtype Code01000000200000
API Transmission TimingReal-time synchronous prior to sharing with buyerAsynchronous within 24 hours of issuance
Who Applies Final Stamp & QR?ZATCA FATOORA clears XML, embeds stamp & returns QRTaxpayer EGS signs XML & generates 9-tag QR locally before printing
Legal Validity ConditionValid only after receiving CLEARED status from ZATCAIssued 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.

Mandatory Field Validation Matrix by Customer Type
FieldB2B (VAT-Registered)Corporate (Non-VAT Registered)B2C (Individual / Walk-in)
Invoice WorkflowStandard (0100000 — Clearance)Standard (0100000 — Clearance)Simplified (0200000 — Reporting)
Buyer 15-Digit VAT NumberMandatory (BR-KSA-81)Not Applicable (Supply CRN / Other ID in BT-46)Optional / Not Required
Buyer National AddressMandatory (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

Frequently Asked Questions

No. Buyer Address is strictly mandatory for Standard Tax Invoices (0100000 — B2B and corporate invoices) under rule BR-10, including Street, Building Number, District, City, 5-digit Postal Code (for KSA), and Country Code. For Simplified Tax Invoices (0200000 — B2C walk-in customers), Buyer Address is optional.
KSA Enterprise Integration Assessment

Request a ZATCA Phase 2 Technical Demo

Share your existing ERP environment and monthly invoice volume. Our integration engineers will walk you through the middleware architecture, UBL 2.1 XML transformation, and CSID onboarding flow.