This blog presents a scalable and governed integration
architecture that automates AR invoice processing from an
on-premise system into Oracle Fusion Receivables,
using Oracle Integration Cloud (OIC)
and Oracle OCI Object Storage. The solution is
designed for high reliability, auditability, and ease of support—without
introducing custom code in the integration layer.
- A CSV file contains invoice header and line details
- A PDF file represents invoice attachments (supporting documents)
- Both files share the same base name and are placed on an SFTP server
The business requirement is to:
- Automatically ingest these files.
- Create or update invoices in Oracle Fusion Receivables
- Attach the PDF document to the corresponding invoice
- Maintain full audit visibility and error traceability
- Archive processed files for compliance and reconciliation
The solution is built around three logical process flows, each with a clear responsibility:
1. Invoice
File Generation (Out of Scope)
The on-premise system produces approved invoice files and places them on SFTP.
2. Inbound
File Ingestion (OIC → OCI Object Storage)
OIC securely transfers invoice files from SFTP into OCI Object Storage.
3. Invoice
Processing and Posting (OIC → Fusion AR)
OIC validates, processes, posts invoices into Fusion Receivables, attaches
documents, and archives files.
This layered approach cleanly separates file movement, business processing, and system-of-record updates, improving reliability and supportability.
Flow 1: File Generation on On-Premise System (Out of Scope)
- A structured CSV file is generated with invoice details
- A corresponding PDF file is created as an attachment
- Both files are placed on a secured SFTP server
- Connect securely to the customer SFTP server
- Identify completed invoice files (CSV and PDF pairs)
- Transfer files into OCI Object Storage, which acts as a durable and scalable staging layer
Why OCI Object Storage?
- Using OCI Object Storage provides several advantages:
- Decouples file ingestion from invoice processing
- Eliminates dependency on SFTP availability during processing
- Enables retry, replay, and controlled processing
- Supports long-term archiving and compliance
Flow 3: Invoice Creation and Attachment in Oracle Fusion Receivables
Scheduled OIC Job: Invoice Processing
A second scheduled OIC integration performs the core business processing:
1. File Discovery and Validation
- Identifies ready-to-process invoice files in OCI Object Storage.
- Ensures required invoice data and attachment files are present
2. Audit and Tracking
Before invoking Fusion APIs, invoice details are recorded in an ATP-based
audit table.
This table serves as a single source of truth for:
- Invoice processing status
- Success or failure details
- Fusion transaction identifiers
- Error messages for operational follow-up
This ensures full end-to-end traceability, a key requirement for finance teams.
3. Invoice Existence Check
The integration verifies whether the invoice already exists in Oracle Fusion Receivables:
- If it exists, the invoice is treated as an update
- If it does not exist, a new invoice is created
This design supports both new invoices and corrections
without manual intervention.
4. Invoice Creation or Update
Validated invoice data from the CSV file is mapped to Fusion Receivables and
submitted using standard Oracle APIs.
- Success responses update the audit table with Fusion transaction IDs
- Errors are logged with detailed messages for analysis and reprocessing
5. Attachment Handling
Once the invoice is successfully created or updated
- The corresponding PDF file is attached to the invoice in Fusion Receivables
- Attachment success or failure is independently tracked
This separation ensures that invoice posting is not blocked by attachment
issues.
Leveraging OCI Object Storage
Through Oracle Integration Cloud
Instead of processing invoices directly from SFTP, OCI Object Storage is intentionally positioned as an intermediate orchestration layer between file ingestion and Fusion Receivables processing.
At runtime, OIC interacts with the OCI Storage bucket to:
- List available invoice files waiting to be processed
- Identify valid invoice file pairs (CSV and PDF with matching names)
- Ensure files are complete and ready for processing
This allows OIC to act as a traffic controller, deciding when and what
to process rather than reacting blindly to file arrivals.
Object
Retrieval for Business Processing
Once a valid invoice file is
identified:
- OIC retrieves the invoice data file from the OCI bucket
for validation and invoice creation
- The PDF attachment is retrieved only after the
invoice is successfully created in Fusion Receivables
This staged access ensures:
- Invoice creation is not blocked by attachment availability
- Partial failures do not corrupt business transactions
OCI Object Storage acts as a state
boundary in the integration:
- Files in the inbound bucket represent pending work
- Files moved to the archive bucket represent completed
work
- Files remaining due to errors represent exceptions
requiring attention
This design eliminates ambiguity and
simplifies operational support.
After successful processing:
- Both CSV and PDF files are moved to an OCI Archive bucket
- Files are retained for audit, reconciliation, and compliance purposes
- Original inbound files are removed to prevent duplicate processing
This controlled archival approach supports:
- Regulatory compliance
- Operational transparency
- Simplified reprocessing if required
The solution is designed with operational resilience
in mind:
- All failures are captured in the audit table with meaningful messages
- Functional errors (data issues) are separated from technical errors
- Invoices can be reprocessed without re-uploading files
- Support teams can track invoice status without accessing OIC directly
Need help with OIC / ADW? Contact Bizinsight Cosulting Inc at
https://www.bizinsightinc.com/
