Module

ZATCA Compliance

Configure Saudi invoice QR output and Wave 2 reporting/clearance workflows with controlled seller identity, onboarding credentials, and per-invoice routing rules.

ZATCA Compliance helps Saudi billing and finance teams configure ZATCA settings, keep seller and VAT information accurate, generate XML where required, and manage reporting vs clearance paths under a controlled rollout process.

What this module helps you control

Seller name and VAT number settings
Visible only for KSA companies (SA) scope control
Phase selection and Enable Wave 2 toggle
Environment selection for sandbox or production
CSID and CSID Secret credential ownership
Device Serial governance
CSR (PEM), Certificate (PEM), Private Key (PEM), and Certificate Chain (PEM)
OTP onboarding actions and readiness validation
Auto-attach ZATCA QR into invoice PDF (experimental) and invoice QR output checks
XML generation and per-invoice reporting vs clearance routing controls

Business outcomes teams expect

Build cleaner Saudi invoice compliance readiness before broad rollout.
Reduce seller/VAT identity mistakes that create invalid QR or submission data.
Control where ZATCA applies using KSA-only scope decisions.
Keep sandbox and production environments clearly separated.
Handle Wave 2 onboarding inputs with clearer credential ownership.
Make QR verification easier across invoice views and PDFs.
Improve control over B2B clearance vs B2C reporting processing.
Retain stronger invoice evidence for finance and audit review cycles.
Roll out by company or tenant with tighter governance.
Prevent confusion between ZATCA Compliance and E-Invoicing (EU).

What teams use most in this module

Practical capabilities that make day-to-day execution faster, cleaner, and easier to govern.

Seller Identity and VAT Settings

Maintain the seller identity fields that drive Saudi invoice compliance output quality.

Seller name and VAT number controls
Company identity consistency on invoice outputs
Finance-owned accuracy checks before go-live
Avoid wrong QR payload values from bad seller setup
Reduce incorrect submission data from stale master settings

KSA Scope and Applicability Control

Apply ZATCA behavior only where it belongs using market-scoping controls.

Enable/disable module behavior by policy
Visible only for KSA companies (SA) option alignment
Country scoping logic for Saudi entities
Avoid unintended use on non-KSA invoices
Cleaner phased rollout by market

QR Output on Invoices

Generate and verify QR data on Saudi invoices for operational and review use.

QR values built from invoice data
Seller and VAT included in encoded output
Timestamp, invoice total, and VAT amount included
HTML and PDF QR rendering support
Finance spot-check workflow for invoice samples

Wave 2 Setup and Credentials

Configure Wave 2 with controlled onboarding inputs before production usage.

Enable Wave 2 when readiness is confirmed
Environment control for sandbox vs production
CSID and CSID Secret management
Device Serial entry and ownership
Onboarding prerequisites review by compliance admins

Certificates and Signing Materials

Manage certificate artifacts with role-based ownership and storage discipline.

CSR (PEM) capture and lifecycle handling
Certificate (PEM) registration
Private Key (PEM) protection workflows
Certificate Chain (PEM) completeness checks
Production-readiness implications documented before live sending

OTP Onboarding and Environment Readiness

Use OTP onboarding with controlled operator access before transmission activities.

OTP onboarding flow from FATOORA portal process
Simulation / sandbox onboarding support
Production onboarding controls
Readiness validation before live invoice sending
Small trusted group executes onboarding actions

XML Generation and File Output

Generate Wave 2 XML artifacts linked to invoice records for evidence and follow-up.

Wave 2 XML generation from invoice context
Signed XML output handling
Invoice-linked XML storage
Downloadable/generated artifact availability
Finance/compliance evidence-pack preparation support

Reporting vs Clearance Routing

Route invoices through reporting or clearance paths using invoice-type logic and governance.

Invoice-type detection support
B2B vs B2C route logic
Auto routing mode option
Manual override / forced routing when required
Reduce operator confusion on when to report vs clear

Per-Invoice Review and Override

Allow controlled correction when a specific invoice needs route review.

Per-invoice route override support
Invoice-specific review controls
Corrective handling when route path is wrong
Admin-only governance for sensitive overrides
Clear audit intent for changes and reruns

Compliance Operations and Evidence

Organize recurring evidence handling for pilot, monthly review, and audit requests.

Sample invoice review routines
XML and PDF evidence retention
Audit folders and compliance pack preparation
Monthly review cadence support
Pilot rollout evidence with issue tracking

Start with this workflow

Follow these structured steps to launch one controlled process first, then expand.

Configure basic ZATCA readiness

1

Enable ZATCA

2

Set seller name and VAT number

3

Decide KSA-only scope

4

Validate invoice output with a test invoice

5

Confirm QR values

6

Capture pilot evidence

Configure Wave 2 environment

1

Enable Wave 2

2

Choose sandbox or production Environment

3

Enter CSID and CSID Secret

4

Set Device Serial

5

Paste CSR / Certificate / Private Key / Certificate Chain (PEM)

6

Validate environment readiness

Onboard with OTP

1

Obtain OTP from FATOORA portal

2

Enter OTP in onboarding flow

3

Onboard in simulation or production environment

4

Confirm credentials are active

5

Document onboarding success

Generate and review Wave 2 XML

1

Choose invoice

2

Generate XML

3

Sign output

4

Save XML

5

Review invoice-linked evidence

