Oracle Fusion Cloud ERP and Cleo integration

What moves between them

Records flow from Oracle Fusion Cloud ERP into Cleo. Supplier invoices, payments, and GL journal lines are read from Oracle Fusion on a polling schedule and mapped to EDI transaction formats (820 for payments, 810 for invoices, 856 for shipments where applicable) and pushed into Cleo as files or API payloads. The mappings align Oracle Fusion's GL accounts and supplier codes with Cleo's connection and action rules so EDI data lands in the correct trading partner workflow.

How ml-connector handles it

ml-connector stores OAuth2 credentials for both systems encrypted and refreshes each side's bearer token when calls return 401. On Oracle Fusion, it accepts the customer-specific pod URL and filters by LastUpdateDate to poll for recently changed records without full table scans. On Cleo, it maps Oracle Fusion invoice and payment records to EDI transaction types and uses Cleo's REST API to post them as files or actions within the tenant. Because Oracle Fusion publishes no rate limits, ml-connector starts with a conservative poll interval (5-15 minutes) and backs off on 503. Cleo rate limits are not documented but follow standard cloud API practices; ml-connector retries with exponential backoff. Every record carries the source Oracle Fusion document ID in its audit trail so payment or invoice disputes can be traced back through Cleo to the GL entry.

A real-world example

A mid-sized electronics manufacturer runs Oracle Fusion Cloud ERP for procurement and financial management across three plants and a distribution center. They use Cleo Integration Cloud to manage EDI and API-based order, shipment, and invoice exchange with key suppliers and the distribution network. Before the integration, the procurement team exported supplier invoices and payment records from Oracle Fusion weekly and manually created EDI 810 and 820 transactions in Cleo for trading partners, which caused delays and re-entry errors. With Oracle Fusion and Cleo connected, each accounts payable invoice and payment automatically generates the corresponding EDI transaction in Cleo and flows to suppliers on schedule, cutting invoice-to-EDI lag from days to minutes and eliminating manual mapping.

What you can do

• •Read supplier invoices and payments from Oracle Fusion Cloud ERP and deliver them as EDI transactions into Cleo for trading partners.
• •Map Oracle Fusion GL accounts and cost allocations to Cleo trading partner codes so financial records align with supply chain transactions.
• •Authenticate Oracle Fusion with OAuth2 Client Credentials and Cleo with OAuth2 password grant, and refresh tokens when they expire.
• •Poll Oracle Fusion on a configurable schedule using LastUpdateDate filters to capture only recently changed records.
• •Maintain a full audit trail linking each Cleo EDI transaction back to the Oracle Fusion source document ID for dispute resolution.

Questions

Which direction does data flow between Oracle Fusion Cloud ERP and Cleo?

Data flows from Oracle Fusion into Cleo. Supplier invoices, payments, and GL journal lines are read from Oracle Fusion and mapped to EDI transaction formats (810, 820, 856) before being pushed into Cleo for delivery to trading partners. Oracle Fusion remains the source of truth and Cleo is the outbound conduit.

How does ml-connector handle Oracle Fusion's lack of native webhooks?

Oracle Fusion has no direct outbound webhooks without Oracle Integration Cloud (OIC) middleware. ml-connector polls Oracle Fusion's REST API on a configurable schedule (typically 5-15 minutes), filtering by LastUpdateDate to retrieve only recently changed invoices and payments. This keeps Cleo synchronized while minimizing API overhead.

What happens if token expiry or rate limits are hit?

ml-connector refreshes OAuth2 tokens on both sides when a call returns 401 (authorization). For rate limits, ml-connector retries with exponential backoff and jitter. Every transaction is logged with its source Oracle Fusion document ID, so if a retry fails, the record can be traced and replayed without losing the audit trail.