New · Tafkiro AI v2 ships predictive cash-flow forecastingRead the release →
SAUDI ARABIA — ZATCA PHASE 2

Wave 23 was March 31. Wave 24 is June 30. Be ready in 8 weeks.

ZATCA Phase 2 e-invoicing is not a feature toggle. It is a re-architecture of how invoices are created, cryptographically signed, transmitted to Fatoora, and returned to your buyer. Every B2B and B2G invoice must receive clearance before it legally exists. Tafkiro's invoice engine was built against this spec — ZATCA integration, Arabic UI, Hijri calendar, and Wave-aware deployment in one platform.

See implementation timeline ↓
8 weeks
ZATCA-ready
Wave Deadlines

The ZATCA Phase 2 clock is running.

Wave 23
Threshold
Turnover ≥ SAR 750,000 in 2022, 2023, or 2024
Deadline
March 31, 2026

The deadline has passed. Companies in Wave 23 that are not yet integrated with Fatoora are issuing invoices that are not legally cleared under Saudi law. Every day of non-compliance is exposure to ZATCA penalties. The path forward is an accelerated implementation — not waiting for the next wave.

Wave 24
Threshold
Turnover ≥ SAR 375,000 in 2022, 2023, or 2024
Deadline
June 30, 2026

June 30 is the hard line for Wave 24 companies. With an 8-week implementation track, the window to start is now — not next month. A scoping call this week means your ZATCA certification provisioning begins within days, keeping you on the right side of the deadline.

Wave 25 and beyond
Threshold
Remaining taxpayers — deadlines announced quarterly
Deadline
Ongoing

ZATCA announces new waves on a rolling basis. Every taxpayer in Saudi Arabia will eventually be in scope. Companies implementing Tafkiro now are ready for their wave regardless of when it arrives — no second implementation, no compliance scramble.

ZATCA penalties for non-compliant invoices start at SAR 1,000 per invoice and escalate. For a mid-market company processing 500 invoices per month, the exposure compounds quickly. Fatoora clearance is not a competitive feature — it is a legal requirement.

Technical Specification

What ZATCA Phase 2 actually requires.

The ZATCA specification is precise. It is not enough to generate a PDF with a QR code — every B2B invoice must be submitted to Fatoora, validated, cryptographically stamped, and returned before it reaches your buyer. What follows is what the spec requires and how Tafkiro handles each element natively.

Real-time Fatoora API integration (not batch upload)

Tafkiro submits B2B invoices to the Fatoora Clearance API synchronously at invoice confirmation. Clearance happens before the invoice is dispatched to your customer. If ZATCA returns an error, the invoice is held with the specific error code — not silently passed through.

UBL 2.1 XML format with ZATCA-specific extensions

Tafkiro generates the complete ZATCA UBL 2.1 document internally. Every mandatory field, tax category code, supply type code, and ZATCA extension namespace is included. Your team never writes XML — invoice confirmation triggers the generation.

Cryptographic stamp using a ZATCA-issued device certificate (CSID)

Tafkiro manages CSID onboarding as part of the ZATCA setup process — certificate signing request, Compliance CCSID API submission, and secure certificate storage. Each legal entity with a separate ZATCA registration requires its own CSID, which Tafkiro handles per entity.

Globally unique UUID per invoice

Tafkiro assigns a UUID to every invoice at generation. The UUID is included in the XML payload, the cleared invoice, and Tafkiro's internal audit log — so every invoice is traceable end to end.

Sequential counter per device — cannot be skipped or reset

Tafkiro maintains the sequential invoice counter per CSID device as a database-enforced constraint. Counter integrity is part of the ZATCA onboarding validation. Gaps or resets are not possible without triggering a compliance alert.

QR code in Base64 TLV format (B2C stamped at issue; B2B post-clearance)

Tafkiro generates QR codes in ZATCA-mandated Base64 TLV encoding. For B2C simplified invoices, the QR is stamped at issue. For B2B standard invoices, the QR is embedded after Fatoora returns the cleared XML — never before, which means your B2B buyer always receives a valid cleared document.

Arabic field labels alongside English

Tafkiro's invoice template includes Arabic field labels in the positions ZATCA requires. Tax category descriptions, total labels, and seller/buyer information are rendered bilingual. Invoice templates are configurable by print format without compromising the underlying XML structure.

24-hour reporting window for B2C invoices

Tafkiro queues B2C simplified invoices for batch reporting to Fatoora within the 24-hour window automatically. The reporting queue is monitored, with alerts for any invoices approaching the deadline that have not yet confirmed submission.

Platform Approach

Why Tafkiro is the fastest path.

ZATCA-native, not ZATCA-retrofitted