6

Prepare reporting or clearance action

Route invoice by B2B or B2C logic

1

Identify invoice type

2

Apply auto route or override

3

Send through reporting or clearance path

4

Review response/result

5

Store evidence and status outcome

Monthly compliance review pack

1

Export invoice sample set

2

Sample-check QR presence and invoice values

3

Review XML generation success

4

Review reporting/clearance route outcomes

5

Store audit evidence pack

6

Flag issues for correction

Who this module is for

Finance lead
Billing operations
Compliance owner / tax operations owner
ERP administrator
Implementation / rollout lead
Audit or internal review team

Common problems this module helps solve

QR missing from invoices
Wrong seller or VAT values
Applying ZATCA outside intended Saudi scope
Confusion between sandbox and production environments
Missing or invalid Wave 2 credentials
Unclear B2B vs B2C routing choices
Weak evidence retention for compliance reviews
Confusion between ZATCA and E-Invoicing (EU) requirements

Where teams apply this module

Saudi billing operations that need controlled QR and Wave 2 processing
Multi-company groups that must apply ZATCA only to KSA entities
Finance teams preparing pilot-to-production Wave 2 rollout
Compliance-led invoice evidence retention and monthly review cycles
Organizations that must separate ZATCA from EU e-invoicing workflows

Connected records across modules

CRM and Sales / invoice generation creates the commercial document baseline
Core Accounting uses invoice records for finance review and period controls
Data Exporter supports sample extraction and compliance evidence packs
E-Invoicing (EU) remains a separate sibling compliance path

Built-in Reports & Analytics

Invoice QR output samples
Invoice PDFs with QR evidence
Generated Wave 2 XML files
Pilot validation sample sets
Reporting / clearance route outcome records
Monthly compliance review packs
Onboarding and settings evidence snapshots where operationally required

FAQ

What data is required before enabling ZATCA?

At minimum, validate seller name, VAT number, company identity consistency, scope decisions, and responsible owners for credentials before enabling operational usage.

Can we restrict ZATCA to Saudi companies only?

Yes. Use the Saudi scope controls and Visible only for KSA companies (SA) policy so non-KSA invoices are not unintentionally processed.

What is ZATCA Wave 2 and when should it be enabled?

Wave 2 covers controlled XML, onboarding credentials, and reporting/clearance flow requirements. Enable it after pilot readiness checks are complete.

What credentials are required for Wave 2?

Operations typically require Environment, CSID, CSID Secret, Device Serial, CSR (PEM), Certificate (PEM), Private Key (PEM), and Certificate Chain (PEM), plus OTP onboarding where required.

Can the module generate QR and XML outputs?

Yes. The module supports invoice QR output and Wave 2 XML generation workflows used for review, routing, and evidence retention.

What is the difference between reporting and clearance?

Reporting and clearance are different processing paths. Teams should define route logic by invoice type and enforce operator guidance to avoid misuse.

How do we handle B2B vs B2C routing?

Use invoice-type logic with auto mode where appropriate and controlled per-invoice override when correction is required.

How should we test before going live?

Use a pilot invoice set, validate QR values, confirm XML generation, test route outcomes, and archive acceptance evidence before production expansion.

Is this the same as E-Invoicing (EU)?

No. E-Invoicing (EU) is a separate compliance track and should not be mixed with Saudi ZATCA configuration or runbooks.

Who should own ZATCA settings and credentials?

A small trusted group should own critical settings and credentials, with finance/compliance reviewers validating outputs and evidence.

Plans that include this module

Confirm commercial fit before rollout planning.

Enterprise Plan

Ready to evaluate ZATCA Compliance with your team?

We will map this module to your current process, owners, controls, and rollout timeline.

User guide

How to use ZATCA Compliance

Setup checklist, key workflows, reports, and troubleshooting.

Talk to Sales

Tell us what you need and we will reply with a rollout plan and recommended modules.

Fields marked with * are required.

Related content

Related Modules

Often fits plan: Enterprise

Accounting

Central financial control with chart of accounts, journal entries, receivables, payables, reconciliation, and financial reporting.

Often fits plan: Enterprise

AI Sales Assistant

AI-assisted calling and qualification workflows for inbound and outbound conversations.

Often fits plan: Enterprise

Asset Management

Control asset records, custody, locations, maintenance, audits, and depreciation from one lifecycle workspace.

Related Use Cases

Accelerate Order to Cash

Connect sales, fulfillment, invoicing, and collections to reduce revenue leakage and improve cash conversion.

order-to-cash revenue-operations cash-flow

Control Production Costs

Tie material usage, labor capture, and overhead allocation to each production order for reliable margins.

manufacturing-management costing inventory-warehousing

Related Industries

ERP for Manufacturing

Manufacturing ERP guidance for production scheduling, material planning, quality control, and real-time shop floor visibility.

manufacturing production inventory

ERP for Clinics and Outpatient Networks

Sector playbook covering pain points, workflows, module fit, and buying checklist for erp for clinics and outpatient networks.

industry operations erp

Related Guides

Build ZATCA audit trail controls for SMB finance teams

Practical guide for build zatca audit trail controls for smb finance teams with execution steps and buying support links.

zatca saudi compliance

ERP Implementation Playbook

A practical, phased guide to planning, launching, and scaling ERP adoption across teams with measurable outcomes.

implementation operations change-management