Oracle Fusion Cloud ERP and ServiceNow integration

What moves between them

The main flow runs from Oracle Fusion into ServiceNow. New invoices, payments, and supplier records are polled from Oracle Fusion using timestamp-based filters every 5-15 minutes and written into ServiceNow's Accounts Payable invoice table and Source-to-Pay staging tables. Purchase orders flow both directions: new orders from Oracle Fusion are synced to ServiceNow's procurement module, and approved orders from ServiceNow can trigger creation or updates in Oracle Fusion. Supplier master data is polished in both directions to ensure procurement teams see a single source of truth.

How ml-connector handles it

ml-connector stores OAuth credentials for both systems encrypted and refreshes tokens as they approach expiry, so authentication failures do not cause outages. It polls Oracle Fusion using LastUpdateDate filters and converts those records into ServiceNow's Table API format, respecting the account combinations and cost center defaults that ServiceNow requires. Because ServiceNow's Source-to-Pay tables are module-licensed add-ons, ml-connector verifies module availability per customer and maps records to the correct staging or operational table based on what the instance supports. Pagination is handled via limit and offset for Oracle Fusion and offset for ServiceNow, and rate limits are respected for both systems. Every invoice and purchase order carries a full audit trail, including the timestamp it was polled, the mapping logic applied, and the result of the write. If a downstream call fails, records can be replayed to ServiceNow without re-querying Oracle Fusion.

A real-world example

A mid-size global manufacturer runs Oracle Fusion Cloud ERP for financial consolidation, procurement, and supply chain planning across five regional plants. They use ServiceNow for IT operations and have recently added the Source-to-Pay module to centralize invoice approval and supplier management. Before the integration, the accounts payable team received email notifications of new invoices in Oracle Fusion and manually created corresponding records in ServiceNow, a process that took 2-3 days and created bottlenecks during high-volume periods. With Oracle Fusion and ServiceNow connected, new vendor invoices are automatically synced to ServiceNow's Accounts Payable table within 15 minutes of creation, matched to the correct cost center, and ready for approval. Purchase orders created in ServiceNow flow back to Oracle Fusion, ensuring procurement and finance see the same commitments. The manual invoice entry step is eliminated, and month-end close becomes a reconciliation rather than a re-keying exercise.

What you can do

• •Poll Oracle Fusion for invoices, payments, and purchase orders using timestamp-based filters, and write them into ServiceNow's Accounts Payable and procurement tables.
• •Authenticate both systems with OAuth 2.0 Client Credentials, refresh tokens as they approach expiry, and handle the different token lifespans on each side.
• •Map Oracle Fusion supplier and account combination data to ServiceNow cost centers and accounting dimensions so invoices land on valid accounts.
• •Sync supplier master data, cost centers, and purchase orders in both directions to keep procurement teams and finance aligned.
• •Track every record with a full audit trail, including the timestamp it was polled, the transformations applied, and the result of each write, with the ability to replay failed records.

Questions

Which direction does data flow between Oracle Fusion and ServiceNow?

The main flow is Oracle Fusion into ServiceNow. Invoices, payments, and supplier records are polled from Oracle Fusion and written into ServiceNow's Accounts Payable and procurement tables. Purchase orders and supplier master data flow in both directions to keep both systems aligned. Because ServiceNow's Accounts Payable module is read-only at the point of creation, the initial record comes from Oracle Fusion, but approved or rejected states in ServiceNow can trigger follow-up actions in Oracle Fusion.

Does ml-connector handle ServiceNow's Source-to-Pay module licensing requirement?

Yes. ml-connector verifies whether the customer's ServiceNow instance has the Source-to-Pay module licensed and routes records to the correct staging or operational table accordingly. If the module is not available, invoices are mapped to the core Accounts Payable table instead. This is confirmed during setup and updated on a per-customer basis.

How does the integration handle the different OAuth token lifespans between Oracle Fusion and ServiceNow?

ml-connector caches and monitors the expiry time of both tokens separately. Oracle Fusion tokens are valid for approximately one hour, while ServiceNow tokens default to 30 minutes. ml-connector refreshes each token before it expires and tracks the refresh timestamp, so a token expiry on either side does not interrupt the polling schedule or cause a failed write to the other system.