Bee Aura Tech Corporation

Free Assessment
Free Assessment

E-Invoicing Saudi Arabia: ZATCA Fatoora Phase 2 & Wave 25

Saudi e-invoicing, cleared by ZATCA before your customer sees it

الفوترة الإلكترونية — المرحلة الثانية (الربط والتكامل)

Wave 25 has pulled businesses with just SAR 187,500 in revenue into Phase 2. Whether you are integrating with Fatoora for the first time or leaving a provider you have outgrown, Bee Aura Tech connects your system to ZATCA from any ERP, POS, or no system at all.
Clearance, reporting, cryptographic stamping and QR codes, handled. Your finance team keeps working the way it does today.
Check if you are in Wave 25
E-invoicing Saudi Arabia ZATCA Fatoora Phase 2 Wave 25
ZATCA
ZATCA-SUBMITTED
e invoicing saudi arabia
Tax

Live

in the Kingdom today

Clearance &

reporting APIs

CSID

onboarding done for you

Any ERP

or POS

New, or switching

Get integrated, or get a better deal

If ZATCA has notified you for Wave 25, the integration date is fixed and it will not move for you. We confirm your wave, onboard your invoicing units, test against ZATCA’s simulation environment and go live before your date. Already integrated and paying too much, or waiting days for support? Your stamps are registered under your own Fatoora account, not your vendor’s moving to us is smaller than your first integration was.

See how it works
How switching works

Instant estimate · takes 20 seconds

See your cost and what you could save

B Invoice · technical architecture

How an invoice travels from your system to ZATCA

Seven steps, fully automated. Your ERP or POS posts the invoice; we check it, route it to the right Fatoora rail, stamp it, send it, read ZATCA’s answer and post the result back to your ledger without anyone in finance opening the Fatoora portal.

Your systems

Oracle Fusion · EBS

SAP S/4HANA · ECC

Dynamics 365

Infor · NetSuite

Odoo

Zoho · QuickBooks

POS & retail tills

API · SFTP · Excel

Read & check

  • Data pulled from your system
  • Seller & buyer VAT numbers validated
  • 15% VAT, zero-rated & exempt reasons checked
  • Arabic fields and SAR totals confirmed
  • Errors sent back to you before ZATCA sees them

Errors caught early

Routed to the right rail

Standard tax invoice

B2B & B2G → Clearance

Simplified tax invoice

B2C → Reporting

Credit & debit notes

Linked to the original

Each type follows ZATCA's own rules

Built & stamped

UBL 2.1 XML

UUID per invoice

Hash chain + counter

Cryptographic stamp (CSID)

TLV QR code

PDF/A-3 with XML

To ZATCA's technical specification

Sent to ZATCA Fatoora

Clearance API

Cleared before the buyer receives it

Reporting API

Cleared before the buyer receives it

Automatic retries

If Fatoora is slow or down

Real-time, over secure API

Reply checked

  • Cleared, reported or rejected status received
  • Warnings fixed before they become violations
  • ZATCA-stamped XML returned for standard invoices
  • Counts matched to your ledger
  • Archived for the statutory period

Proof you complied

Back in your system

Oracle Fusion · EBS

SAP S/4HANA · ECC

Dynamics 365

Infor · NetSuite

Odoo · Zoho · QuickBooks

POS & retail tills

Cleared invoice & QR posted against the record

THROUGHOUT Nobody in finance changes how they work · Every step logged · Failed invoices retried automatically · Live status at all times

The rule, in plain terms

Saudi E-Invoicing Clearance vs Reporting

Two kinds of invoice, two different journeys

Phase 2 splits every invoice you issue into one of two tracks. Get the track wrong and the invoice is wrong, however good it looks on paper. A PDF your customer can open is not, on its own, a valid tax invoice anymore the structured XML behind it is.

Standard tax invoice · B2B & B2G

Clearance

ZATCA approves it first. Your buyer gets it second.

  1. Your system generates the XML invoice.
  2. It goes to Fatoora for validation in real time.
  3. ZATCA clears it and applies its own stamp.
  4. Only then is it shared with your buyer.

