Saudi e-invoicing has two phases: generation and storage, followed by integration with ZATCA’s Fatoora platform. In Phase 2, invoices use a defined electronic format. Standard tax invoices are generally cleared before sharing, while simplified tax invoices are reported to ZATCA within 24 hours of issue, according to the authority’s official guidance.
Important: This article is a general explanation, not tax or technical advice. ZATCA regulations, guidance, and direct notices are authoritative. Onboarding groups, dates, and requirements may change; check the company’s ZATCA account and official notices.
What is an electronic invoice?
ZATCA defines an electronic invoice as one generated and stored in a structured electronic format through a compliant system. It is not simply a scanned document or a file manually created in word-processing or spreadsheet software.
E-invoicing also covers associated debit and credit notes. Required fields and processing differ according to invoice type and the phase that applies to the taxpayer.
What are the two phases?
Phase 1: generation and storage
Phase 1 began on 4 December 2021 for persons subject to the e-invoicing regulation and parties issuing invoices on their behalf. It requires a compliant electronic solution to generate and retain invoices with the required elements and disallows handwritten invoices or invoices produced with tools not designed as invoicing systems.
Phase 2: integration
Phase 2 began in waves from 1 January 2023. It requires the invoicing solution to integrate with Fatoora, generate invoices in the specified format, and include additional fields and technical controls.
ZATCA states that Phase 2 applies by taxpayer group and that affected taxpayers receive at least six months’ notice. Do not use a general article to infer your onboarding date; rely on the notice addressed to your entity.
Standard vs simplified tax invoices
| Type | Typical use | Phase 2 processing |
|---|---|---|
| Standard tax invoice | Business-to-business transactions | XML is submitted to Fatoora for clearance, then the cleared invoice is shared with the buyer |
| Simplified tax invoice | Business-to-consumer transactions | The seller issues it to the buyer, then reports it automatically to Fatoora within 24 hours |
These are simplified descriptions of typical use, not replacements for the legal definitions. Special cases exist, and fields and formats depend on the transaction.
What do clearance and reporting mean?
Clearance for standard tax invoices
The taxpayer’s system submits invoice XML to Fatoora through APIs. The platform validates it against the implementation standard. After successful validation, the cleared invoice is returned with technical elements added through the process. The invoice can then be shared with the buyer in an accepted format.
Reporting for simplified tax invoices
The system generates a compliant simplified invoice and provides it to the buyer, then reports it automatically to Fatoora within 24 hours. The time window should not become an uncontrolled manual queue; the solution needs monitored submission, responses, and exception handling.
Which practical capabilities should be checked?
Do not attempt to build a final technical specification from a blog post. ZATCA’s official documents contain updated fields, business rules, and security requirements. At project level, verify that the solution supports:
- Required invoice types and debit and credit notes.
- XML format, fields, and Phase 2 business rules.
- Integration with Fatoora APIs.
- QR codes where required.
- Identifiers, stamps, sequence, and time controls under the specifications.
- Record retention, backup, and recovery.
- Prevention of unauthorised deletion or modification.
- User and event audit trails.
- Offline operation and controlled resubmission.
- Visible clearance or reporting status and rejection reasons.
Review ZATCA’s Simplified Technical Guide and developer materials with your internal team or solution provider.
A ten-step readiness plan
1. Confirm the entity’s status
List legal entities, VAT numbers, branches, and invoicing systems. Confirm whether a Phase 2 notice has arrived and who owns the response.
2. Map the current invoice flow
Document how orders or contracts begin, who sets prices and tax, who approves invoices, and how invoices are issued, delivered, retained, and adjusted.
3. Classify transactions
Separate B2B and B2C, domestic and export, advance payments and returns, and debit and credit notes. Classification helps the team test realistic cases.
4. Clean master data
Review legal names, VAT numbers, addresses, units of measure, items, tax rates, and special treatments. A data-quality problem can present itself as a technical failure.
5. Complete a gap assessment
Compare the current solution against official requirements. Classify each gap as:
- Missing function.
- Missing or poor data.
- Integration or security.
- Internal procedure.
- Training or ownership.
6. Select an upgrade or solution path
The path may be an upgrade to the current system, middleware from a provider, or migration to a new platform. ZATCA publishes an indicative provider directory, but explicitly states that it is not mandatory and does not constitute approval of individual solutions. The taxpayer remains responsible for using a compliant solution.
7. Prepare onboarding and test environments
Define certificates, keys, devices or solution units, ownership of secrets, and renewal responsibilities. Do not use production data in uncontrolled testing.
8. Test normal and exceptional cases
Test:
- Successful standard invoice.
- Successful simplified invoice.
- Debit or credit note.
- Discount, shipping charge, and advance payment.
- Rejection caused by missing data.
- Connection interruption and resubmission.
- User deactivation or permission change.
- Transaction volume close to production demand.
One successful sample invoice is not adequate testing.
9. Train teams and define support
Train sales, finance, customer service, and IT on the scenarios relevant to them. Define who resolves rejections, who authorises corrections, and how incidents escalate to the provider.
10. Monitor after go-live
Build a dashboard that covers:
- Cleared and reported invoice volumes.
- First-submission success rate.
- Rejections by reason.
- Simplified invoices approaching the 24-hour limit.
- API response time and downtime.
- Debit and credit notes.
Monitoring is part of compliance, not an optional technical activity.
How should an e-invoicing solution be evaluated?
Ask the provider to demonstrate:
- A live standard and simplified invoice.
- XML, status, and platform response in an understandable view.
- Rejection, connection loss, and controlled resubmission.
- Multiple branches, devices, or VAT numbers where relevant.
- Audit trail, permissions, and segregation of duties.
- Export, archive, and recovery.
- Update process when specifications change.
- Support agreement with response and escalation times.
Do not rely solely on a provider’s appearance in ZATCA’s directory. ZATCA describes the list as indicative and non-mandatory and says it is not an endorsement of the solutions.
Common mistakes
- Treating a manually created PDF as a compliant electronic invoice.
- Waiting for the integration date before cleaning data.
- Testing only B2B invoices and ignoring simplified invoices or notes.
- Failing to monitor API rejections or the reporting deadline.
- Granting broad permissions without an audit trail.
- Assuming the provider carries all regulatory responsibility.
- Changing invoicing without involving sales and customer service.
How can Jazalla support the invoicing journey?
Jazalla states that it supports ZATCA e-invoicing within a platform connecting sales, procurement, and accounting. The potential operational advantage is that customer, order, tax, and invoice data does not need to be retyped across disconnected systems.
Before contracting, ask Jazalla’s team to demonstrate the scenarios that apply to your entity and confirm integration status, required functions, and the division of responsibilities. Evidence against your use case is more valuable than a broad claim.
Frequently asked questions
Is every business subject to Phase 2 now?
Phase 2 is applied progressively by group. ZATCA says affected taxpayers receive at least six months’ notice. Check the entity’s official notice and account rather than making an assumption.
Is a PDF an electronic invoice?
Not by itself. A compliant electronic invoice is generated through a suitable system using specified formats, fields, and controls. A readable copy may be shared, but a manually created PDF is not sufficient.
When is a simplified tax invoice reported?
ZATCA’s simplified guide says a simplified tax invoice is reported automatically to Fatoora within no more than 24 hours after issue.
Must a business use a provider from ZATCA’s directory?
No. The list is indicative and non-mandatory and is not an approval of the listed solutions. Any solution may be used if it complies, while responsibility remains with the taxpayer.
What should happen when an invoice is rejected?
Read the rejection code and reason, correct the source data or configuration, and reprocess it under the approved procedure without breaking sequence or deleting the audit record. The system and team should have a defined route for each error type.
Conclusion
E-invoicing readiness is not merely a technical plug-in. It is a data, process, and control programme. Confirm entity status and invoice flows, clean data, compare the solution against official requirements, test normal and exceptional cases, train teams, and monitor clearance and reporting after launch.
