Simplified vs Standard Tax Invoice in Saudi Arabia

Ask a Saudi business owner what a tax invoice looks like and you will usually get one answer. ZATCA recognises two. A standard tax invoice and a simplified tax invoice carry different fields, follow different rules once you are in Phase 2 of the e-invoicing mandate, and are triggered by different customers. Issue the wrong one and the document may not be valid for your buyer's input VAT deduction — or for your own records during an audit.

This guide explains which invoice type applies to which sale, what each one has to contain, and what happens to it after you issue it. If you are still mapping out the mandate as a whole, start with our complete ZATCA Phase 2 guide and come back here for the invoice-level detail.

The two invoice types ZATCA recognises

Saudi Arabia's VAT framework, and the e-invoicing regulations built on top of it, split every taxable supply into one of two documents:

• Standard tax invoice (فاتورة ضريبية) — the full document, used mainly for business-to-business and business-to-government sales. It identifies the buyer, including their VAT registration number where they have one, and it is the document a VAT-registered buyer relies on to reclaim input VAT.
• Simplified tax invoice (فاتورة ضريبية مبسطة) — the shorter document, used for business-to-consumer sales. Think retail counters, restaurants, salons, workshops and any point-of-sale transaction where the buyer is an end consumer who will not reclaim the VAT.

The deciding factor is who the customer is, not how big the sale is or whether you print it on paper. A supply to a VAT-registered business needs a standard tax invoice even if the amount is small. A cash sale to a walk-in consumer can be covered by a simplified invoice even if it is large.

Both types are in scope of the e-invoicing mandate. Both must be generated by a compliant electronic system — a handwritten pad or a free-text word processor document does not qualify, and neither does a scanned image of one.

When to issue a standard tax invoice

Use a standard tax invoice when the buyer is a business or a government entity. In practice that covers:

• Any sale to a VAT-registered customer in Saudi Arabia.
• Sales to government bodies and public-sector entities.
• Supplies where the reverse-charge mechanism applies and the buyer accounts for the VAT.
• Exports and zero-rated supplies, where you need to evidence the treatment applied.
• Any transaction where the buyer asks for a document they can use to recover input VAT.

The rule of thumb: if your customer's accountant will ever look at this document, it should be a standard tax invoice. Getting this wrong is one of the most common sources of friction in B2B relationships — the buyer discovers at filing time that they hold a simplified receipt, cannot support the deduction with it, and asks you to reissue. That means a credit note plus a new invoice, and under Phase 2 both of those have to go through the compliance flow too.

When a simplified tax invoice is enough

A simplified tax invoice is designed for retail-speed transactions with end consumers. It does not require the buyer's name, address or VAT number, which is what makes it workable at a till. Typical cases:

• Retail and e-commerce sales to individuals.
• Food and beverage, hospitality, personal services.
• Any point-of-sale environment where the customer walks away with a printed or emailed copy immediately.

Two things are worth flagging. First, "simplified" describes the field set, not the compliance burden — a simplified invoice still has to be produced by a compliant system, still needs a QR code, and still has to reach ZATCA. Second, if a business customer identifies themselves during the transaction, you should switch to a standard tax invoice rather than issue a simplified one and patch it later.

Field by field: what each invoice must contain

The two field sets overlap heavily. The difference is concentrated in buyer identification and in the treatment of the QR code.

Common to both invoice types

• The seller's name, address and VAT registration number.
• A unique, sequential invoice number that cannot be reused.
• The date of issue, and the date of supply where it differs.
• A description of the goods or services, with quantity and unit price.
• The taxable amount, the VAT rate applied, and the VAT amount shown separately.
• The total payable including VAT.
• Amounts expressed in Saudi riyals — if you invoice in another currency, the VAT amount still has to appear in SAR at the applicable exchange rate.
• Arabic content. Arabic is the required language of the invoice; you can present it bilingually alongside English, but Arabic cannot be dropped.
• A QR code.

Additional on a standard tax invoice

• The buyer's name and address.
• The buyer's VAT registration number where the buyer is registered.
• Where relevant, other identifiers for the buyer accepted by ZATCA (commercial registration number, national ID and similar) when no VAT number exists.
• A reference to the reason for zero-rating or exemption where the supply is not standard-rated.

Not required on a simplified tax invoice

• Buyer name, address and VAT number are not mandatory, precisely because the buyer is an end consumer.

The standard VAT rate in Saudi Arabia is 15%, but zero-rated and exempt supplies exist and each has its own evidencing rules. Rates, registration thresholds and category treatments do change — confirm the current position for your sector on the ZATCA website or with your tax adviser before you configure your system.

What changes after issue: clearance versus reporting

This is the single biggest practical difference between the two types once Phase 2 applies to you.

