E-invoice automation is the automated management of the full electronic invoice lifecycle — both for invoices issued (AR/sales invoices) and invoices received (AP/purchase invoices) — using technology to handle every step from creation to archiving without manual intervention at standard processing steps. In a GCC enterprise context, e-invoice automation encompasses: generating compliant electronic invoices in the format required by the applicable tax authority (ZATCA UBL 2.1 XML for Saudi Arabia, Egypt ETA format for Egyptian operations), digitally signing invoices with the organisation’s ZATCA-registered cryptographic certificate, submitting invoices to the regulatory clearance API (ZATCA Fatoora, ETA portal), monitoring clearance status and handling rejections, updating the ERP with clearance confirmation and the signed invoice UUID, and archiving the cleared invoice and its XML response for the mandatory retention period. On the AP side, e-invoice automation encompasses receiving supplier e-invoices in digital format, validating their ZATCA clearance status (for Saudi B2B invoices), extracting structured data for ERP posting, matching to purchase orders, and processing payment — without manual data entry at any standard step.
ZATCA Phase 2 E-Invoice Automation Architecture
| Step | Automated Component | System |
|---|---|---|
| AR invoice generation | Oracle EBS AR invoice triggered by order/contract/delivery event | Oracle EBS AR module |
| ZATCA XML generation | Transform Oracle EBS AR invoice data to ZATCA UBL 2.1 XML with required fields and UUID | ZATCA integration component (OIC or custom) |
| Cryptographic signing | Sign XML with organisation’s ZATCA-registered X.509 certificate; generate QR code from invoice hash | ZATCA signing service (OCI Vault or HSM-backed certificate) |
| Fatoora API submission | Submit signed XML to ZATCA Fatoora clearance endpoint via REST API | OIC ZATCA adapter or custom REST client |
| Clearance status monitoring | Poll ZATCA status endpoint; receive clearance UUID or rejection reason | OIC scheduled flow or event-driven polling |
| EBS update | Update Oracle EBS AR invoice with ZATCA clearance UUID and signed XML reference | Oracle EBS REST API or RPA bot |
| PDF generation | Generate human-readable PDF invoice with ZATCA QR code via BI Publisher | Oracle BI Publisher |
| Buyer distribution | Deliver PDF and XML to buyer via email, buyer portal, or EDI | OIC email delivery or EDI adapter |
| Archiving | Archive signed XML and clearance response for ZATCA’s 10-year retention requirement | OCI Object Storage with lifecycle policy; or enterprise EDMS |
Egypt ETA E-Invoice Automation
GCC holding companies with Egyptian subsidiaries must implement a separate e-invoice automation track for ETA (Egyptian Tax Authority) compliance alongside their ZATCA implementation for Saudi entities. Egypt’s ETA e-invoicing mandate requires a different XML format (UBL 2.1 with ETA-specific extensions), a different signing mechanism (ETA-issued digital signature), and a different clearance portal (ETA’s invoicing portal rather than ZATCA’s Fatoora). For group holding companies with entities in both Saudi Arabia and Egypt, the e-invoice automation architecture must handle both regulatory tracks — with the appropriate format, signing credential, and submission endpoint selected based on the issuing entity’s jurisdiction. Oracle Integration Cloud supports both ZATCA and ETA integration patterns; the integration design must parameterise the regulatory destination based on the entity code in the source invoice.
What Goes Wrong in Practice
The most common e-invoice automation failure is an implementation that handles the ZATCA clearance success path correctly but does not implement rejection handling — when ZATCA rejects an invoice (for XML validation errors, duplicate UUID, or schema non-compliance), the automation marks the invoice as submitted and moves on, leaving the rejected invoice uncollected and unresolvable until the next VAT return preparation reveals the mismatch. Every ZATCA rejection must generate an immediate alert to the AR team with the rejection reason code and the specific invoice details — because ZATCA rejections often require human intervention (correcting an XML field, resubmitting with a new UUID) that cannot be automated.
How Loop Wise Solutions Implements E-Invoice Automation
We implement ZATCA and ETA e-invoice automation as integrated components of the Oracle EBS and Oracle Fusion deployment — using Oracle Integration Cloud for the clearance API connectivity, Oracle BI Publisher for PDF generation, and OCI Object Storage for archiving — with explicit rejection handling, clearance status monitoring, and daily reconciliation that confirms all invoices in the Oracle EBS AR period are accounted for in the ZATCA clearance log.
