xMatix
Sign in Request demo
xMatix
PRODUCTS
SalesField SalesCRMRewardsClaimsInventoryProcurementWarehouse ManagementField ServiceServiceSupportTelephony & MessagingFinance & AccountingPayrollExpense ManagementCommercePortalsAnalytics & ReportingData StudioMobile AppSee all products →
PLATFORM
Platform overviewApp BuilderAutomationIntegrationsSecurity & GovernanceChange ManagementDevelopers
SENSE AI
Sense AI overviewSense AssistSense ControlSense VisionAI StudioTrust & governanceIn Claude & ChatGPTUse cases
SOLUTIONS
FMCG & DistributionManufacturing & Dealer NetworksAutomotive & DealershipsPharma & HealthcareConsumer DurablesAgri-InputsBuilding MaterialsService NetworksWarehousing & 3PLFinancial AccountingERP SoftwareIndia GST ComplianceUAE VAT & e-InvoicingSaudi ZATCA & VATAll solutions →
RESOURCES
Knowledge CenterDeveloper & CLIBlogGuidesWhat is xMatix?Company facts
COMPANY
AboutCareersPartnersEventsContactAuthorsLegal
Sign in Request demo
SOLUTIONS · KSA COMPLIANCE

Invoices that clear with ZATCA as they are born

What Phases 1 and 2 require — XML invoices, real-time clearance, cryptographic stamps, QR codes, the tamper-evident chain — and how xMatix clears, stamps and reports invoices from daily operations, including offline van sales.

Request a demo Explore KSA Compliance →

ZATCA e-invoicing is not a reporting obligation — it is a clearance regime. Since Phase 1 (December 2021), every VAT-registered business in Saudi Arabia must generate invoices electronically in a compliant system: no handwritten invoices, no plain PDFs, no editable formats. Phase 2 — the integration phase, rolling out in waves since January 2023 — connects that system to ZATCA's Fatoora platform: standard (B2B) invoices are cleared by ZATCA in real time before they are valid, and simplified (B2C) invoices are cryptographically stamped at issue and reported within 24 hours. The waves keep reaching smaller revenue bands, so the question is not whether your integration wave arrives, but whether your invoicing will be ready when it does.

What Phase 2 actually requires

  • Structured XML invoices. Invoices are generated in the prescribed XML format with the mandated fields — seller and buyer VAT registrations, line-level tax data — not as document images.
  • Clearance for standard invoices. B2B invoices go to ZATCA in real time; the platform validates and cryptographically stamps them, and only then is the invoice valid to share. A rejected invoice is a stopped transaction, not a month-end note.
  • Stamping and reporting for simplified invoices. B2C invoices are stamped by your own system at issue — including at a van or a counter — with a compliant QR code on the document, and reported to ZATCA within 24 hours.
  • Tamper evidence. Each invoice carries a UUID, a hash of the previous invoice and a cryptographic stamp, forming a chain ZATCA can verify. Deleting or editing an issued invoice is not a correction path — credit and debit notes are.
  • Device onboarding. Invoice-generating systems are onboarded with ZATCA-issued cryptographic identities, renewed and managed per unit.

Why bolted-on ZATCA compliance keeps breaking

A clearance regime turns every data-quality problem into a customer-facing incident. When billing lives in one system and ZATCA integration in another, rejected invoices strand between the two: the goods have shipped, the customer is waiting, and the invoice exists in your books but not in the authority's. Cash-register add-ons stamp the receipt but never post the ledger, so the books and the Fatoora record drift apart — and the VAT return, prepared from the books, disagrees with the invoice data ZATCA already holds. In a regime where the authority sees your invoices first, that disagreement is an audit finding waiting to be mailed.

How xMatix runs ZATCA e-invoicing

In xMatix, the ZATCA obligation is a property of the invoice itself. Order-to-cash and finance produce VAT-correct invoices with validated registrations and line-level tax data; the platform generates the compliant XML, clears standard invoices with ZATCA in real time, stamps simplified ones at issue, and attaches the outcome — clearance status, QR code, hash chain position — to the invoice record for audit. Credit and debit notes travel the same path, so corrections stay inside the rules. And because the invoice that cleared is the invoice that posted, the VAT return reconciles against what ZATCA already knows.

Simplified invoices where they actually happen

Saudi route-to-market runs on van sales and counter sales — exactly where simplified invoices are born. xMatix's offline-first mobile app generates and stamps the invoice at the point of sale, prints the QR-coded document for the customer, queues it durably, and reports it to ZATCA when connectivity returns — inside the 24-hour window, with no salesperson checklist.

Common questions

What is the difference between ZATCA Phase 1 and Phase 2?

Phase 1 (generation, since December 2021) requires invoices to be created electronically in a compliant system — no manual or editable invoices. Phase 2 (integration, waves since January 2023) connects your system to ZATCA's Fatoora platform for real-time clearance of standard invoices and 24-hour reporting of simplified ones. Wave membership is announced by revenue band.

What is the difference between standard and simplified e-invoices?

Standard invoices cover B2B and B2G supplies and must be cleared by ZATCA before being shared with the buyer. Simplified invoices cover B2C sales, are stamped by your own system at issue with a compliant QR code, and are reported to ZATCA within 24 hours. xMatix handles both flows from the same ledger.

Does xMatix support offline simplified invoicing for van sales?

Yes. The mobile app generates and cryptographically stamps simplified invoices offline at the point of sale — QR code on the customer document — then reports them to ZATCA automatically when the device reconnects, within the reporting window.

How are corrections handled once an invoice is cleared?

Issued e-invoices cannot be edited or deleted; corrections travel through credit and debit notes, which are themselves cleared or reported. xMatix treats this as one workflow, so the books, the customer document and the Fatoora record stay in agreement.

What should we fix before our integration wave is announced?

Master data first: customer VAT registrations, address particulars and line-level tax classifications. xMatix validates these at the transaction, so cleanup is a one-time exercise rather than a per-invoice firefight after go-live.

RELATED
See your invoices clear as they are raised.
Request a demo