Oracle PeopleSoft and Tipalti integration

What moves between them

Vendor master records and invoices flow from Oracle PeopleSoft into Tipalti. When a new vendor (VENDOR_CI) or invoice (AP_VOUCHER or esfetchinvoiceinquiry) is created or updated in PeopleSoft, ml-connector polls and reads those changes, then writes them into Tipalti as Payees and Invoices. Purchase order and GL account mappings are kept in sync bidirectionally so invoice lines land on valid Tipalti GL accounts and PO references. The polling schedule is controlled per customer, and ml-connector can also receive Tipalti payment status updates via webhook if configured, allowing payment records to flow back into PeopleSoft for reconciliation.

How ml-connector handles it

ml-connector accepts each customer's unique PeopleSoft hostname, port, and node name, since PeopleSoft is self-hosted. It encrypts and securely stores the OPRID/password or OAuth2 credentials, and refreshes OAuth2 tokens before expiry. For Tipalti, ml-connector stores the payer_name and api_key for SOAP calls and client credentials for REST calls, computing HMAC-SHA256 signatures inline on each request. Because PeopleSoft has no outbound webhooks, ml-connector polls on a cadence tied to your business cycle (daily, weekly, or after month-end close), using date-range filters to retrieve only new or modified records. Vendor records are matched by vendor ID to prevent duplicate Payees in Tipalti, and invoices are tracked with a natural key (vendor ID plus invoice number) to ensure safe replay if a Tipalti write fails. GL account mappings are validated against both systems before an invoice write so that line items land on accounts that exist in Tipalti. Every record carries a full audit trail, and failed records can be inspected and replayed without data loss.

A real-world example

A mid-market manufacturing company runs Oracle PeopleSoft on-premise for finance and procurement, processing 200-300 vendor invoices per month. The finance team uses Tipalti to automate approval workflows, supplier compliance, and mass payments across 15 countries. Before the integration, invoices were entered manually into both systems, creating a week-long lag and frequent mismatches between PeopleSoft's GL and what was actually paid in Tipalti. With Oracle PeopleSoft and Tipalti connected, new invoices and vendor updates from PeopleSoft flow into Tipalti automatically, eliminating the manual re-keying step. The AP team can focus on exception handling and supplier compliance instead of data entry, and month-end reconciliation between systems is instant.

What you can do

• •Sync vendor master records from Oracle PeopleSoft into Tipalti as Payees, preventing duplicate suppliers and stale contact information.
• •Move invoices and AP vouchers from PeopleSoft into Tipalti's approval workflow automatically, eliminating manual re-entry between finance and payments.
• •Map PeopleSoft GL accounts and cost centers to Tipalti GL accounts so invoice line items land on valid accounts.
• •Bridge PeopleSoft's HTTP Basic Auth and OAuth2 with Tipalti's HMAC-SHA256 and OAuth2 APIs, handling credential refresh and secure storage.
• •Poll PeopleSoft on a schedule you control, with full audit trail, error replay, and reconciliation reporting for all synced records.

Questions

How does ml-connector handle PeopleSoft's lack of webhooks and self-hosted architecture?

ml-connector accepts the full hostname, port, and node name unique to each customer's PeopleSoft environment. Since PeopleSoft has no native outbound webhooks, ml-connector polls on a schedule you set (daily, weekly, or after key business events), using date-range filters to read only new or modified records without overwhelming the system.

How are vendor and invoice records matched between Oracle PeopleSoft and Tipalti?

Vendors are matched by vendor ID to prevent duplicate Payees. Invoices use a natural key combining vendor ID and invoice number for safe replay and deduplication. GL account mappings are validated before an invoice write so line items land on accounts that exist in Tipalti, preventing downstream approval failures.

What happens if a vendor or invoice write to Tipalti fails?

ml-connector logs the full error and audit trail for every record. Failed records can be inspected, corrected if needed, and replayed without data loss. The system tracks which records have been successfully synced so retries do not create duplicates.