We received multiple emails from ZATCA authority relating to unsuccessful attempt to onboard E-invoicing generation solution Unit (EGS Unit).
Below is the part of email we received irrespective of trying to initiate the onboarding. here we are unsure if this is related to the existing onboarded EGS Unit for the an actual attempt to onboard a new EGS Unit.
Blockquote
Thank you for initiating the onboarding / renewal process for your E-Invoice Generation Solution with the Zakat, Tax and Customs Authority (ZATCA). During the process, the sample XML document(s) uploaded have not passed the validation rule(s) and the specific error(s) that are listed in the API response that was communicated to your solution through the respective Application Programming Interface (API).
Please contact your E-invoice Generation Solution vendor to take corrective action.
We are the implementation partner for ZATCA Phase 2 for several clients. Recently, our clients have been receiving emails about XML document compliance failures during onboarding, even though no actual onboarding attempts were made.
After investigating, we found that our solution includes a validation process with ZATCA before documents are sent for clearance or reporting. This validation is done by sending an API request to the compliance API, rather than using the SDK validation.
If a document fails this validation step, the VAT member receives an email indicating a failed onboarding attempt.
We opted not to use SDK validation because it only checks schema structures, whereas the compliance API validates against all ZATCA rules.
Kindly note that the notification service are disabled, and will get bake to all TPs once it re-published, However, It’s not a good thing to deal with compliance check as validation as per we provide our SDK to validate all the business rules for the invoices,
one more thing, there are nothing prevent you to share the invoices during the right APIs (Reporting/Clearance) and based on API response you can deal with your invoices.