Clarification Request on QR Code Timestamp Warning in B2C E-Invoice Validation

QR code
1

Dear ZATCA Team,

We are generating QR codes using the official ZATCA .NET SDK v3.4.2. Our invoice XML includes:

<cbc:IssueDate>2025-07-09</cbc:IssueDate>
<cbc:IssueTime>13:51:37</cbc:IssueTime>

We use the following code for QR generation:

EInvoiceQRGenerator validator = new EInvoiceQRGenerator();
var result = validator.GenerateEInvoiceQRCode(EInvoiceSigningResult.SignedEInvoice);

However, when we report the invoice, we get:

{"validationResults":{"status":"WARNING","warningMessages":[{"type":"WARNING","code":"timestamp_QRCODE_INVALID","category":"QRCODE_VALIDATION","message":"The timestamp in QR Code should be based on Invoice Issue Time (KSA-25) and Invoice Issue Date (BT-2). It can either be in format YYYY-MM-DD'T'HH:MM:SS (for local time in KSA) or YYYY-MM-DD'T'HH:MM:SS'Z' (for UTC time or Zulu time)","status":"WARNING"}],"errorMessages":[],"infoMessages":[{"type":"INFO","code":"XSD_ZATCA_VALID","category":"XSD validation","message":"Complied with UBL 2.1 standards in line with ZATCA specifications","status":"PASS"}]},"reportingStatus":"REPORTED"}

We are not passing a custom timestamp, so the QR timestamp is being automatically generated by the SDK from the signed invoice.

Please advise:

  • Why this warning is being raised despite matching values.
  • Whether a specific SDK configuration is needed.
  • If this can be safely ignored or resolved via future SDK updates.

Thank you.

Best regards,
Anish AK

2

Dear @anishak,

Would you please share a full API request including one of the effected invoices to our email

“Sp_Support@zatca.gov.sa”

It will help us investigating such issue to provide you with the proper solution.

Regards,

3

Hi,

As per your guidance, we have sent a mail to the given address
Sp_Support@zatca.gov.sa.
Since our customers facing the problem, please consider this as a serious issue and provide us a solution
Thank you.

Best regards,
Anish AK

4

Dear @anishak,

Thank you for sharing, kindly check your direct messages.

Regards,