Error 1001: Seller VAT Number Is Invalid (ZATCA Fatoora)

When you submit your e-invoice to the Fatoora platform run by the Zakat, Tax and Customs Authority (ZATCA), the system may return a rejection message carrying the code 1001 with the description “Seller VAT number is invalid.” This code does not mean your accounting system has broken down; it means the VAT number registered for your business (you, the seller) does not match the format ZATCA requires, or does not match the certificate used to sign the invoice. The result is the same: the invoice is not cleared, and you cannot legally hand it to the customer until you fix the cause.

In this guide we focus on this error alone. We will explain what the correct seller VAT number is, why ZATCA rejects it, how to pinpoint the exact cause in minutes, how to fix it step by step, and how to prevent it from recurring. The goal is for you to leave this page with an accepted invoice, not to collect general information.

What does “Seller VAT number is invalid” mean?

The seller VAT number is your business’s VAT registration number, known for short as the VAT number or the business VAT number. In e-invoicing, this number is embedded in the invoice file in a field dedicated to the seller. The Fatoora platform validates this field before clearing the invoice, so if it finds the number does not match the approved rules, it responds with code 1001 and rejects the invoice.

The rejection here happens at the data-validation level, meaning the invoice reached ZATCA but did not pass the VAT number validity check. This error is therefore classified among the validation errors the platform checks before clearance. It is part of the broader group of ZATCA e-invoicing errors you may encounter during integration.

It is issued to every taxpayer who exceeds the mandatory VAT registration threshold, which is SAR 375,000 in annual taxable revenue. After registration, ZATCA issues the business a registration certificate carrying the VAT number. This number is what must appear in the seller field inside every e-invoice. That is why the registration certificate is the only trusted reference for your correct number, not any other source.

An important distinction here: code 1001 concerns the sellerVAT number, that is, your own number as the invoice issuer. If the error relates instead to the buyer’s VAT number in business invoices, that is a different error with a separate code and description (code 1002: buyer VAT number is missing). We explain the difference between them in a later section, but our main focus on this page is the seller VAT number only.

The practical difference between a rejection at the validation level and a rejection at a deeper level is worth clarifying. When your invoice is rejected with code 1001, it means the invoice’s overall structure is sound and the platform received it and began checking its fields, but it stopped at the seller VAT number field because it did not pass the validity rule. In other words, the problem is confined to a single field, not to the entire invoice makeup. This distinction matters because it saves you needlessly reviewing the rest of the fields and directs your effort straight to the VAT number.

Where the VAT number is stored in your system

Before fixing it, it helps to know that the seller VAT number is not usually written on each invoice separately; it is saved once in the business settings, then inserted automatically into every invoice you issue. This means a single mistake in the settings will show up on all your invoices, not on a single one. The good news is that a single correction in the right place solves the problem for all subsequent invoices at once.

On the invoice itself, the seller VAT number sits inside the supplier data or selling-party section. That is why the rejection message points to the exact field location inside the invoice file, as we will see in the response example later. Knowing this location helps your technical team if you need to trace the source of the value.

The correct VAT number format in Saudi Arabia

ZATCA enforces a specific, fixed format for the VAT number. Any number that does not match this format exactly is rejected with code 1001. The basic rule:

• The number consists of exactly 15 digits , no more and no less.
• The first digit starts with 3.
• The last digit ends with 3 as well.
• All digits are numbers only, with no spaces, dashes, or letters.

An example of a correctly formatted number: 300000000000003. Notice that it starts with 3, ends with 3, and consists of 15 digits. Any number that violates one of these four rules will be rejected, even if your business’s actual number is correct in the register but was entered in the wrong format.

The VAT number structure, visually

Common format mistakes

Most cases of code 1001 do not arise from a completely wrong number, but from a simple input mistake. The most prominent of these mistakes:

• Too few or too many digits: entering 14 digits or 16 digits instead of 15.
• Wrong start or end: a number that does not start with 3 or does not end with 3, which often happens when the VAT number is mixed up with another number such as the commercial registration.
• Hidden spaces present: a space at the start or end of the number when copied and pasted from another file.
• Arabic-Indic digits: entering the digits in Indic form instead of Western numerals (0 to 9), which some systems do not accept.
• Mixing the VAT number with another number: entering the commercial registration number or the business unified number instead of the VAT number.