Most ERP platforms built their ZATCA Phase 2 integration as a compliance module attached to an existing invoice workflow. The invoice is created in one system, exported to a middleware, cleared through a separate tool, and returned to the ERP. Every handoff is a point of failure. Tafkiro's invoice engine was designed against the ZATCA specification from the architecture stage — clearance is a step in the invoice posting flow, not a separate process.

8-week implementation for Wave 24-eligible companies

SAP Business One implementations in Saudi Arabia average 16-24 weeks. Tafkiro's implementation methodology — modular activation, a pre-configured Saudi compliance pack, and structured parallel testing — completes in 8 weeks for mid-market companies. This is not a simplified version of the platform. It is the full platform delivered through a methodology built for this market.

Arabic UI from day one, not from a translation layer

Some ERPs offer Arabic as a language file applied over an English interface — field labels translate but the underlying form logic, error messages, and help text remain in the source language. Tafkiro's Arabic interface is part of the base product: right-to-left layouts, Hijri date display alongside Gregorian, and Arabic business defaults for Saudi invoice templates.

Built for Equipment Rental and Manpower Supply — not adapted

Two of Saudi Arabia's largest mid-market verticals have ZATCA requirements beyond a standard invoice: equipment rental contracts generate mobilization invoices, periodic invoices, and demobilization invoices — each requiring Fatoora clearance. Manpower supply companies invoice service delivery with worker deployment details. Tafkiro has industry packs for both verticals, with ZATCA-compliant billing workflows pre-configured for how these businesses actually operate.

Implementation Timeline

What 8 weeks looks like.

This is the standard Tafkiro implementation track for a Saudi mid-market company entering on a ZATCA Phase 2 deadline. Weeks are sequential. The critical path is ZATCA certification provisioning — which is why the scoping call matters now.

Week 1

Scoping and data audit

We map your business structure: legal entities, ZATCA registration details, invoice types (B2B, B2C, B2G), current ERP or accounting tool, and data volumes. We identify which modules you need beyond finance — HR for Iqama tracking, rental management, project billing. The output is a scoped implementation plan with defined deliverables.

Week 2

ZATCA certification provisioning

We initiate CSID provisioning with ZATCA's Fatoora platform — generating the certificate signing request, submitting through the ZATCA Compliance CCSID API, and storing the issued device certificate in Tafkiro. For companies with multiple entities (each requiring a separate CSID), this runs in parallel. The ZATCA sandbox environment is activated for test invoice submission.

Weeks 3–4

Master data migration and ZATCA test invoices

Customer master, vendor master, chart of accounts, item master, and open balances are migrated from your current system. Tax category codes and buyer classification (B2B vs B2C) are validated against your customer list. We run 50–100 test invoices through the ZATCA sandbox — verifying clearance, QR code generation, and error handling for edge cases in your invoice mix.

Weeks 5–6

Parallel run with your current system

Tafkiro goes live for new transactions. Your current system remains in read-only mode for reference. Every invoice posted in Tafkiro clears through Fatoora — live, not sandbox — confirming the production integration is working. Finance team processes actual transactions in Tafkiro with daily reconciliation against the current system.

Week 7

User training and edge case validation

Full team training on the modules in scope — finance, operations, HR as applicable. We work through your specific edge cases: multi-currency invoices, partial payments, credit notes, advance billing, equipment rental invoice cycles. ZATCA error handling is trained with real examples from the test phase. Arabic interface validation with your Saudi team.

Week 8

Go-live with ZATCA compliance active

Tafkiro becomes the system of record. Every invoice from go-live day clears through Fatoora in production. The rollback plan is documented — your old system's data remains accessible. Post-go-live hypercare runs for 30 days with direct access to the implementation team for any production issues.

What We Need From You

What we need from your side.

An honest list. These are the things that determine whether an 8-week implementation holds its timeline. We have delivered this on schedule for mid-market companies across Saudi Arabia — the constraint is almost always data readiness and decision-maker availability, not Tafkiro configuration.

  • 01

    A project sponsor with authority to make decisions on data structure and business process. Not a committee — one person who can say yes.

  • 02

    Access to your current invoice data, customer master, and ZATCA registration details (VAT number, CRN, CSID if already provisioned).

  • 03

    Two to three power users — typically a finance lead and an operations lead — available four to six hours per week during weeks three through seven for configuration review and testing.

  • 04

    One Arabic-speaking team member for invoice template review and Arabic field validation.

  • 05

    A decision on Phase 2 integration approach by the end of week two: which entities are in scope, which invoice types, and which go-live sequence if you have multiple entities.

  • 06

    Your current ERP or accounting tool export in a readable format. We work with SAP Business One, Oracle, Microsoft Dynamics, Odoo, local Saudi ERPs, and Excel-based setups.

Qualification

Who's a good fit.

