Hi. I am using the latest .NET SDK (3.3.3) to sign a B2C invoice. When sending the XML to reporting API(simulation), I receive the following error: “The invoice hash API body does not match the (calculated) hash of the XML.”
Initially, I was generating the hash before signing the invoice. I then tried using the hash from the signing result, but in both cases, I encounter the same error. Is this a bug with the SDK, or am I missing something?
Dear @Ebrahim
Thank you for reaching out, and welcome to our community.
The hash should be calculated on the final version of the XML document after it has been signed. If you’re generating the hash before signing, the XML will change when signed, leading to a mismatch.
Kindly ensure you are correctly using the hash from the signed XML, not the unsigned version, The order should be:
Please Confirm that you’re signing the XML before generating the hash and that the hash is from the final, signed XML document.
It’s likely not a bug but rather an issue with the order of operations or a mismatch between the hash and the XML content. Ensuring the correct sequence first, then hashing should resolve this issue. If the error still occurs, please don’t hesitate to reach out with our support team via email:
SP email: sp_support@zatca.gov.sa
Thanks & Regards,
Thank you for your reply.
Based on your feedback, here is the code I am using:
var signer = new EInvoiceSigner();
var sigingResult= signer.SignDocument(xml, certificate, privateKey); // here I get true for the signing process
var hashGenerator = new EInvoiceHashGenerator();
var hashResult = hashGenerator.GenerateEInvoiceHashing(sigingResult.SignedEInvoice); //here I get true for generating hash
After generating the hash, I encode the signed XML to base64 and send it along with the hash and uuid. However, I am still encountering the following error: “The invoice hash API body does not match the (calculated) Hash of the XML.”
I followed the steps mentioned, but if there is anything I might be missing, please let me know.
Dear @Ebrahim
Please refer to the Fatoora Simulation Portal and find the tab for API documentation to locate the correct endpoint for each step in the onboarding process.
Thank you for your reply.
I have successfully completed the onboarding steps and can see the device listed in the Fatoora portal. However, I encountered an issue later for reporting:
https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/invoices/reporting/single, I received a 400 response with the error message: “The invoice hash API body does not match the (calculated) hash of the XML.”Dear @Ebrahim
The issue you’re encountering with the invoice hash not matching is likely from how the invoice is being signed or how the hash is being calculated before it’s reported to ZATCA
Kindly Doble check and make sure to send the signed XML to the correct reporting endpoints, ensure that you are using the correct certificate and private key when signing the invoice.
You should be able to resolve this issue, if further assistance is needed, sharing more details will help in providing more detailed guidance.
SP email: sp_support@zatca.gov.sa
Thanks,
Thank you for your ongoing support.
While browsing the community, I came across others experiencing the same issue, as detailed in this post: link.
It seems that there is an issue with the latest .NET SDK. I hope this matter can be addressed promptly.
Thank you once again.
@Ebrahim Did this issue solved ? Thanks in advance
Hi, what worked for me is using an older version of the SDK. I used 3.2.6 SDK and I could sign and report invoices correctly.
@Ebrahim Thank you for response
@Ebrahim sorry for inconvenience. Why did you choose SDK 3.2.6 , as other latest SDK’s are available ?
I used it once it was released and it was working. you may try later SDK versions and see if they work.
Please use latest version 3.3.3 it is fine no issues and it will always have fixes of old bugs. thanks