# Fatoora errors: why your invoice was rejected and how to fix it

> Fatoora rejects a document when a check fails and accepts it with a warning when the failure is not fatal. ZATCA, the Zakat, Tax and Customs Authority, documents these categories.

- **URL:** https://www.snad.io/en/zatca/fatoora-errors
- **Official sources:** https://zatca.gov.sa/ar/E-Invoicing/SystemsDevelopers/Documents/20230519_ZATCA_Electronic_Invoice_XML_Implementation_Standard_%20vF.pdf · https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-invoicing-Detailed-Technical-Guideline.pdf
- **Accessed:** 2026-11-17

This page explains the official standard and does not replace it. Read the error message in the platform response: it is the reference.

## Three possible outcomes for every document

The platform checks syntax first (well-formed XML that follows UBL 2.1), then content: EN 16931 rules, then the Saudi rules. It returns one of three outcomes.

- **Valid — No error and no warning:** For a standard (B2B) invoice the platform returns the document stamped with a QR code. For a simplified (B2C) one it returns a confirmation that it is valid.
- **Accepted with warnings (202) — Accepted, with at least one warning:** The document is accepted, so do not resubmit it. Read the warning and fix its cause: repeated non-compliance is investigated and may carry penalties.
- **Rejected — One error rejects the whole document:** A standard (B2B) invoice that was not cleared is not a valid tax invoice. Fix the cause and send a new document, as in the section below.

## Rule categories: meaning, cause and fix

The table selects commonly hit rules; the standard has further families (BR-KSA-EN16931-nn, BR-KSA-F-nn, BR-KSA-CL-nn, BR-KSA-DEC-nn) with the same meaning structure. Causes are our reading, not the standard's text.

### Seller VAT number and identifier

- **Official rule IDs:** BR-KSA-39 · BR-KSA-40 · BR-KSA-08
- The seller needs a 15-digit VAT number that starts and ends with 3, and exactly one seller ID with an approved scheme: CRN, MOM, MLS, 700, SAG or OTH.
- **Usual cause:** A short number or one not starting and ending with 3, two seller IDs, or symbols beyond letters and digits.
- **Fix:** Correct the VAT number in the organization profile and keep one seller ID with a scheme from the list, using letters and digits only.

### Buyer name and VAT number

- **Official rule IDs:** BR-KSA-42 · BR-KSA-44 · BR-KSA-46 · BR-KSA-14
- A tax invoice and its notes need the buyer name. A buyer VAT number has 15 digits starting and ending with 3, and is not allowed on an export invoice.
- **Usual cause:** An empty buyer name, an incomplete VAT number, a VAT number on an export invoice, or a buyer not registered for VAT and given no ID.
- **Fix:** Enter the buyer's official name. If the buyer is not VAT-registered, give an ID with an approved scheme such as NAT, IQA or CRN.

### National address

- **Official rule IDs:** BR-KSA-09 · BR-KSA-37 · BR-KSA-66 · BR-KSA-10 · BR-KSA-63 · BR-KSA-67
- The seller address needs street, building number (4 digits), postal code (5 digits), city, district and country. A buyer in Saudi Arabia needs the same fields.
- **Usual cause:** A missing address field, a postal code that is not five digits, or a building number that is not four.
- **Fix:** Complete the national address for your organization and for the customer as registered, and check the digit count of building number and postal code.

### Totals, VAT and rounding

- **Official rule IDs:** BR-CO-13 · BR-CO-14 · BR-CO-15 · BR-CO-16 · BR-CO-17 · BR-S-08 · BR-S-09 · BR-KSA-51 · BR-DEC-12
- Every total equals its formula: total without VAT + VAT = total with VAT. Each category's VAT = taxable amount × rate ÷ 100, to two decimals at most.
- **Usual cause:** Rounding that differs between line and invoice, a discount or charge left out of the category taxable amount, or totals computed from numbers other than those sent.
- **Fix:** Compute VAT on each category's taxable amount, round it to two decimals, then derive every total from the same rounded numbers you send in the file.

### VAT category and exemption reason

- **Official rule IDs:** BR-KSA-18 · BR-KSA-23 · BR-KSA-69 · BR-KSA-24 · BR-KSA-11 · BR-KSA-25 · BR-KSA-49
- The VAT category is S, Z, E or O. Exempt, zero-rated and not-subject lines each need a reason code, and category O takes a zero rate if one is given.
- **Usual cause:** An unapproved category, an exemption with no reason code, or an education or health exemption (VATEX-SA-EDU, VATEX-SA-HEA) with no national ID for the buyer.
- **Fix:** Pick the right category per line and attach the reason code to every exemption or zero rate. For education and health, attach the buyer's national ID.

### Credit and debit notes

- **Official rule IDs:** BR-KSA-17 · BR-KSA-56 · BR-55
- A credit note (381) or debit note (383) needs the reason for issuing it and a reference to the original invoice number.
- **Usual cause:** A note issued with no reason text, or with no original invoice number.
- **Fix:** Write the reason and reference the original invoice number. Our article on the two notes, at the bottom of this page, covers the difference.

### Counter, UUID and hash chain

- **Official rule IDs:** BR-KSA-03 · BR-KSA-33 · BR-KSA-34 · BR-KSA-61 · BR-KSA-26
- Each document has a unique UUID, a counter (ICV) of digits only, and the previous document hash (PIH) as base64 SHA-256. The first document uses a fixed starting hash.
- **Usual cause:** A document reusing a counter or UUID used before, or a previous hash computed on a document other than the one generated just before.
- **Fix:** Give every document, resubmissions included, a new UUID and counter, and a previous hash equal to the hash of the last document generated before it.

### QR code, signature and stamp

