Oracle PeopleSoft and ServiceNow integration

What moves between them

The integration moves vendor masters and accounts payable invoices from PeopleSoft into ServiceNow's staging tables on a polling schedule tied to the accounting calendar. Vendor records flow first so invoice staging references valid suppliers. Invoices are staged in ServiceNow's sn_apo_invoice staging table where Source-to-Pay operations pick them up for approval and posting. The flow is unidirectional; ServiceNow does not write back to PeopleSoft. Payment status and GL posting happen inside ServiceNow and are captured for audit only.

How ml-connector handles it

ml-connector accepts the full PeopleSoft hostname and port per customer along with the Integration Broker node name, since each instance is self-hosted and publishes no shared base URL. It authenticates using HTTP Basic Auth with the configured OPRID and password, or OAuth2 token if PeopleTools version 8.58 or later is in use. On the ServiceNow side, ml-connector uses OAuth2 Client Credentials to obtain a 30-minute bearer token, which it refreshes before expiry. Because PeopleSoft REST endpoints are read-only inquiry operations with no webhook system, ml-connector polls on a fixed schedule, filtering by date range to capture new and updated vendors and invoices. Vendor codes and names are mapped directly to ServiceNow cost centers and supplier records. Invoice staging payloads include line-item detail, GL distribution codes mapped to ServiceNow GL accounts, and cost center references. PeopleSoft's lack of published API pagination requires filters on inquiry operations rather than bulk retrieval. Every record carries a source reference ID and timestamp for audit and replay.

A real-world example

A mid-market financial services firm runs PeopleSoft on-premise for general ledger, accounts payable, and procurement. They recently adopted ServiceNow to centralize their Source-to-Pay operations and automate invoice approval workflows. Before the integration, the accounts payable team exported vendor and invoice data from PeopleSoft monthly, manually cleaned formatting issues, and loaded them into ServiceNow staging tables via CSV. With the integration live, vendor master changes from PeopleSoft flow automatically into ServiceNow twice a week, and invoices are staged as they are entered in the ERP, eliminating the manual export and the downstream reconciliation work. The approval workflow in ServiceNow now references validated PeopleSoft cost centers and GL accounts, reducing invoice holds for bad master data.

What you can do

• •Sync vendor masters from Oracle PeopleSoft to ServiceNow on a regular schedule, keeping supplier records current across both systems.
• •Stage accounts payable invoices with full line-item detail and GL distribution into ServiceNow's Source-to-Pay staging tables for downstream approval workflows.
• •Bridge OAuth2 and HTTP Basic Auth between PeopleSoft's on-premise endpoints and ServiceNow's cloud API, handling each customer's unique hostname and authentication scheme.
• •Poll PeopleSoft with date-range filters to capture new vendors and invoices without re-fetching the entire history.
• •Maintain a full audit trail of every staged record with source IDs and timestamps for troubleshooting and replay if a downstream approval fails.

Questions

What records move from PeopleSoft to ServiceNow?

Vendor masters and accounts payable invoices move from PeopleSoft into ServiceNow's Source-to-Pay staging tables. Vendors flow first so invoice staging records reference valid suppliers. Invoice staging includes line items, GL account codes, cost center references, and payment terms. Payment status and GL posting remain in ServiceNow and are not written back to PeopleSoft.

How does the integration handle PeopleSoft's on-premise topology and lack of webhooks?

ml-connector accepts the unique hostname, port, and Integration Broker node name for each PeopleSoft instance, since there is no Oracle-managed shared endpoint. Because PeopleSoft does not expose webhooks, ml-connector polls on a fixed schedule, filtering by date range to retrieve only new and changed records. This avoids full table scans and reduces load on the on-premise system.

Which authentication method does ml-connector use, and how does token refresh work?

ml-connector supports both HTTP Basic Auth (OPRID plus password) for all PeopleTools versions and OAuth2 Bearer tokens for PeopleTools 8.58 and later, configured per customer. On ServiceNow, it uses OAuth2 Client Credentials to obtain a 30-minute token, refreshing it before expiry on each polling cycle. This keeps both sides authenticated without requiring manual token rotation.