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
Business outcomes teams expect
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.
KSA Scope and Applicability Control
Apply ZATCA behavior only where it belongs using market-scoping controls.
QR Output on Invoices
Generate and verify QR data on Saudi invoices for operational and review use.
Wave 2 Setup and Credentials
Configure Wave 2 with controlled onboarding inputs before production usage.
Certificates and Signing Materials
Manage certificate artifacts with role-based ownership and storage discipline.
OTP Onboarding and Environment Readiness
Use OTP onboarding with controlled operator access before transmission activities.
XML Generation and File Output
Generate Wave 2 XML artifacts linked to invoice records for evidence and follow-up.
Reporting vs Clearance Routing
Route invoices through reporting or clearance paths using invoice-type logic and governance.
Per-Invoice Review and Override
Allow controlled correction when a specific invoice needs route review.
Compliance Operations and Evidence
Organize recurring evidence handling for pilot, monthly review, and audit requests.
Start with this workflow
Follow these structured steps to launch one controlled process first, then expand.
Configure basic ZATCA readiness
Enable ZATCA
Set seller name and VAT number
Decide KSA-only scope
Validate invoice output with a test invoice
Confirm QR values
Capture pilot evidence
Configure Wave 2 environment
Enable Wave 2
Choose sandbox or production Environment
Enter CSID and CSID Secret
Set Device Serial
Paste CSR / Certificate / Private Key / Certificate Chain (PEM)
Validate environment readiness
Onboard with OTP
Obtain OTP from FATOORA portal
Enter OTP in onboarding flow
Onboard in simulation or production environment
Confirm credentials are active
Document onboarding success
Generate and review Wave 2 XML
Choose invoice
Generate XML
Sign output
Save XML
Review invoice-linked evidence
Prepare reporting or clearance action
Route invoice by B2B or B2C logic
Identify invoice type
Apply auto route or override
Send through reporting or clearance path
Review response/result
Store evidence and status outcome
Monthly compliance review pack
Export invoice sample set
Sample-check QR presence and invoice values
Review XML generation success
Review reporting/clearance route outcomes
Store audit evidence pack
Flag issues for correction
Who this module is for
Common problems this module helps solve
Where teams apply this module
Connected records across modules
Built-in Reports & Analytics
Compliance & Implementation Resources
Practical guides to help you rollout and validate workflows.
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.
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.
تواصل مع فريق المبيعات
شارك متطلباتك وسيتواصل معك فريقنا خلال وقت قصير.
الحقول المعلَّمة بعلامة * مطلوبة.