Validate ZATCA (Fatoora) e-invoices before you submit

Check your Saudi UBL 2.1 e-invoice XML against EN 16931 and core BR-KSA rules — and see exactly what will be rejected, in plain language. Built for ERP vendors and integrators.

Drag and drop your XML file here

or click to browse

XML only · 1 MB max · 20 transactions

Guided demo samples

Use these only to preview the diagnostics experience. Your own XML remains the main workflow.

Prefer downloads? valid XML

Files are processed in memory only — nothing is stored or transmitted to third parties.

EN 16931 core

BR-KSA rules

Readable diagnostics

No account required

Not just XML validation

A valid XSD is not a compliant ZATCA invoice.

ZATCA rejects invoices for EN 16931 and BR-KSA business-rule reasons XSD never checks. Ifriqa combines structure checks, EN 16931 rules, KSA-specific rules and readable reports.

Layer	What it catches
UBL 2.1 structure	Required elements, well-formedness
EN 16931 rules	Invoice number, dates, type code, parties, currency
BR-KSA rules	SAR tax currency, seller VAT format, building number (SA), Previous Invoice Hash
Explanation layer	Human-readable diagnostics and machine-readable JSON

Supported profiles

Standard tax invoice (388)Debit note (383)Credit note (381)EN 16931 coreBR-KSA extensions

Built for the ZATCA Phase 2 wave

Pre-check the UBL XML your ERP or middleware produces against EN 16931 + BR-KSA before it reaches the ZATCA clearance/reporting API — and get readable reasons for every failure.

Cryptographic signature, QR content and clearance are out of scope — this is a pre-submission validator, not a generator.

Human-readable diagnostics

Error	Explanation
Missing UUID / PIH	ZATCA requires a UUID and a Previous Invoice Hash (hash chain) on every invoice.
Tax currency not SAR	The tax currency code must be SAR for KSA invoices.
Missing building number (SA)	When the party country is SA, the postal address must include a building number (BR-KSA-63).

Guides & Reference

ZATCA mandate & phases

Saudi e-invoicing (Fatoora) Phase 2: what it requires and how to prepare.

BR-KSA rules

Every rule checked, why invoices are rejected, and how to fix each one.

Technical Reference

Document structure

16 fields · 14 rules · 1 tables

▸

invoice//*[local-name()='Invoice']

◦invoice.profileIdProfileID

◦invoice.idInvoice number

◦invoice.uuidInvoice UUID

◦invoice.issueDateIssue date

ISO_DATE_EXTENDED

◦invoice.typeCodeInvoice type code

CODE

◦invoice.currencyCodeDocument currency code

CURRENCY_CODE

◦invoice.taxCurrencyCodeTax currency code

CURRENCY_CODE

◦invoice.pihPrevious Invoice Hash (PIH)

TEXT

◦invoice.qrQR code (base64 TLV)

TEXT

◦seller.nameSeller name

TEXT

◦seller.vatSeller VAT registration number

VAT_KSA

◦seller.countryCodeSeller country code

COUNTRY_CODE

◦seller.buildingNumberSeller building number

TEXT

◦buyer.nameBuyer name

TEXT

◦buyer.countryCodeBuyer country code

COUNTRY_CODE

◦buyer.buildingNumberBuyer building number

TEXT

Fields

16 defined

Identifier	Label	Type	Required
`invoice.profileId`	ProfileID	ID	—
`invoice.id`	Invoice number	ID	—
`invoice.uuid`	Invoice UUID	ID	—
`invoice.issueDate`	Issue date	ISO_DATE_EXTENDED	—
`invoice.typeCode`	Invoice type code	CODE	—
`invoice.currencyCode`	Document currency code	CURRENCY_CODE	—
`invoice.taxCurrencyCode`	Tax currency code	CURRENCY_CODE	—
`invoice.pih`	Previous Invoice Hash (PIH)	TEXT	—
`invoice.qr`	QR code (base64 TLV)	TEXT	—
`seller.name`	Seller name	TEXT	—
`seller.vat`	Seller VAT registration number	VAT_KSA	—
`seller.countryCode`	Seller country code	COUNTRY_CODE	—
`seller.buildingNumber`	Seller building number	TEXT	—
`buyer.name`	Buyer name	TEXT	—
`buyer.countryCode`	Buyer country code	COUNTRY_CODE	—
`buyer.buildingNumber`	Buyer building number	TEXT	—

