Oracle PeopleSoft and Procurify integration

What moves between them

The primary flow is from Procurify into PeopleSoft. Approved requisitions and ordered items from Procurify are polled on a schedule you set and posted into PeopleSoft as purchase orders, mapped to the corresponding vendors and GL account codes. Vendor master data is synchronized in both directions so that new vendors registered in Procurify exist in PeopleSoft before any order references them. Account codes and cost centers are aligned in both directions so each order line lands on a valid GL dimension. PeopleSoft invoice records can be read back to close matching purchase orders in Procurify if reconciliation workflows require it.

How ml-connector handles it

ml-connector accepts each customer's unique PeopleSoft hostname and node name since PeopleSoft publishes no shared base URL. It authenticates PeopleSoft with either HTTP Basic Auth or OAuth2 bearer token depending on PeopleTools version, and Procurify with OAuth2 client credentials, refreshing the Procurify token on every 24-hour boundary. It polls Procurify's requisitions and order items endpoints with date-range filters, maps the Procurify cost center and account code fields to PeopleSoft GL dimensions and vendor identifiers, and posts the result to PeopleSoft SOAP Component Interface services. Because both systems are pull-only, polling is the only option. PeopleSoft service operations must be explicitly activated by the customer's PeopleSoft administrator in the Integration Broker console before ml-connector can use them. The integration tracks processed requisition IDs to avoid duplicate posts and retries failed writes with exponential backoff. Both credential sets are encrypted at rest, and every transaction carries a full audit trail.

A real-world example

A mid-market manufacturing company runs Oracle PeopleSoft for finance and supply chain on their own servers and uses Procurify for procurement and vendor management in the cloud. Before the integration, the procurement team approved requisitions in Procurify and the finance team manually entered matching purchase orders into PeopleSoft, a process prone to order-quantity and account-code errors and taking 2-3 days to reconcile. With Procurify and PeopleSoft connected, each approved requisition syncs automatically as a purchase order in the ledger, mapped to the correct vendors and GL accounts, eliminating manual entry and accelerating the purchase-to-pay cycle.

What you can do

• •Sync approved requisitions and ordered items from Procurify into PeopleSoft as purchase orders, mapped to the correct vendors and GL account codes.
• •Keep vendor master data aligned between Procurify and PeopleSoft so new suppliers can be registered in procurement before any order references them.
• •Map Procurify cost centers and account codes to PeopleSoft GL dimensions so purchase orders land on valid ledger accounts.
• •Authenticate PeopleSoft with HTTP Basic Auth or OAuth2 bearer tokens and Procurify with OAuth2 client credentials, storing both encrypted and refreshing tokens on schedule.
• •Poll both systems on a schedule you control, with automatic deduplication, retries, and a full audit trail on every record.

Questions

Which direction does data move between Oracle PeopleSoft and Procurify?

The primary flow is from Procurify into PeopleSoft. Approved requisitions and ordered items move from Procurify into PeopleSoft as purchase orders. Vendor and account code data is synchronized in both directions so that reference tables stay aligned. PeopleSoft invoice records can be read back to close matching orders in Procurify if your reconciliation workflow requires it.

How does the integration handle PeopleSoft's self-hosted architecture and unique hostname?

ml-connector accepts the full PeopleSoft hostname, port, and Tuxedo node name as configuration per customer, since PeopleSoft publishes no shared API base address. It also requires the customer's PeopleSoft administrator to explicitly activate the necessary service operations in the Integration Broker console before the integration can use them. This is a one-time setup step unique to on-premise PeopleSoft.

Does the integration support real-time synchronization or webhooks?

Both PeopleSoft and Procurify are pull-only; neither system publishes webhooks for procurement events. ml-connector polls both systems on a schedule you configure using date-range filters to identify new or updated records. This approach avoids the firewall complexity of exposing a webhook endpoint to PeopleSoft while keeping procurement in sync with finance on a regular cadence.