Issue coming in Simulation

XML and business rules
1

We are trying to integrate Zatca with our Logistic application for e-invoicing. Now we are completed our development process. and we checked that in developer portel. it is working. But it is not working in simulation. how to get a support to overcome this issue?

Our error messages are shown below,

  1. The invoice hash API body does not match the (calculated) Hash of the XML
  2. Invalid signed properties hashing, SignedProperties with id=‘xadesSignedProperties’

Detailed error response is,

“errorMessages”:
[
{
“code”: “invalid-invoice-hash”,
“type”: “ERROR”,
“status”: “ERROR”,
“message”: “The invoice hash API body does not match the (calculated) Hash of the XML”,
“category”: “INVOICE_HASHING_ERRORS”
},
{
“code”: “signed-properties-hashing”,
“type”: “ERROR”,
“status”: “ERROR”,
“message”: “Invalid signed properties hashing, SignedProperties with id=‘xadesSignedProperties’”,
“category”: “CERTIFICATE_ERRORS”
}
],

Generated XML is:

<?xml version="1.0" encoding="UTF-8"?> urn:oasis:names:specification:ubl:dsig:enveloped:xades urn:oasis:names:specification:ubl:signature:1 urn:oasis:names:specification:ubl:signature:Invoice not(//ancestor-or-self::ext:UBLExtensions) not(//ancestor-or-self::cac:Signature) not(//ancestor-or-self::cac:AdditionalDocumentReference[cbc:ID='QR']) Ekz92Q7wtcufZUhPn6FisNHBIGfsCZ4ebPppFCFl5XA= MmFkNTRhOTQyMmY5ZDI2MDMyYzc1OGJkZmYwMzFjYzhiM2E5NjJiZTNkOGQ4NWUxMzIyYmQzNmVmODdmYzU5OA== MEUCID0denr2r+BfgN5xHa3q7izh5+XLQsGFaGglbktQwdNZAiEA+cBXLqdeE73Pf+d3ucqZrAjpjGpnsX4q4/87U5C7ZjU= MIICYDCCAgagAwIBAgIGAY4X0wugMAoGCCqGSM49BAMCMBUxEzARBgNVBAMMCmVJbnZvaWNpbmcwHhcNMjQwMzA3MDczMTI1WhcNMjkwMzA2MjEwMDAwWjBoMRcwFQYDVQQDDA5FR1MxLTg4NjQzMTE0NTETMBEGA1UECwwKMTIzNDU2Nzg5MDErMCkGA1UECgwiZ2xhdWJldGVjaCBjb21wYW55IHByaXZhdGUgbGltaXRlZDELMAkGA1UEBhMCU0EwVjAQBgcqhkjOPQIBBgUrgQQACgNCAATKYRETfwyk2lMc28bHYtnlf106pzse5oc/Ln7nlfUJrDhGvmBqeEnJnToLNPlojlS1EIqc0o2ub+FckEi76IYco4HxMIHuMAwGA1UdEwEB/wQCMAAwgd0GA1UdEQSB1TCB0qSBzzCBzDFBMD8GA1UEBAw4MS1CUklER0VMQ1N8Mi1JT1N8My05YjgxNGU2Zi1jYTA0LTQ2NWEtODM2Ny1lZmJjYWJkNjU5NzgxHzAdBgoJkiaJk/IsZAEBDA8zMTA5MDYzOTA4MDAwMDMxDTALBgNVBAwMBDAxMDAxSDBGBgNVBBoMPzAwMDAgRmFsYXN0aW4sIE1pc2hyaWZhaCwgSmVkZGFoIDIzMzMxLCBTYXVkaSBBcmFiaWEsMTIsIEplZGRhaDENMAsGA1UEDwwERm9vZDAKBggqhkjOPQQDAgNIADBFAiEAsAgDMinr13928oK11fXuzVJ5IYfhEglncnRxIU58wBkCIGOVn3y7dbsKEvyWDc/JTVhe5IHrupUe1kHsLnEaGw0a 2024-03-07T07:31:31Z ZWYxZDNkZjRhYTA1ODQ0N2ViZTU5ODJkMGViMDk4NjBmNzQ3ZjZlY2U1NzMwMTIyN2I1YjQxOTI0NDRiYjdmNQ== CN=eInvoicing 1709796690848 reporting:1.0 EGS1-886431145-1 9b814e6f-ca04-465a-8367-efbcabd65978 2024-03-07 07:31:31 388 SAR SAR ICV 1 PIH qZ4nI3/XvuxAdpghvbXWbJVbGRDtoPTXdUNwphGZmuo= QR ASJnbGF1YmV0ZWNoIGNvbXBhbnkgcHJpdmF0ZSBsaW1pdGVkAg8zMTA5MDYzOTA4MDAwMDMDFDIwMjQtMDMtMDdUMDc6MzE6MzFaBAc0NjU4LjM0BQU5MS4zNAYsRWt6OTJRN3d0Y3VmWlVoUG42RmlzTkhCSUdmc0NaNGViUHBwRkNGbDVYQT0HYE1FVUNJRDBkZW5yMnIrQmZnTjV4SGEzcTdpemg1K1hMUXNHRmFHZ2xia3RRd2ROWkFpRUErY0JYTHFkZUU3M1BmK2QzdWNxWnJBanBqR3Buc1g0cTQvODdVNUM3WmpVPQhYMFYwEAYHKoZIzj0CAQYFK4EEAAoDQgAEymERE38MpNpTHNvGx2LZ5X9dOqc7HuaHPy5+55X1Caw4Rr5ganhJyZ06CzT5aI5UtRCKnNKNrm/hXJBIu+iGHAlHMEUCIQCwCAMyKevXf3bygrXV9e7NUnkhh+ESCWdydHEhTnzAGQIgY5WffLt1uwoS/JYNz8lNWF7kgeu6lR7WQewucRobDRo= urn:oasis:names:specification:ubl:signature:Invoice urn:oasis:names:specification:ubl:dsig:enveloped:xades 400004645645654 Falastin, Mishrifah, Jeddah 23331, Saudi Arabia,12 0000 0000 Jeddah Jeddah 31952 SA 300000000000003 VAT glaubetech company private limited 91.34 4567.00 91.34 S 2.00 VAT 91.34 4567.00 4567.00 4658.34 0 0 4658.34 1531 1 4567.00 91.34 4658.34 A Sub Test S 2.00 VAT 4567

Please help me to fix this issue.

2

Hi,

It seems that you are facing a problem in signing the invoice. Kindly follow the below steps for signing the invoice:
You can follow the below steps:
1- Locate the cert.pem file in the SDK’s Data/Certificates folder in SDK.
2- Replace the content of the original cert.pem file with the new certificate content… please note that the certificate (PCSID) must be decoded using a base64 decoder before putting it in the pem file
3- Save the changes to the cert.pem file.
4- Restart the SDK to apply the signing process with the new certificate by the command >> fatoora -sign -invoice <filename(XML file)>

If you still face problems, please reach out to your relationship manager to schedule a meeting with us.

Thanks