Connecting Oracle Fusion to ZATCA: Two Practical Integration Paths

Businesses running Oracle Fusion in Saudi Arabia face a specific question once they reach ZATCA's Integration Phase: how should the ERP actually talk to the Fatoora Portal? In practice, most implementations fall into one of two patterns, and the right choice depends less on which is "better" and more on what the business already has in place.

Path 1: Cloud-native connectors

Oracle's own cloud infrastructure offers pre-built tooling that can shorten the integration timeline considerably. Because the connectors are maintained by Oracle, they tend to track platform updates automatically and come with built-in security and scalability. The trade-off is that a business becomes more tied to Oracle's ecosystem, and the subscription costs can be a meaningful line item for smaller finance teams.

Path 2: A custom integration layer

The alternative is building a bespoke integration between Fusion and a ZATCA-compliant e-invoicing platform. This suits organizations with a hybrid IT landscape, non-Oracle systems in the mix, or specific workflow requirements that off-the-shelf connectors don't cover. It takes longer to build and test, but it gives finance and IT teams full control over how invoice data is validated, transformed and transmitted.

What actually determines the right choice

• Scale: larger, high-volume taxpayers tend to benefit from the reliability of a managed connector; smaller businesses often find a lighter custom build more cost-effective.
• Existing footprint: a business already deep in Oracle's cloud stack will usually find native tooling faster to stand up.
• Timeline pressure: with Wave 24's 30 June 2026 integration deadline, pre-built tooling can materially de-risk a tight schedule.
• Long-term plans: businesses anticipating further ERP consolidation may prefer to avoid deepening a single-vendor dependency.

Where a compliance partner fits in

Regardless of the path chosen, the underlying requirement doesn't change: invoices must be cryptographically stamped, carry a valid UUID, and reach ZATCA's Fatoora Portal in the correct format and time window. JFC Fatoora sits between Oracle Fusion and ZATCA either way, handling validation, formatting and transmission so the integration decision becomes an implementation detail rather than a compliance risk.

Conclusion

There is no universally "correct" integration pattern for Oracle Fusion and ZATCA — only the pattern that fits a given business's scale, existing infrastructure and timeline. What matters is getting a qualified compliance partner involved early enough to validate the approach before the integration deadline, not after.