What ZATCA Phase 2 actually requires from your ERP and EPM stack
Phase 2 of ZATCA’s e-invoicing programme — the integration phase — requires businesses to connect their invoicing systems directly to the Fatoora platform so that every invoice is validated or reported in real time. The compliance obligation sits primarily in the ERP layer: the system that generates invoices.
But the EPM implication is significant and frequently overlooked. Here is why.
Oracle EPM systems — whether Hyperion Planning, FCCS, or Oracle Cloud EPM — draw actuals data from the ERP layer. That integration is the foundation on which financial planning, consolidation, and close reporting is built. When ZATCA Phase 2 changes how transactions are recorded, validated, and structured in the ERP system, the data flowing into the EPM environment changes with it.
Organizations that have not validated their ERP-to-EPM integration since ZATCA Phase 2 compliance was implemented are running a financial close on data whose structure may have shifted in ways the EPM model was not designed to accommodate.
Three specific EPM impacts that emerge post-ZATCA
1. Chart of accounts and VAT coding alignment. Phase 2 introduces new requirements around how VAT is coded, classified, and reported at the transaction level. If the chart of accounts in your ERP was updated to accommodate ZATCA compliance — as most implementations required — and that update was not reflected in the account mapping inside your EPM system, your actuals data is being loaded into the wrong accounts. The financial close produces numbers that are technically compliant at the ERP level and structurally wrong at the EPM level.
2. Real-time data flow requirements vs EPM batch integration. Most Oracle EPM implementations in the Gulf operate on scheduled batch integrations from the ERP — typically nightly or weekly loads. ZATCA Phase 2’s real-time validation model means that invoice data exists in a validated state in Fatoora before it appears in the ERP in its final form. Organizations that need to close their books on data that is fully validated against ZATCA — not just recorded in the ERP — need to revisit the timing and architecture of their EPM integration layer.
3. Tax Reporting Cloud (TRCS) configuration for ZATCA. Oracle’s Tax Reporting Cloud Service was designed precisely for the kind of multi-jurisdiction, multi-regime tax reporting that ZATCA Phase 2 introduces. Most organizations in Saudi Arabia that have TRCS implemented configured it before Phase 2 requirements were finalized. Reviewing the TRCS configuration against current ZATCA requirements is not a large project. It is a targeted assessment — but it is one that most finance teams have not completed.
The close cycle problem that appears six months after ZATCA compliance
The pattern we see consistently: an organization implements ZATCA Phase 2 compliance as an ERP project. The ERP team handles it. The EPM team is not involved. The compliance go-live is clean.
Six months later, the finance team is reconciling unexplained variances between ERP-reported tax positions and EPM-reported tax positions. The close cycle is absorbing extra days because somebody needs to manually bridge the gap before the numbers can be presented to the CFO. The monthly management report carries a footnote about the VAT reconciliation difference.
None of this is a ZATCA compliance failure. All of it is an EPM integration failure that was created by a compliance project that did not account for its downstream effects on the financial close.
What to check in your current EPM environment
If your organization implemented ZATCA Phase 2 compliance in 2024 or 2025 and your Oracle EPM environment has not been reviewed since, there are four specific things worth assessing.
First, validate that the chart of accounts mapping between your ERP and EPM system reflects the current state of your ERP COA — including any ZATCA-driven additions or reclassifications. Second, confirm that the data integration timing is aligned with your close process requirements given Phase 2’s real-time validation model. Third, if TRCS is installed, confirm the current configuration reflects Saudi Arabia’s Phase 2 requirements. Fourth, review the reconciliation process between your ERP tax reports and your EPM management reports — if that reconciliation requires manual intervention, there is a structural gap to address.
None of these checks requires a reimplementation. Each of them can be completed in a structured assessment engagement. The value is clarity on where the gap is — and a precise plan to close it.
Loop Wise Solutions implements and optimizes Oracle EPM environments for enterprises operating in Saudi Arabia and across the GCC, with direct experience in ZATCA compliance integration and Tax Reporting Cloud configuration.
Loop Wise Solutions designs and implements finance automation programmes for enterprise organizations across Egypt and the GCC — starting with the process, not the tool.
Contact: Contact@loop-wise.com | www.loop-wise.com
