Oracle Fusion Cloud ERP and Tipalti integration

What moves between them

Suppliers flow primarily from Oracle Fusion into Tipalti. When a new supplier is created or updated in Oracle Fusion, ml-connector reads the supplier record via REST polling every 10 minutes and writes it to Tipalti via SOAP PayeeFunctions, mapping Oracle supplier attributes to Tipalti payee fields. Payment records flow from Tipalti back into Oracle Fusion. Once Tipalti marks a payment as completed via IPN webhook notification, ml-connector posts the payment as a GL journal entry in Oracle Fusion's AP module, mapped to the correct supplier and GL account. The supplier master is maintained in both systems so that invoice creation in either direction references a valid payee in Tipalti and a valid supplier in Oracle Fusion.

How ml-connector handles it

ml-connector stores both OAuth2 and HMAC credentials encrypted. On the Oracle Fusion side, it refreshes the OAuth2 Bearer token when calls return 401, then polls the REST API every 10 minutes using LastUpdateDate filtering to capture only changed records. SOAP calls to Tipalti include the HMAC-SHA256 signature computed from payer name and API key. The integration receives payment completion events from Tipalti's IPN endpoint, verifies the webhook signature using HMAC-SHA256, and then posts the payment amount and invoice reference to Oracle Fusion's journal entry API, allocating it to the correct GL account and cost center based on the original invoice. Supplier fields are mapped from Oracle Fusion's supplier master (name, tax ID, address, payment terms) to Tipalti payee custom fields, and Tipalti's compliance status is reflected back as a supplier attribute in Oracle Fusion. The integration retries failed calls with exponential backoff when Tipalti or Oracle return transient errors, and every record carries an audit trail so a failed payment can be replayed once the downstream issue is fixed.

A real-world example

A mid-sized manufacturing company runs Oracle Fusion Cloud for financials and procurement, and uses Tipalti to automate AP and mass payments across a global supplier base. Before the integration, the accounts payable team manually keyed payment approvals from Tipalti into Oracle Fusion, creating duplicate work and invoice reconciliation delays. With the integration, new suppliers created in Oracle are automatically registered in Tipalti for onboarding and compliance checks. Once Tipalti approves and submits a payment via its workflow, the GL posting occurs in Oracle Fusion immediately, the accounts payable team no longer re-enters payment data, and the AP subsidiary ledger is always reconciled with the general ledger.

What you can do

• •Sync suppliers from Oracle Fusion to Tipalti for automated payee onboarding and compliance verification.
• •Post completed payments from Tipalti into Oracle Fusion's general ledger as invoice payments without manual re-entry.
• •Map supplier master data (name, tax ID, address, terms) from Oracle Fusion to Tipalti payee fields and custom attributes.
• •Authenticate Oracle Fusion with OAuth2 token refresh and Tipalti with HMAC-SHA256 SOAP signatures.
• •Receive payment events via Tipalti IPN webhook, verify signatures, and replay failed payments for full audit trail.

Questions

Which direction do suppliers and payments move between Oracle Fusion and Tipalti?

Suppliers move from Oracle Fusion into Tipalti so that Tipalti has current payee master data for onboarding and compliance. Payments move from Tipalti back into Oracle Fusion as GL journal entries. The supplier master is kept in sync in both directions so invoices always reference valid accounts.

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

ml-connector polls the Oracle Fusion REST API every 10 minutes using LastUpdateDate filters to capture new and changed suppliers and invoices. This pull-based approach works without Oracle Integration Cloud middleware. Payment events still arrive instantly via Tipalti's IPN webhook endpoint, so payment GL postings happen near-real-time.

What authentication and signing does ml-connector perform for each system?

For Oracle Fusion, ml-connector refreshes OAuth2 Bearer tokens on 401 responses and caches them for the full token lifetime. For Tipalti SOAP calls, ml-connector computes and includes the HMAC-SHA256 signature for every request using the payer name and API key. For incoming IPN webhooks from Tipalti, ml-connector verifies the HMAC-SHA256 signature before processing the event.