ZATCA E-Invoicing in Saudi Arabia: Requirements & Integration Guide
ZATCA e-invoicing integration in Saudi Arabia connects ERP, POS, and invoicing systems to the FATOORA platform under Phase 2 requirements.
ZATCA e-invoicing integration in Saudi Arabia connects ERP, POS, and invoicing systems to the FATOORA platform under Phase 2 requirements. Businesses must generate structured invoices, validate tax data, apply the required XML and QR security elements, and follow the correct process: clearance for standard tax invoices or reporting for simplified invoices. This guide explains the rollout phases, technical architecture, integration steps, testing, failure recovery, vendor selection, and how to evaluate Reachware Fatoora.
Executive Summary: What Problems Does ZATCA E-Invoicing Integration Solve?
Disconnected invoicing systems: Sales and financial records may sit in different POS, ERP, and accounting applications, making it difficult to generate consistent electronic invoices without additional data exchange.
Incorrect invoice classification: A business may send a standard tax invoice through the simplified reporting workflow or attempt to clear an invoice that should follow different requirements.
Missing mandatory fields: Incomplete seller details, relevant buyer information, invoice references, tax categories, or item-level values can cause validation failures.
Incorrect VAT calculations: Discounts, exempt or zero-rated transactions, tax categories, and rounding rules can produce errors if the source system and invoicing solution interpret them differently.
Unstructured invoice formats: PDF files or printed receipts alone do not satisfy the structured electronic data requirements applicable to Phase 2.
Invalid XML or QR information: Documents may fail technical checks if their structure, identifiers, hashes, cryptographic elements, or QR encoding do not meet the relevant specifications.
Delayed clearance: Standard tax invoices requiring ZATCA clearance may remain pending or be rejected, preventing normal completion of the invoice-sharing process.
Late simplified-invoice reporting: Businesses may miss the applicable 24-hour reporting requirement because of failed submissions, disconnected branches, or inadequate monitoring.
Uncontrolled invoice corrections: Editing an issued invoice or replacing it without the prescribed process can create document-integrity and VAT-record problems.
Missing submission evidence: Finance teams may lack the original document, submission reference, ZATCA response, or processing history required to investigate a disputed invoice.
Unreliable ERP/POS synchronization: The source application may record a sale while the invoicing solution or accounting system holds a different invoice status or reference.
Weak integration security: Poor credential management, unauthorized document changes, and inadequate access controls can expose financial and customer information.
Unclear Phase 2 applicability: Organizations may not know whether their taxpayer entity has received a wave notification, which integration deadline applies, or which invoicing units require onboarding.
What Should an Effective Integration Deliver?
Correct invoice routing: Apply the required clearance or reporting process according to the invoice's legal classification.
Valid electronic documents: Generate invoices and associated notes using the applicable ZATCA data, format, and security specifications.
Traceable submissions: Preserve identifiers, requests, responses, invoice states, and relevant processing timestamps.
Reliable ERP/POS exchange: Synchronize the approved invoice information without creating duplicate or conflicting documents.
Controlled failure recovery: Identify unsuccessful processing and apply the prescribed correction, retry, or contingency procedure.
Compliance visibility: Provide finance and tax teams with evidence to assess requirements and investigate exceptions.
Integration can reduce manual work and make controls more consistent. It does not automatically guarantee regulatory compliance; the taxpayer remains responsible for the accuracy of its invoices and the obligations applicable to its business.
ZATCA E-Invoicing Phases and Applicability
1. Phase 1 versus Phase 2
Requirement | Phase 1 — Generation | Phase 2 — Integration |
Start date | December 4, 2021 | January 1, 2023, progressively by wave |
Primary objective | Generate and store compliant electronic invoices and notes | Connect compliant invoicing solutions to ZATCA's FATOORA platform |
Application | Taxpayers within the e-invoicing regulation's scope | Taxpayers in notified integration waves |
Structured XML | Specific Phase 2 XML requirement not yet mandated | Required for submission through the applicable APIs |
Additional technical fields | Phase 1 requirements | Additional Phase 2 fields and identifiers |
QR code | Required for simplified tax invoices under Phase 1 rules | Expanded requirements according to invoice type |
Cryptographic requirements | Phase 2 controls not generally required | Applicable cryptographic controls and onboarding |
Standard invoice clearance | Not required | Required through the clearance process |
Simplified invoice reporting | Not required | Required within 24 hours of issuance |
Operational preparation | Compliant electronic invoice generation | Onboarding, connectivity, validation, and monitoring |
2. Which Businesses Must Comply?
Resident taxable persons: ZATCA's e-invoicing framework applies to resident persons within the scope of the regulation and relevant parties issuing invoices on their behalf.
Nonresident taxpayers: Nonresident taxable persons are excluded from the e-invoicing obligation described in ZATCA's published guidance.
Phase 2 wave selection: The integration timetable depends on the taxpayer group identified by ZATCA, not simply on whether a business uses electronic invoicing.
Advance notification: ZATCA states that targeted taxpayers are notified of their integration date at least six months in advance.
Legal-entity review: Businesses operating multiple entities should verify the obligations and notification status associated with the relevant taxpayer registrations.
3. What Is the Latest Announced Integration Wave?
ZATCA announced the selection criteria for Wave 25 on July 24, 2026.
Revenue criterion: Taxpayers whose VAT-subject revenues exceeded SAR 187,500 during 2022, 2023, 2024, or 2025 fall within the stated Wave 25 criteria.
Announced deadline: Notified taxpayers in this wave are required to integrate by February 1, 2027.
Individual applicability: The announcement does not make February 1, 2027 the universal deadline for every Saudi business.
Required action: Verify the taxpayer's official notice, applicable wave, existing compliance status, and the current instructions published by ZATCA.
4. Clearance versus Reporting
Comparison | Clearance | Reporting |
Invoice type | Standard tax invoice and related notes | Simplified tax invoice and related notes |
Typical business setting | B2B and B2G | B2C retail and service transactions |
Timing | Before sharing the cleared invoice with the buyer under normal procedures | Within 24 hours after invoice issuance |
Document generation | Compliant EGS prepares the standard invoice | Compliant EGS generates and stamps the simplified invoice |
ZATCA's role | Validates and clears the document | Receives and validates the reported document |
Cryptographic stamping | ZATCA applies the clearance stamp | The onboarded invoicing solution applies the required stamp |
QR processing | Follows the clearance and applicable QR requirements | EGS generates the required QR information |
Customer delivery | Cleared invoice is shared after successful clearance | Compliant invoice is presented when issued |
Primary risk | Invoice cannot be cleared in the normal flow | Invoice is not reported within the required period |
Main operational control | Clearance response verification | Reporting deadline and acknowledgment monitoring |
Important: B2B and B2C are useful general examples, not complete legal classification rules. The appropriate invoice type depends on the applicable VAT requirements and transaction circumstances. Certain qualifying B2B transactions may permit a simplified tax invoice.
Reference Architecture and End-to-End Process
1. Which Systems Participate in E-Invoicing?
POS or commerce platform: Captures sales transactions, items, quantities, discounts, payment information, and originating references.
ERP or accounting system: Maintains approved financial records, customer and supplier information, tax configurations, and relevant transaction relationships.
Electronic Invoice Generation Solution (EGS): Produces electronic invoices and associated notes using the required data structure and applicable technical controls.
Integration layer: Exchanges source data, transforms fields, transfers relevant documents and statuses, and coordinates supported technical workflows.
ZATCA FATOORA platform: Receives the required standard-invoice clearance or simplified-invoice reporting submissions.
Document archive: Stores the appropriate electronic invoices, notes, responses, and records under the applicable retention and access requirements.
Monitoring and exception workflow: Tracks incomplete, rejected, delayed, or unresolved transactions so responsible teams can investigate them.
2. How Does a Standard Tax Invoice Reach Clearance?
Capture: An approved B2B transaction becomes eligible for invoicing in ERP or another authorized system.
Classify: The invoicing workflow identifies the standard tax invoice type under the applicable rules.
Validate: Required seller, buyer, item, VAT, and transaction values are checked.
Generate: The EGS creates the required structured document and technical identifiers.
Submit: The standard invoice is sent to ZATCA's clearance service.
Confirm: The invoicing system evaluates the returned clearance result and associated document.
Deliver: The cleared invoice is shared with the buyer through an approved channel.
Archive and reconcile: The final document, ZATCA response, and accounting references are stored and matched.
3. How Does a Simplified Tax Invoice Reach Reporting?
Capture: The merchant records an eligible retail or service transaction.
Classify: The document is identified as a simplified tax invoice.
Validate: The EGS checks applicable transaction and VAT fields.
Generate and stamp: The solution creates the electronic invoice with the required cryptographic elements and QR code.
Present: The customer receives the compliant invoice through the permitted method.
Report: The relevant invoice XML is submitted to ZATCA within 24 hours of issuance.
Monitor: The business records the reporting response and investigates any validation issues.
Reconcile: Finance matches the reported document with the original sale and archive.
4. XML, QR Codes, and Required Invoice Information
Element | Purpose | What must be checked |
Invoice type | Select the correct legal and technical process | Standard, simplified, or associated note |
Seller identification | Identify the taxable supplier | Required seller details and VAT registration data |
Buyer information | Identify the customer where required | Applicable buyer fields and identification requirements |
Invoice reference | Distinguish the issued document | Valid and traceable invoice numbering |
Issue date and time | Establish document timing | Consistent required timestamps |
Currency | Identify transaction currency | Applicable currency and formatting rules |
Line items | Describe goods or services | Item description, quantity, unit price, and other applicable fields |
Discounts and charges | Adjust taxable values | Correct amounts and distribution |
VAT category | Determine tax treatment | Appropriate category and supporting information |
Taxable amount | Determine the tax base | Correct calculation and rounding |
VAT amount | Record tax charged | Applicable rate and amount |
Invoice total | Record the required total | Consistency between lines, tax, and final value |
UUID | Provide a document identifier | Required uniqueness and structure |
Invoice hash | Support document integrity | Correct calculation according to the specification |
Cryptographic stamp | Support authenticity and integrity | Applicable certificate and signing requirements |
QR code | Support required invoice verification information | Correct content and encoding for the relevant phase and document |
Original invoice reference | Link credit or debit notes | Correct relationship with the issued document |
XML structure | Provide machine-readable invoice data | Applicable ZATCA XML implementation standard |
Clearance/reporting result | Record regulatory processing status | Actual response and any warnings or errors |
5. Why XML and QR Must Be Treated Separately
XML is the structured document: The Phase 2 integration process uses XML that must satisfy the applicable ZATCA implementation requirements.
QR is a verification element: It contains prescribed encoded information; it is not a replacement for the underlying electronic invoice.
Different document paths exist: Standard and simplified invoices have different stamping and ZATCA-processing responsibilities.
Readable copies are not the submission format: Where a PDF/A-3 document with embedded XML is used, the submitted structured invoice follows the prescribed XML API requirements.
Cryptographic details matter: Implementations must follow the current security specifications rather than generating a QR code from an arbitrary group of text fields.
Reference Architecture in One Flow
ERP/POS sale → invoice classification → data validation → structured XML generation → applicable security and QR processing → clearance or reporting → ZATCA response → approved document delivery → ERP/POS status update → archiving and monitoring.
Implementation, Testing, and Ongoing Compliance
1. Prepare the Technical Environment
Identify taxpayer scope: Document the affected legal entities, VAT registrations, branches, and integration deadlines.
Inventory issuing systems: List the ERP applications, POS devices, accounting systems, and invoicing units that generate relevant documents.
Confirm connectivity: Check the available integrations and technical requirements for communicating with the invoicing solution and ZATCA.
Assign ownership: Identify finance, tax, IT, information security, and vendor responsibilities before production onboarding.
2. Test with Official ZATCA Resources
Developer documentation: Use the published data dictionary, XML implementation standard, and security requirements.
SDK: Validate generated documents using the official compliance and enablement tools.
Web validator: Check representative XML documents against supported technical rules.
Integration Sandbox: Test supported API interactions and response handling before production onboarding.
Production onboarding: Complete the required EGS onboarding and compliance process for the applicable taxpayer environment.
Passing the SDK or Sandbox is not equivalent to official production clearance, reporting acknowledgment, or a general guarantee of regulatory compliance.
3. Establish an Ongoing Compliance Process
Regulatory change review: Monitor relevant ZATCA publications and update the system only after assessing the changes that apply.
Invoice-type monitoring: Check whether standard and simplified documents are consistently routed through the correct process.
Certificate management: Track required cryptographic credentials and their lifecycle.
Exception resolution: Investigate warnings, rejections, connectivity problems, and unreported invoices.
Archive checks: Verify that issued documents and associated records remain retrievable under applicable requirements.
Implementation Blueprint and Data Flow: Step by Step
1. Step One: Determine Applicability and Scope
Confirm the wave: Review the taxpayer's official ZATCA integration notification and effective date.
Identify invoice types: Map standard invoices, simplified invoices, and related credit or debit notes.
Choose the pilot: Select one representative business process and a limited group of issuing systems.
Define acceptance criteria: Agree on document validity, successful processing, monitoring, and reconciliation requirements.
2. Step Two: Audit ERP, POS, and Invoicing Data
Map applications: List all systems involved in generating, transferring, approving, or storing invoices.
Identify authoritative fields: Determine which system controls tax codes, customer information, transaction values, and original document references.
Inspect source quality: Review missing buyer information, incorrect VAT categories, inconsistent item values, and branch identifiers.
Document existing gaps: Identify manual transfers and duplicated invoice generation.
3. Step Three: Define the Invoice Classification Rules
Establish document types: Apply the relevant VAT requirements to determine standard or simplified invoicing.
Map transaction conditions: Include eligible sales, advance payments, discounts, returns, and other relevant invoice scenarios.
Define notes: Specify when credit or debit notes are required and how they refer to original invoices.
Approve exceptions: Assign ambiguous tax treatment to the responsible tax team.
4. Step Four: Design XML and Security Processing
Map data fields: Convert approved ERP/POS information into the required structured document fields.
Apply valid formats: Check monetary amounts, timestamps, currencies, tax values, and the prescribed XML structure.
Configure identifiers: Establish UUID, invoice numbering, and other relevant technical fields.
Apply security requirements: Implement applicable hashes, QR elements, cryptographic stamps, and certificate handling according to the document type.
5. Step Five: Configure EGS Onboarding and ZATCA Connectivity
Identify EGS units: Determine the issuing units or devices requiring the appropriate onboarding approach.
Complete onboarding: Follow the prescribed compliance and production credential procedures.
Route API requests: Send standard invoices to clearance and simplified invoices to reporting, where Phase 2 applies.
Protect credentials: Restrict certificate and API credential access to authorized components.
6. Step Six: Build Response and Exception Handling
Record the result: Capture the applicable clearance or reporting response.
Classify failures: Distinguish invalid invoice content, authentication failures, network interruptions, and uncertain submission outcomes.
Protect document integrity: Prevent uncontrolled edits to issued or cryptographically processed invoices.
Set recovery rules: Use the appropriate correction or resubmission procedure, with escalation when tax review is necessary.
7. Step Seven: Synchronize ERP/POS and Archive Records
Match source references: Connect the original sale, issued invoice, associated note, and ZATCA processing result.
Update invoice status: Share the confirmed state with the authorized financial and operational applications.
Store required records: Preserve the appropriate XML, readable document, technical response, and related evidence.
Reconcile totals: Compare eligible invoices and notes with the underlying sales and accounting records.
8. Step Eight: Test Normal and Failure Scenarios
Standard invoice: Verify generation, clearance, delivery, and archiving.
Simplified invoice: Verify issue-time processing and reporting within the required deadline.
Credit/debit note: Check correct reference and processing route.
Invalid data: Test missing identifiers, inaccurate tax calculations, and XML validation errors.
Connectivity failure: Simulate API timeouts and unavailable services.
Business approval: Require finance and tax owners to confirm representative results before launch.
9. Step Nine: Launch and Maintain Production Operations
Pilot first: Begin with a defined set of transactions, branches, or issuing devices.
Monitor daily: Track pending, failed, cleared, reported, and unresolved documents using valid status definitions.
Review cutoffs: Watch simplified invoice reporting deadlines and unresolved clearance problems.
Expand carefully: Introduce additional entities and locations after validating the first production workflow.
Update procedures: Maintain documentation, credentials, escalation rules, and regression tests as requirements change.
Evaluation Framework: Requirements, Decision Matrix, and Alternatives
1. Essential Requirements for Vendor Selection
Saudi regulatory coverage: Demonstrable support for the relevant ZATCA document types, technical specifications, and integration processes.
ERP/POS compatibility: Working connectivity with the exact source applications and versions used by the business.
XML validation: Reliable generation and validation of the required structured invoice data.
Security capabilities: Appropriate onboarding, credential handling, cryptographic processing, and access controls.
Submission management: Separate clearance and reporting workflows with traceable response handling.
Exception recovery: Procedures for rejected, delayed, duplicated, and uncertain submissions.
Document storage: Suitable retrieval, access controls, and retention arrangements.
Commercial suitability: Transparent implementation, licensing, support, maintenance, and expansion costs.
2. Comparison of Integration Approaches
Decision factor | Native ERP/POS module | Dedicated e-invoicing solution | Custom API integration |
Main approach | E-invoicing functionality within an existing application | Specialized invoice processing connected to business systems | Business builds the required interfaces and processing |
Potential strength | Fewer separate application components | Dedicated workflow and compliance-focused functionality | Greater architectural control |
Source connectivity | Depends on the existing vendor | Depends on available connectors and interfaces | Requires custom development |
Clearance and reporting | Must be verified for the deployment | Must be demonstrated | Must be implemented and tested |
XML and QR processing | Depends on native capabilities | Core evaluation requirement | Internal implementation responsibility |
Security and onboarding | Vendor and customer responsibilities | Vendor and customer responsibilities | Primarily internal engineering responsibility |
Exception management | Product-dependent | Platform-dependent | Custom design and operation |
Regulatory updates | Dependent on vendor maintenance | Dependent on provider release process | Internal change-management responsibility |
Main limitation | Constraints of the current software | Vendor dependency and integration costs | Engineering and maintenance effort |
Best fit | Existing software meets the complete requirement | Multiple systems need dedicated invoicing coordination | Specialized requirements with capable internal teams |
3. Weighted Decision Matrix
Evaluation factor | Suggested weight | Evidence to request |
ZATCA workflow and document coverage | 25% | Validated standard, simplified, and note scenarios |
ERP/POS compatibility | 20% | Live integration with the actual systems |
Security and onboarding | 15% | EGS, certificates, access, and security evidence |
Error recovery and auditability | 15% | Rejected, delayed, and duplicate submission tests |
Operational scalability | 10% | Representative transaction-volume tests |
Support and regulatory maintenance | 10% | Documented responsibilities and update process |
Total ownership cost | 5% | Full commercial proposal |
Total | 100% | Evidence-based evaluation |
Score each alternative from 1 to 5 for every criterion and calculate:
Weighted vendor score = Sum of (criterion score ÷ 5 × criterion weight).
Mandatory legal, regulatory, and security requirements remain pass/fail conditions. A higher commercial score must not compensate for failing one of those requirements.
4. Questions to Ask Before Signing
Can the provider demonstrate both standard clearance and simplified reporting?
Which ERP/POS systems and versions are actually supported?
How are invoice rejections, warnings, and timeouts handled?
Which component performs EGS onboarding and cryptographic processing?
What evidence is preserved for each issued invoice?
How are regulatory changes assessed, tested, and released?
What happens when connectivity or the invoicing service becomes unavailable?
What are the support commitments, implementation costs, and data-exit arrangements?
Failure Modes, Security, Governance, and Validation
1. Invoice and Integration Failure Modes
Prevent incorrect documents
Invalid tax classification: Review whether the invoice should follow the standard or simplified process before document generation.
Wrong tax data: Validate applicable rates, categories, taxable amounts, and rounding.
Missing references: Check required identifiers, buyer information, and original-document links.
Invalid structured content: Reject or quarantine documents that fail required XML or security checks.
Recover processing failures
Clearance rejection: Do not treat the document as cleared; investigate the response and follow the permitted correction procedure.
Reporting rejection: Track the unsuccessful submission, determine the cause, and take the appropriate recovery action.
Timeout after submission: Verify the actual processing outcome before creating another invoice or repeating a request in a way that may cause duplication.
System outage: Apply ZATCA's relevant failure-notification and contingency requirements when an incident meets the applicable conditions.
2. Security and Document Integrity
Protect technical credentials
Restricted credentials: Limit access to the certificate information and keys associated with authorized invoicing components.
Protected communication: Apply the required secure transmission and authentication mechanisms.
Credential lifecycle: Manage onboarding, renewal, replacement, and revocation as applicable.
Access logs: Record relevant administrative changes and use of sensitive integration functions.
Preserve issued invoices
Integrity controls: Protect the structured invoice and required cryptographic relationships.
No uncontrolled editing: Correct issued-document problems through the applicable note or authorized correction process.
Secure archives: Restrict access to invoice records and preserve the information needed for retrieval.
Retention rules: Apply current legal and regulatory recordkeeping obligations to the storage design.
3. Governance and Compliance Ownership
Assign business responsibilities
Tax team: Approves invoice classification, VAT treatment, and regulatory interpretation.
Finance team: Owns accounting reconciliation, document history, and relevant transaction controls.
ERP/POS owners: Maintain correct source data, transaction records, and application configuration.
Integration team: Operates field mapping, data exchange, monitoring, and technical recovery.
Security team: Reviews certificate handling, access controls, and relevant system risks.
Maintain operational governance
Regulatory updates: Review official ZATCA releases before changing production behavior.
Change approval: Test new fields, mappings, certificate procedures, and application versions.
Exception ownership: Send errors to the team authorized to correct their underlying cause.
Evidence retention: Preserve the information needed to explain why a document was accepted, rejected, corrected, or reprocessed.
4. Validation Before and After Launch
Verify technical behavior
Schema tests: Validate structured XML against applicable technical rules.
API tests: Check successful, failed, delayed, and uncertain responses.
Security tests: Verify credential scope and protection against unauthorized submission.
Load tests: Simulate representative invoice volumes across branches or issuing systems.
Verify business results
Invoice completeness: Compare eligible source transactions with correctly generated electronic invoices.
Processing completeness: Verify the expected clearance or reporting outcome for each document.
Financial accuracy: Reconcile tax and invoice totals with approved source records.
Timeliness: Measure submission and response times against the applicable business and regulatory requirements.
Invoice Risk and Validation Matrix
Risk | Business consequence | Required control | Test evidence |
Wrong invoice classification | Incorrect submission process | Document-type rules | Standard/simplified test |
Missing seller VAT data | Invalid invoice | Required-field validation | Missing-field rejection |
Invalid VAT treatment | Incorrect tax values | Tax-rule verification | Representative VAT scenarios |
XML structure failure | Rejected document | Schema and business-rule checks | Validator result |
Invalid QR data | Verification failure | QR encoding validation | QR test |
Cryptographic processing error | Integrity or validation failure | Security implementation checks | Cryptographic validation |
Duplicate invoice generation | Conflicting invoice records | Stable document references | Replay test |
Clearance failure | Standard invoice cannot follow normal issuance flow | Response and correction procedure | Rejected clearance scenario |
Late simplified reporting | Missed regulatory reporting requirement | Deadline monitoring | Delayed reporting scenario |
Expired or invalid credentials | Submission failure | Credential lifecycle management | Authentication test |
Incorrect ERP/POS mapping | Financial inconsistency | Source mapping and reconciliation | Transaction-level comparison |
Unsupported invoice correction | Document integrity problem | Approved note and correction process | Credit/debit note test |
Missing archive record | Audit and retrieval difficulty | Archive reconciliation | Document retrieval test |
Unresolved system outage | Accumulating failed submissions | Incident and contingency procedures | Recovery exercise |
Saudi Arabia Use Cases and Measurable KPIs
Restaurants and cafés: Generate simplified tax invoices from eligible POS transactions and monitor their reporting status.
Retail chains: Coordinate invoice processing from multiple branches and preserve the original store and transaction references.
Supermarkets: Handle high volumes of simplified invoices with appropriate validation, queue monitoring, and reporting controls.
E-commerce businesses: Connect checkout, order management, and financial systems to the designated electronic invoicing process.
Wholesale distributors: Generate and clear standard tax invoices for eligible commercial customers before the required buyer-delivery step.
Professional services firms: Connect approved billing milestones, customer information, and tax calculations with the correct invoicing workflow.
Manufacturing companies: Link ERP sales invoices, delivery-related references, and related credit or debit notes.
Multi-entity businesses: Maintain the correct taxpayer, branch, and issuing-unit relationships across separate business entities.
Companies preparing for Phase 2: Use the official integration notice to plan onboarding, testing, and system upgrades before their individual deadline.
Finance shared-service teams: Monitor document status, unresolved rejections, and accounting reconciliation from a controlled operating process.
Illustrative Saudi Enterprise Use Case
Consider a hypothetical Saudi distribution company operating from Riyadh, Jeddah, and Dammam.
It uses ERP for commercial invoices, POS terminals for direct customer sales, and a dedicated e-invoicing component to process applicable electronic documents.
The business needs two distinct workflows:
Standard invoices: ERP supplies the approved commercial data, the invoicing solution generates the structured document, and the standard invoice follows clearance before the approved customer-delivery stage.
Simplified invoices: POS transactions produce the required electronic documents and QR information, while the reporting process sends them to ZATCA within the applicable 24-hour window.
The company monitors responses, investigates validation failures, and reconciles documents against source transactions.
Illustrative data flow:
ERP/POS → invoice classification → data validation → XML and applicable security elements → ZATCA clearance or reporting → response monitoring → document archive → finance reconciliation.
This example is hypothetical, not a documented Reachware implementation.
KPIs for E-Invoicing Integration
KPI | Formula or measurement | Business purpose |
Invoice generation success rate | Correctly generated eligible invoices ÷ eligible source transactions × 100 | Document completeness |
First-pass validation rate | Invoices passing defined initial validation ÷ invoices checked × 100 | Source data quality |
Standard clearance success rate | Standard invoices successfully cleared ÷ standard invoices submitted for clearance × 100 | Clearance reliability |
Simplified reporting success rate | Simplified invoices receiving the required successful reporting outcome ÷ eligible reporting submissions × 100 | Reporting reliability |
Reporting deadline compliance | Eligible simplified invoices reported within 24 hours ÷ all eligible simplified invoices due × 100 | Regulatory timeliness |
Invoice rejection rate | Rejected invoice submissions ÷ relevant total submissions × 100 | Submission quality |
Processing latency | Final confirmed response time − submission time | Technical processing performance |
Exception resolution time | Total time to resolve exceptions ÷ resolved exceptions | Recovery effectiveness |
Duplicate document incidents | Confirmed unintended duplicate issued invoices | Document integrity |
ERP/POS reconciliation rate | Records passing approved reconciliation ÷ records tested × 100 | Financial consistency |
Archive completeness | Required documents and records successfully retained ÷ eligible documents × 100 | Record availability |
Invoice retrieval time | Time required to locate an authorized document | Audit readiness |
Unresolved submission backlog | Number and age of pending invoices | Operational risk |
Manual processing hours | Staff hours spent on invoicing preparation and exception handling | Administrative effort |
Example 1: Measuring Clearance Success
Assume a company submits 4,000 eligible standard tax invoices for clearance in a defined reporting period. Of these, 3,940 receive successful clearance outcomes.
Clearance success rate = (3,940 ÷ 4,000) × 100 = 98.5%.
The remaining 60 invoices must be investigated. The business should separately identify rejected, pending, and unresolved submissions.
Example 2: Measuring Reporting Timeliness
Suppose a retailer issues 12,000 simplified tax invoices and confirms that 11,880 received the required reporting outcome within the prescribed time window.
Reporting deadline compliance = (11,880 ÷ 12,000) × 100 = 99%.
The remaining 120 require investigation. This metric does not establish compliance for an individual late document.
Example 3: Measuring Validation Errors
Assume 2,500 invoices are checked before submission, and 75 fail the approved initial validation rules.
Initial validation error rate = (75 ÷ 2,500) × 100 = 3%.
This calculation helps the team assess the quality of source data and transformation logic. It is not a measure of ZATCA's regulatory approval rate.
All examples use hypothetical figures and standard percentage calculations. They are not verified Reachware customer outcomes or published Saudi market benchmarks.
Where Reachware Fits and When to Request a Demo
Reachware Fatoora is presented as an electronic invoicing solution for Saudi businesses, with published capabilities relating to data validation, source-system integration, structured invoicing, secure transmission, QR codes, cryptographic processing, archiving, and operational dashboards.
These functions make it relevant to businesses evaluating ZATCA e-invoicing integration in Saudi Arabia. Actual suitability depends on the source applications, issuing units, taxpayer configuration, document types, and implementation evidence.
1. Which Problems Can Reachware Fatoora Help Address?
Multiple source systems: Reachware describes support for processing invoicing information from single or multiple data sources.
ERP/POS integration: The product is positioned to connect business applications with electronic invoicing workflows.
Data validation: Its published capabilities include checking invoice information before submission.
Submission and acknowledgment: Reachware describes integration with the relevant ZATCA processes and returning submission information.
Document management: The product page identifies QR generation, cryptographic capabilities, sequential numbering, and archiving.
Monitoring: Reachware describes dashboards for viewing invoice statuses, submissions, and exceptions.
These capabilities should be tested in the customer's environment. The product description does not independently prove that every requested ERP/POS connector, regulatory scenario, or compliance requirement is supported without additional configuration.
2. When Should a Business Request a Demo?
It has received a Phase 2 integration notice or needs to validate existing compliance workflows.
Its ERP and POS systems generate invoices through separate manual processes.
Finance teams repeatedly investigate clearance failures or missing reporting outcomes.
Multiple branches create difficulties with issuing-unit management and invoice reconciliation.
Tax staff need better visibility into document status and validation exceptions.
The organization is comparing native ERP invoicing, dedicated solutions, and custom integration.
Management wants to test a specific ZATCA workflow before choosing a provider.
3. What Should Reachware Demonstrate?
Evaluation area | Required demonstration | Key decision question |
ERP compatibility | Actual ERP invoice extraction | Can the required data be retrieved correctly? |
POS compatibility | Representative store transaction | Does the source system connect as expected? |
Standard invoices | Full clearance workflow | Is the successful clearance result captured? |
Simplified invoices | Generation and reporting workflow | Is reporting handled within the required window? |
XML | Representative structured invoice | Does the document pass applicable validation? |
QR and security | QR and cryptographic processing | Are the required technical controls implemented? |
EGS onboarding | Issuing-unit setup and credential process | Who owns and manages onboarding? |
Credit/debit notes | Referenced correction document | Can adjustments be processed correctly? |
Error handling | Invalid data and rejected submission | Can the cause be identified and resolved? |
Recovery | Connectivity failure and uncertain response | Is duplicate or incorrect processing prevented? |
Monitoring | Cleared, reported, rejected, and pending examples | Can staff trace document status? |
Archiving | Retrieval of original records and responses | Is the required evidence available? |
Security | Restricted access and credential management | Are sensitive functions protected? |
Commercial terms | Implementation, support, and licensing proposal | Is the operating model appropriate? |
4. How Should the Final Decision Be Made?
Confirm the business's applicable ZATCA wave and required document types.
Validate the exact ERP/POS integrations and issuing-unit arrangements.
Test standard clearance, simplified reporting, credit/debit notes, and negative scenarios.
Review credential management, data access, monitoring, and archiving.
Require finance and tax approval of the proposed processing rules.
Compare the full cost and operating responsibilities of all suitable alternatives.
For the technical process of turning transactions into structured invoices, read (From POS to Tax-Ready Invoice).
For a focused discussion of business-system connectivity, see (POS and ERP E-Invoice Integration).
To evaluate the product, explore (ZATCA e-invoicing solution) or request a tailored Reachware Fatoora demonstration using your actual invoice types, source systems, and ZATCA processing requirements.
Frequently Asked Questions About ZATCA E-Invoicing Integration
1. How do businesses integrate e-invoicing with ZATCA?
Businesses identify their applicable requirements, configure a compliant Electronic Invoice Generation Solution, map ERP/POS invoice data, complete the necessary onboarding, and connect to the relevant clearance or reporting APIs. They must also test security, responses, corrections, and archiving.
2. What is the difference between ZATCA clearance and reporting?
Clearance applies to standard tax invoices and requires ZATCA processing before normal buyer delivery. Reporting applies to simplified tax invoices, which are generated and presented to customers before their XML is submitted to ZATCA within 24 hours of issuance.
3. Which invoice data fields require validation?
Relevant fields include seller identification, applicable buyer information, invoice references, dates, line items, quantities, prices, discounts, tax categories, VAT amounts, and totals. Phase 2 also requires prescribed technical identifiers, structured XML, and applicable security and QR elements.
4. How can ERP and POS systems connect to e-invoicing?
They can use supported APIs, connectors, or approved data exchange mechanisms to send transaction details to a compliant invoicing solution. The integration validates and transforms records, routes the document to the required ZATCA process, and returns confirmed status information.
5. What is the difference between Phase 1 and Phase 2?
Phase 1 requires compliant electronic invoice generation and storage. Phase 2 introduces additional structured-data and technical requirements, onboarding, and integration with ZATCA's FATOORA platform according to the taxpayer's applicable wave.
6. Are XML and QR codes required for every invoice?
Requirements depend on the implementation phase and invoice type. Phase 2 requires the applicable structured XML for submission, and QR and cryptographic rules vary by document and processing route. The current technical specifications should guide implementation.
7. Must simplified invoices be cleared before giving them to customers?
No. Under the normal Phase 2 reporting workflow, compliant simplified tax invoices are generated and presented to customers, then submitted to ZATCA for reporting within 24 hours of issuance.
8. What happens if ZATCA rejects an invoice?
The business should review the rejection, identify whether the cause is data, structure, tax treatment, or technical configuration, and follow the permitted correction or resubmission procedure. A rejected document should not be treated as successfully cleared or reported.
9. Can businesses correct issued invoices by editing the original document?
Issued electronic invoices and related notes must follow the applicable legal and technical correction requirements. Credit or debit notes may be required for relevant adjustments and must preserve the appropriate link to the original document.
10. Is passing the ZATCA Sandbox enough to prove compliance?
No. Testing tools help identify technical problems, but successful Sandbox or SDK results do not replace the required production onboarding, actual ZATCA processing, or the taxpayer's compliance obligations.
11. How should companies choose an e-invoicing provider?
They should verify invoice-type coverage, ERP/POS connectivity, XML validation, security, onboarding, error recovery, archiving, support, regulatory maintenance, and total cost using real demonstrations.
12. When should a company evaluate Reachware Fatoora?
Reachware Fatoora is worth evaluating when a business needs to connect invoicing sources, validate structured documents, manage the appropriate ZATCA workflows, or improve invoice-processing visibility. Suitability should be confirmed against the actual taxpayer and technology environment.