Choosing an E-Invoicing System in Saudi Arabia: Standard vs Simplified Invoices
Picking the right e-invoicing system in Saudi Arabia starts with one decision most owners overlook: knowing exactly when you issue a standard tax invoice and when you issue a simplified one. Get that right in 2026 and the rest of ZATCA compliance falls into place. Get it wrong and you will chase rejected invoices every month.
This article explains the two invoice types in plain language, shows how they differ, and walks through what it takes to move off Excel and paper onto a compliant cloud system.
The two invoice types ZATCA expects
The Zakat, Tax and Customs Authority built e-invoicing around two document types. Both are electronic, both apply 15% VAT, and both are mandatory under the rules that began in Phase 1 on 4 December 2021.
Standard tax invoices cover business-to-business and business-to-government sales. Under Phase 2, which has rolled out in waves since 1 January 2023, these invoices are cleared by ZATCA through the Fatoora platform before you send them to the buyer.
Simplified tax invoices cover business-to-consumer sales, such as a retail counter or a restaurant bill. They carry a QR code and are reported to ZATCA within 24 hours rather than cleared in advance.
Why the distinction matters day to day
If a shop issues a standard invoice where a simplified one was correct, or omits the buyer VAT number on a B2B document, the invoice can be rejected. A good system decides the type for you based on the customer record, so your staff do not have to memorise the rule.
Standard vs simplified: a side-by-side view
| Feature | Standard tax invoice | Simplified tax invoice |
|---|---|---|
| Typical use | B2B and B2G sales | B2C retail and services |
| Buyer VAT number | Required | Not required |
| ZATCA handling | Cleared before sharing | Reported within 24 hours |
| QR code | Optional under rules | Mandatory |
| Format | UBL 2.1 XML | UBL 2.1 XML or PDF/A-3 |
| Cryptographic stamp | Yes | Yes |
Both formats must be XML in UBL 2.1, or PDF/A-3 with embedded XML, each carrying a cryptographic stamp. When you are unsure which wave or rule applies, check ZATCA’s current wave announcements instead of relying on old blog posts.
Moving from Excel and paper to a cloud system
Many Saudi SMEs still raise invoices in Excel and keep receipts in a folder. That approach cannot produce UBL 2.1 XML, apply a stamp, or report to Fatoora, so it is no longer compliant. The migration is less painful than owners fear if you follow a clear order.
- Export your customer list and clean it: VAT numbers, Arabic and English names, and addresses.
- Separate B2B customers from B2C so the system can pick the right invoice type.
- Rebuild your product and service catalogue with correct VAT treatment.
- Import open balances so nothing is lost in the switch.
- Run a parallel week where you issue test invoices before going fully live.
Platforms like Daftarix bring customers, quotations, VAT invoices, and support into one cloud workspace, so a quotation can flow into a cleared invoice without re-keying. That single flow removes the most common source of errors.
What to look for in a vendor
- Native UBL 2.1 XML generation and the cryptographic stamp.
- Automatic QR codes on simplified invoices.
- Arabic and English interface and invoice output.
- A clear audit trail for every cleared or reported document.
- Support you can actually reach when a deadline is close.
If you bring in outside help to migrate, use reliable local experts who understand both the accounting side and the Saudi tax rules.
What integration actually involves
Phase 2 integration connects your invoicing system to the Fatoora platform so standard invoices are cleared and simplified invoices are reported automatically. Owners often imagine a heavy IT project, but for a cloud system most of the work is configuration, not coding.
The real effort sits in three places. You need accurate master data, a clear split between B2B and B2C customers, and a short testing period against the sandbox. Once those are in place, the day-to-day experience for your staff barely changes. They raise an invoice, the system picks the type, applies the format and stamp, and handles clearance or reporting in the background.
A short timeline you can plan around
- Week one: export and clean customer and product data.
- Week two: configure invoice types, VAT treatment, and branding.
- Week three: run test invoices in the sandbox and fix any rejections.
- Week four: go live, then monitor the first cleared and reported invoices closely.
If your data is already tidy, this can move faster. If it is messy, the cleanup is where you should spend your time, because clean data prevents most rejections later.
Signs it is time to replace your current process
Some businesses stay on spreadsheets long after they should have switched. Watch for these warning signs that your current process is holding you back.
- You re-type the same customer and product details for every invoice.
- You cannot produce UBL 2.1 XML or apply a cryptographic stamp.
- Month-end VAT reconciliation takes days and still has errors.
- Billing disputes get lost because invoices and conversations live in different places.
- Only one person knows how the invoicing file works.
If three or more of these sound familiar, a compliant cloud system will pay for itself quickly in saved hours and fewer rejected invoices.
How do I know which invoice type to issue?
The simplest rule: if your buyer is a VAT-registered business that needs to reclaim input VAT, issue a standard tax invoice with their VAT number. If your buyer is a consumer, issue a simplified tax invoice with a QR code. A connected system reads the customer record and applies the correct type automatically, which removes the guesswork at the counter.
Frequently Asked Questions
Do I need a different e-invoicing system in Saudi Arabia for each invoice type?
No. A single compliant system should handle both standard and simplified invoices, choosing the correct type from the customer record and applying the right format and QR code.
Is the QR code required on every invoice?
The QR code is mandatory on simplified tax invoices. Standard invoices follow the clearance process. You can confirm the current technical requirements on the official ZATCA e-invoicing portal.
Can I still issue paper receipts?
Paper or free-text PDFs do not meet the structured XML and stamping rules. You must generate compliant electronic invoices, though you can print a copy for the customer.
What VAT rate applies?
The standard VAT rate in Saudi Arabia is 15%. Your system should calculate and round it correctly on every line.
Make the right choice before your deadline
A compliant e-invoicing system in Saudi Arabia should make the standard versus simplified decision for you, generate the correct XML and QR code, and keep a clean audit trail. Clean your data, separate your customer types, and test before you go live. To see how one connected platform handles both invoice types from a single customer record, book a demo and request a quote from Daftarix.
