This is not an Official Translation:
Controls, Requirements, Technical Specifications and Procedural Rules for Implementing the Provisions of the E-Invoicing Regulation based on the decision of His Excellency the Governor - Decision No. (62738) dated 23/11/1443 H
First: Scope of the application
This Resolution, its attached Annexes (1) and (2) and the documents referred to in the Annexes which are an integral part thereof, are set to define the controls, requirements, technical specifications, or procedural rules required for the implementation of E-Invoicing Regulation provisions which are related to the following:
The Generation of Electronic Invoices and Electronic Notes Phase, including provisions related to its processing, and record keeping of Electronic Invoices and Electronic Notes, which is applied to all Persons subject to the E-Invoicing Regulation effective 4th of December 2021.
The Integration Phase on the transmission of Electronic Invoices and Electronic Notes, and sharing them with the Authority, which shall be applied to all Persons subject to the E-Invoicing Regulation in phases starting from 1st of January 2023, and according to the timelines to be determined pursuant to Clause (Sixth) of this Resolution.
Persons subject to Article 3 of the E-Invoicing Regulation shall be subject to this Resolution.
Electronic Invoices generated in accordance with the provisions of this Resolution, the timelines for implementing the requirements and details specified in Annexes (1) and (2) thereof, the Integration implementation phases as determined by the Authority and in the format referred to in Clause (Second) are the tax invoices that are considered for exercising the right of deduction referred to in Article 48, paragraph (1) of the Unified VAT Agreement in relation to transactions subject to Article 3 of E-Invoicing Regulation. In order to claim Input Tax Deduction, the electronic invoices and notes should be Cleared by or Reported to the Authority as per the Integration Phase requirements within this resolution starting from the date announced by the Authority in a subsequent resolution.
Electronic Invoices shall include Tax Invoices and Simplified Tax Invoices set forth under Article 53 of the VAT Implementing Regulation.
Transactions subject to Article 3 of the E-Invoicing Regulation include the cases for which tax invoices must be issued and set forth under Article 53 of the VAT Implementing Regulation, shall include the following:
Supplies of taxable goods and services, either they are subject to the standard VAT rate or Zero rate;
Export of goods and services from the Kingdom;
Intra-GCC supplies in accordance with the Unified VAT Agreement, VAT Law and the VAT Implementing Regulation;
Nominal supplies by the taxable person in accordance with the Unified VAT Agreement, VAT Law and VAT Implementing Regulation;
Any payments related to supply of goods or services and received by the taxable person before the actual supply.
Transactions subject to Article 3 of the E-Invoicing Regulation include the cases for which notes must be issued as per the VAT Implementing Regulation.
Transactions set forth under Article 3 of E-Invoicing Regulation shall not include the following:
Supplies fully exempted from VAT.
Any payments related to supplies fully exempted from VAT and received by a taxable person before such supply.
Supplies subject to VAT according to the Reverse Charge Mechanism.
Import of goods to the Kingdom.
Second: Requirements and details for Generation of Electronic Invoices and Electronic Notes
The Electronic Invoices and Electronic Notes should be generated in a format that must be compliant with the requirements and details specified in Annexes (1) and (2), and in accordance with the timelines specified for the application of these requirements and details, subject to the following:
Electronic Invoices, whether they represent a Tax Invoice or a Simplified Tax Invoice, and their associated Electronic Notes, must be generated in a format that covers all details and fields required for each type of invoices as specified in Annex (2) and as per the timelines set forth under Annexes (1) and (2) of this Resolution.
All Electronic Invoices, whether they represent Tax Invoice or Simplified Tax Invoice, and their associated Electronic Notes, must be generated in XML format or PDF/A-3 format (with embedded XML) as per the timelines specified for application and set forth under Annexes (1) and (2) of this Resolution.
Electronic Invoices and their associated Electronic Notes shall contain a Cryptographic Stamp pursuant to what is specified in this Resolution, starting from the date determined by the Authority in accordance with the timelines specified in Annexes (1) and (2) of this Resolution. A Cryptographic Stamp, for the purposes of implementing this Resolution, means an electronic stamp which is created via cryptographic algorithms to ensure authenticity of origin and integrity of content of the data of the Electronic Invoices and their associated Electronic Notes, and to ensure verification of the identity of the issuer of those Invoices and Notes for the purpose of ensuring compliance with the provisions and controls of the VAT Law and its Implementing Regulation regarding the generation of tax Invoices and Notes. The Cryptographic Stamp must be generated as follows:
With regards to Tax Invoices and their associated Notes which are generated electronically, the Authority shall - starting from the date which will be determined to oblige the persons subject to E-Invoicing Regulation to integrate with the Authority's systems - clear such Electronic Tax Invoices and their associated Electronic Notes in accordance with the mechanism determined by The Authority. The Authority has the power to revise, amend such mechanisms as well as ensure the adherence of the persons subject to E-Invoicing Regulation to it. Clearance means that the Authority shall verify that the Electronic Tax Invoices and their associated Electronic Notes transmitted to it by the persons subject to E-Invoicing Regulation fulfil the controls and details specified in this Resolution and Annexes (1) and (2) thereof. The Authority shall insert the Cryptographic Stamp only on the Invoices and Notes which fulfil the aforesaid controls and details as well as notify the issuers of such Invoices and Notes prior to sharing them with the customers.
With regards to Simplified Tax Invoices and their associated Notes which are generated electronically, such Simplified Tax Invoices and their associated Electronic Notes must be reported to the Authority within a period which must not exceed 24 hours from its generation - in accordance with the mechanism determined by the authority — starting from the date which will be determined by the Authority to oblige the persons subject to E-Invoicing Regulation to integrate with the Authority's systems. The Authority has the power to revise, amend such mechanisms as well as ensure the adherence of the persons subject to E-Invoicing Regulation to it. Reporting is the process of sharing of the Simplified Tax Invoices and their associated Notes which are generated electronically- which include the Cryptographic Stamp as specified in Clause (Fourth) of this Resolution- with the Authority by the persons subject to E- Invoicing Regulation.
All Electronic Notes must satisfy all the requirements specified in Article 54 of the VAT Implementing Regulation, in addition to all requirements and details set forth under this Clause.
Third: The specifications and Requirements of E-Invoice Solutions for Electronic Invoices and Electronic Notes
The E-Invoice Solution used for generating Electronic Invoices and Electronic Notes must be compliant with the specifications and requirements set forth under the E-Invoicing Regulation, this Resolution, and Annexes (1) and (2) thereof. The E-Invoice Solution shall be considered as compliant after verifying its conformity to all specifications and requirements by the Authority, or a third party, or self-certified by the person subject to E-Invoicing Regulation, in accordance with mechanisms and requirements set out by the Authority.
In addition to the above-mentioned requirements in paragraph 1 of this Clause, the Compliant Solution must fulfill the following requirements:
Electronic Invoices and Electronic Notes' formats and its sharing mechanism with customers
The Compliant E-Invoice solution must be able to generate invoices and their associated notes in the XML format or PDF/A-3 format (with embedded XML) as per the requirements of Electronic Invoices formats specified in Annex (1) of this Resolution.
Persons subject to E-Invoicing Regulation must share the Tax Invoice, or its associated Notes that has been electronically generated with customers.
Persons subject to E-Invoicing Regulation must present to their customers a printed copy of the Simplified Tax Invoice or its associated Notes that has been generated electronically, such Simplified Tax Invoice or its associated Notes- upon the agreement between the transaction parties-may also be shared with customers in its electronic format or any other human readable format with customers.
Electronic Invoices and Electronic Notes' Content
The Compliant E-Invoice solution must be able to generate Electronic Invoices and Electronic Notes which include all the data fields required in addition to all requirements and other details specified in this Resolution and Annexes (1) and (2) thereof, for each Invoice or Note based on its type or nature, and including all taxable supplies and set forth under Clause (First) of this Resolution.
Data and Information Security Requirements:
The Compliant E-Invoice solution must be tamper-resistant and include a mechanism, which prevents tampering and reveals any tampering attempts that might occur by the user or any third party in accordance with the specifications and requirements specified by the Authority. The Authority has the power to verify the conformity of the E-Invoice solution to the specifications and requirements in accordance with the verification mechanism set forth under Clause (Fourth) of this Resolution.
The Compliant E-Invoice solution must be able to protect the generated electronic Invoices and Electronic Notes from alteration or deletion, and contain some functionalities which enable the person subject to E-invoicing Regulation to save Electronic Invoices and Electronic Notes and archive them in the format as specified in Annexes (1) and (2) of this Resolution without the need for internet connection and in accordance with the specifications, requirements and timelines specified in Annex (1) of this Resolution.
The Compliant E-Invoice solution must be able to generate a Universally Unique Identifier (UUID) in addition to the Electronic Invoice sequential number which identifies and distinguish each VAT Tax Invoice, Simplified Tax Invoice, and their associated notes in accordance with the specifications, requirements and timelines specified in Annex (2) of this Resolution. This shall be for each Electronic Invoice or Electronic Note generated by such E-Invoice Generation Solution, as per the requirements and timelines specified in Annexes (1) and (2) of this Resolution.
The Compliant E-Invoice solution which is used for generating Simplified Tax Invoices and their associated Notes, must be able to generate a Cryptographic Stamp for each Electronic Invoice or Electronic Note. Such Cryptographic Stamp must have an identifier as per the requirements and timelines specified in Annexes (1) and (2) of this Resolution, and requirements and mechanisms set forth under Clause (Fourth) of this Resolution.
The Compliant E-Invoice solution must be able to generate a Hash for each generated Electronic Invoice or Electronic Note within the sequence of the Electronic Invoices and Electronic Notes. The Hash of the Electronic Invoice is then embedded in the next Electronic Invoice in the sequence. This Hash is used to protect the sequence of Invoices from tampering whether by deletion or replacement. Hash is an enciphered text obtained by applying a one way algorithm upon data which prevents the return to the original data or amending or tampering it as specified in Annex (1) of this Resolution.
The Compliant E-Invoice solution must be able to generate a QR code which is a type of matrix barcode, with a pattern of black and white squares that is machine readable by a QR code scanner or the camera of smart devices in order to enable basic validation of Electronic Invoices and Electronic Notes (Referred to as "QR Code") as specified in Annex (1) of this Resolution.
The Compliant E-Invoice solution must have a tamper-resistant Electronic Invoice counter that cannot be reset or reformatted. The counter must increment for each generated Electronic Invoice or associated note and the Compliant Solution must record the value of this counter in each Electronic Invoice or associated Notes in the field indicated in Annex (2).
Integration requirements:
The approved formats for all Electronic Invoices and Electronic Notes for Integration shall be XML format as referred to in this Resolution.
The Compliant E-Invoice solution must be able to connect to an internet connection and integrate with external systems by using Application Programming Interface (API) specified by the Authority and published on its website.
Prohibited functions
The Compliant E-Invoice solution shall not have the prohibited functionalities as specified in Annex (1) of this Resolution.
The Compliant E-Invoice solution must not be able to generate more than one sequence of Electronic Invoices and Electronic Notes issued through each of the units within the E-Invoice Solution used. For the purposes of this Resolution, a Unit is the key component of the E-Invoice Solution that generates the tamper-proofing features of the sequence of Electronic Invoices by inserting a Hash on the Electronic Invoice or Electronic Note, in addition to including the Hash of the previous Electronic Invoice or Electronic Note in a sequence of Electronic Invoices and Electronic Notes, generates the Cryptographic Stamp for Simplified Tax Invoices and their associated Electronic Notes, and contains a Cryptographic Stamp Identifier for each Cryptographic Stamp as specified in Annex (1) and Annex (2) of this Resolution.
Fourth: Requirements and mechanisms for verifying the conformity of E- Invoice Solutions, Issuance of Cryptographic Stamps, and Cryptographic Stamp Identifiers.
The Authority shall determine the special mechanism for verifying the conformity of E-Invoice Solutions to the specifications and requirements referred to in Clause (Third) of this Resolution, it shall also determine the requirements and mechanisms for issuing Cryptographic Stamps referred to in Clauses (Second) and (Third) of this Resolution, in addition to determining the requirements of The Cryptographic Stamp Identifiers which is issued as a result of registering the units used for generating Simplified Tax Invoices and their associated Electronic Notes with the Authority, which are referred to in Clause (Third), sub-clause (2/c/4) of this Resolution.
Fifth: Keeping of records, Electronic Invoices, Electronic Notes and its associated data
Persons subject to the E-Invoicing Regulation must keep records, Electronic Invoices, Electronic Notes, and their associated data in a way that is compliant with the format and timelines specified in Annexes (1) and (2) of this Resolution and in accordance with the record-keeping requirements set forth under Article 66 of the VAT Implementing Regulation, Persons subject to the E-Invoicing Regulation are obliged to provide the Authority with all records, Electronic Invoices, Electronic Notes or data upon its request for the purpose of verifying the validity of Electronic Invoices and Electronic Notes, and verify their compliance with the provisions of the Unified VAT Agreement, VAT Law, the VAT Implementing Regulation and the E- Invoicing Regulation.
Sixth: Integration
The Integration phases implementation, transmission of Electronic Invoices and Electronic Notes, and sharing them with the Authority, shall be implemented through phases starting from 1st of January 2023, as follows:
The Authority shall determine the targeted groups and phases of Integration for the persons subject to E-Invoicing Regulation. The Authority shall notify each target group with the implementation procedures for the integration with its systems at least (6) months prior to the due date;
Persons subject to the E-Invoicing Regulation must integrate their systems with the Authority's systems by using an Application Programming Interface "API" in accordance with the timelines, targeted groups, and implementation phases of Integration with the Authority's systems.
In addition to Integration requirements specified in Clause (Third), Sub-Clause (2/D), additional details related to Integration and its implementation phases and timelines will be determined through a subsequent resolution(s) from the Governor based on the powers set forth in Article 6, Paragraph (b) of the E-Invoicing Regulation.
Seventh: Obligations of the Persons Subject to the E-Invoicing Regulation
Taking into consideration all the obligations set forth under the Unified VAT Agreement, VAT Law and the VAT Implementing Regulation, all persons subject to the E-Invoicing Regulation as specified in Article 3 thereof must adhere to the controls and obligations stipulated in such regulation and this Resolution, and in particular, adhere to the following:
Generate all tax invoices and notes that must be issued within the timelines specified in the VAT law, in an electronic form starting from the day following the expiration date of the grace period specified in Article 7, paragraph B of the E-Invoicing Regulation.
Comply with all the provisions set forth under the E-Invoicing Regulation in addition to the controls, requirements, technical specification and procedural rules specified in this Resolution and Annexes (1) and (2) thereof, and any subsequent resolutions for E-Invoicing.
Adhere to the specified timelines for compliance with the specifications and requirements of Electronic Invoices and Electronic Notes as per the details and timelines specified in this Resolution and Annexes (1) and (2) thereof.
Adhere to the record keeping requirements of Electronic Invoices, Electronic Notes and its associated data referred to in Clause (Fifth) of this Resolution, and any other requirements as per the applicable laws and regulations.
Notify the Authority through the means specified by the Authority of any incidents, technical error or emergency matters which hinder the generation of Electronic Invoices or Electronic Notes, or hinder the integration of E-Invoicing. The Authority may determine the procedure which should be taken after the validation of such incident, technical error or emergency matter as per its policies. Persons subject to the E-Invoicing Regulation must notify the Authority in the event of the disappearance of such incident, technical error or emergency matter. Persons Subject to the E- Invoicing Regulation shall resume generation of Tax Invoices and associated Notes, and any Invoices or Notes for Transactions conducted during such incidents, technical error or emergency matters electronically, and integrate them with the Authority according to Integration obligations promptly as soon as such incident, technical error or emergency matter that prevented the Generation or Integration of The Electronic Invoices or The Electronic Notes is fixed.
Not to use any E-Invoice Solution which is not compliant with the specifications and requirements referred to in Clause (Third), and in accordance with the timelines and controls specified in this Resolution and Annexes (1) and (2) thereof.
Register the units used for generating Simplified Tax Invoices and their associated Electronic Notes as part of the E-Invoice solution with the Authority, in accordance with the mechanisms and controls referred to in this Resolution and any subsequent resolutions.
Preserve the Cryptographic Stamp Identifiers and its associated components in a safe way, and protect them from copying or illegal use, and not use them for purposes other than those which they are intended for.
Integrate the E-Invoice solution of the persons subject to the E-Invoicing Regulation with the Authority's systems starting from the date specified in this Resolution and any subsequent resolution in this regard.
Sharing the Electronic invoices and the notices associated thereto with the Authority shall be in XML format as of the dates specified for the Integration implementation and according to the timelines specified by the Authority.
Eighth: Closing Provisions
The Authority may authorize one or more entities to perform the verification procedures for the E- Invoice Generation Solution in order to ensure its conformity to the specifications and requirements as per Clause (Third), and verify the fulfillment of the requirements and mechanisms for issuing Cryptographic Stamps referred to in Clauses (Second), (Third), and (Fourth) of this Resolution. Such entity shall verify the conformity of each E-Invoice Generation Solution to the specifications and requirements specified in this Resolution and Annexes (1) and (2) thereof.
Penalties and fines set forth under the VAT Law shall be applied on persons violating the E- Invoicing Regulation and this Resolution, according to the violation's classifications specified in the relevant Board of Directors' resolutions.
Ninth: Enforcement and Obligation
Persons subject to the E-Invoicing Regulation shall comply with the specifications and requirements set forth in this Resolution starting from the day following the expiration date of the grace period as per Article 7, paragraph B of the E-Invoicing Regulation, taking into consideration the specified timelines for the implementation and compliance with each of the specifications and requirements as specified in Annexes (1) and (2) of this Resolution.
This Resolution shall come into force and take effect as of the date of its publication in the Official Gazette.
Annexes
Annexures (1) and (2) below are concerned with specifying the details of the functional and technical requirements and specifications necessary to implement the rules and regulations of the electronic invoicing resolution and the relevant decisions, which will be implemented in two main stages:
The first stage: Generation of Electronic Invoices and Electronic Notes, including provisions related to its processing, and record keeping, effective 4th of December 2021.
The second stage: Integration phase, transmission of Electronic Invoices and Electronic Notes, and sharing them with the Authority for each target group based on the implementation waves announced by the Authority for the integration with the ZATCA.
Annex (1)
Technical Requirements of E-invoice Generation Solutions
This annex contains the following requirements details and shall be reviewed and updated periodically by the Authority.
Electronic Invoice requirements covering types of invoices, invoice formats and invoice structure.
Security and stamps requirements covering cryptographic stamping, hashing, etc.
Data and connectivity requirements of the E-Invoice Generation Solutions for Electronic Invoices and Electronic Notes.
Prohibited capabilities and functions.
Technical Functionalities Mandated from 4th December 2021
| Requirements | Description |
|---|---|
Types of Invoices and Notes | Ability to generate the main types of e-invoices and notes:
|
Invoice and Credit/Debit Note Format |
|
Invoice and Credit/Debit Note Structure |
|
Data Processing & Security |
|
Data Storage and Archival |
|
QR Code | For Simplified Electronic Invoices and associated Notes, it is mandatory to generate and print QR code that must contain:
|
Additional Technical Functionalities mandated from 1st of January 2023 for each target group based on the implementation waves announced by the Authority for the integration with the ZATCA
| Additional Requirements | Description | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Electronic Invoice and Credit/Debit Note Format |
| ||||||||||||||||||||
Electronic Invoice and Credit/Debit Note Structure |
| ||||||||||||||||||||
Data Processing & Security |
| ||||||||||||||||||||
Cryptographic Stamp (Simplified Tax Invoices only and its associated Notes) |
| ||||||||||||||||||||
Additional Cryptographic Capabilities |
| ||||||||||||||||||||
UUID | The UUID is a 128-bit number, generated by an algorithm chosen to make it unlikely that the same identifier will be generated by anyone else in the known universe using the same algorithm. | ||||||||||||||||||||
QR Code |
| ||||||||||||||||||||
Connectivity |
|
Prohibited Functionalities
The functionalities described under this table are not permitted to be enabled in any of the E-Invoice Solutions used for E-Invoicing subject of this Resolution.
Any E-invoice Solution that is deemed to have enabled any of the below functions will be deemed non- compliant with the E-Invoicing requirements set by the Authority.
| Prohibited Functionalities | Description | Enforced on 4th of December 2021 | Enforced as of 1st of January 2023 only for each target group based on the implementation waves |
|---|---|---|---|
Uncontrolled access |
| x | |
Tampering of e-invoices or their associated notes or logs |
| x | |
Multiple Electronic Invoice sequences |
| x | |
Export of stamping keys |
| x | |
Time change |
| x |
In addition to all the technical requirements mentioned above, additional details, requirements, and specifications relevant to the information above in the “Electronic Invoice Security Implementation Standards” must be abided by. This file is an essential part of this annexure and is applied alongside the annex and the resolution.
Annex (2) E- Invoices Fields
This annex shall contain the list of fields that are required to be present on electronic invoices to be enforced in accordance with the timelines specified for each field. The timelines are as follows and are indicated individually for each field:
4th of December 2021
Starting from 1st of January 2023 for each target group based on the implementation waves announced by the Authority for the integration with the ZATCA.
As part of the implementation of the Resolution, the below Electronic Invoice fields included within each Electronic Invoice type are represented by 3 levels of obligation as defined under the column “Obligation”:
Mandatory: A field that must be included in the Electronic Invoice and its associated Note with its details at all times.
Conditional: A field that must be included in the Electronic Invoice and its associated Note if it satisfies certain conditions, and can be excluded if the conditions are not present.
Optional: A field that is not obligatory to be included within the Electronic Invoice and its associated Note, but needs to be available to be filled by the taxpayer in the E-Invoice Generating Solution.
The Implementation of the resolution also includes requirements of visibility of the specific field on the Electronic Invoice or Credit/Debit Note in human readable form such as the PDF or the printed Electronic Invoice or Credit/Debit Note:
Required: A field that must be present on the Electronic Invoice or Credit/Debit Note printout by the corresponding enforcement date of the field.
Not Required: A field that is not mandatory to be presented on the printed version of the Electronic Invoice or Credit/Debit Note, and is up to the discretion of the taxpayer to be included within the printout.
A Tax Invoice shall contain the following specifications:
| # | Field | Validation | Visibility on Invoice (such as PDF, printout, any other human readable form) | Obligation | Enforced on 4th of December 2021 | Enforced as of 1st of January 2023 only for each target group based on the implementation waves | |
|---|---|---|---|---|---|---|---|
1. Type of Invoice | |||||||
1.1 | Invoice Type Description Tax Invoice as per of Article 53(5) VAT Implementing Regulation | Enumerated value | Document title is Tax Invoice | Mandatory | x | ||
1.2 | Special billing agreement flags upon the Authority Approval;
| The self-billing option is only allowed where both parties are VAT registered and it is not allowed in Simplified Tax Invoices. Enumerated value | Required The invoice should be marked as a ”Self- billed Invoice” | Conditional | x | ||
1.3 | Special billing agreement flags upon the Authority approval:
| Not Required | Conditional | x | |||
1.4 | Special transaction type flags (not mutually exclusive)
| If any of the conditions are present | Not Required | Conditional | x | ||
2. Invoice Identifiers | |||||||
2.1 | Invoice Reference Number (IRN): A unique, sequential note number, issued by taxpayer, as per Article 53(5)(b) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
2.2 | Universally Unique Invoice Identifier in UUID format. UUID is A 128-bit number, generated by an algorithm chosen to make it unlikely that the same identifier will be generated by anyone else. | N/A | Not Required | Mandatory | x | ||
2.3 | Previous document (invoice/note) hash. A hash is a digital fingerprint of a document obtained using a standardized hashing algorithm to prevent modifying or tampering with the original data. | N/A | Not required | Mandatory | x | ||
2.4 | QR Code. This field needs to be present in the human readable format, to validate the visualized invoice. | QR Code provided by ZATCA. It should contain the fields as mentioned in Annex (1) | Required | Mandatory | x | ||
2.5 | Invoice tamper-resistant counter value | N/A | Not required | Mandatory | x | ||
3. Date | |||||||
3.1 | Invoice issue date as per Article 53(5)(a) of the VAT Implementing Regulation | The format needs to be YYYY-MM-DD | Required | Mandatory | x | ||
3.2 | Invoice issue time | The format needs to be HH:mm:ss | Not Required | Mandatory | x | ||
3.3 | Supply date. The supply date needs to be present, if it is different from the invoice issue date, as per Article 53(5)(g) of the VAT Implementing Regulation | The format needs to be YYYY- MM-DD | Required | Conditional | x | ||
4 | Seller Identification | ||||||
4.1 | Name as per Article Article 53(5)(e) of the VAT Implementing Regulation | N/A | Required | Mandatory | x | ||
4.2 | Address as per Article 53(5)(e) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
4.3 | VAT registration numbers as per Article 53(5)(c) of the VAT Implementing Regulation and in case the seller is part of a VAT group then the VAT group Registration number should be entered. | Required | Mandatory | x | |||
4.4 | Additional seller IDs. one of the following IDs must be entered:
It consists of:
Note: If the CR is chosen and in case of multiple commercial registrations, the seller should fill the commercial registration of the branch in respect of which the Tax Invoice is being issued. In case multiple IDs exist then one of the above must be entered following the sequence specified above. | N/A | Required | Mandatory | x | ||
5 | Buyer Identification | ||||||
5.1 | Name, as per Article 53(5)(e) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
5.2 | Address as per Article 53(5)(e) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
5.3 | VAT registration number (if applicable) for the buyer and in case the buyer is part of a VAT group then the VAT group Registration number should be entered. | Not mandatory for export invoices. Not Mandatory for internal supplies | Required | Conditional | x | ||
5.4 | Additional buyer ID if the buyer is not VAT registered. One of the following IDs has to be provided:
It consists of:
In case multiple IDs exist then one of the above must be entered following the sequence specified above. | Not mandatory for export invoices. | Required | Conditional | x | ||
6 | Order Reference | ||||||
6.1 | Purchase order | N/A | Not required | Optional | x | ||
6.2 | Contract number | N/A | Not required | Optional | x | ||
7 | Line Items | ||||||
7.1 | Goods or Service Description as per Article 53(5)(f) of the VAT Implementing Regulation | N/A | Required | Mandatory | x | ||
7.2 | Goods or Service Code | N/A | Not required | Optional | x | ||
7.3 | Unit Price as per Article 53(5)(h) of the VAT Implementing Regulation | N/A | Required | Mandatory | x | ||
7.4 | Quantity as per Article 53(5)(f) of the VAT Implementing Regulation | N/A | Required | Mandatory | x | ||
7.5 | Discount or rebate percentage, if discount is provided at line item level | To be filled if the discount is provided at line item levels (goods or service) | Not Required | Conditional | x | ||
7.6 | Discount or rebate amount, if discount is provided at line item level as per Article 53(5)(h) of the VAT Implementing Regulation. | To be filled if the discount is provided at line item levels (goods or service). | Required | Conditional | x | ||
7.7 | Subtotal (exclusive of VAT) | N/A | Required | Mandatory | x | ||
7.8 | VAT rate as per Article 53(5)(i) of the VAT Implementing Regulation. | It is mandatory if the goods / service is not Out Of Scope or Exempt from VAT. | Required | Conditional | x | ||
7.9 | VAT category code | N/A | Not required | Mandatory | x | ||
7.10 | VAT amount as per Article 53(5)(j) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
7.11 | Subtotal (inclusive of VAT) | N/A | Required | Mandatory | x | ||
7.12 | Charge amount, without VAT if charge is provided at line item level. | To be filled only if charge is applied. | Required, if populated. | Conditional | x | ||
7.13 | Prepayment subtotal (Exclusive of VAT) per Rate or exemption | To be filled only if prepayment is used. | Required, if populated. | Conditional | x | ||
7.14 | Prepayment VAT amount per Rate or exemption | To be filled only if prepayment is used. | Required, if populated | Conditional | x | ||
7.15 | Prepayment VAT rate, per Rate or exemption | To be filled only if prepayment is used. | Required, if populated | Conditional | x | ||
8 | Total Amounts | ||||||
8.1 | Discount or rebate percentage, if discount is provided at invoice level. | To be filled if discount is provided at invoice level. | Not required | Conditional | x | ||
8.2 | Discount or rebate amount, if discount is provided at invoice level as per Article 53(5)(h) of the VAT Implementing Regulation. | To be filled if discount is provided at invoice level. | Required | Conditional | x | ||
8.3 | Invoice Taxable Amount per rate or exemption as per Article 53(5)(h) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
8.4 | VAT Total as per Article 53(5)(j) of the VAT Implementing Regulation. | VAT Total must be in SAR | Required | Mandatory | |||
8.5 | Invoice Gross Total (inclusive of VAT) Statement - "Amount includes VAT". | N/A | Required | Mandatory | x | ||
8.6 | Charge amount, without VAT if charge is applied at document level. | To be filled only if charge is applied. | Required, if populated. | Conditional | |||
8.7 | Advanced payment adjustment amount (inclusive of VAT). | Adjustment towards Advanced payment on which VAT is charged by a separate invoice. To be filled only if prepayment is applied. | Required, if populated. | Conditional | x | ||
8.8 | Rounding Amount | To be filled only if rounding adjustment is applied. | Required, if populated. | Optional | x | ||
8.9 | Amount due for payment | To be filled only if prepayment subtotal (Exclusive of VAT) per Rate or exemption (7.13) or rounding amount (8.7) is used. | Required, if the condition is satisfied. | Mandatory | x | ||
9 | Payment Terms | ||||||
9.1 | Payment means, to specify if mode of payment is cash, credit/debit cards, bank transfer, credit, and/or others. | N/A | Not required | Mandatory | x | ||
9.2 | Payment Terms, if mode of payment is by credit. | N/A | Not required | Optional | x | ||
9.3 | Supplier's Bank Account details, if mode of payment is by credit. | To be filled if Payment Method is credit. | Not required | Optional | x | ||
10 | Notes | ||||||
10.1 | Notes, to enter any information not captured in invoice fields. | N/A | Not required | Optional | x | ||
11 | Special Tax Treatment | ||||||
11.1 | Where Tax is not charged at the standard rate, this field should have a narration “Tax treatment applied to the supply” as per Article 53(5)(k) of the VAT Implementing Regulation. | Narration to be entered if Tax is not charged at basic rate. | Required | Conditional | x | ||
12 | Cryptographic Stamp | Cryptographic Stamp provided by ZATCA. It must match the Electronic Invoice content | Not required | Mandatory | x | ||
A Simplified Tax Invoice shall contain the following specifications:
| # | Field | Validation | Visibility on Invoice (such as PDF, printout, any other human readable form) | Obligation | Enforced on 4th of December 2021 | Enforced as of 1st of January 2023 only for each target group based on the implementation waves | |
|---|---|---|---|---|---|---|---|
1 | Type of Invoice | ||||||
1.1 | Invoice Type Description Simplified Tax Invoice as per Article 53(8) of VAT Implementing Regulation. | Enumerated value | Document title is Simplified Tax Invoice. | Mandatory | x | ||
1.2 | Special billing arrangement flags upon the Authority approval:
| N/A | Not Required | Conditional | x | ||
1.3 | Special transaction type flags (not mutually exclusive)
| N/A | Not Required | Conditional | x | ||
2 | Invoice Identifiers | ||||||
2.1 | Invoice Reference Number (IRN): A unique, sequential note number, issued by taxpayer, as per Article 53(5)(b) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
2.2 | Universally Unique Invoice Identifier in UUID format. UUID is A 128-bit number, generated by an algorithm chosen to make it unlikely that the same identifier will be generated by anyone else. | N/A | Not Required | Mandatory | x | ||
2.3 | Previous invoice/note hash. A hash is a digital fingerprint of a document obtained using a standardized hashing algorithm to prevent modifying or tampering with the original data. | N/A | Not required | Mandatory | x | ||
2.4 | QR Code. This field needs to be present in the human readable format, to validate the printed invoice. | QR Code should contain the fields as mentioned in Annex (1) | Required | Mandatory | x | ||
2.5 | Invoice tamper-resistant counter | N/A | Not Required | Mandatory | x | ||
3 | Date | ||||||
3.1 | Invoice issue date as per Article 53(8)(a) of the VAT Implementing Regulation | The format needs to be YYYY-MM-DD | Required | Mandatory | x | ||
3.2 | Invoice issue time | The format needs to be HH:mm:ss | Not Required | Mandatory | x | ||
3.3 | Supply date. The supply date needs to be present, if it is different from the invoice issue date, as per Article 53(7)(c) and (d) of the VAT Implementing Regulation. | The format needs to be YYYY-MM-DD | Required | Conditional | x | ||
4 | Seller Identification | ||||||
4.1 | Name as per Article 53(8)(b) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
4.2 | Address as per Article 53(8)(b) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
4.3 | VAT registration number as per Article 53(8)(b) of the VAT Implementing Regulation and in case the seller is part of a VAT group then the VAT group Registration number should be entered. | Required | Mandatory | x | |||
4.4 | Additional seller ID. one of the following ID's must be entered:
Note: In case of multiple commercial registrations, the seller should fill the commercial registration of the branch in respect of which the Tax Invoice is being issued. In case multiple IDs exist then one of the above must be entered following the sequence specified above. | N/A | Not required | Mandatory | x | ||
5 | Buyer Identification | ||||||
5.1 | Name | Name is mandatory to be filled as per the transactions mentioned in article 53(7) and for private education and private healthcare to citizens. | Required | Conditional | x | ||
5.2 | Address | N/A | Not required | Optional | x | ||
5.3 | Additional buyer ID. Required only for private education or private healthcare supplies to Citizens. This field should contain the National ID only for invoices pertaining to private education and private healthcare to citizens. | National ID is mandatory to be filled for private education and private healthcare to citizens. | Required | Conditional | x | ||
6 | Order Reference | ||||||
6.1 | Purchase order | N/A | Not required | Optional | x | ||
6.2 | Contract number | N/A | Not required | Optional | x | ||
7 | Line Items | ||||||
7.1 | Goods or Service Description as per Article 53(8)(c) of the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
7.2 | Goods or Service Code | N/A | Not required | Optional | x | ||
7.3 | Unit Price | N/A | Required | Mandatory | x | ||
7.4 | Quantity | N/A | Required | Mandatory | x | ||
7.5 | Discount or rebate percentage | N/A | Not required | Optional | x | ||
7.6 | Discount or rebate amount | N/A | Not required | Optional | x | ||
7.7 | Subtotal (exclusive of VAT) | N/A | Not required | Mandatory | x | ||
7.8 | VAT rate | N/A | Not required | Optional | x | ||
7.9 | VAT category code | N/A | Not required | Mandatory | x | ||
7.10 | VAT amount as per Article Article 53(8)(e) of the VAT Implementing Regulation. | N/A | Not required | Optional | x | ||
7.11 | Subtotal (inclusive of VAT) as per Article 53(8)(d) of the VAT Implementing Regulation with a statement saying “inclusive of VAT". | N/A | Required | Mandatory | x | ||
7.12 | Charge amount, without VAT if charge is provided at line item level. | To be filled only if charge is applied. | Required, if populated. | Conditional | x | ||
7.13 | Prepayment subtotal (Exclusive of VAT) per Rate or exemption. | To be filled only if prepayment is used. | Required, if populated. | Conditional | x | ||
7.14 | Prepayment VAT amount per Rate or exemption. | To be filled only if prepayment is used. | Required, if populated. | Conditional | x | ||
7.15 | Prepayment VAT rate, per Rate or exemption. | To be filled only if prepayment is used. | Required, if populated. | Conditional | x | ||
8 | Total Amounts | ||||||
8.1 | Discount or rebate percentage, if discount is provided at invoice level. | Not required | Optional | x | |||
8.2 | Discount or rebate amount, if discount is provided at invoice level. | Not required | Conditional | x | |||
8.3 | Invoice Taxable Amount per rate or exemption. | Required | Conditional | x | |||
8.4 | VAT Total as per Article 53(8)(e) of the VAT Implementing Regulation. | Required | Conditional | x | |||
8.5 | Invoice Gross Total (inclusive of VAT) as per Article 53(8)(d) of the VAT Implementing Regulation If VAT total is not entered, Gross Total to be entered Statement - "Amount includes VAT". | If VAT total and invoice taxable amount is not entered, Gross Total to be entered Statement - "Amount includes VAT". | Required | Conditional | x | ||
8.6 | Charge amount, without VAT if charge is applied at document level. | To be filled only if charge is applied. | Required, if populated. | Conditional | x | ||
8.7 | Advanced payment adjustment amount (inclusive of VAT). | Adjustment towards Advanced payment on which VAT is charged by a separate invoice To be filled only if prepayment is applied. | Required, if populated. | Conditional | x | ||
8.8 | Rounding Amount | To be filled only if rounding adjustment is applied. | Required, if populated. | Optional | x | ||
8.9 | Amount due for payment. | To be filled only if prepayment subtotal (Exclusive of VAT) per Rate or exemption (7.13) or rounding amount (8.7) is used. | Required, if the condition is satisfied. | Mandatory | x | ||
9 | Payment Terms | ||||||
9.1 | Payment means. For Simplified Tax Invoices, this field should specify if the mode of payment is cash, credit/debit cards, bank transfer or others. | N/A | Not required | Optional | |||
9.2 | Payment Terms, if mode of payment is credit. | N/A | Not required | Optional | x | ||
9.3 | Supplier's Bank Account details, if mode of payment is credit. | N/A | Not required | Optional | x | ||
10 | Notes | ||||||
10.1 | Notes, to enter any information not captured in invoice fields. | N/A | Not required | Optional | x | ||
11 | Special Tax Treatment | ||||||
11.1 | Where Tax is not charged at the standard rate, this field should have a narration "Tax treatment applied to the supply" as per Article 53 of the VAT Implementing Regulation. | Narration to be entered if Tax is not charged at basic rate. | Not Required | Conditional | x | ||
12 | Cryptographic Stamp | Cryptographic Stamp must match the Electronic Invoice content and the device Cryptographic Stamp Identifier. | Not required | Mandatory | x | ||
Tax Invoice Credit/Debit Notes shall contain the following specifications:
(1) The fields for credit / debit note should correspond exactly to the type of Electronic Invoice for which the Credit/Debit Note is issued, as specified by Article 54 of VAT regulations.
| # | Field | Validation | Visibility on Invoice (such as PDF, printout, any other human readable form) | Obligation | Enforced on 4th of December 2021 | Enforced as of 1st of January 2023 only for each target group based on the implementation waves |
|---|---|---|---|---|---|---|
1 | Type of Invoice (No change to 1.2 and 1.3) | |||||
1.1 | Invoice Type Description Credit Note or Debit Note as per Article 54 of VAT Implementing Regulation. | Enumerated value representing Credit Note / Debit Note. | Document title is Credit Note or Debit Note. | Mandatory | x | |
2 | Invoice Identifiers (No change to 2.1 - 2.5) | |||||
3 | Date | |||||
3.1 | Note issue date as per Article 54(3) of the VAT Implementing Regulation. | The date format should be YYW-MM-DD. | Required | Mandatory | x | |
3.2 | Note issue time | The format needs to be HH:mm:ss. | Not Required | Mandatory | x | |
3.3 | Supply date | The date format should be YYW-MM-DD. | Required | Conditional | x | |
4 | Seller Identification (No change to 4.1 - 4.4) | |||||
5 | Buyer Identification (No change to 5.1 - 5.4) | |||||
6 | Order Reference (No change to 6.1 and 6.2) | |||||
7 | Line Items (No change to 7.1 - 7.15) | |||||
8 | Total Amounts (No change to 8.1 - 8.9) | |||||
9 | Payment Terms (No change to 9.1 - 9.3) | |||||
10 | Notes (No change) | |||||
11 | Special Tax Treatment (No change) | |||||
12 | Cryptographic Stamp (No change) | |||||
13 | Reference | |||||
13.1 | A reference to the original invoice(s) that the credit/debit note is related to. | N/A | Required | Conditional | x | |
13.2 | Reason for issuance of credit / debit note as per the VAT Implementing Regulation. | N/A | Required | Mandatory | x | |
A Simplified Tax Invoice Credit/Debit Note shall contain the following specifications:
| # | Field | Validation | Visibility on Invoice (such as PDF, printout, any other human readable form) | Obligation | Enforced on 4th of December 2021 | Enforced as of 1st of January 2023 only for each target group based on the implementation waves | |
|---|---|---|---|---|---|---|---|
1 | Type of Invoice (No change to 1.2 and 1.3) | ||||||
1.1 | Invoice Type Description Credit Note or Debit Note as per Article 54 of VAT Implementing Regulation. | Enumerated value representing Credit Note or Debit Note. | Document title is Credit Note or Debit Note. | Mandatory | x | ||
2 | Invoice Identifiers (No change to 2.1 - 2.5) | ||||||
3 | Date | ||||||
3.1 | Note issue date as per Article 54(3) of the VAT Implementing Regulation. | The date format should be YWY-MM-DD. | Required | Mandatory | x | ||
3.2 | Note issue time | The format needs to be HH:mm:ss. | Not Required | Mandatory | x | ||
3.3 | Supply date | The date format should be YWY-MM-DD. | Required | Optional | x | ||
4 | Seller Identification (No change to 4.1 - 4.4) | ||||||
5 | Buyer Identification (No change to 5.1 - 5.4) | ||||||
6 | Order Reference (No change to 6.1 and 6.2) | ||||||
7 | Line Items (No change from 7.1 - 7.15) | ||||||
8 | Total Amounts (No change from 8.1 - 8.9) | ||||||
9 | Payment Terms (No change to 9.1 - 9.3) | ||||||
10 | Notes (No changes) | ||||||
11 | Special Tax Treatment (No changes) | ||||||
12 | Cryptographic Stamp (No changes) | ||||||
13 | Reference | ||||||
13.1 | A reference to the original invoice(s) that the note is related to. | N/A | Required | Conditional | x | ||
13.2 | Reason for issuance of credit / debit note as per the VAT Implementing Regulation. | N/A | Required | Mandatory | x | ||
In addition to all the requirements mentioned above, all detailed technical and functional requirements, business rules, and specifications for each of the previous fields listed in the files “Electronic XML Implementation Standards” and “Electronic Invoice Data Dictionary” must be abided by. These files are an essential part of this annexure and are applied alongside the annex and the resolution.