CSR or Certificate Signer request is a mandatory requirement laid down by ZATCA for the EGS onboarding process and obtaining a Cryptographic Stamp Identifier (CSID) for the EGS unit. CSR contains the VAT details and other information of the company, which are used in creating CSID.
In this blog, we will discuss the relationship between CSR and CSID.
When is CSR be submitted?
CSR is essentially an encoded text that is mandatory to be submitted by the EGS unit to the e-Invoicing platform and ZATCA. At the time of EGS onboarding of the device or the renewal of a device, the CSR needs to be submitted to the e-Invoicing platform.
What is the relation between CSR & Compliance CSID?
To verify the identity of the seller and the EGS unit, the CSID establishes a connection between the EGS unit and a trusted third party. Moreover, a compliance CSID is utilized by the EGS to call the compliance APIs and conduct compliance checks.
When making API calls for necessary processes, it's essential to include the compliance CSID in the request header. The e-invoicing platform generates this compliance CSID, which ensures that EGS units adhere to ZATCA regulations.
As a part of the ZATCA onboarding process, the organization is required to provide a CSR for obtaining a compliance CSID.
CSR Inputs
The following are the inputs required for CSR:
|
Inputs
|
Description
|
|
Common name
|
Name or Asset Tracking Number for the Device/ EGS Unit.
|
|
EGS serial number
|
Details to be submitted,
- Manufacturer/ EGS provider name
- Model/Version
- Serial Number
The Unique Identification Code of the EGS unit shall be automatically filed.
|
|
Organization identifier
|
VAT Registration Number to verify whether the OTP is associated with it or not.
|
|
Organization unit name
|
Name of the Organization Unit and the branch name.
In the case of the VAT group, a 10-digit TIN number of the individual group members whose EGS unit is being onboarded
|
|
Organization Name
|
Name of the individual or the organization
|
|
Country name
|
The name of the country pertaining to the establishment
|
|
Invoice type(functionality map)
|
The document type that the Taxpayer’s solution unit will be issuing/generating.
It can be one or a combination of Standard Tax Invoice (T), Simplified Tax Invoice (S), (X), (Y).
The input should be using the digits 0 & 1 and mapping those to “TSXY” where: 0 = False/Not supported 1= True/Supported (X) and (Y) are for future use and should be set to 0 by default for the time being.
For example, 1000 would mean Solution will be generating Standard Invoices only. 0100 would mean Solution will be generating Simplified invoices (B2C) only and 1100 means Solution will be generating both Standard (B2B) and Simplified invoices (B2C).
|
|
Location
|
Branch address or location where the device or EGS unit is primarily situated.
|
|
Industry
|
Industry or sector for which the device or EGS unit generates the invoices.
|
All CSR fields are mandatory and the input must follow the specification; otherwise, a CSR could be rejected