Simplified tax invoice · B2C

Reporting

Your customer gets it now. ZATCA gets it within 24 hours.

  • Your till or system issues the invoice with a QR code.
  • The customer walks away with it immediately.
  • The invoice is reported to Fatoora within 24 hours.
  • Rejections come back to you for correction.

What makes Phase 2 technical.

Every invoice carries a UUID, an invoice counter and the hash of the invoice before it, so the chain cannot be edited without it showing. It is sealed with a cryptographic stamp tied to a CSID a certificate each of your invoicing units receives when it is onboarded through your Fatoora portal. That is why deleting or changing an invoice after issuance is treated as one of the most serious violations: the maths makes it detectable.

E-Invoicing Saudi Arabia

Saudi E-Invoicing Requirements : What Businesses Need to Prepare

Saudi Arabia e-invoicing requires businesses to use an electronic invoicing solution that meets the applicable ZATCA requirements. Phase 2 adds integration with the Fatoora platform, structured invoice formats, additional invoice data and technical requirements for connected invoicing systems.

01 - The keys are in your Fatoora account

Confirm that your business is subject to Saudi VAT and falls within the scope of the ZATCA e-invoicing regulations.

02 - Electronic Invoice Generation

Generate and store invoices electronically using an e-invoicing solution that meets the applicable ZATCA requirements.

03 - Fatoora Integration

For Phase 2, your e-invoicing solution must integrate with ZATCA’s Fatoora platform through the required technical connection. Zatca

04 - Structured Invoice Data

Phase 2 invoices must follow the required electronic format and contain the applicable mandatory and additional data fields. ZATCA’s technical guidance specifies XML requirements for Phase 2 tax invoices. Zatca

05 - Cryptographic Security

Your invoicing solution must support the applicable cryptographic and security requirements, including the Cryptographic Stamp Identifier (CSID) for onboarded invoicing units. Zatca

06 - QR Code

Invoices must include the applicable QR code requirements. ZATCA’s Phase 1 and Phase 2 requirements include QR-code requirements as part of compliant electronic invoicing. Zatca

07 - Clearance or Reporting

Depending on the invoice type, documents follow either the clearance or reporting process through Fatoora. Standard tax invoices are subject to clearance, while simplified tax invoices follow reporting requirements. Zatca

08 - ERP, POS or Accounting Integration

Connect your existing ERP, POS or accounting system to your e-invoicing workflow so invoice data can be validated and submitted without replacing your core business system.

09 - Invoice Records & Audit Trail

Maintain electronic invoice records and transaction data in accordance with the applicable Saudi e-invoicing requirements.

10 - Check Your ZATCA Wave & Deadline

Maintain electronic invoice records and transaction data in accordance with the applicable Saudi e-invoicing requirements.

Saudi E-Invoicing

Saudi E-Invoicing Readiness Checklist

Before starting your ZATCA integration, use this checklist to identify the main areas your finance and IT teams should prepare.

VAT registration details configured

Your legal entity, VAT number and business information are correctly configured.

Electronic invoice generation

Your current system can generate compliant electronic invoices.

Fatoora integration

Every rejection and warning comes back with the reason in plain language, routed to the person who can fix it  not buried in a log.

Structured invoice data

Inbound invoices from your suppliers validated against ZATCA’s rules and matched to purchase orders, with AI extraction for anything still arriving as PDF

CSID & cryptographic setup

Your invoicing units are prepared for the applicable cryptographic requirements.

QR code requirements

Your invoices generate the applicable QR code information.

Clearance / reporting workflow

Your system can handle the applicable ZATCA clearance or reporting process.

ERP / POS integration

Your existing ERP, accounting or POS system can exchange invoice data with the e-invoicing platform.

Invoice status handling

Your existing ERP, accounting or POS system can exchange invoice data with the e-invoicing platform.

Wave & deadline confirmed

Your business has checked its ZATCA notification, applicable wave and integration deadline.

Need help checking your current setup?

Before starting your ZATCA integration, use this checklist to identify the main areas your finance and IT teams should prepare.

ZATCA WAVE 25

