Multi-Channel AP Invoice Processing

This case study describes the integration architecture designed to support multi-channel accounts payable invoice processing within an enterprise finance environment. The solution addressed two fundamentally different submission channels—internal portal users requiring immediate acknowledgement, and external partners submitting high-volume B2B invoice batches—through a single consistent architecture that protected ERP stability while providing auditable status tracking and controlled recovery.

Two fundamentally different channels required support from a single AP processing capability. Internal portal users submitted invoices individually and expected an immediate technical confirmation. External partners submitted high-volume B2B invoice batches where transactional API calls would have placed unacceptable load on ERP processing capacity.

In both cases, Oracle ERP needed to remain the authority for supplier, purchase order, tax, match and accounting validation. Failures required auditable reprocessing without the risk of duplicate invoice creation. Status and correlation details needed to remain available to the originating source throughout the processing lifecycle.

A single synchronous design would have been straightforward to build for the portal channel but would have been inappropriate for high-volume batch submissions—exposing ERP to uncontrolled concurrent load and making error recovery complex. A single asynchronous design would have worked for batch but would have degraded the portal user experience.

The challenge was to serve both channels from a single integration capability while applying the right processing mechanism to each, without exposing the complexity of that distinction to the source systems. ERP had to remain isolated from volume spikes, and failed invoices had to be correctable and reprocessable without creating duplicates.

The portal channel uses a REST submission with immediate technical acknowledgement. The integration layer validates the format and contract, assigns a correlation identifier, and returns confirmation before ERP processing begins. This gives the portal user a definitive receipt without tying the response to the duration of ERP validation.

The B2B batch channel uses file-based import through Oracle's FBDI mechanism. Rather than invoking ERP transactionally for each invoice in a high-volume batch, invoices are accumulated, validated at the integration layer and submitted as a controlled bulk import. This protects ERP from concurrent load that would have affected other business processing.

In both cases, ERP remains the authority for business validation. OIC performs only structural and contract validation. Supplier existence, purchase order matching, tax treatment and accounting rules are evaluated entirely within ERP.

Duplicate invoice prevention was a primary design concern. Correlation identifiers were assigned at the point of submission and carried through every processing stage, ensuring that a resubmitted invoice could be identified and handled without creating a duplicate ERP record.

Import and business validation statuses were retrieved and returned to the originating source, giving each channel visibility into whether their submission succeeded, failed at the integration layer or failed at the ERP business-rule level—each requiring a different response. Failed invoices could be individually corrected and reprocessed without re-submitting the entire batch. Every transaction retained full audit and reconciliation data throughout.