The XML file
The whole invoice in a format systems read: seller, buyer, lines and VAT, with the validation and signature elements. It is what goes to the Fatoora platform.
invoice.xmlMeets ZATCA requirements Phase 1 & 2
The e-invoice template in Saudi Arabia
An e-invoice is not a design you fill in but structured data the system generates: an XML file with validation elements, and a readable copy for your customer. Here is what it contains and how to issue it.
14 days free · No credit card · Cancel anytime
Supported by
- Arabic and English invoices
- Sensitive data encrypted, every business isolated
- No lock-in, cancel anytime
XML and PDF
Two faces of one invoice
In phase two the invoice is issued as a structured XML file following ZATCA's requirements based on UBL 2.1, and a readable copy for your customer is made from it. A PDF copy is not forbidden in itself, but the original is the structured file.
The readable copy
A PDF in Arabic and English with the QR code, to print or send to your customer by email or WhatsApp.
invoice.pdfElements
What makes it an e-invoice?
Beside the seller, buyer, lines and VAT, a phase-two invoice carries elements the system generates and no one types:
Unique identifier (UUID)
A number that never repeats, telling the invoice apart in every system.
Invoice counter (ICV)
A sequential counter per issuing unit that rises with every invoice, so none can be removed or slipped in unnoticed.
Previous invoice hash (PIH)
Each invoice carries the hash of the one before it, forming a linked chain that is hard to tamper with.
Signature and cryptographic stamp
The file is signed with the issuing unit's certificate from ZATCA, so its source is known and any change is detected.
QR code
In phase two it carries nine fields: seller name, VAT number, issue time, total and VAT, then the hash, signature and public key, and ZATCA's signature for simplified invoices.
Clearance or reporting
A business-to-business tax invoice is cleared by the Fatoora platform before it is shared with the buyer; a simplified one is reported within 24 hours.
The file
An extract of an e-invoice file
This is what part of the structured file the system generates for every invoice looks like. You never have to write or read it, but it helps to know what is inside.
- cbc:IDInvoice number
- cbc:UUIDUnique identifier
- cbc:InvoiceTypeCodeInvoice type: 388 tax invoice, 0100000 standard
- ICVInvoice counter
- PIHPrevious invoice hash
- cbc:PayableAmountTotal including VAT
<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2">
<cbc:ProfileID>reporting:1.0</cbc:ProfileID>
<cbc:ID>INV-000124</cbc:ID>
<cbc:UUID>3cf5ee18-ee25-44ea-a444-2c37ba7f28be</cbc:UUID>
<cbc:IssueDate>2026-11-03</cbc:IssueDate>
<cbc:InvoiceTypeCode name="0100000">388</cbc:InvoiceTypeCode>
<cac:AdditionalDocumentReference>
<cbc:ID>ICV</cbc:ID> <cbc:UUID>124</cbc:UUID>
</cac:AdditionalDocumentReference>
<cac:AdditionalDocumentReference>
<cbc:ID>PIH</cbc:ID> NWZlY2ViNjZmZmM4NmYzOGQ5NTI3ODZjNmQ2OTZj…
</cac:AdditionalDocumentReference>
<cac:LegalMonetaryTotal>
<cbc:PayableAmount currencyID="SAR">4600.00</cbc:PayableAmount>
</cac:LegalMonetaryTotal>
</Invoice>The two phases
Phase one and phase two
| Phase one: issuing and storing | Phase two: integration | |
|---|---|---|
| Started | 4 December 2021 | In waves of taxpayers since 1 January 2023, as ZATCA notifies |
| Issuing | By a compliant electronic solution | By an electronic solution connected to the Fatoora platform |
| Format | Electronic, with the required elements | An XML file on UBL 2.1 |
| QR code | The basic fields | Nine fields including the hash and signature |
| Platform | — | Tax invoices cleared before sharing; simplified ones reported within 24 hours |
Check which wave your business belongs to and its date through ZATCA's official channels.
In WonderFatoora
These elements are generated with every invoice
- An XML file for every invoice and note, with the unique identifier, counter and previous invoice hash.
- The file signed with the issuing unit's certificate once your business is connected to the Fatoora platform.
- Tax invoices cleared and simplified ones reported automatically, with what did not complete followed up.
- A PDF in Arabic and English with the QR code for your customer.
E-invoice template FAQ
A PDF alone is not enough. In phase two the original is a structured XML file following ZATCA's requirements based on UBL 2.1, and a readable copy for your customer is made from it. A PDF copy is not forbidden in itself.
No. The invoice has to be generated by a compliant electronic solution; making it in a word processor or spreadsheet and printing it does not meet the e-invoicing requirements.
The UUID is a number that never repeats for each invoice, and the counter rises with every invoice an issuing unit makes. The system generates both; no one types them.
A business-to-business tax invoice is sent to the Fatoora platform for validation before it is shared with the buyer; a simplified one is issued by the system and reported within 24 hours.
Phase two applies to waves of taxpayers as ZATCA announces. Check your wave and its date through ZATCA's official channels.
Yes, for every invoice and note, with the required elements; it signs it and sends it to the Fatoora platform once your business is connected.
Issue your first e-invoice today
The system generates the file, the elements, the signature and the QR code; you only write the lines.
14 days free · No credit card · Cancel anytime