Oracle Fusion Cloud ERP and Wise integration

What moves between them

The main flow runs from Oracle Fusion Cloud ERP into Wise. ml-connector polls Oracle Fusion Cloud ERP for invoices marked ready-to-pay, retrieves the supplier bank account details, creates a quote for the payment amount and currency, registers a recipient if it does not exist, and submits a Wise transfer. Payment status flows back via Wise webhooks so Oracle Fusion Cloud ERP knows when a transfer has completed, failed, or been returned. Supplier master data is read from both systems to keep recipient details aligned.

How ml-connector handles it

ml-connector stores OAuth2 credentials for both systems encrypted and refreshes bearer tokens on expiry. On the Oracle Fusion Cloud ERP side, it polls for invoices using the REST API with a LastUpdateDate filter to retrieve only recent changes. It accepts the customer-specific pod URL per tenant. On the Wise side, it handles the 4-step transfer sequence: first retrieving a quote to lock the exchange rate, then registering a recipient bank account, then creating the transfer order referencing the quote, and finally funding the payment. Wise webhooks notify ml-connector when a transfer state changes or a payout fails, so payment status can be written back to Oracle Fusion Cloud ERP. Invoices that fail to transfer are queued for retry after a backoff period, with full audit trail for every record.

A real-world example

A mid-sized technology services company operates Oracle Fusion Cloud ERP across multiple geographies and pays suppliers in ten different currencies across Europe, Asia, and North America. Before the integration, the accounts payable team downloaded approved invoices from Oracle Fusion Cloud ERP, logged into Wise separately, created transfers by hand, and then manually updated Oracle Fusion Cloud ERP to mark invoices as paid after each transfer completed. With Oracle Fusion Cloud ERP and Wise connected, each approved invoice automatically triggers a transfer in Wise without manual data entry, the correct exchange rates are locked and quoted before transfer, and payment status updates flow back automatically so Oracle Fusion Cloud ERP always shows the current payment state. The AP team saves hours per week on manual transfer entry and reconciliation.

What you can do

• •Read approved-for-payment invoices from Oracle Fusion Cloud ERP and automatically create Wise transfers to supplier bank accounts.
• •Lock exchange rates via Wise quotes so payment amounts are known before the transfer executes.
• •Register new supplier bank accounts as Wise recipients on first use, with immutability handled via delete-and-recreate where updates are needed.
• •Authenticate both systems with OAuth2 tokens, refreshing expiry automatically, and verify Wise webhook signatures on payment status updates.
• •Poll Oracle Fusion Cloud ERP on a schedule tied to your AP process, with automatic retries for failed transfers and a full audit trail on every record.

Questions

How does the integration handle Wise's 4-step transfer sequence?

ml-connector orchestrates all four steps internally. It retrieves a quote to lock the exchange rate, registers or reuses a recipient for the supplier bank account, creates the transfer order referencing the quote, and funds the payment. The entire sequence is atomic from Oracle Fusion Cloud ERP's perspective - an invoice either moves through all steps or the entire transfer is queued for retry.

Which invoices in Oracle Fusion Cloud ERP trigger a Wise transfer?

ml-connector polls Oracle Fusion Cloud ERP for invoices that match a criteria you define, typically invoices with a status of approved and an amount greater than zero. Supplier bank account details are retrieved from the supplier master record. Invoices that fail to transfer are retried with exponential backoff until they succeed or are manually flagged.

Does payment status in Wise update Oracle Fusion Cloud ERP?

Yes. Wise webhooks for transfersstate-change and transferspayout-failure are registered by ml-connector and routed to Oracle Fusion Cloud ERP so you see the current payment state in your GL immediately. If a payout fails, the invoice remains in Oracle Fusion Cloud ERP and ml-connector can retry via a different method or notify your AP team.