Validation rules

14 rules

ZATCA-PROF-001ERROR

A ZATCA invoice must carry a ProfileID (cbc:ProfileID), e.g. "reporting:1.0".

Assertion

ProfileID is required

ZATCA-HDR-001ERROR

An invoice shall have an invoice number (cbc:ID). (EN16931 BR-02)

Assertion

Invoice number is required

ZATCA-HDR-002ERROR

A ZATCA invoice must carry a unique identifier (cbc:UUID).

Assertion

Invoice UUID is required

ZATCA-HDR-003ERROR

An invoice shall have an issue date (cbc:IssueDate). (EN16931 BR-03)

Assertion

Issue date is required

ZATCA-HDR-004ERROR

An invoice shall specify a document type code (cbc:InvoiceTypeCode). (EN16931 BR-04)

Assertion

Invoice type code is required

ZATCA-HDR-005ERROR

The invoice type code must be one of the accepted ZATCA UNTDID 1001 codes (388 tax invoice, 383 debit note, 381 credit note, 386 prepayment).

When

Invoice type code is present

Assertion

Invoice type code ∈ ZATCA invoice type codes (UNTDID 1001): {388, 383, 381, 386}

ZATCA-CUR-001ERROR

An invoice shall specify the document currency code (cbc:DocumentCurrencyCode).

Assertion

Document currency code is required

ZATCA-CUR-002ERROR

The tax currency code (cbc:TaxCurrencyCode) must be SAR for ZATCA invoices. (BR-KSA)

When

Tax currency code is present

Assertion

Tax currency code = "SAR"

ZATCA-SEL-001ERROR

An invoice shall contain the seller name (PartyLegalEntity/RegistrationName). (EN16931 BR-06)

Assertion

Seller name is required

ZATCA-SEL-002ERROR

The seller VAT registration number (PartyTaxScheme/CompanyID) is required and must be 15 digits starting and ending with 3.

Assertion

Seller VAT registration number is required

ZATCA-BUY-001ERROR

An invoice shall contain the buyer name (PartyLegalEntity/RegistrationName). (EN16931 BR-07)

Assertion

Buyer name is required

ZATCA-KSA-01ERROR

When the buyer country is SA, the buyer postal address must include a building number (cbc:BuildingNumber). (BR-KSA-63)

When

Buyer country code = "SA"

Assertion

Buyer building number is required

ZATCA-KSA-02ERROR

When the seller country is SA, the seller postal address must include a building number (cbc:BuildingNumber). (BR-KSA)

When

Seller country code = "SA"

Assertion

Seller building number is required

ZATCA-KSA-03ERROR

A ZATCA invoice must reference the Previous Invoice Hash (AdditionalDocumentReference ID="PIH"); the first invoice uses an empty base hash. (BR-KSA hash chain)

Assertion

Previous Invoice Hash (PIH) is required

Reference tables

1 lists

ZATCA invoice type codes (UNTDID 1001)

zatca-invoice-type-codes

388383381386

Built for

ERP and accounting software vendors serving KSA clients
Integrators and middleware connecting ERPs to ZATCA
Developers implementing ZATCA Phase 2 export
Consultants debugging ZATCA rejections

Feature	Free	Paid
Single invoice validation	Yes	Yes
EN 16931 + BR-KSA diagnostics	Yes	Yes
Full business explanation	Partial	Yes
JSON/API report	Preview	Yes
Batch / ZIP	No	Yes
Full BR-KSA coverage	Core	Yes
History / saved reports	No	Yes
API access	No	Yes

Need batch validation or an API for your ERP?

API access, ZIP/batch processing, saved reports and full BR-KSA coverage are planned for paid usage.

Contact Ifriqa