ZATCA Wave 25: Check Your Saudi E-Invoicing Deadline

ZATCA announced Wave 25 on 24 July 2026. The wave covers taxpayers whose VAT-subject revenue exceeded SAR 187,500 during any one of 2022, 2023, 2024 or 2025. Targeted taxpayers must integrate their e-invoicing solution with the Fatoora platform no later than 1 February 2027. Zatca

SAR 187,500

VAT-subject revenue threshold used for Wave 25 selection.

2022–2025

Revenue from any one of these years can meet the announced selection criterion.

1 February 2027

Confirm that your business is subject to Saudi VAT and falls within the scope of the ZATCA e-invoicing regulations.

Check Your Wave 25 Readiness

Where you stand

The wave you fall into is set by your revenue

Phase 2 started with the Kingdom’s largest companies in 2023 and has stepped down, wave by wave, to small businesses. ZATCA notifies each wave at least six months before its integration date and the test is whether you crossed the threshold in any one of the listed years, not all of them.

Stage
Who is in scope
Integrate by
Status
Phase 1 — Generation
All VAT-registered taxpayers
4 Dec 2021
In force. Electronic invoices only.
Phase 2 — Wave 1
VAT-subject revenue above SAR 3 billion
1 Jan 2023
Live
Waves 2 to 22
Thresholds stepped down through 2023–2025
Various
Live
Wave 23
Above SAR 750,000 in 2022, 2023 or 2024
31 Mar 2026
live
Wave 24
Above SAR 375,000 in 2022, 2023 or 2024
30 Jun 2026
Live. Enforcement from 1 July 2026.
Wave 25 Now
Above SAR 187,500 in any of 2022–2025
1 Feb 2027
Notifications going out. Integrate now.
Future waves
To be announced by ZATCA
6+ months' notice
ContentWatch for your notification.

Not notified yet?

The notice goes to the email and phone registered on your ZATCA account, so an out-of-date contact can mean a deadline you never saw. Check your Fatoora portal access now, and look at every year from 2022 to 2025  one strong year is enough to put you in scope.

Changing provider, without a gap

Switching Your Saudi E-Invoicing Provider

Moving off your current e-invoicing provider is smaller than you think

Plenty of businesses integrated in a hurry to hit their wave date, often with whatever their accounting software bundled in. If yours is expensive, slow to answer when an invoice is rejected, or struggles with volume at month-end, you can move and you keep control the whole way.

Why you are not locked in

The keys are in your Fatoora account

Invoicing units are onboarded with a one-time password generated inside your own Fatoora portal. Your vendor cannot onboard, or hold on to, anything without you.

ZATCA already holds your history

Every invoice you have cleared or reported already sits with ZATCA. We import your own archive as well, so your retention obligation continues without a break.

No double submission, no gap

We prove the new setup in ZATCA’s simulation environment with your real invoice data while your current provider stays live, then switch at a clean period boundary.

What the move involves

1
Map it in a day.
ERP or POS, invoice types, B2B/B2C split, number of invoicing units and branches. You get a fixed migration quote, not an open-ended project.
2
Connect, don't rebuild.
We plug into the system you already use. Nothing changes for the people raising invoices.
3
Prove it in simulation.
New invoicing units are onboarded and tested against ZATCA's simulation environment until clearance and reporting pass cleanly.
4
Switch and save
Production CSIDs are issued, transmission moves to Bee at the agreed cut-off, the old units are retired, and you start paying our rate.
Get a switch quote

B INVOICE FOR SAUDI BUSINESSES

Saudi E-Invoicing Software for ERP, POS & Accounting Systems

B Invoice connects your existing business systems with the Saudi e-invoicing workflow, helping finance and IT teams manage ZATCA integration without replacing their core ERP or accounting environment.

ZATCA Fatoora Integration

Connect your invoicing workflow with the Fatoora platform through the applicable integration process.

Clearance & Reporting

Handle the applicable clearance and reporting workflows for different invoice types.

CSID Onboarding

Support the onboarding and cryptographic setup required for connected invoicing units.

ERP Integration

Support the onboarding and cryptographic setup required for connected invoicing units.