Good fit
  • Mid-market Saudi companies — 50 to 500 employees — currently in Wave 23, 24, or anticipating an upcoming wave.
  • Currently running SAP Business One, Oracle NetSuite, Microsoft Dynamics 365, Odoo, or a local Saudi accounting system.
  • Operating across multiple Saudi cities or planning expansion across the Gulf region — multi-entity and multi-site operations are a native capability.
  • Equipment rental or manpower supply companies needing ZATCA-compliant billing workflows specific to their contract structures.
  • EPC and construction contractors on Vision 2030 projects requiring real-time project accounting alongside ZATCA compliance.
  • Time-pressed on ZATCA compliance but unwilling to trade operational capability for compliance speed — you need both.
Probably not a fit — yet
  • Companies with fewer than 50 employees and simple invoicing needs — a lighter tool may serve you better at this stage.
  • Businesses requiring extensive custom development before go-live — Tafkiro's implementation methodology is configuration-based. Deep customisation extends timelines.
  • Companies that have already signed an implementation contract with another ZATCA-certified provider and are mid-project.
FAQ

ZATCA Phase 2 questions, answered.

Questions we hear from Saudi CFOs and CIOs in ZATCA implementation conversations.

Can you really implement in 8 weeks?
For a mid-market company with 50–500 employees, clear scope, and available stakeholders — yes. Eight weeks is our standard track for Saudi implementations that include ZATCA Phase 2, finance, and one or two operational modules. The timeline holds when data is available at the start and decision-makers are accessible during the configuration weeks. We have delivered this in manufacturing, equipment rental, and manpower supply companies across Saudi Arabia. If your business has unusually high complexity — multiple entities with different ZATCA registrations, heavy customisation requirements, or very large data volumes — we scope the timeline honestly in week one before you commit.
What happens if we miss the Wave 24 deadline?
ZATCA penalties for non-compliant invoices begin at SAR 1,000 per invoice for a first violation and escalate for repeated infractions. More immediately, customers and counterparties operating in Phase 2 may begin requesting cleared invoices as a condition of doing business — non-cleared invoices create friction in your receivables. If you have already missed your wave deadline, the fastest path to compliance is still the right path. Contact us for an accelerated scoping call.
How do you handle our existing invoice history?
Invoice history prior to your Tafkiro go-live date does not need to go through ZATCA clearance — the clearance obligation applies to invoices issued after your wave integration deadline. We migrate your open receivables, vendor balances, and historical transaction data into Tafkiro for operational continuity. Closed historical invoices are available for reference in the migrated data. Your existing ZATCA-compliant invoices (if you have already integrated with Fatoora through another system) remain valid.
Can we run parallel with our current system?
Yes. Weeks five and six of the implementation are designed as a structured parallel run. Your current system stays in read-only reference mode. Every new transaction is posted in Tafkiro and clears through Fatoora. Daily reconciliation confirms the two systems agree. You control the cutover timing — we do not force a big-bang switch. For most companies, the cutover happens at month-end when books are clean.
What if ZATCA changes the spec mid-implementation?
We maintain the ZATCA API integration and schema compliance in-house. When ZATCA updates its API version, UBL schema, or technical specification — as it has done several times since Phase 2 launched — we push the update to all customers simultaneously before the effective date. You do not manage the ZATCA integration. We do. This is also why we recommend against using a third-party ZATCA middleware: when the spec changes, you are waiting on a vendor you do not control.
Do you handle Arabic invoice templates?
Yes. Tafkiro's standard Saudi invoice template includes Arabic field labels alongside English — seller name, buyer name, tax category descriptions, totals, and ZATCA-mandated fields. The template is configurable for your company branding while maintaining ZATCA compliance. We validate the Arabic invoice template with your team during week seven of the implementation.
How do you integrate with our existing payment systems and banking?
Tafkiro has pre-built integrations with major Saudi commercial banks for payment reconciliation and outgoing payment processing. WPS (Wage Protection System) integration is available through the MUDAD platform for payroll. For Accounts Receivable, Tafkiro matches bank statement lines against open invoices automatically, flagging unmatched receipts for manual review. Your specific banking relationships are confirmed in the scoping call.
What ongoing support is included after go-live?
A 30-day hypercare period immediately after go-live includes direct access to the implementation team — not a general support queue. After hypercare, you move to Tafkiro's standard support model: email and phone support with SLA-based response times, and direct escalation to the ZATCA integration team for compliance-related issues. Every ZATCA specification update is deployed to your instance before its effective date as part of the support agreement.
ZATCA Phase 2 — Wave 24 Deadline June 30

Book a ZATCA readiness assessment.

  • 30-minute scoping call with no commitment
  • ZATCA consultant with Phase 2 implementation experience in Saudi Arabia
  • Wave-specific implementation plan delivered within 48 hours of the call

Ready to see Tafkiro
in action?

Book a personalized demo with our enterprise team. We'll show you how Tafkiro works for your specific industry, your specific scale, and your specific operations.