Oracle Fusion Cloud ERP and Basware integration

What moves between them

The main flow is Oracle Fusion into Basware. Invoices and purchase orders are polled from Oracle Fusion every 5 to 15 minutes using LastUpdateDate filters and pushed into Basware's AP automation workflow. Supplier master data is synchronized in both directions so that new vendors created in Oracle Fusion are registered in Basware, and vendor updates in Basware flow back to Oracle Fusion. Payment confirmations generated by Basware after invoice processing are read back and posted into Oracle Fusion's receivables or AP module as payment records, updating the status of the original invoice.

How ml-connector handles it

ml-connector maintains OAuth 2.0 client credentials for both Oracle Fusion and Basware and presents the correct bearer token on every call, refreshing when a 401 response is returned. It polls Oracle Fusion using LastUpdateDate filtering to detect new and modified invoices and POs, and it listens for Basware webhooks on accounting document status changes to ensure low-latency processing of approved invoices. When pushing data into Basware, ml-connector maps Oracle Fusion supplier IDs to Basware vendor references and validates that account combinations reference existing Basware dimensions. On the pull side, when Basware payment confirmations are returned, ml-connector extracts the payment amount and document reference, queries Oracle Fusion to locate the matching invoice, and posts a payment application into Oracle Fusion's AR or AP ledger. All calls are idempotent: Oracle Fusion calls carry a unique Idempotency-Key header to prevent duplicate journal entries if a network fault causes a retry, and Basware webhook events carry the X-BW-REQUEST-ID for deduplication. Every record carries a full audit trail so failed downstream steps can be replayed without manual intervention.

A real-world example

A mid-sized industrial distributor runs Oracle Fusion for global finance and procurement and uses Basware for AP automation across three regional teams in Europe, North America, and Asia-Pacific. Before the integration, the AP team received supplier invoices in Basware, approved them, but then had to log into Oracle Fusion separately to record the payment and update the invoice status, a process that took 2 to 3 days and often resulted in duplicate or mismatched records. With Oracle Fusion and Basware connected, invoices approved in Basware automatically flow into Oracle Fusion as matched payables, and when Basware confirms payment, the status syncs back to Oracle Fusion without manual re-entry. The AP process now runs end-to-end: invoice receipt, approval, payment processing, and reconciliation all happen across both platforms in real time, and the finance team no longer spends time on data entry.

What you can do

• •Poll invoices and purchase orders from Oracle Fusion every 5 to 15 minutes and push them into Basware for approval and payment processing.
• •Synchronize supplier master data bidirectionally so new vendors in Oracle Fusion register in Basware and vendor updates in Basware flow back to Oracle Fusion.
• •Receive Basware webhook notifications on invoice approval and payment status to ensure low-latency processing without polling delays.
• •Map Oracle Fusion supplier and cost center references to matching Basware vendors and dimensions so invoices post to the correct AP accounts.
• •Apply payment confirmations from Basware back into Oracle Fusion's AR or AP ledger with full audit trails and replay capability on failure.

Questions

Which direction does data move between Oracle Fusion and Basware?

The main flow is Oracle Fusion into Basware for invoices and purchase orders, which Basware then processes for approval and payment. Supplier master data flows in both directions so that new vendors and updates stay synchronized. Payment confirmations flow from Basware back into Oracle Fusion to update the status of the original invoice and post payment records.

How does ml-connector handle the different authentication methods between Oracle Fusion and Basware?

ml-connector stores OAuth 2.0 client credentials for both systems separately, encrypted at rest, and presents the correct bearer token on every request to each API. When a token expires or returns a 401, ml-connector refreshes it automatically before retrying the call.

Does the integration work across all Basware regional deployments?

Yes. ml-connector accepts the Basware region and base URL as part of the connector configuration (EU, US, AU, or CA), validates that the region matches the customer's Basware instance, and routes all calls to the correct regional endpoint. Credentials are provisioned by your Basware delivery consultant during setup.