Error In Validation While Using ZATCA New Release 3.3.5

@Ankit_Tiwari @Embro @Malik @eCloud

Hope you are doing well.
We are facing the validation error with new release of 3.3.5 of ZATCA SDK. Before we are using 3.3.2 and everything is work fine for B2B and B2C Invoices. But now, we have below errors. even though no changes in XML Format. Can someone please guide ? Is it due to any bug in the sdk ?

[Error] occurred in validating Schematrons. [Error] occurred in validating Schematrons.

Roohul-Amin-Seidor fine, Thanks
I am sorry, I am not using sdk , i designed zatca work using code

Hi, Please share your xml as file attachment here it is possible a tag was optional not enforced etc so can comment if can see xml file. Thanks

@Roohul-Amin-Seidor

for this error, let see

there is no issue for eInvoice Signed using CCSID Certificate, but
i have issue for eInvoice that signed with PCSID Certificate.

I use NonProduction Certificate for my test, maybe you can test it with Simulation Certificate.

Dear @Roohul-Amin-Seidor

Kindly to have a clear understanding provide some screenshots for the error from the SDK.

Thank you.

@eCloud I picked Data folder and placed inside my Project My executable project is having Target .NET framework 4.8 So, I picked all the dlls from Net48 folder under zatca-einvoicing-sdk-238-R3.3.5\Lib\Dot-Net8\DLL\Zatca.EInvoice.SDK

Is this correct ?

@saalotaibi

This is the error message from SDK on Step 3 and 4.
[Error] occurred in validating Schematrons. [Error] occurred in validating Schematrons.

@Roohul-Amin-Seidor

Sorry, I haven’t been able to try Net Framework 4.8. There are many similar questions for Validation but it seems there is no solution or answer from Zatca Team.

Dear @Roohul-Amin-Seidor

can you share the invoice that passed on sdk3.3.2 and failed on 3.3.5.

Kindly can i ask to share all of the details and screenshots & also can you share the invoice that passed on sdk3.3.2 and failed on 3.3.5. to ensure a comprehensive support.

Please Share via

sp_support@zatca.gov.sa
E-invoicing@zatca.gov.sa

Thank you.

@saalotaibi
Sure. Sharing it now.

1 Like

@Roohul-Amin-Seidor

Have you got the answer for this discussion? Please share it here.

So far SDK v 3.3.3 is working fine for NetFx 4.8. This library is very good and easy to use.

Thank you

@eCloud

No, Not yet! Still waiting for your response! @saalotaibi
we already sent an email with details with Support!

@saalotaibi
I noticed that the official ZATCA document states that invoice documents should be shared in PDF/A-3 format with embedded XML. I’m currently using the mPDF library in PHP, but it only supports PDF/A-1B, producing output with the following details:

  • Conformance:
    • Standard: PDF/A-1B
    • ISO Name: ISO 19005-1
    • Status: Not yet verified
  • Output Intent:
    • Identifier: sRGB IEC61966-2.1
    • Info: sRGB IEC61966-2.1 (with XML embedded)

Will this PDF/A-1B format cause any issues? Also, does PDF/A-3 refer to the page size? Do I need to change the invoice page width and height to meet the PDF/A-3 requirements?

Are there any PHP libraries available that support PDF/A-3?

@saalotaibi I have posted some of my doubts. it is not yet approved. please consider it. that’s why I commenting my doubts under different topic sections. Thank you

@arjun_tech24
PDF/A3 is not the page size, its compliance Level of PDF.

Here are some key features of PDF/A-3:

  1. Archiving with Attachments: Unlike its predecessors, PDF/A-1 and PDF/A-2, PDF/A-3 allows the embedding of other file formats (like XML, CAD files, etc.) within the PDF. This is useful for archiving related documents together.
  2. Self-Containment: All necessary information to render the document must be included within the file, such as fonts and color profiles, ensuring consistent display.
  3. No Encryption: PDF/A-3 files cannot be encrypted, which supports long-term access and usability.
  4. Metadata: PDF/A-3 requires the inclusion of metadata, which helps in the identification and categorization of documents.
  5. Use Cases: It’s particularly beneficial for businesses and organizations that need to store complex documents along with their supporting files in a single, easily accessible format.

Overall, PDF/A-3 enhances the capabilities of PDF/A formats by allowing more flexibility while still maintaining the core focus on long-term preservation.

1 Like

Thank you.

  • Right now I refer to the invoice properties of the ZATCA SDK, its properties are:

    Standard: PDF/A-3A
    ISO Name: ISO 19005-3

  • I generated a PDF, and its properties are as follows:

    Standard: PDF/A-3B
    ISO Name: ISO 19005-3

Does this difference will cause any problem?

1 Like


This is the sample invoice from Zatca SDK. in this it is PDF/A-3A instead of PDF/A-3B. Does this difference will cause any problem?

I think both should be Accepted

1 Like

Thank you, brother. Are you using any PDF library, like iText, mPDF, or FPDF, to achieve the PDF/A-3 format? If you don’t mind, please mention it so that I can refer to it.