Invoice Validation

Support the onboarding and cryptographic setup required for connected invoicing units.

Status Write-Back

Return invoice status and submission information to your business system for easier finance-team tracking.

Keep your existing ERP. Connect your invoicing workflow.

B Invoice connects your existing business systems with the Saudi e-invoicing workflow, helping finance and IT teams manage ZATCA integration without replacing their core ERP or accounting environment.

What we actually do

Saudi E-Invoicing Software for ERP, POS & Accounting Systems

Built for how Saudi businesses really invoice

Head office on SAP, branches on a POS, a finance team that closes the month in three days. The platform is designed around that mix, not around a single clean system.

Branches & tills

Every branch, till and invoicing unit onboarded and monitored from one screen, each with its own CSID and hash chain.

Month-end volume

Queues absorb the spike and retry automatically if Fatoora is slow, so a busy last day does not become a backlog of unreported invoices.

Rejections handled

Every rejection and warning comes back with the reason in plain language, routed to the person who can fix it  not buried in a log.

Supplier invoices too

Inbound invoices from your suppliers validated against ZATCA’s rules and matched to purchase orders, with AI extraction for anything still arriving as PDF

Any ERP, or none

Deep connectors for the large suites, API for everything else, and a portal plus bulk upload for businesses without an ERP

Arabic built in

Bilingual invoice layouts with the Arabic content ZATCA expects, generated from your existing data.

Audit-ready archive

Every XML, stamp and ZATCA response kept together and searchable, ready for an inspection or a VAT review.

One platform, the region

The same integration covers the UAE, Oman and Malaysia, so a GCC group runs one e-invoicing platform, not one per country.

Cost of getting it wrong

Saudi E-Invoicing Penalties

The first mistake is a warning. The ones after it are not.

ZATCA’s violation guideline opens every e-invoicing violation with a warning and a window to correct it. Repeat the same violation within twelve months and fines climb a fixed ladder; go twelve months clean and the ladder resets.
Violation
First time
If repeated within 12 months
Not integrating with Fatoora by your wave date
Warning
Fines escalate up to SAR 50,000
Deleting or amending an invoice after issuance
Warning
Not issuing or storing invoices electronically
Consolidating a transaction of RM10,000 or more
Warning
Fines from SAR 5,000, escalating
Missing QR code on a simplified invoice
Warning
SAR 1,000, then escalating up to SAR 40,000
Not telling ZATCA about a fault that stops invoicing
Warning
SAR 1,000, then escalating up to SAR 40,000

The fine is rarely what hurts most

A standard invoice that fails clearance cannot legally be sent to your customer, which means it cannot be paid. For a business raising hundreds of B2B invoices a month, a few days of rejections is a cash-flow problem long before it is a penalty and repeated failures are exactly what moves you up the ladder.

frequently asked questions

Saudi E-Invoicing FAQ

What finance and tax teams ask us

Product-level questions. For country rules, deadlines and penalties, open the relevant market page.
Is e-invoicing mandatory in Saudi Arabia?

Yes. Every VAT-registered business has had to issue electronic invoices since Phase 1 began on 4 December 2021. Phase 2 adds integration with ZATCA’s Fatoora platform, rolled out in waves by revenue. ZATCA notifies each wave at least six months before its integration date.

Wave 25 was announced on 24 July 2026. It covers taxpayers whose VAT-subject revenue exceeded SAR 187,500 in any one of 2022, 2023, 2024 or 2025, and they must integrate with Fatoora by 1 February 2027. If a single one of those years crossed the line, you are in scope. ZATCA sends notifications to the contact details on your account.

