Clarification on Configuration of Organization Unit Name (OU) and CRN Usage During Onboarding and Invoice Submission to ZATCA

@Ankit_Tiwari , @idaoud , @Aturkistani
I have a few clarifications regarding the use of “Organization Unit Name (OU)” and Other Seller ID (CRN) in the context of onboarding clients and submitting invoices to ZATCA. Kindly help me confirm the correct approach in the following scenarios:


1. For a Tax Group client using the same invoicing software across all branches under the same TIN (with active CRNs):

  • In this case, should we use the TIN number as the Organization Unit Name (OU) in the onboarding configuration?
  • And include the respective branch CRN (of the issuing branch) in the invoice XML under “Other Seller ID”?

2. For a Tax Group client with multiple CRNs, but they are using this invoicing software only in one branch:

  • Should the Organization Unit Name (OU) in this case be the TIN number or the name of the branch using the software?
  • And in the invoice XML, we are including the CRN of the branch that is issuing the invoice – is that correct?

3. For a client that is not a Tax Group and does not have a TIN, only a single CRN (standalone branch):

  • In this case, should we use the Branch Name as the Organization Unit Name (OU) in the config file?
  • And continue using the same branch CRN in the invoice XML?

4. For a previously onboarded Tax Group client who is using the software in only one branch (but the OU was set as the TIN):
They received a notification from ZATCA stating:

“It has been noted that your invoices do not comply with the requirements of the second phase of electronic invoicing – linking and integration, which includes:
Commercial Records: When choosing the commercial record identifier and there are multiple commercial records, the supplier must enter the commercial record of the branch from which the tax invoice is issued. Therefore, all branches through which invoices are issued must be registered, and the correct entry of the identifier field for the commercial record must be verified, which is considered a violation of the provisions of the electronic invoicing regulations…”

In this case:

  • Do we need to revoke the existing Device and re-onboard it using the Branch Name as the OU?
  • Or can we continue using the current setup with OU as TIN without any technical or compliance issues, as they are issuing invoices only from one branch?

Please confirm if the above understanding is correct for these three onboarding scenarios, or let us know the appropriate guidelines as per ZATCA requirements.

1 Like

@Ankit_Tiwari , @idaoud , @Aturkistani
please reply

@Ankit_Tiwari , @idaoud , @Aturkistani

Any admins, please reply to this post. It has been a long time since it was posted. This issue needs to be resolved as we are continuously receiving emails from ZATCA. We urgently need assistance from the official admins to address this.