FATOORA is ZATCA’s electronic invoicing platform that supports the submission, validation, clearance, and reporting of electronic invoices in Saudi Arabia. For businesses using Dynamics 365 Finance & Operations, FATOORA is part of the wider e-invoicing process that connects the ERP’s financial transactions and invoice data with ZATCA’s regulatory requirements.
- FATOORA: What It Is and How It Works With Dynamics 365 Finance & Operations
- How FATOORA and Dynamics 365 F&O Work Together
- FATOORA Clearance Vs. Reporting: How ZATCA Processes Different Invoices
- FATOORA Simulation Testing: What Dynamics 365 F&O Needs to Validate Before Go-Live
- Dynamics 365 F&O And FATOORA: What Needs to Be Ready Before Production
- How CaliberFocus Approaches FATOORA Integration With Dynamics 365 F&O
Saudi Arabia’s mandatory e-invoicing requirements make this connection important for businesses across major industries. D365 Finance & Operations remains the system where financial transactions and invoices are generated, while the connected FATOORA process supports the required submission, clearance, reporting, and validation. If the ERP and e-invoicing process are not aligned, businesses can face invoice rejections, processing delays, and compliance gaps.
The relationship can be understood simply:
Finance & Operations
Generation
Integration
Reporting
to ERP
For finance, tax, and technology leaders, this raises several practical questions:
- How does an invoice move from Dynamics 365 Finance & Operations to FATOORA?
- Which invoices require clearance or reporting?
- How are invoice data and required ZATCA controls handled?
- What does FATOORA simulation testing validate?
- How can a business determine whether its D365 F&O environment is ready for production?
For organizations managing Dynamics 365 ZATCA e-invoicing, the ERP configuration and FATOORA interaction need to work as one connected business process. The Dynamics 365 ZATCA e-invoicing framework provides the broader implementation context for connecting these requirements with an enterprise ERP environment.
Connect FATOORA With Your Dynamics 365 Finance & Operations Environment
Understand how Dynamics 365 Finance & Operations, FATOORA, and ZATCA e-invoicing requirements come together within the invoice workflow.
FATOORA: What It Is and How It Works With Dynamics 365 Finance & Operations
FATOORA is the ZATCA e-invoicing environment through which businesses in Saudi Arabia submit and process electronic invoices under the Kingdom’s e-invoicing requirements. When Dynamics 365 Finance & Operations is the ERP, FATOORA becomes part of the connected e-invoicing process rather than a replacement for the finance system.
How FATOORA and Dynamics 365 F&O Work Together
Dynamics 365 Finance & Operations remains the system where financial transactions are recorded and invoice information is generated, while the connected FATOORA process supports the applicable ZATCA e-invoicing requirements.
The relationship can be viewed as a connected flow:
A FATOORA ERP integration connects the business’s invoicing environment with the applicable ZATCA e-invoicing process. Depending on the implementation, the integration layer handles the exchange of invoice information and responses between Dynamics 365 F&O and the ZATCA environment through the required interfaces and APIs.
The integration is not simply an API connection. D365 F&O configuration, invoice data, invoice classification, integration, and response handling all need to work together.
For organizations implementing or modernizing D365 F&O, this also needs to fit into the wider Dynamics 365 implementation process, including ERP configuration, integrations, testing, and business process validation.
This is where Dynamics 365 ZATCA e-invoicing becomes relevant at the implementation level, covering the ERP configuration, ZATCA connectivity, invoice scenarios, response handling, and testing required for the e-invoicing process.
What Needs to Work Across the Integration
For the process to operate correctly, businesses need alignment across several areas:
- ERP configuration: D365 F&O must generate the required invoice information.
- Integration: Invoice data and responses need to move correctly between the ERP and ZATCA environment.
- Invoice processing: The applicable clearance or reporting workflow needs to be supported.
- Authentication: Required credentials and certificates must be configured for the relevant environment.
- Response handling: Validation results, errors, and rejections need to be handled within the business process.
- Testing: End-to-end scenarios should be validated before production use.
The key point is that FATOORA and Dynamics 365 F&O perform different roles within the same e-invoicing process: the ERP manages the business transaction and invoice, while the connected ZATCA environment applies the required electronic invoicing workflow.
How an Invoice Moves From Dynamics 365 F&O to FATOORA
The invoice starts in Dynamics 365 Finance & Operations and moves through the connected FATOORA and ZATCA process before the result returns to the ERP.
Dynamics 365 Finance & Operations
D365 F&O generates the invoice from the underlying business transaction, customer information, tax setup, and configured financial data.
Invoice Moves Through the FATOORA Workflow
The connected e-invoicing process sends the required invoice information to the applicable FATOORA and ZATCA workflow.
Validation, Clearance or Reporting
FATOORA applies the applicable ZATCA processing workflow based on the invoice type, including clearance or reporting where required.
Result Returns to the ERP
The processing result returns to the connected ERP workflow for successful completion, correction, or resubmission where required.
The process works as one connected finance workflow. D365 F&O creates and manages the invoice, the integration carries the required information into the FATOORA and ZATCA process, and the resulting status or response comes back into the ERP.
This connection allows businesses to manage Saudi e-invoicing within their existing finance operations instead of treating compliance as a separate process.
FATOORA Clearance Vs. Reporting: How ZATCA Processes Different Invoices
FATOORA does not process every Saudi e-invoice through the same workflow. The applicable ZATCA process depends on the type of invoice being issued, with standard tax invoices generally following the clearance model and simplified tax invoices following the reporting model.
| Clearance | Reporting | |
| Typically applies to | Standard tax invoices | Simplified tax invoices |
| ZATCA process | Invoice is submitted to ZATCA for clearance before completion of the issuance process | Invoice is issued and then reported to ZATCA within the applicable reporting requirement |
| Business focus | Successful ZATCA processing is part of the invoice flow | Accurate invoice generation and timely reporting are critical |
| Dynamics 365 F&O consideration | The ERP and connected FATOORA process need to support the clearance workflow | The ERP and connected FATOORA process need to support the reporting workflow |
What This Means for Dynamics 365 Finance & Operations
The distinction needs to be reflected in the way invoices are configured and processed in D365 F&O. A business may have different invoice scenarios running through the same ERP, so the connected FATOORA process needs to apply the appropriate ZATCA treatment to each one.
For finance and tax teams, this means looking beyond the API connection itself. Invoice classification, required data, submission timing, responses, and exception handling all form part of the e-invoicing workflow.
This becomes particularly important for organizations operating across GCC markets, where e-invoicing models and implementation requirements differ by country. The Dynamics 365 GCC e-invoicing readiness guide provides a broader view of how these requirements can affect an enterprise D365 environment.
Why the Difference Matters
Getting the workflow right helps reduce invoice exceptions, processing delays, and manual corrections across finance operations.
When the invoice type, ERP configuration, and ZATCA submission process are not aligned, an issue that begins in e-invoicing can affect downstream finance activities. That makes clearance and reporting an important part of the overall Dynamics 365 F&O e-invoicing process, rather than a separate technical consideration.
FATOORA Simulation Testing: What Dynamics 365 F&O Needs to Validate Before Go-Live
FATOORA simulation testing helps businesses validate whether their Dynamics 365 Finance & Operations e-invoicing process works correctly before moving to production. It provides a controlled environment to test invoice scenarios, ZATCA submission workflows, and system responses without affecting live transactions.
The testing should cover the key parts of the FATOORA API integration and the business process behind it:
| What to Test | What It Confirms |
| Invoice generation | D365 F&O produces the required invoice information |
| ZATCA submission | Invoice data reaches the applicable FATOORA/ZATCA process |
| Clearance or reporting | The correct workflow is applied to each invoice type |
| Invoice scenarios | Standard, simplified, credit and debit notes work as required |
| Responses | Validation results and exceptions are handled correctly |
The objective is not simply to confirm that the API connection works. It is to verify that invoices can move from Dynamics 365 F&O through the FATOORA process correctly and that the resulting responses can be handled within the finance workflow.
For businesses preparing for production, simulation testing can also expose gaps in D365 F&O configuration, invoice data, integration, and business scenarios before they affect live transactions. This provides a practical starting point for a broader ZATCA readiness assessment in Dynamics 365
Dynamics 365 F&O And FATOORA: What Needs to Be Ready Before Production
For a business already running its finance operations in Dynamics 365 Finance & Operations, FATOORA readiness starts with understanding how existing invoice processes connect with ZATCA’s e-invoicing requirements. The objective is to make that connection work reliably across the invoices, transaction types, and finance workflows the business actually handles.
| What the Business Already Has | What Needs to Work With FATOORA | What to Confirm Before Production |
| Transactions and invoices in D365 F&O | Invoice information moves into the applicable ZATCA e-invoicing process | Required customer, tax, transaction, and invoice data is generated correctly |
| Existing D365 F&O configuration | Saudi e-invoicing requirements are reflected in the ERP workflow | The configuration supports the applicable invoice scenarios |
| ERP-to-FATOORA integration | Invoice data and responses are exchanged between the systems | FATOORA API integration works reliably without creating manual processing points |
| Different invoice types | Each invoice follows its applicable ZATCA treatment | Clearance and reporting workflows are correctly supported |
| Finance operations | ZATCA responses become part of the normal invoice process | Errors, rejections, and validation responses can be identified and acted on |
| Business transaction scenarios | Real transactions are processed through the FATOORA workflow | Key scenarios are tested before production |
What Businesses Should Validate
The key question is whether FATOORA works with the way the business already creates, processes, and manages invoices in Dynamics 365 Finance & Operations.
Before production, finance, tax, and technology teams should be able to answer:
- Is D365 F&O generating the required invoice information correctly?
- Are the applicable FATOORA and ZATCA workflows configured for each invoice type?
- Does the integration handle successful responses, errors, and rejected invoices?
- Have the business’s actual invoice scenarios been tested?
- Can finance teams identify and resolve exceptions without creating separate manual processes?
- Has the complete D365 F&O → FATOORA → ZATCA → ERP workflow been validated?
A working API connection is only one part of production readiness. The ERP configuration, invoice data, integration, ZATCA processing, testing, and finance operations all need to work together.
For organizations managing e-invoicing across Saudi Arabia and other GCC markets, these considerations also form part of a broader GCC e-invoicing services approach covering ERP configuration, integration, testing, and compliance workflows.
How CaliberFocus Approaches FATOORA Integration With Dynamics 365 F&O
CaliberFocus starts with the existing Dynamics 365 Finance & Operations environment and works outward to align invoice configuration, data, integration, ZATCA processing, and finance operations with the applicable FATOORA requirements.
1. Assess the Existing D365 F&O Environment
Review the current D365 F&O configuration, invoice types, tax setup, customer and transaction data, and existing e-invoicing processes to identify what can be retained and where changes are required.
2. Map ZATCA Requirements to the ERP
Translate the applicable FATOORA and ZATCA e-invoicing requirements into the actual invoice and transaction workflows used in D365 F&O. This includes identifying the appropriate clearance or reporting treatment for different invoice scenarios.
3. Configure and Connect the E-Invoicing Process
Configure the required D365 F&O e-invoicing capabilities and establish the FATOORA API integration needed to exchange invoice information and responses with the ZATCA environment.
4. Validate Real Invoice Scenarios
Test the scenarios the business actually processes, including applicable standard and simplified invoices, credit notes, debit notes, clearance, and reporting workflows.
5. Test Responses and Exceptions
Validate how successful responses, validation errors, rejected invoices, corrections, and resubmissions move through the process so that exceptions can be handled within normal finance operations.
6. Validate Production Readiness
Complete end-to-end testing across D365 F&O, FATOORA, ZATCA processing, and business workflows before production. The focus is on ensuring that e-invoicing works reliably as part of the existing finance process.
The objective is not to add another disconnected compliance layer to the ERP. It is to make the FATOORA and ZATCA requirements work within the way the business already generates, processes, and manages invoices in Dynamics 365 Finance & Operations.
Planning Your FATOORA Integration?
Talk to our team about your Dynamics 365 Finance & Operations environment, integration requirements, and ZATCA e-invoicing process.
Frequently Asked Questions
The connection depends on the e-invoicing architecture and integration approach used by the business. D365 F&O manages the underlying financial transactions and invoice information, while the connected integration handles the exchange with the applicable ZATCA/FATOORA process. The architecture should support submission, responses, errors, and required invoice scenarios.
Businesses should review their D365 F&O configuration, invoice and tax data, applicable clearance or reporting workflows, integration architecture, invoice scenarios, and response handling. Testing these areas together is important because a successful API connection alone does not confirm that the complete e-invoicing process is ready for production.
Yes, the applicable clearance or reporting workflow can be supported within a properly configured Dynamics 365 F&O e-invoicing process. The important consideration is correctly identifying the invoice scenario and ensuring the ERP and connected FATOORA/ZATCA integration follow the corresponding submission and response process.
A rejected invoice needs to be identified, corrected, and resubmitted according to the applicable ZATCA process. For a Dynamics 365 F&O environment, response and exception handling should be considered part of the integration design so that rejected invoices do not create unnecessary manual work or disrupt downstream finance operations.
Testing should cover more than connectivity. Businesses should validate invoice generation, required data, applicable clearance or reporting workflows, standard and simplified scenarios, credit and debit notes where relevant, ZATCA responses, and exception handling. FATOORA simulation testing provides a controlled environment to validate these workflows before production.