Standard (B2B) vs Simplified (B2C) Tax Invoices in ZATCA: Clearance vs Reporting Rules

Q: Can a registered business claim input VAT using a Simplified Tax Invoice?

No. Input VAT can only be claimed on cleared Standard Tax Invoices containing the buyer's official Tax Registration Number (TRN).

Q: What happens if our internet connection goes down during B2B invoicing?

Transactions must be queued locally and cannot be delivered to corporate clients until internet connectivity is restored and clearance is granted.

Q: What is the reporting deadline for Simplified B2C invoices?

Simplified B2C invoices must be submitted to ZATCA's reporting API within 24 hours of issuance.

Q: Are export invoices treated as B2B Standard or B2C Simplified?

Export invoices must always be formatted as Standard Tax Invoices and submitted through real-time clearance.

Q: Can an enterprise issue both Standard and Simplified invoices from the same ERP?

Yes. Onboarding with capability code '1100' enables the EGS unit to issue both cleared B2B and reported B2C documents.

Direct Answer / Quick Summary:

Under Saudi Arabia's ZATCA Phase 2 E-Invoicing mandate, electronic invoices are strictly divided into two distinct legal categories, each governed by an entirely different technical architecture:

Standard Tax Invoice (Fatoorah Dareebiyyah - B2B/B2G): Issued for transactions between commercial businesses or government entities. Governed by the Real-Time Clearance Model. The seller's ERP must submit the UBL 2.1 XML invoice to ZATCA via API in real-time. ZATCA validates and cryptographically clears the document, returning a signed clearance stamp. The invoice cannot be legally delivered to the buyer or accounted for input VAT deduction until it has been successfully cleared by ZATCA.*

Simplified Tax Invoice (Fatoorah Dareebiyyah Mubassatah - B2C): Issued for retail, Point-of-Sale (POS), and consumer transactions. Governed by the 24-Hour Reporting Model. The invoice is issued to the consumer immediately upon payment (containing a mandatory Phase 2 cryptographic QR code) and must be programmatically reported to ZATCA's API within 24 hours of issuance*.

Buyer Input Tax Rule: A corporate buyer can only* claim a 15% input VAT deduction on an invoice that qualifies as a valid Standard Tax Invoice cleared by ZATCA. Simplified invoices cannot be used by registered businesses for input tax deduction.

Architectural Taxonomy: Clearance vs Reporting Models

To prevent tax fraud while accommodating high-speed retail checkout counters, the Zakat, Tax and Customs Authority designed two complementary technical pathways:

Stage 01Real-Time Clearance

Standard Invoice (B2B)

ERP generates XML → Real-time API call to ZATCA → ZATCA issues Clearance Stamp → Delivered to Buyer

Stage 0224-Hour Reporting

Simplified Invoice (B2C)

POS generates XML + QR code → Receipt handed to consumer immediately → Sent to ZATCA within 24h

Stage 03Linked Clearance

B2B Credit/Debit Notes

Associated upward/downward adjustments must pass real-time clearance referencing original UUID

Stage 04Linked Reporting

B2C Credit/Debit Notes

Associated consumer return adjustments reported to ZATCA within 24 hours referencing original receipt

Side-by-Side Comparison: Standard (B2B) vs Simplified (B2C)

The following comprehensive regulatory matrix details the contrasting requirements between the two invoice classifications:

