BR-KSA-60: Cryptographic stamp is missing from a simplified invoice

A warning: the invoice is accepted with a note; fix the cause in the next invoices.

Official text

Cryptographic stamp (KSA-15) must exist in simplified tax invoices and associated credit notes and debit notes (KSA-2, position 1 and 2 = 02).

Warning · Source: ZATCA E-Invoicing SDK 238-R3.3.8 · Electronic Invoice XML Implementation Standard v1.2, 19 May 2023, §13.3.1, p. 57 · Checked: 26 October 2026

What it means

Simplified invoices and their notes (02) are stamped by the seller's own device before sending. The cac:Signature reference must be in the invoice.

When it happens

How to fix it

  1. Make sure the device is onboarded and holds a valid production certificate.
  2. Sign the invoice, then build the QR, then send it, in that order.
  3. Remove Signature only from the copy you hash, never from the file you send.

Example

Wrong: raises BR-KSA-60
<cbc:InvoiceTypeCode name="0200000">388</cbc:InvoiceTypeCode>
…
<!-- no cac:Signature -->
<cac:AccountingSupplierParty>
Correct
<cbc:InvoiceTypeCode name="0200000">388</cbc:InvoiceTypeCode>
…
<cac:Signature>
  <cbc:ID>urn:oasis:names:specification:ubl:signature:Invoice</cbc:ID>
  <cbc:SignatureMethod>urn:oasis:names:specification:ubl:dsig:enveloped:xades</cbc:SignatureMethod>
</cac:Signature>
<cac:AccountingSupplierParty>

We ran the wrong example through ZATCA's SDK 238-R3.3.8 on 26 October 2026 and it raised BR-KSA-60, along with BR-KSA-29, BR-KSA-30. The example is an excerpt of ZATCA's sample Simplified/Invoice/Simplified_Invoice.xml with one change; the sample without it does not raise the code.

Related codes

Terms on this page

Frequently asked questions

What does BR-KSA-60 mean?

Simplified invoices and their notes (02) are stamped by the seller's own device before sending. The cac:Signature reference must be in the invoice.

Is the invoice rejected when BR-KSA-60 appears?

A warning: the invoice is accepted with a note; fix the cause in the next invoices. This is its severity in ZATCA's SDK 238-R3.3.8.

How do I fix BR-KSA-60?

1. Make sure the device is onboarded and holds a valid production certificate. 2. Sign the invoice, then build the QR, then send it, in that order. 3. Remove Signature only from the copy you hash, never from the file you send.

Last updated: 26 October 2026 · What we don't do · Methodology · Correct us · Changelog

First published 2026-10-26 · Archived copy

First 500 restaurants, cafés, bakeries and sweet shops: a SAR 99 monthly cap.

Instead of SAR 149, per branch, for a full year. Free to join, no commitment.

Reserve your seat