Generating an electronic tax invoice inside an ERP does not by itself complete Saudi Arabia’s Phase 2 e-invoicing requirement. Finance and IT teams also need to make sure invoice data, XML generation, validation, security, FATOORA connectivity, regulatory responses, and reconciliation work as one controlled process.
That is the challenge behind ZATCA ERP Integration.
Saudi Arabia’s Phase 2, known as the Integration Phase, requires targeted taxpayers to connect their e-invoicing solutions with ZATCA’s FATOORA Platform, generate invoices in the prescribed electronic format, and include the additional information required under the Phase 2 framework. The rollout began on January 1, 2023 and continues in waves.
For organizations running Microsoft ERP environments, Dynamics 365 ZATCA e-invoicing therefore needs to extend beyond invoice generation into the broader tax and finance workflow.
The connected process looks more like:
ERP Transaction → ZATCA-Compliant XML → Validation and Security → FATOORA → Clearance or Reporting → Response → ERP Reconciliation
As of September 2026, ZATCA’s latest published selection is Wave 25, covering taxpayers whose VAT-subject revenues exceeded SAR 187,500 during 2022, 2023, 2024, or 2025. ZATCA states that taxpayers in this wave must integrate by no later than February 1, 2027. Individual businesses should still rely on their direct ZATCA notification when determining their applicable deadline.
Connect Your ERP to ZATCA End to End
Bring ERP data, FATOORA APIs, regulatory processing, responses, and reconciliation into one controlled integration.
What Is ZATCA ERP Integration?
ZATCA ERP integration connects invoice transactions created inside an ERP with the structured documents, validation, security, API communication, regulatory processing, and responses required by Saudi Arabia’s e-invoicing framework.
ZATCA defines an electronic invoice as a tax invoice generated in a structured electronic format through electronic means. A paper invoice that has simply been scanned, copied, or converted into an electronic file is not considered an electronic invoice.
The distinction matters for ERP teams.
Customer information, VAT treatment, invoice lines, legal entities, currency, product or service information, and adjustment references may already exist inside the ERP. ZATCA e-invoicing integration extends those transactions into a regulated electronic process.
A disconnected model may stop at:
ERP → Invoice → External Handling
A production-ready model continues through:
ERP → Structured XML → FATOORA API → ZATCA Response → ERP Status → Reconciliation
For Microsoft environments, FATOORA integration for Dynamics 365 Finance and Operations should therefore be designed around the full transaction lifecycle rather than XML generation alone.
How Does ZATCA Phase 2 Change ERP Requirements?
Phase 1 established electronic invoice generation, while Phase 2 adds direct integration between the taxpayer’s electronic invoicing solution and ZATCA’s FATOORA Platform.
| Area | Phase 1: Generation | Phase 2: Integration |
| Start date | December 4, 2021 | January 1, 2023 in waves |
| Core requirement | Generate and store compliant e-invoices | Integrate the e-invoicing solution with FATOORA |
| Invoice structure | Required electronic fields | Prescribed electronic format plus Phase 2 fields |
| ZATCA connection | No Phase 2 API integration | Integrated communication with ZATCA |
| Standard tax invoices | Generated electronically | Subject to clearance |
| Simplified tax invoices | Generated electronically | Reported to ZATCA |
| Security | Phase 1 controls | Onboarding and additional cryptographic requirements |
ZATCA states that the Integration Phase introduces system integration, specific electronic formats, and additional invoice fields. This is why a business that met the Generation Phase requirements should not assume its existing ERP configuration is automatically ready for ZATCA Phase 2 integration.
How Does ZATCA ERP Integration Work?
The invoice starts inside the ERP, but the regulatory path changes depending on whether the transaction requires clearance or reporting.
The Transaction Is Created in the ERP
The process begins with the financial transaction. Seller, buyer, product or service, VAT, invoice lines, currency, legal entity, and document references originate in the ERP.
If this information is incomplete, the problem moves downstream into XML validation or ZATCA processing.
ERP Data Is Mapped Into the Required Electronic Structure
The e-invoicing solution converts the source transaction into the structured format required for Saudi e-invoicing.
This is not simply a file conversion exercise. Each ERP field must map to the appropriate electronic invoice element, including applicable tax categories, document references, identifiers, totals, and transaction details.
Required Security Controls Are Applied
Phase 2 introduces onboarding and cryptographic requirements for the electronic invoicing solution.
For Dynamics 365 Finance, Microsoft’s Saudi onboarding process obtains a Compliance CSID first and then a Production CSID after the required compliance checks are completed. These identifiers are used when communicating with ZATCA’s electronic invoicing environment.
Standard Tax Invoices Follow Clearance
Standard tax invoices, commonly associated with B2B transactions, are submitted in XML to FATOORA for invoice clearance.
ZATCA validates the electronic tax invoice against applicable requirements. Once it passes the required checks, FATOORA clears the invoice and returns the processed XML before it is presented to the buyer.
Simplified Tax Invoices Follow Reporting
Simplified tax invoices, commonly associated with B2C transactions, follow a different route.
The compliant solution generates and stamps the invoice, includes the required QR code, and reports the XML to FATOORA within 24 hours of generation.
ZATCA Responses Return to the Finance Process
Acceptance, warnings, validation errors, clearance results, and reporting statuses need to remain connected to the original ERP transaction.
This return path is critical. Otherwise, an invoice may appear complete inside the ERP while the regulatory process is still unresolved.
Connect ZATCA Compliance to the Full Transaction Lifecycle
A successful FATOORA connection is only one part of readiness. Invoice creation, validation, regulatory responses, corrections, and reconciliation also need to operate reliably.
What Does Dynamics 365 Need for ZATCA Integration?
Dynamics 365 needs the right legal-entity data, tax configuration, Electronic Invoicing setup, ZATCA onboarding, security, and response handling before Phase 2 transactions can run reliably.
Microsoft currently lists Saudi Arabia as available for generation and direct submission of electronic invoices to ZATCA from Dynamics 365 Finance. Supported scenarios include sales and project invoices, customer prepayments, credit notes, and debit notes.
Microsoft’s Saudi configuration also requires both Electronic Invoicing service setup and Finance-side business-data configuration.
| Readiness Area | What to Confirm in Dynamics 365 | Why It Matters for ZATCA Phase 2 |
| Legal Entity and VAT Registration | Confirm the Saudi legal entity, registered business details, VAT registration number, and taxpayer information used in invoice generation. | ZATCA must identify the correct issuing taxpayer. Incomplete or incorrect entity data can affect invoice validation, onboarding, and regulatory submission. |
| Customer and Buyer Information | Validate customer names, addresses, registration details, VAT numbers where applicable, and other identifiers required for the invoice type. | Buyer information flows directly into the structured electronic invoice. Missing or inconsistent data can result in incomplete invoices or validation failures. |
| VAT and Tax Configuration | Review VAT codes, tax categories, rates, exemptions, zero-rated scenarios, and the tax treatment applied to transactions. | ERP tax configuration determines how VAT values and categories appear in the ZATCA invoice. Incorrect setup can lead to inaccurate tax reporting or failed business-rule validation. |
| Invoice and Transaction Data | Confirm invoice numbers, dates, document types, currencies, line items, quantities, prices, discounts, references, and adjustment information. | These transaction fields form the core of the ZATCA-compliant electronic invoice. Missing data can prevent the invoice from passing structural or regulatory validation. |
| Electronic Invoicing Configuration | Verify the required Saudi Electronic Invoicing features, processing parameters, mappings, and submission logic for the relevant legal entities. | These configurations control how Dynamics 365 converts ERP transactions into the required electronic format and moves them into the ZATCA processing workflow. |
| FATOORA Onboarding and CSIDs | Confirm that Compliance CSIDs, Production CSIDs, credentials, and environment-specific onboarding requirements are completed and correctly configured. | These credentials allow the e-invoicing solution to authenticate with FATOORA for compliance testing and production submission. Without valid onboarding, Phase 2 transactions cannot move into production. |
| Response and Exception Handling | Define how clearance results, reporting statuses, warnings, validation errors, rejected invoices, corrections, and resubmissions return to Dynamics 365. | Production readiness depends on how failures are handled after submission. Teams need to identify the issue, correct it, resubmit the invoice, and keep ERP and ZATCA statuses aligned. |
A ZATCA readiness assessment in Dynamics 365 should therefore assess the full transaction path, not only whether the ERP can produce an XML file.
What Data Must Be Accurate Before ZATCA Integration?
ZATCA integration depends on the accuracy of the invoice and tax data already stored in the ERP. If that source information is incomplete or inconsistent, the issue will surface later during XML validation, clearance, reporting, or reconciliation.
Before FATOORA connectivity is tested, teams should confirm that the ERP can consistently produce the data required for each electronic invoice.
- Legal entity data: The registered seller name, VAT registration number, business address, and entity details must identify the correct taxpayer issuing the invoice.
- Customer information: Buyer names, addresses, identifiers, and VAT numbers where applicable need to match the requirements for the invoice type being processed.
- Invoice header data: Invoice number, issue date, currency, document type, payment information, and transaction references need to flow correctly into the electronic invoice.
- Invoice line data: Product or service details, quantities, unit values, prices, discounts, taxable amounts, and applicable tax information need to remain accurate at line level.
- VAT configuration: Tax categories, VAT rates, exemptions, zero-rated treatments, taxable values, and VAT totals need to reflect the actual transaction.
- Credit and debit note data: Adjustments should reference the correct original invoice and include the appropriate reason, values, and VAT treatment.
- Units and permitted codes: ERP values need to map correctly to the units, codes, and classifications accepted within the required electronic invoice structure.
The main risk is not simply a missing field. A value can exist in the ERP and still be unusable if it is inconsistent, incorrectly mapped, or maintained in a format that does not meet the ZATCA requirement.
For implementation teams, the practical question is:
Can the ERP generate every required invoice and tax value correctly, without manual correction or enrichment before submission to FATOORA?
If not, the data issue should be resolved before end-to-end ZATCA integration testing begins.
How Does FATOORA Onboarding Fit Into ERP Integration?
FATOORA onboarding establishes the credentials and compliance status the electronic invoicing solution needs before it can submit production transactions to ZATCA.
For Dynamics 365 environments, the Saudi legal entity needs valid VAT registration details and access to the Saudi taxation portal. The onboarding process first obtains a Compliance CSID for compliance testing and then a Production CSID for live invoice submission.
That is why onboarding should be planned as part of the broader FATOORA integration for Dynamics 365 Finance and Operations, alongside ERP configuration, Electronic Invoicing setup, credentials, API connectivity, testing, and production deployment.
ERP Configuration → Electronic Invoicing Setup → CSID Onboarding → FATOORA API Integration → Compliance Testing → Production
Where the integration also needs to exchange data with middleware, external applications, or additional enterprise systems, API development and system integration services can support the required authentication, data exchange, response handling, and monitoring.
How Should ZATCA ERP Integration Be Tested?
Testing should prove that both successful transactions and failed transactions can move through a controlled finance process.
| Test area | What to confirm |
| ERP transaction | Correct entity, customer, invoice type, and transaction data |
| VAT | Correct rates, categories, exemptions, and totals |
| Data mapping | Required ERP fields populate the correct electronic elements |
| XML validation | Invoice meets ZATCA structural and business rules |
| Security | Applicable cryptographic and authentication controls work |
| Clearance | Standard tax invoices complete the clearance lifecycle |
| Reporting | Simplified invoices are submitted within the required process |
| Responses | Warnings, errors, and successful statuses return correctly |
| Adjustments | Credit and debit notes reference the right invoice |
| Reconciliation | ERP status matches the final ZATCA status |
Testing should deliberately include scenarios such as missing VAT information, incorrect customer identifiers, XML validation errors, API failures, authentication issues, rejected invoices, and corrections.
The real production test is:
Error → Identify Cause → Correct → Resubmit → Receive Response → Reconcile
A successful API call alone does not demonstrate operational readiness.
What Business Value Can ZATCA ERP Integration Create?
A connected ZATCA integration can reduce manual invoice work, improve visibility, and make compliance easier to manage within the existing ERP process.
Less Manual Invoice Work
Invoices can move from the ERP into FATOORA without repeated uploads, re-entry, or separate status tracking, reducing processing effort and manual handoffs.
Fewer Avoidable Errors
VAT issues, missing fields, and mapping problems can be identified earlier, helping teams reduce rework and correct issues before submission failures occur.
Clearer Invoice Status
Clearance, reporting, warning, and rejection statuses can remain connected to the original ERP transaction, making it easier to identify which invoices are complete and which need attention.
Easier Reconciliation
The ERP invoice, ZATCA submission, response, and subsequent adjustment can remain linked through one process, improving traceability, VAT control, and audit readiness.
7 Best Practices for ZATCA ERP Integration
Reliable FATOORA integration depends on how well the ERP, regulatory configuration, data, APIs, and finance processes continue to work after go-live.
- Validate source data first. Correct seller, customer, VAT, line-level, and reference information before integration testing.
- Separate clearance and reporting scenarios. Standard and simplified tax invoices follow different ZATCA processing paths.
- Map requirements before customizing the ERP. Determine what existing platform capabilities already support before introducing custom development.
- Complete onboarding early. Compliance and Production CSIDs need to be available for realistic end-to-end validation.
- Test real finance scenarios. Include invoices, credit notes, debit notes, VAT variations, and relevant legal entities.
- Design exception handling with the successful path. Every rejected or failed invoice needs an owner, correction path, resubmission process, and final reconciliation.
- Establish post-go-live ownership. ZATCA requirements, ERP configurations, APIs, security credentials, and finance procedures all need ongoing governance.
For Microsoft environments, these controls should align with broader Dynamics 365 Finance and Operations implementation practices.
Enterprises operating the same ERP across Saudi Arabia and other GCC jurisdictions should also keep ZATCA-specific processing separate from other national frameworks. The Dynamics 365 GCC e-invoicing readiness guide provides the wider multi-country context without treating GCC mandates as interchangeable.
How CaliberFocus Supports ZATCA ERP Integration
CaliberFocus connects Saudi e-invoicing requirements with ERP data, Dynamics 365 configuration, FATOORA integration, security, testing, and finance operations.
The objective is not simply to establish connectivity with ZATCA. It is to make invoice creation, XML generation, VAT validation, clearance, reporting, responses, exceptions, and reconciliation work as one production-ready process.
For Dynamics 365 environments, that can include readiness assessment, Electronic Invoicing configuration, data mapping, onboarding, Phase 2 testing, integration design, exception workflows, and deployment support.
After go-live, Dynamics 365 managed services can support regulatory configuration changes, integration monitoring, production issues, and ongoing platform maintenance.
Move From FATOORA Connectivity to Production Readiness
Build a ZATCA e-invoicing process that finance and IT teams can monitor, correct, reconcile, and maintain after go-live.
Key Takeaways for ZATCA ERP Integration
ZATCA Phase 2 turns Saudi e-invoicing into an integrated ERP and regulatory transaction lifecycle.
Phase 2 requires targeted taxpayers to connect compliant e-invoicing solutions with FATOORA.
The process begins with accurate invoice and VAT data inside the ERP.
Standard tax invoices follow the clearance model.
Simplified tax invoices follow reporting and must be submitted within 24 hours.
FATOORA onboarding and CSIDs form part of production integration.
Dynamics 365 Finance supports direct Saudi electronic invoice submission, but configuration and testing are still required.
Regulatory responses and exceptions need to return to the finance workflow.
Production ownership continues after go-live.
Frequently Asked Questions
ZATCA ERP integration connects invoice and VAT data generated in an organization’s ERP with Saudi Arabia’s FATOORA Platform. It covers structured electronic invoice generation, regulatory validation, security, API submission, clearance or reporting, response processing, exception handling, and reconciliation with the original financial transaction.
ZATCA Phase 2 is the Integration Phase of Saudi Arabia’s e-invoicing program. It requires targeted taxpayers to connect compliant electronic invoicing solutions with FATOORA, issue invoices in the prescribed format, and meet additional technical and data requirements. ZATCA is implementing Phase 2 progressively through taxpayer waves.
Clearance applies to standard tax invoices. The XML is submitted to FATOORA for validation and clearance before the cleared invoice is presented to the buyer. Reporting applies to simplified tax invoices, which are generated by the compliant solution and transmitted to FATOORA within 24 hours.
Yes. Microsoft lists Saudi Arabia as available for direct electronic invoice submission to ZATCA from Dynamics 365 Finance. Supported scenarios include sales invoices, project invoices, customer prepayments, credit notes, and debit notes. Businesses still need the required Saudi configuration, onboarding, credentials, tax data, and testing.
A Cryptographic Stamp Identifier is obtained during onboarding of the electronic invoicing solution. Microsoft describes separate Compliance and Production CSIDs in its Dynamics 365 onboarding process. These credentials support compliance testing and production communication with ZATCA’s electronic invoicing environment.
No. A QR code is one component of the Saudi e-invoicing requirements and does not replace the required invoice data, electronic structure, VAT rules, security controls, FATOORA integration, and applicable clearance or reporting process. Compliance depends on the complete invoice and transaction lifecycle defined by ZATCA.
Make ZATCA ERP Integration Production-Ready
CaliberFocus helps enterprises design and implement production-ready ZATCA ERP integration within Dynamics 365 and complex finance environments.
