Oracle Fusion Cloud ERP and BILL integration

What moves between them

The primary flow is Oracle Fusion to BILL. Vendor suppliers from Oracle Fusion are polled and created or updated in BILL as vendors. Invoice headers and line items from Fusion are read on a schedule and posted into BILL as bills, with supplier names matched to BILL vendors. Payments processed in Fusion can be synced to BILL to keep payment status aligned. The direction is primarily read from Fusion and write to BILL; BILL records are not written back into Fusion.

How ml-connector handles it

ml-connector stores your OAuth2 credentials for Oracle Fusion encrypted and refreshes the bearer token when it expires (approximately every 60 minutes). It polls Fusion's invoices, payments, and suppliers endpoints using OData filters (LastUpdateDate>{timestamp}) to retrieve only new or changed records. Vendor suppliers in Fusion are mapped to BILL vendors by a normalized supplier name or ID; if a BILL vendor for a Fusion supplier does not yet exist, ml-connector creates it. Invoice headers and line items from Fusion are translated into BILL bills, with the invoice number, supplier reference, amount, and due date preserved. BILL's 10-webhook-subscription limit means ml-connector can listen for vendor or bill changes in BILL and validate them against Fusion, or rely on polling both systems for full synchronization. If Fusion rate limits a request (though not documented), ml-connector backs off and retries. Every record carries an audit trail so if a bill creation fails, it can be replayed once the issue is resolved.

A real-world example

A mid-market services company runs Oracle Fusion Cloud ERP for enterprise financials and procurement, with hundreds of supplier accounts. The AP team uses BILL to manage vendor payments, approvals, and cash flow forecasting. Before the integration, when new invoices arrived from suppliers, the procurement team entered them into Fusion, then the AP team had to re-enter them into BILL to schedule and approve payments, creating duplicate work and reconciliation errors. With Oracle Fusion and BILL connected, suppliers and invoices sync automatically from Fusion into BILL on a daily schedule, so the AP team sees each invoice in BILL ready for approval and payment, eliminating the re-entry step and keeping supplier records aligned across both systems.

What you can do

• •Sync suppliers from Oracle Fusion into BILL as vendors, mapped by normalized names or IDs so invoice lines find the right vendor.
• •Poll Oracle Fusion invoices and line items on a schedule and post them into BILL as bills with amounts, due dates, and supplier references intact.
• •Authenticate to Oracle Fusion via OAuth2 against OCI Identity Domain, with automatic token refresh before expiry.
• •Validate BILL vendors and bill records by listening to BILL webhooks or polling both systems to ensure alignment after changes.
• •Maintain a complete audit trail of every supplier and invoice synced, with error replay so failed records can be retried.

Questions

Which direction does data move between Oracle Fusion and BILL?

The primary flow is Oracle Fusion to BILL. Suppliers and invoices are read from Fusion and posted into BILL for AP processing. Payments can also be synced to keep payment status aligned. BILL records are not written back into Oracle Fusion; Fusion remains the system of record for suppliers and invoicing.

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

Oracle Fusion Cloud ERP does not support direct outbound webhooks to external systems without Oracle Integration Cloud (OIC) middleware. ml-connector polls the Fusion REST API on a schedule you control, using OData filters to retrieve only new or changed records since the last poll. This approach works well for batch AP processing tied to your invoice receipt cadence.

How are Oracle suppliers matched to BILL vendors?

ml-connector normalizes supplier names or IDs from Oracle Fusion and searches for matching vendors in BILL. If a vendor does not exist in BILL, ml-connector creates it with the supplier name and any contact details from Fusion. This ensures every Fusion invoice can be matched to a BILL vendor so payment approval workflows flow correctly.