BR-KSA-03: Invoice unique identifier (UUID) is missing

Official text

The invoice must contain a unique identifier ("UUID") (KSA-1) given by the unit that issued the document (unique message identifier for interchange process). This value must contain only letters, digits, and dashes.

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

What it means

Every invoice must carry a unique identifier (UUID) that your system generates, made of letters, digits and dashes only. It is separate from the sequential invoice number.

When it happens

• The field is present but empty.
• The system copied the invoice number into the UUID field or used characters that are not allowed.
• An old invoice template that does not include the field at all.

How to fix it

1. Generate a new UUID for each invoice when it is created (random version 4 is the usual choice).
2. Store it with the invoice and keep it unchanged when you resend.
3. Never reuse one identifier for two invoices.

Example

<cbc:ID>SME00010</cbc:ID>
<cbc:UUID></cbc:UUID>

<cbc:ID>SME00010</cbc:ID>
<cbc:UUID>8e6000cf-1a98-4174-b3e7-b5d5954bc10d</cbc:UUID>

We ran the wrong example through ZATCA's SDK 238-R3.3.8 on 26 October 2026 and it raised BR-KSA-03. 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

• BR-KSA-33 Invoice counter (ICV) is missing
• BR-02 An Invoice shall have an Invoice number (BT-1).
• BR-KSA-04 Issue date is later than today

Terms on this page

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

First published 2026-10-26 · Archived copy