Why does ZATCA reject the invoice with this code?

Rejection with code 1001 happens for one of two main reasons, and it is important to determine which applies to your case because the solution differs:

Reason one: an error in the number format

The number entered in your business settings does not match the approved format (15 digits, starts with 3 and ends with 3). This is the most common reason, and it is usually a human input error that occurred when the system was first configured. The solution here is to correct the number in the settings.

This error most often occurs at specific moments: when the system is first set up, when data is migrated from an old system to another, or when business data is edited manually. In all these moments, a human hand intervenes in entering the number, and with it the possibility of error enters. The simplest prevention, therefore, is to review the number digit by digit after any input or data migration, before issuing the first invoice.

Reason two: the number does not match the signing certificate

In the second phase of e-invoicing, every invoice is digitally signed using the Cryptographic Stamp Identifier (CSID) certificate issued by ZATCA. This certificate is tied to a specific VAT number. If the VAT number entered in the system does not match the number tied to the certificate, the platform rejects the invoice because the seller identity declared in the invoice differs from the seller identity in the certificate. This reason is less common, but it happens when the certificate is renewed or when another business’s certificate is used by mistake.

Qoyod manages the Cryptographic Stamp Identifier (CSID) certificate constraints automatically, reducing the likelihood of this conflict, but it remains essential to make sure the VAT number in your settings is the same one registered with ZATCA when the certificate was issued.

To understand this reason well, remember that the Cryptographic Stamp Identifier certificate acts as a digital identity for your business before the platform. Every invoice is signed with this certificate, and the signature carries within it the VAT number tied to it. When the invoice reaches the platform, the platform compares the number written in the seller field with the number embedded in the signature. If they differ, the platform considers there to be a contradiction in the seller identity and rejects the invoice. This design protects against impersonation of businesses, but it also means that any change in the VAT number must be reflected in the certificate as well.

When does this conflict happen in practice? Most often in three cases: when the VAT registration is renewed and the number changes, when another business’s certificate is used by mistake in a multi-business environment, or when the certificate expires and an old copy is used. In each case, the solution is to realign the VAT number with the correct, valid certificate.

The 1001 rejection paths

How to pinpoint the exact cause

Before you correct anything, determine the cause precisely so you do not treat the symptom without the root of the problem. Follow these steps in order:

1. Read the full rejection message: code 1001 comes with a text description that clarifies whether the rejection is due to the format or due to a mismatch with the certificate. Do not rely on the code alone.
2. Check the number in the business settings: go to the e-invoicing settings in your system and count the digits of the VAT number. Make sure they are 15 digits, starting with 3 and ending with 3.
3. Match the number against the VAT certificate: open the registration certificate issued by ZATCA and compare the number digit by digit with what is entered in the system.
4. Check for hidden spaces or characters: delete the number and retype it manually instead of copying and pasting it, to avoid invisible spaces.
5. Review the certificate status: if the format is sound but the rejection persists, the cause is most likely the number not matching the CSID certificate. Check that the certificate in use belongs to your business and has not expired.

Reading the message’s text description is the fastest route to diagnosis. A description such as “the format is incorrect” points you to the first reason, while a description referring to a mismatch in the seller identity points you to the second reason.

If you want a diagnosis in under two minutes, always start from the simplest toward the most complex. The first thing you check is the number of digits: are they exactly 15? Then the start and end: does it start with 3 and end with 3? Then the hidden spaces: retype the number manually. These three checks reveal more than nine out of every ten cases. But if the number passes these three checks and the rejection remains, only then move to checking the certificate, because it is the least common reason and the most complex to solve.

Avoid the common diagnostic mistake: changing the number randomly hoping it will pass. The VAT number is a single official value that is not guessed but taken from the registration certificate. Any attempt to edit it without referring to the certificate may produce a number that is correctly formatted but does not belong to your business, and this puts you in a more complex problem than code 1001 itself.

