Oracle Fusion Cloud ERP and Airbase integration

What moves between them

The main flow runs from Airbase into Oracle Fusion Cloud ERP. When a purchase request is approved in Airbase, ml-connector creates a matching purchase order in Fusion. Vendor invoices posted to Airbase are synced as AP invoices into Fusion's AP module and mapped to the GL accounts and cost centers that match Airbase subsidiary and cost allocation rules. Vendor reference data and GL account validation is pulled from Fusion first to ensure every invoice lands on a valid account. Invoices can flow either direction: Airbase can receive AP invoice records from Fusion if they are approved externally and need to appear in the Airbase audit trail.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the Oracle Fusion side it accepts the tenant-specific pod URL per customer and authenticates with OAuth2 Client Credentials, refreshing the JWT when it approaches expiry (approximately one hour). On the Airbase side it presents the Bearer token on every call and can subscribe to webhook events for approved purchase requests to catch them more promptly than polling alone. Because Oracle Fusion has no direct outbound webhooks without middleware, ml-connector polls Airbase-approved POs and invoices every 5-15 minutes, filtering by creation and update timestamps. Vendor names and cost centers are mapped first so every invoice references a valid GL account and supplier ID in Fusion. When Airbase returns a GL account that does not exist in Fusion or has a different number, ml-connector flags the record for manual review rather than creating a blind account. Every record carries full audit trail metadata and can be replayed if a downstream Fusion API call fails.

A real-world example

A mid-sized SaaS company uses Oracle Fusion Cloud ERP for accounting and reporting, with spend spread across multiple offices and departments. The finance team adopted Airbase for centralized spend management, vendor management, and corporate card reconciliation, but invoices and POs approved in Airbase had to be re-entered into Fusion by hand. Before the integration, the AP team spent several hours each week matching Airbase approvals to Fusion GL accounts, resolving cost center mismatches, and entering data twice. With Airbase and Fusion connected, approved purchase requests flow automatically into Fusion as POs, vendor invoices post as AP entries on the correct cost centers, and the AP team focuses on exception handling and vendor disputes instead of data entry.

What you can do

• •Sync approved purchase requests from Airbase into Oracle Fusion Cloud ERP as purchase orders on the correct GL account and cost center.
• •Post vendor invoices from Airbase into Fusion's AP module with GL account and subsidiary mapping enforced.
• •Validate vendor names and GL accounts against Fusion before syncing, and flag mismatches for manual review rather than creating blind records.
• •Authenticate Oracle Fusion with OAuth2 Client Credentials and refresh tokens before expiry, and Airbase with Bearer token authentication.
• •Poll Airbase and Fusion on a configurable schedule filtered by creation and update timestamps, with full audit trail on every record.

Questions

Which direction does data move between Oracle Fusion and Airbase?

The primary flow is Airbase into Oracle Fusion. Approved purchase requests and vendor invoices from Airbase sync into Fusion's PO and AP modules mapped to the correct GL accounts. Vendor reference data and GL account validation pull from Fusion first to ensure every record lands on a valid account. Invoices can optionally flow from Fusion back into Airbase if they are approved externally.

How does ml-connector handle the fact that Oracle Fusion Cloud ERP has no native outbound webhooks?

ml-connector polls Airbase-approved POs and invoices every 5-15 minutes, filtering by creation and update timestamps to catch only new and recently changed records. Airbase itself supports webhooks for approved purchase requests, so ml-connector can subscribe to those events to catch approvals more promptly than polling alone.

How are GL accounts and cost centers mapped between Airbase and Oracle Fusion?

ml-connector pulls vendor names, GL accounts, and cost center codes from Oracle Fusion first and validates every Airbase invoice against those records before posting. If Airbase references a GL account that does not exist in Fusion or a cost center with a different number, the record is flagged for manual review rather than blindly created.