• Standard tax invoices are cleared. Your system sends the invoice to ZATCA before you share it with the buyer. ZATCA validates it and returns a cleared version carrying its own stamp. The cleared document is the legally valid invoice — the copy you send the customer has to be that one, not your local draft.
• Simplified tax invoices are reported. You give the customer their copy immediately at the point of sale, then your system reports the invoice to ZATCA afterwards, within the window set by the regulations (24 hours from issue). Nothing blocks the sale while that happens.

The design logic is straightforward: clearance protects the input-VAT chain on B2B transactions, while reporting keeps a retail queue moving. It also means the two flows fail differently. A clearance failure stops you from issuing a valid B2B invoice at all, so it is visible immediately. A reporting failure is silent — the customer has already left with their receipt — which is why any system handling simplified invoices needs a retry queue and an alert when reporting falls behind. We cover the technical side of both flows in the Phase 2 integration requirements guide.

The QR code: required on both, but not the same

Both invoice types carry a QR code, and in both cases it encodes structured data rather than a link. On a simplified invoice the QR code is the customer's and the inspector's primary verification tool — it carries the seller's name and VAT number, the timestamp, the invoice total and the VAT amount, plus the cryptographic elements added in Phase 2. It has to be printed or displayed on the copy the customer receives.

On a standard invoice the QR code is generated as part of the clearance response. That ordering matters when you design your document template: you cannot render the final PDF, hand it to the buyer, and add the code afterwards. The document is only complete once it has been through ZATCA.

A practical consequence for anyone still working from templates: the QR code cannot be a static image dropped into a header. It is regenerated per invoice from that invoice's own data, which is one of the clearest reasons the mandate effectively rules out manual document creation. If you are moving off spreadsheets, our guide to creating professional invoices online covers what a structured billing setup gives you beyond compliance.

Credit and debit notes follow the same split

Corrections inherit the type of the document they correct. A credit note against a standard tax invoice is itself a standard document and goes through clearance; a credit note against a simplified invoice is reported like the original. In both cases the note has to reference the original invoice so the adjustment can be traced.

You cannot simply delete or overwrite an issued invoice. Once a document has been cleared or reported it exists in ZATCA's records, and the only compliant correction is a properly referenced credit or debit note. Systems that let users edit a sent invoice in place are a real liability under this regime — the same principle drives Spain's VeriFactu rules, which we compare in our VeriFactu explainer.

Common mistakes worth avoiding

• Treating small B2B sales as retail. Value does not determine the invoice type; the customer does.
• Collecting the buyer's VAT number too late. Under clearance you need it before the invoice is submitted, not at month end. Capture it when you create the customer record.
• Sending the pre-clearance copy. Automated emails that fire on invoice creation rather than on clearance response will send the wrong document. Trigger delivery on the cleared version.
• Dropping Arabic. An English-only invoice is not compliant, however complete the rest of it is.
• Showing VAT only in a foreign currency. Cross-border billing is fine, but the VAT amount belongs in SAR. If you invoice across markets, see our guide to invoicing international clients in multiple currencies.
• Ignoring the reporting backlog. Simplified invoices that never reach ZATCA are still non-compliant, even though the sale completed normally.

Frequently asked questions

Can I issue standard tax invoices for everything?

Technically a standard tax invoice contains everything a simplified one does, so it satisfies the disclosure requirements. The catch is operational: standard invoices require clearance before you hand them over, which is impractical at a retail counter, and you need buyer details you may not have. Most businesses run both.

What if a consumer asks for an invoice with their company name?

That is a signal to issue a standard tax invoice. If you have already issued a simplified one, correct it with a credit note and issue the standard invoice properly, rather than editing the original.

Does a simplified invoice need to be sent to the customer electronically?

The customer has to receive a copy, but it can be printed. What matters is that it was generated by a compliant electronic system and carries the required QR code — not the medium it is handed over in.

Do these rules apply to businesses below the VAT registration threshold?

The e-invoicing obligations attach to VAT-registered taxpayers. If you are not registered, you are not issuing tax invoices at all. Registration thresholds are set by ZATCA and are worth checking directly if your turnover is near the line.

Does my software need to know which type to issue?

Yes, and this is a good test when evaluating a system. It should decide the document type from the customer record, apply the right field set, and route the invoice to clearance or reporting automatically. If a user has to choose manually on every sale, expect errors.

Get the invoice type right, automatically

The split between standard and simplified invoices is easy to describe and easy to get wrong at volume — which is exactly the kind of rule software should enforce rather than leave to staff. Facturi handles structured invoicing, customer records with tax identifiers, sequential numbering, credit notes tied to their originals, and multi-language documents, across markets with very different compliance regimes. Start free and set your billing up once, properly.

New to structured billing altogether? Begin with what an online invoicing system actually does, then work back through the ZATCA guides above.