Oracle Fusion Cloud ERP and Stampli integration

What moves between them

The primary flow runs from Stampli into Oracle Fusion. When invoices are approved in Stampli, they export to the SFTP directory as flat files (CSV format). ml-connector polls the SFTP directory on your schedule (e.g. every 15 minutes), reads new invoice files, and posts them into Oracle Fusion's AP module and general ledger. Vendor names from Stampli are matched to Oracle Fusion suppliers via a lookup table, and GL line items are mapped to the correct GL account combinations in Oracle before posting. Reference data (GL accounts, vendors, cost centers) may also be synchronized from Stampli into Oracle Fusion to ensure lookup tables stay aligned. Because Oracle Fusion's API does not natively support invoice matching and line distribution the way Stampli's workflows do, the integration delegates that logic to Stampli and only posts final approved records into Oracle.

How ml-connector handles it

ml-connector stores Stampli SFTP credentials encrypted and connects to the outbound directory on each polling cycle. It reads CSV files exported by Stampli (parsed according to Stampli's export templates), validates that all referenced vendors exist in Oracle Fusion (querying the suppliers endpoint), and looks up GL account combinations via Oracle Fusion's account setup APIs. Each line item is mapped to a GL account and cost center before posting. For invoices already in Oracle Fusion (detected via a dedup key combining vendor number and invoice number), ml-connector skips re-posting to avoid duplicates. Oracle Fusion's API does not document public rate limits, so ml-connector implements adaptive backoff on 503 responses and retries failed posts up to three times with exponential jitter. Because Stampli files are written by an asynchronous export process, ml-connector tracks which files have been fully processed (persisting the list in a local state file or database) to avoid re-reading partial or in-flight exports. The integration also logs every vendor lookup, GL account match, and invoice post to a full audit trail.

A real-world example

A mid-sized manufacturing company uses Oracle Fusion Cloud ERP for AP, AR, and GL accounting, and Stampli for invoice capture and three-way PO matching across multiple business units. Before the integration, the AP team received Stampli's approval notifications and spent one to two hours per day manually entering invoice details into Oracle Fusion, allocating charges to the correct cost centers, and then reconciling discrepancies. With Oracle Fusion and Stampli connected, each approved invoice exports from Stampli automatically, maps to the correct vendors and cost centers in Oracle, and posts to the GL. The AP team is freed from data entry and now focuses on exception handling and policy compliance.

What you can do

• •Poll Stampli's SFTP directory and read approved invoices in CSV format on your schedule.
• •Post Stampli invoices into Oracle Fusion's AP and GL modules, mapped to the correct vendors and GL account combinations.
• •Validate that vendors referenced in Stampli invoices exist as suppliers in Oracle Fusion before posting.
• •Encrypt SFTP credentials and maintain a full audit trail of every invoice entry, lookup, and GL post.
• •Deduplicate invoices by vendor and invoice number to avoid re-posting approved records already in Oracle Fusion.

Questions

Why does this integration use SFTP instead of REST API with Stampli?

Stampli does not publish a public REST API for third-party developers without a formal partnership agreement. File-based integration via SFTP is the only path available to external connectors. ml-connector polls your Stampli SFTP directory on a regular schedule (e.g. every 15 minutes) and processes the CSV files Stampli exports.

How does ml-connector prevent duplicate invoices from posting into Oracle Fusion?

ml-connector uses a composite dedup key combining the vendor number (from the Stampli vendor lookup in Oracle) and the invoice number from the Stampli file. On each polling cycle, it checks whether that combination already exists in Oracle Fusion AP and skips posting if a match is found. It also maintains a local state file tracking which Stampli export files have been processed to avoid re-reading the same file.

What happens if a vendor in a Stampli invoice is not set up in Oracle Fusion?

ml-connector validates each vendor in the Stampli file against Oracle Fusion's suppliers endpoint before posting. If a vendor is not found, the integration logs the mismatch to the audit trail and skips that invoice. The record is available for manual review or reconciliation once the vendor is created in Oracle Fusion and the integration re-runs.