Oracle PeopleSoft and Wise integration

What moves between them

Employee banking records and payroll balances flow from Oracle PeopleSoft into Wise. ml-connector reads employee records and payroll data on a schedule tied to your payroll cycle, creates or updates Wise recipient profiles for each employee's bank account, and initiates transfers from your Wise multi-currency account to each recipient using the payroll amount in the employee's destination currency. Direction is one-way from PeopleSoft into Wise for payout execution. Wise transfer status webhooks or polling updates flow back to provide confirmation that payouts have completed or failed.

How ml-connector handles it

ml-connector stores both Oracle PeopleSoft and Wise credentials encrypted, refreshes OAuth2 tokens on demand, and polls PeopleSoft employee and payroll records at a cadence you define. For each new or changed record, it retrieves the employee's banking details and payroll amount, then constructs a Wise transfer by querying a quote (which locks the exchange rate), registering or matching an existing Wise recipient, and funding the transfer order with a unique customerTransactionId to prevent duplicate payouts if a retry occurs. Wise rate limits (100 req/sec) are respected across concurrent payout batches. Employee banking details must already exist in PeopleSoft before ml-connector can build the Wise recipient. The integration tracks which payroll runs have been sent to prevent re-processing, and every transfer attempt is logged with the Wise transfer ID for reconciliation.

A real-world example

A mid-sized financial services firm with employees across Europe, Asia, and Latin America uses Oracle PeopleSoft for global payroll and benefits. Previously, the payroll team ran payroll in PeopleSoft, then manually exported employee banking details and payroll amounts, created payment orders in Wise one by one, verified exchange rates, and initiated transfers. Month-end payout day took a full day of manual work and carried the risk of typos or missed employees. With Oracle PeopleSoft and Wise connected, the payroll run triggers automatically: employee records and amounts flow into Wise, a transfer order is created and funded for each recipient, and the team can focus on exception handling and compliance instead of data entry. Payout completion is visible in both systems, and the audit trail proves every payment was authorized and executed.

What you can do

• •Poll Oracle PeopleSoft employee records and payroll data on a schedule tied to your payroll cycle.
• •Create and update Wise recipient profiles from PeopleSoft employee banking details so payouts reach the correct accounts.
• •Automatically request a Wise quote, register recipients, and initiate transfers with unique IDs to prevent duplicate payouts.
• •Refresh OAuth2 tokens on both sides and respect Wise rate limits to ensure reliable payout execution.
• •Track payout status in Wise and maintain a full audit trail of every transfer for reconciliation and compliance.

Questions

Which direction does data move between Oracle PeopleSoft and Wise?

Employee records and payroll data flow from Oracle PeopleSoft into Wise to initiate payouts. Banking details stored in PeopleSoft employee records are used to create or match Wise recipients. Transfer status flows back from Wise for confirmation and reconciliation. The direction is one-way for payout execution.

How does ml-connector handle the multi-step Wise transfer sequence?

Wise requires a quote first, then a registered recipient, then a transfer order funded by payment. ml-connector obtains a fresh quote on each payout cycle to lock the correct exchange rate, registers or matches an existing Wise recipient from the PeopleSoft employee banking details, creates a transfer order with a unique customerTransactionId for deduplication, and then funds it. If any step fails, the transaction is logged for retry.

What authentication is required on the Oracle PeopleSoft side?

Oracle PeopleSoft requires HTTP Basic Auth with an OPRID and password, or OAuth2 Bearer tokens if you are running PeopleTools 8.58 or later. ml-connector stores both credential sets encrypted and refreshes OAuth2 tokens when needed. Your PeopleSoft administrator must activate the REST service operations used by the integration in the Integration Broker console.