The step-by-step solution

After determining the cause, apply the appropriate solution. We present both paths here.

If the cause is a format error

1. Log in to your accounting system and go to the business settings or the e-invoicing settings.
2. Open the seller VAT number field.
3. Delete the current value entirely.
4. Enter the correct number from the VAT registration certificate manually: 15 digits, starting with 3 and ending with 3, Western numerals only with no spaces.
5. Save the settings.
6. Reissue the rejected invoice and resend it to the Fatoora platform.

If the cause is a mismatch with the certificate

1. First make sure the VAT number in the settings has the correct format and matches the registration certificate.
2. Review the Cryptographic Stamp Identifier (CSID) certificate used in signing, and make sure it was issued to your business with the same VAT number.
3. If you have renewed your VAT registration or changed your business data with ZATCA, you may need to reissue the certificate to match the new number.
4. After the number matches the certificate, reissue the invoice and send it.

In the vast majority of cases the cause is of the first type, and it is solved by a simple correction in the settings that takes only minutes.

A practical example of a real-world case

Let’s take a common case. A commercial business entered its VAT number when configuring the system by copying it from an old email. The number in the email was written with a space at its start due to formatting, so its length became 16 digits instead of 15 after pasting. The system saved the value as is, and when the first invoice was issued the platform responded with code 1001 and a description indicating that the number format is incorrect.

On diagnosis, the accountant opened the business settings and counted the digits, finding 16 digits instead of 15. He deleted the value entirely and typed the number manually from the official VAT registration certificate: 15 digits starting with 3 and ending with 3 with no spaces. He saved the settings, then reissued the invoice and sent it. This time the platform cleared it immediately. The lesson here: do not copy the VAT number from unofficial sources, and type it manually from the approved certificate.

Another, less common case: a business renewed its VAT registration and its number changed, but it updated the number in the system and forgot to reissue the Cryptographic Stamp Identifier (CSID) certificate. The format of the new number was sound, but the certificate was still tied to the old number, so code 1001 appeared with a description referring to a seller identity mismatch. The solution was to reissue the certificate to match the new number, after which the invoices passed without rejection.

An example of the error message

When the invoice is rejected, the Fatoora platform returns a structured response containing the error code, its description, and the location of the problem. The following is an illustrative example of the response shape for code 1001:

{
  "validationResults": {
    "status": "ERROR",
    "errorMessages": [
      {
        "type": "ERROR",
        "code": "1001",
        "category": "SELLER_VAT_NUMBER",
        "message": "Invalid seller VAT registration number.",
        "field": "Invoice/AccountingSupplierParty/Party/PartyTaxScheme/CompanyID"
      }
    ]
  }
}

Read the following fields for a quick diagnosis: the value of code equals 1001, andcategory points to the seller VAT number, andfield specifies the location of the number inside the invoice file. The description in message confirms that the rejection is due to an invalid seller VAT registration number.

Valid number vs. rejected number

How to prevent the error from recurring

Correcting a single invoice is easy, but permanent prevention saves you from repeating the problem with every batch of invoices. Follow these practices:

• Enter the number once, accurately: when configuring the system, copy the number from the official registration certificate and verify it digit by digit before saving.
• Adopt a system that validates the format automatically: systems that check the number of digits and its start and end before sending prevent code 1001 from the outset.
• Unify the number across all templates: make sure the VAT number is fixed in the business settings and is not written manually on every invoice.
• Monitor the certificate validity: renew the Cryptographic Stamp Identifier (CSID) certificate before it expires, and make sure it is tied to the correct VAT number.
• Update the data on any change: if your VAT registration changes with ZATCA, update the number in the system immediately before issuing new invoices.

Businesses that rely on an accounting system that manages the VAT number and the certificate together rarely face this error, because the system aligns both fields before sending to the platform.

Extra precautions when migrating systems

