XML for organization with single VAT Registration Number and different CRN

XML and business rules
1

I have a scenario related to ZATCA integration and need some clarification:

  1. Background: My client has a single VAT registration number, but multiple CRN numbers for different branches. I created a common PCSID using the VAT number, without including any CRN in the config file. During the onboarding process, I submit all invoice types to the compliance/invoices API to get the PCSID. After getting the PCSID, I use it to sign all invoices. For each branch, I change the CRN in the XML (e.g., <cbc:ID schemeID="CRN">3111111114</cbc:ID>) and adjust the <cac:PostalAddress> based on the branch.

Questions:

  1. Do I need to include any CRN information in the CSR config file? If yes, how should I include it?
  2. Should all CRNs be mentioned in the XML used during the onboarding process (i.e., invoices submitted to the compliance/invoices API to get the PCSID)?
  3. After getting the PCSID, is my approach to including the CRN in each invoice sent to the reporting/clearance API correct?
  4. Is it correct to change the <cac:PostalAddress> details for each branch based on the CRN?
  5. Each branch has its own short address (e.g., RRRD2929). Which short address should I provide in the CSR config file?
  6. Are there any additional steps I need to implement in this scenario?
2 Likes
2

@Ankit_Tiwari Please Reply

3

Dear @arjun_tech24,

Please find the response below:

A1- No, it’s not required to include any CRN details in the CSR configurations.

A2- No, as the compliance checks (compliance invoices API) doesn’t capture any invoice submission, so you can send dummy invoices with fake data as it only for testing & compliance checks purposes, only reporting & clearance submissions will be captured as real invoices.

A3- Yes, including the CRN inside the XML based on the branch that generates the invoice is correct.

A4- Yes, it’s correct to reflect the branch details that generates the invoice inside the XML.

A5- as you wish, there is no such restrictions by ZATCA in this area, you can put the address where the device is located.

A6- Please check the implementation resolution to ensure that your solution is fully compliant.

Regards,

3 Likes
4

@Aturkistani
Thank you so much for your detailed and insightful response.