ZATCA Phase 2 E-Invoicing (KSA)

Key Features

UBL 2.1 XML generation for both standard (B2B clearance) and simplified (B2C reporting) invoices, credit memos and debit notes, mapped from your Business Central VAT posting groups and document lines

ECDSA cryptographic stamp and SHA-256 hash chaining (PIH/previous-invoice-hash + ICV counter) applied automatically at posting time, keeping each invoice cryptographically linked to the last

ZATCA-compliant TLV-encoded QR code rendered onto the invoice report layout (Word/RDLC) for the printed and PDF document

Direct integration with the ZATCA Fatoora APIs for real-time clearance of standard invoices and reporting of simplified invoices, with full request/response capture

Built on AL event subscribers hooked into Codeunit 80/Sales-Post events so compliance fires on the standard posting flow — no parallel posting process to maintain

Table and page extensions storing clearance status, ZATCA UUID, hash, QR, warning/error codes and cleared XML directly on the posted sales invoice

Job queue entry for automatic retry of failed submissions and to enforce the 24-hour B2C reporting window without manual intervention

Compliance status tracking with a dashboard/list view: cleared, reported, pending, failed and warning states filterable across all documents

ZATCA onboarding support in-app: CSR generation, compliance CSID and production CSID handling so your EGS unit completes device onboarding correctly

Dedicated permission set isolating e-invoicing actions and configuration for clean role-based access and SOX/audit separation

Configurable seller/branch (VAT registration, CRN, address) setup supporting multiple branches or business units under one tenant

Designed as a per-tenant extension so it can coexist with your other ISV apps and survive Business Central monthly platform updates

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

ZATCA Phase 2 e-invoicing, built into your Business Central

Saudi Arabia's ZATCA "Fatoora" mandate requires that standard (B2B) tax invoices are cleared with ZATCA before they reach the buyer, and that simplified (B2C) invoices are reported within 24 hours — each one carrying a UBL 2.1 XML payload, a cryptographic stamp, a hash chain (PIH/previous invoice hash), and a TLV-encoded QR code. Microsoft Dynamics 365 Business Central does not ship this for the KSA market out of the box.

This is a build-to-order solution. ECOSIRE designs, builds, installs and supports a per-tenant AL extension directly on your Business Central environment (Online or on-prem). It is not an instant Microsoft AppSource download — we scope it to your chart of accounts, VAT posting setup, document layouts and Fatoora onboarding, then deploy and run the compliance cycle with you.

What it does

The extension subscribes to Business Central's posting events (via AL event subscribers on the sales invoice/credit-memo posting routines), generates the ZATCA-compliant UBL 2.1 XML, applies the ECDSA cryptographic stamp and hash chaining, builds the TLV QR code, and calls the ZATCA Fatoora APIs for clearance (standard) or reporting (simplified). Clearance status, ICV/PIH counters, XML, and ZATCA response codes are stored on the document and exposed on page extensions so AR staff can see compliance state without leaving the invoice.

A job queue entry handles retries and the 24-hour B2C reporting window. The onboarding flow (CSR generation, compliance CSID, production CSID) is wired in so your environment can complete ZATCA device/EGS onboarding cleanly. Everything is gated behind a dedicated permission set and is fully auditable.

You own the tenant; we deliver compliance.

What you get

A per-tenant Business Central AL extension (.app) built for your environment, installed on your sandbox first then promoted to production

ZATCA Fatoora onboarding completed with you: CSR generation, compliance CSID and production CSID, in your tenant

Configured mapping from your VAT posting setup and document layouts to ZATCA UBL 2.1 fields

Updated sales invoice / credit-memo report layout carrying the compliant QR code and required Phase 2 fields

A dedicated permission set plus role/security configuration for your AR and finance users

End-to-end test evidence: sample cleared B2B invoice and reported B2C invoice validated against ZATCA, plus retry/failure handling

Source AL code and a deployment/runbook document, with a short admin handover session

An agreed support and update window for ZATCA spec changes and BC version upgrades

Who this is for

Finance / VAT Compliance Manager

Owns ZATCA compliance risk and must guarantee every standard invoice is cleared before issue and every simplified invoice reported within 24 hours. Wants visible clearance status and an audit trail inside Business Central, not a separate portal.

Business Central Administrator / IT Lead

Responsible for the tenant and its extensions. Needs a clean per-tenant AL extension that survives BC monthly updates, uses proper permission sets, and doesn't fork the standard posting flow into something unmaintainable.

Accounts Receivable / Billing Team

Posts and issues invoices daily. Needs clearance to happen automatically at posting with clear pending/cleared/failed states and a one-click retry — no manual XML uploads to the Fatoora portal.

How ZATCA Phase 2 E-Invoicing (KSA) Compares

Criterion	ECOSIRE	Custom Build	Competitor
ZATCA Phase 2 UBL 2.1 + cryptographic stamp out of the box	Included	Partial support	Included
Built and installed specifically for your tenant's VAT setup, branches and layouts	Included	Included	Partial support
Real-time Fatoora clearance (B2B) and 24h reporting (B2C) via job queue	Included	Partial support	Included
Uses standard AL event subscribers without forking the posting flow	Included	Partial support	Partial support
Installed and supported on your environment by the vendor	Included	Not included	Partial support
Ongoing updates for ZATCA spec changes and BC monthly upgrades	Included	Not included	Included
Source AL code and runbook handed over to you	Included	Included	Not included
One-time build price with no mandatory per-document SaaS metering	Included	Included	Not included

Frequently Asked Questions about ZATCA Phase 2 E-Invoicing (KSA)

How long until it's live on our Business Central?

This is build-to-order, so there is an honest lead time. After a short scoping call to confirm your VAT setup, branches and document layouts, typical delivery is around 3 to 5 weeks: build and unit-test in a sandbox, complete ZATCA compliance CSID onboarding, validate sample cleared B2B and reported B2C invoices against ZATCA, then promote to production. Existing or complex multi-branch setups can extend this, and we give you a firm timeline before you commit.

Do we download this from Microsoft AppSource?

No. There is no instant AppSource download. ECOSIRE builds and installs it as a per-tenant AL extension directly on your Business Central environment (Online or on-prem) and supports it. This lets us tailor the UBL mapping, onboarding and layouts to your tenant rather than shipping a one-size-fits-all listing.

What happens when ZATCA changes the specification or we upgrade Business Central?

ZATCA periodically revises the Fatoora technical spec (schema, validation rules, API versions) and Microsoft ships BC platform updates roughly monthly. Your agreed support and update window covers regression-checking against those changes and shipping a refreshed extension build, so you stay compliant without re-engineering it yourself.

Does it handle both standard (B2B) and simplified (B2C) invoices?

Yes. Standard tax invoices go through the real-time clearance flow and are only issued once ZATCA returns a cleared XML; simplified (B2C) invoices are reported, with the QR code printed at point of issue and submission within the 24-hour window enforced by a job queue. Credit and debit notes are handled with the correct hash chaining (PIH/ICV).

Will it interfere with our existing posting process or other apps?

No. It uses AL event subscribers on the standard Business Central posting routines rather than replacing them, and it ships as an isolated per-tenant extension with its own permission set. It coexists with your other ISV apps and keeps your normal Post / Post and Send flow intact — compliance just happens alongside it.

Where is the compliance data stored and can we audit it?

Clearance status, ZATCA UUID, the cryptographic hash, the cleared UBL XML, the QR payload and any ZATCA warning/error codes are stored on the posted sales invoice via table and page extensions inside your own tenant. You can filter and report on them in BC, and the cleared XML is retained for audit and reconciliation.