If you are moving from one accounting system to another, this moment is the most exposed to code 1001. During migration, the business data is transferred, including the VAT number, and an error may occur in the transfer, or a space may slip in, or part of the number may be truncated. To avoid this, do not rely on the automatic transfer alone. After the migration is complete, open the business settings in the new system and verify the VAT number manually before issuing any actual invoice.

Also, issue a single test invoice after any major change to the system, and make sure it is cleared before issuing a batch of real invoices. A single test invoice reveals the VAT number error immediately and saves you from having dozens of invoices rejected at once. This is a simple step but it prevents the most annoying cases of code 1001.

The difference between code 1001 and code 1002

Many people confuse code 1001 with code 1002 because both relate to the VAT number, but the difference between them is fundamental and determines where to look for the solution:

• Code 1001: concerns the VAT number seller, that is, your own business number. The cause is a wrong format in your settings or a mismatch with the signing certificate. Place of fix: your business settings.
• Code 1002: concerns the VAT number the buyer VAT number missing in business invoices. The cause is that an invoice directed to a business registered for VAT was issued without the buyer number. Place of fix: the customer data in the invoice.

The simplified rule: if the error is in your own number as the seller it is 1001, and if it is in your customer’s number as the buyer it is 1002. Identifying the party with the problem is the first step in correct diagnosis, and it saves you from searching in the wrong place.

Where this error sits among e-invoicing errors

Code 1001 is not the only error you may encounter. It is classified among the data-validation errors, a group of errors in which the platform checks the validity of the invoice content before clearance. To understand the full picture and the other error types, see the guide ZATCA e-invoicing errors, and the guide validation errors, in addition to the e-invoicing learning hub that brings together the integration and connectivity guides in one place.

To learn how to issue compliant invoices from the outset, see the page Qoyod e-invoicing.

Why you must not ignore this error

Code 1001 may seem like a small technical problem, but its practical impact is greater than some think. A rejected invoice is not a cleared invoice, and this means you have not issued a legal document to the customer. In business invoices that require immediate clearance from the platform, you cannot hand the invoice to the customer before it is cleared, so proof of sale is delayed and collection may be delayed with it.

Over the longer term, accumulating rejected invoices disrupts your accounting records and makes it harder to reconcile sales with tax returns. Every stuck invoice is revenue not yet documented legally. And because the VAT number is a fixed error in the settings, ignoring it means rejecting every subsequent invoice, not a single one. It is therefore preferable to handle it as soon as it appears, because the correction takes minutes while postponing accumulates a problem that widens with each day.

The practical bottom line: handle the VAT number in its correct place once, verify it from the official registration certificate, and issue a test invoice to confirm clearance. With these three steps you close the door on code 1001 permanently.

Frequently asked questions

What does code 1001 mean in e-invoicing?

It means the VAT number registered for your business as the seller is invalid. Either its format is wrong (not 15 digits, or does not start with 3 and end with 3), or it does not match the number tied to the invoice signing certificate. The result is that the platform rejects the invoice before clearing it.

How many digits does the correct VAT number have?

The VAT number in Saudi Arabia consists of exactly 15 numeric digits, starting with the digit 3 and ending with the digit 3, without spaces or letters. Any deviation from this format causes rejection with code 1001.

I entered the correct number and the invoice is still rejected, what is the reason?

If you have confirmed that the format is correct, the reason is most likely that the number does not match the Cryptographic Stamp Identifier (CSID) certificate used in signing. Verify that the certificate was issued to your business with the same VAT number and has not expired. You may need to reissue the certificate if you have changed your registration data.

Does code 1001 concern the seller number or the buyer number?

It concerns the seller VAT number, that is, your own business number as the invoice issuer. Errors related to the buyer VAT number in business invoices have a separate code and description.

Does Qoyod solve this error automatically?

Qoyod validates the VAT number format and manages the Cryptographic Stamp Identifier (CSID) certificate automatically, reducing the likelihood of this error from the outset. But the correctness of the number entered in the settings remains your responsibility, as it must match what is registered with ZATCA.

Do I need to reissue the invoice after correcting it?

Yes. The rejected invoice is not cleared, so after correcting the VAT number in the settings, reissue the invoice and resend it to the Fatoora platform for clearance.