Compliance Dimension	Standard Tax Invoice (B2B / B2G)	Simplified Tax Invoice (B2C)
Target Recipient	Taxable commercial businesses, corporations, government ministries.	End-consumers, walk-in retail shoppers, unregistered individuals.
ZATCA Integration Model	*Clearance Model (Nizam Al-I'timad)*	*Reporting Model (Nizam Al-Iblagh)*
API Transmission Timing	Real-Time / Synchronous. Must clear before sharing with buyer.	Asynchronous. Permitted up to 24 hours after transaction time.
ZATCA API Endpoint	`/e-invoicing/core/invoices/clearance/single`	`/e-invoicing/core/invoices/reporting/single`
Buyer Information Required	Mandatory: Full legal name, registered address, and 15-digit VAT TRN.	Optional / Not Required: Generic consumer checkout allowed.
Document Delivery Format	Human-readable PDF/A3 format embedding the cleared UBL 2.1 XML.	Printed paper thermal slip, electronic SMS, or emailed PDF with QR code.
QR Code Requirements	Embedded inside XML; optional on human-readable layout.	Mandatory on printed receipt. Must contain 9 cryptographic TLV tags.
Input VAT Deductibility	Fully Deductible by the buyer on quarterly VAT returns.	Non-Deductible. Cannot be used for corporate input tax claims.
System Failure Contingency	Invoices queued locally; cannot be legally finalized until cleared.	Invoices issued offline to consumers; synced upon network recovery.

Deep Dive: The Clearance Model for Standard B2B Invoices

For business-to-business commerce, ZATCA acts as a mandatory intermediary gatekeeper. A commercial agreement between two corporate parties is not legally enforceable for VAT deduction without government verification:

1. Step-by-Step Clearance Execution

1Invoice Generation: The seller's ERP generates the transaction payload conforming to the UBL 2.1 XML standard.

2Local Cryptographic Hashing: The ERP calculates the SHA-256 digest, signs it with the company's private key, and embeds its active Production CSID.

3API Clearance Request: The ERP calls the ZATCA clearance endpoint via HTTP POST:

http|Technical Specification / Reference

Verified Schema

   POST /e-invoicing/core/invoices/clearance/single HTTP/1.1
   Host: gw-fatoora.zatca.gov.sa
   Accept-Language: en
   Clearance-Status: 1
   Accept-Version: V2
   Content-Type: application/json
   Authorization: Basic <Base64_Encoded_CSID_Credentials>

4ZATCA Validation Engine: ZATCA validates business rules, tax arithmetic, VAT number authenticity, and cryptographic signatures in under 1.5 seconds.

5Clearance Stamp Issuance: ZATCA returns HTTP 200 OK with status CLEARED, appending an official ZATCA Cryptographic Stamp and clearance timestamp.

6Buyer Delivery: The seller embeds this cleared XML into an archival PDF/A-3 container and delivers it to the corporate buyer.

Mandatory Regulatory Requirement

Prohibition Against Pre-Clearance Delivery:

Delivering a B2B invoice to a corporate client before receiving ZATCA clearance is a direct statutory violation. Un-cleared invoices lack legal standing under Saudi tax law.

Deep Dive: The Reporting Model for Simplified B2C Invoices

Retail cash registers, restaurants, and e-commerce stores serving everyday consumers cannot withstand API latency during peak transaction hours. Therefore, ZATCA allows offline immediate issuance followed by delayed reporting:

1. Step-by-Step Reporting Execution

1Instant POS Generation: At the checkout counter, the POS creates the transaction XML and instantly generates the Phase 2 2-Dimensional QR Code.

2Customer Handoff: The receipt is printed or sent electronically to the customer immediately. The customer can scan the QR code using the official ZATCA (Zad) App to confirm authenticity.

3Local Queuing & Hash Chaining: The POS registers the transaction in its local tamper-proof ledger, chaining its cryptographic hash to the preceding invoice counter value (ICV).

424-Hour Batch/Single API Reporting: Within 24 hours, the POS transmits the invoice to the reporting endpoint:

http|Technical Specification / Reference

Verified Schema

   POST /e-invoicing/core/invoices/reporting/single HTTP/1.1
   Host: gw-fatoora.zatca.gov.sa
   Accept-Language: en
   Accept-Version: V2
   Content-Type: application/json
   Authorization: Basic <Base64_Encoded_CSID_Credentials>

5ZATCA Confirmation: The API returns status REPORTED. ZATCA logs the transaction into the national ledger for corporate tax reconciliation.

The Hybrid Dilemma: B2B Transactions Under SAR 1,000

Under Article 53 of the Saudi VAT Executive Regulations, transactions under SAR 1,000 can technically be issued as simplified tax invoices. However, a critical business rule applies:

Statutory Safeguards & Rights Protection

Mandatory protections enforced by MHRSD & Saudi Labor Law

Corporate Buyer RequestIf a business buyer purchases office supplies, fuel, or hardware under SAR 1,000 and demands an invoice to claim input VAT, the seller MUST issue a Standard Tax Invoice.

Mandatory Buyer DataTo convert the transaction into a Standard Tax Invoice, the seller must collect the buyer's company name, physical address, and 15-digit VAT number.

Mandatory Real-Time ClearanceThe moment a transaction is classified as a Standard Tax Invoice, it MUST pass through real-time clearance, even if the value is only SAR 50.

Simplified Invoices Ineligible for Input TaxIf the seller issues a Simplified receipt with only a QR code, the corporate buyer's auditors CANNOT legally claim the 15% VAT on their corporate tax return.

Phase 2 QR Code Requirements: B2B vs B2C

The cryptographic QR code is the most visible compliance component:

QR Code Tag / TLV Element	Tag ID	Required on Simplified (B2C)?	Required on Standard (B2B)?
Seller Legal Name	Tag 1	Mandatory	Embedded in XML (Optional on layout)
Seller 15-Digit VAT TRN	Tag 2	Mandatory	Embedded in XML (Optional on layout)
Invoice Timestamp (ISO 8601)	Tag 3	Mandatory	Embedded in XML (Optional on layout)
Invoice Total (With VAT)	Tag 4	Mandatory	Embedded in XML (Optional on layout)
Total VAT Amount	Tag 5	Mandatory	Embedded in XML (Optional on layout)
SHA-256 Invoice XML Hash	Tag 6	Mandatory	Embedded in XML
ECDSA Digital Signature	Tag 7	Mandatory	Embedded in XML
Public Key Certificate	Tag 8	Mandatory	Embedded in XML
ZATCA Certificate Signature	Tag 9	Mandatory	Injected by ZATCA upon clearance

On Simplified B2C printed receipts, the QR code must be rendered with high contrast, measuring at least 20mm x 20mm, allowing instant optical scanning by consumer smartphones.

Handling Adjustments: Credit and Debit Notes

When merchandise is returned, discounts are applied retroactively, or billing errors are corrected, businesses cannot simply edit or delete the invoice. They must issue an electronic note that inherits the exact architecture of the original document:

B2B Adjustments: A Credit Note (*Ish'ar Da'in*) or Debit Note (*Ish'ar Madeen*) issued to a corporate client must reference the original invoice UUID and must pass real-time clearance through /invoices/clearance/single.

B2C Adjustments: A credit or debit note issued to a consumer must reference the original receipt and must be reported to ZATCA within 24 hours via /invoices/reporting/single.

Frequently Asked Questions (FAQ)

Can a registered business claim input VAT using a Simplified Tax Invoice?

No. Under Saudi VAT Executive Regulations, registered enterprises are legally prohibited from claiming input tax deductions based on Simplified Tax Invoices. Taxable entities must insist on receiving a fully cleared Standard Tax Invoice containing their 15-digit VAT number.

What happens if our internet connection goes down during B2B invoicing?

Because Standard B2B invoices require real-time clearance, your ERP cannot legally issue finalized invoices to corporate buyers during a connectivity outage. The transactions must be held in a local queue and cleared as soon as connectivity is restored before dispatching them to clients.

What is the reporting deadline for Simplified B2C invoices?

Simplified invoices must be reported to ZATCA's Fatoora API within 24 hours of the transaction timestamp. Failing to report within this window triggers compliance penalties and potential audit investigations.

Are export invoices treated as B2B Standard or B2C Simplified?

All export invoices—regardless of whether the foreign buyer is a business or individual—must be issued as Standard Tax Invoices (B2B) and submitted to ZATCA's clearance engine.

Can an enterprise issue both Standard and Simplified invoices from the same ERP?

Yes. During EGS onboarding, an enterprise can register its solution with invoice capability code 1100, which authorizes the system to generate both Standard (clearance) and Simplified (reporting) tax invoices from a unified platform.