- **Official rule IDs:** BR-KSA-27 · BR-KSA-28 · BR-KSA-29 · BR-KSA-30 · BR-KSA-60
- The QR code is required, base64-encoded. The signature block carries exact text values, and a simplified invoice needs your own cryptographic stamp.
- **Usual cause:** A signature with identifiers or a method other than those specified, a simplified invoice with no stamp, or a signature made with an invalid certificate.
- **Fix:** Use the signature values the standard specifies, character for character, and complete onboarding to get a valid CSID certificate before sending.

### Dates, times and currency

- **Official rule IDs:** BR-KSA-04 · BR-KSA-70 · BR-KSA-15 · BR-KSA-35 · BR-KSA-36 · BR-KSA-68
- The issue date cannot be after today, and the issue time is required as hh:mm:ss. A tax invoice also needs a supply date and a tax currency code.
- **Usual cause:** An issue date after today, a missing issue time or supply date, or a supply end date earlier than the supply date.
- **Fix:** Generate the issue date and time from an accurate clock at creation, and fill the supply date and tax currency on every tax invoice.

### Invoice type and transaction code

- **Official rule IDs:** BR-KSA-05 · BR-KSA-06 · BR-KSA-07 · BR-KSA-31
- The invoice type code comes from an approved set. The 7-digit transaction code follows NNPNESB: type, third party, nominal, export, summary, self-billed.
- **Usual cause:** A wrong value in one digit of the transaction code, self-billing on an export invoice, or a simplified invoice with an option it does not accept.
- **Fix:** Check the seven transaction-code digits against the document type, and for a simplified invoice use only the options accepted for it.

> ZATCA treats some errors as warnings without rejecting the document (exception handling). Check in the response whether the rule came back as an error or a warning.

## After a rejection: what to do and what not to do

A summary of ZATCA's own FAQ on resubmitting a rejected document.

1. **Read the whole platform response:** The response lists every error and warning with its message. Do not resubmit before you know which rule failed.
2. **Fix the cause at the source:** Correct the document data or the organization settings. The counter and hash of the rejected document are never changed.
3. **Send a new document:** Resubmit as a new document with a new UUID, counter, hash and timestamp. ZATCA's FAQ also allows cancelling the invoice by credit note and issuing a new one.
4. **Point the previous hash at the last document generated:** The previous hash is the hash of the document generated just before it, even if that one was rejected, because the platform records rejected hashes.
5. **The date, for the two invoice types:** For an uncleared standard (B2B) invoice the new invoice gets an updated date. A simplified invoice keeps the original transaction date, and no second invoice goes to the customer.

Test before sending with ZATCA's tools: the Compliance and Enablement Toolbox (SDK or web validator) and the integration sandbox.

## What Snad does when ZATCA responds

For every document it sends, Snad keeps the attempt history and ZATCA's responses to each attempt.

**In Snad**

- Shows ZATCA's response to each attempt as it arrived: errors, warnings and notices, with the response status code.
- Checks the VAT number, organization currency and country, and certificate validity before sending, and writes the reason and how to fix it.
- Groups failures under a “Failed invoices” filter, marks documents that used up their attempts as “Permanently failed”, and retries the failed ones only.
- Tells you when the national address or commercial registration is incomplete, since ZATCA attaches a warning to every invoice until it is.
- Lets you download the XML and PDF/A-3 of each document.

**Not in Snad**

- Shows ZATCA's message as it came and does not explain the rule ID in it. Use the categories on this page for its meaning.

## Questions about rejected invoices

### What is the difference between an error and a warning on Fatoora?

An error is a failed check on a rejected document, and one error rejects the whole document. A warning is a failed check on an accepted document.

### Should I resubmit an invoice answered “202 accepted with warnings”?

No, ZATCA accepted it. But fix the cause of the warning soon: repeated non-compliance is investigated and may carry penalties.

### Can I edit the rejected invoice and send it with the same counter?

No. Send a new document with a new UUID, counter, hash and timestamp. A counter or UUID is not reused and the rejected document's hash is not changed.

### Reporting of a simplified invoice I gave the customer was rejected. What now?

Fix the error and report a new document with the original transaction date. No second invoice is needed for the customer, and the transaction goes into the VAT return.

### Do I include a rejected invoice in my VAT return?

You may have to. A technical fault in the XML does not cancel the transaction, and VAT is due whether or not a valid invoice was issued.

### What happens if I sign an invoice with an invalid certificate?

The invoice is rejected. Complete onboarding to get a valid CSID certificate; it is issued once at onboarding, not with each invoice.

## Related pages and tools

- [E-invoicing and ZATCA requirements](https://www.snad.io/en/zatca) — Phases, waves and the difference between clearance and reporting
- [Wave 25: who is covered and by when?](https://www.snad.io/en/zatca/wave-25) — Check whether your organization is in the wave
- [Tax invoice generator](https://www.snad.io/en/tools/invoicing/invoice-generator) — A tax invoice as a PDF with a QR code
- [Credit note generator](https://www.snad.io/en/tools/invoicing/credit-note-generator) — A credit note referencing the original invoice
- [Credit notes vs debit notes: a ZATCA compliance guide](https://www.snad.io/en/blog/credit-and-debit-notes-guide-zatca) — When each note is issued and the data it needs

---
## About the publisher
**Snad (سند)** — a private Saudi software company
based in Madinah, founded 2025. Legal form: Sole proprietorship.
Commercial registration: 7038154642
VAT number: 310959226500003
Only official domain: snad.io
> Snad is a private commercial business-management platform. It is not a
> government body, not a bank, and not a government services portal, and it
> is not affiliated with any government entity. Any site or app with a
> similar name is unrelated to Snad.