Web design for Riyadh.
Fatoora first, design second.
Saudi Arabia is further down the e-invoicing road than anywhere else we build for, and in Riyadh it is not a future project — it is a wave with a date on it. ZATCA runs the Integration Phase in waves, notifying each group at least six months before its integration date, and the thresholds have come down to the point where most trading businesses are now in scope. Any system issuing invoices in the Kingdom is built around Fatoora or it is built wrong.
Start a projectThe waves, and which one you are in
Read from ZATCA on 31 October 2026. Check your own notification rather than relying on this page: notification is individual.
What the Integration Phase requires
Not just reporting. Invoices in a prescribed format, additional invoice fields, and the solution integrated with ZATCA’s Fatoora platform. That is a technical requirement on the system, which is why it is a developer’s problem and not only an accountant’s.
Wave 24
Taxpayers whose VAT-subject revenue exceeded SAR 375,000 in 2022, 2023 or 2024, integrating by 30 June 2026.
Wave 25
VAT-subject revenue above SAR 187,500 across 2022 to 2025, integrating by no later than 1 February 2027. The threshold falling to SAR 187,500 is the reason small businesses are now in scope.
The standing rule
ZATCA notifies each wave directly at least six months before its integration date. Six months is the real planning window for a system change, and it is not long for one.
Sources, checked 31 October 2026
- Zakat, Tax and Customs Authority (Saudi Arabia), Wave notices for the e-invoicing Integration Phase: Wave 24 covers VAT-subject revenue above SAR 375,000 in 2022, 2023 or 2024 and integrates by 30 June 2026
- Zakat, Tax and Customs Authority (Saudi Arabia), Wave 25: VAT-subject revenue above SAR 187,500 in 2022 to 2025, integrated with the Fatoora platform by 1 February 2027, with at least six months’ notice to later waves
- Zakat, Tax and Customs Authority (Saudi Arabia), E-invoicing: the Integration Phase requires invoices in a prescribed format, extra invoice fields and integration with Fatoora, rolled out in waves from 1 January 2023
What that means for the build itself
- The invoice is a regulated artefact Fields, format and clearance are specified, which means the invoice cannot be a PDF template somebody designed. It is generated by the system to a specification.
- Arabic is not optional here The interface mirrors, the invoice renders in Arabic, and the numeral and calendar choices are deliberate. This is a build decision, not a translation task.
- Offline cannot mean unrecorded A till that loses its connection still has to produce a compliant document and reconcile afterwards. That is the hardest part of retail work in the Kingdom.
- A fine exemption is not an extension ZATCA has published fine exemption periods. An exemption from a penalty is not permission to miss the integration date, and treating it as one is a common and expensive misreading.
When we are the wrong firm for this
We are not an accredited Saudi e-invoicing solution provider and we will not claim to be. For a business whose only requirement is compliant invoicing, the right purchase is a certified local solution, and it will be cheaper and faster than anything we would build. We are worth talking to when you have an operational system to build — ordering, portal, logistics, internal tools — that has to produce compliant invoices as one of the things it does.
If the whole brief is Fatoora compliance, buy local. If Fatoora is one requirement inside a bigger system, call us.
Before you ask.
Does our Riyadh system need ZATCA integration?
Are you a certified e-invoicing provider?
Will the till keep working if the connection drops?
Ready to get started?
Tell us what you need. We will scope it, price it and build it.
Start a project →