Phase 1 required you to generate and store invoices electronically instead of on paper or in unstructured files. Phase 2 requires your invoicing system to connect directly to Fatoora, produce structured XML, apply a cryptographic stamp, and clear or report each invoice with ZATCA.
Standard tax invoices to businesses and government are cleared: ZATCA validates them before they reach the buyer. Simplified tax invoices to consumers are reported: the customer receives the invoice immediately and it is sent to ZATCA within 24 hours.
A Cryptographic Stamp Identifier is a certificate issued to each of your invoicing units when it is onboarded to Fatoora. It is what lets that unit stamp invoices ZATCA will trust. You generate the one-time password for onboarding in your own Fatoora portal, and we handle the rest of the process.
Yes. Because onboarding runs through your own Fatoora account, no provider can lock you in. We onboard new invoicing units under your VAT number, test your real invoices in ZATCA’s simulation environment while your current provider stays live, import your archive, and switch at a clean period boundary so there is no gap and no double submission.
Every violation starts with a warning and a correction period. Repeats within twelve months escalate: up to SAR 40,000 for a missing QR code on simplified invoices, and up to SAR 50,000 for failing to integrate on time or amending invoices after issuance. Twelve clean months reset the ladder.
Tax invoices must include Arabic, and they may carry another language alongside it. Our layouts are bilingual by default and generate the Arabic content from the data already in your system.
Oracle Cloud ERP, Oracle Fusion and EBS, SAP S/4HANA and ECC, Microsoft Dynamics 365, Infor, NetSuite, Odoo, Zoho, QuickBooks, POS systems and effectively anything else through API, SFTP or file upload. Businesses without an ERP can use our portal or bulk upload.
It depends on your invoice volume, how many branches and invoicing units you run, your B2B/B2C mix and how you connect. Use the calculator at the top of this page for an instant estimate, or send us your current bill and we will return a like-for-like quote.

Ready for Saudi E-Invoicing?

Two ways to start. Both are free.

Whether you are preparing for ZATCA Phase 2, checking your Wave 25 requirement or considering a switch from your current e-invoicing provider, B Invoice can help you assess your current setup and plan the integration.

Check My ZATCA Readiness
Talk to B Invoice
Fatoora Integration · Clearance · Reporting · CSID · QR Codes · ERP Integration

ZATCA e-invoicing software and Fatoora integration in Saudi Arabia

Bee Aura Tech provides B Invoice, an e-invoicing compliance platform for VAT-registered businesses in the Kingdom of Saudi Arabia. It reads invoice data from Oracle Cloud ERP, Oracle Fusion, Oracle EBS, SAP S/4HANA, SAP ECC, Microsoft Dynamics 365, Infor, NetSuite, Odoo, Zoho, QuickBooks, point-of-sale systems and any other ERP or non-ERP application; validates seller and buyer VAT numbers, VAT treatment and mandatory fields; generates UBL 2.1 XML with a UUID, invoice counter, previous-invoice hash, cryptographic stamp and TLV-encoded QR code; and submits each document to the Zakat, Tax and Customs Authority (ZATCA) Fatoora platform through the clearance API for standard tax invoices or the reporting API for simplified tax invoices.

Saudi e-invoicing began with Phase 1, the Generation Phase, on 4 December 2021. Phase 2, the Integration Phase, began on 1 January 2023 for taxpayers with VAT-subject revenue above SAR 3 billion and has since been rolled out in waves to progressively smaller businesses: Wave 23 above SAR 750,000 by 31 March 2026, Wave 24 above SAR 375,000 by 30 June 2026, and Wave 25 above SAR 187,500 in any of 2022 to 2025 by 1 February 2027. ZATCA notifies taxpayers at least six months before their integration date. E-invoicing violations begin with a warning and escalate for repeat offences within twelve months, reaching up to SAR 50,000 for failing to integrate on time or deleting or amending invoices after issuance.

B Invoice handles CSID onboarding for each invoicing unit, clearance and reporting, credit and debit notes, rejection and warning management, automatic retry, bilingual Arabic invoice layouts, PDF/A-3 with embedded XML, inbound supplier invoice validation, two-way and three-way matching, AI extraction from PDF supplier invoices, status write-back to the ERP and audit-ready archiving. Businesses already integrated with another provider can migrate through a process that onboards new invoicing units under their own Fatoora account, validates in ZATCA’s simulation environment and cuts over at a clean period boundary. The same platform supports e-invoicing in the UAE and e-invoicing in Malaysia, so GCC and Asia-Pacific groups can run one integration across countries.

Need Help?