How does ml-connector handle Oracle PeopleSoft's self-hosted architecture?

Each PeopleSoft customer has a unique hostname, port, and node name. ml-connector accepts these values per customer and uses them to construct the correct REST endpoint URL for each polling cycle. There is no shared Oracle-managed sandbox, so integration testing requires access to the customer's own development or test environment.

Which direction does data move between Oracle PeopleSoft and Ramp?

The main flow is from PeopleSoft into Ramp. Vendor master records and AP invoices are polled from PeopleSoft and synced into Ramp as vendors and bills. Bill status changes in Ramp (approval, payment, archival) are logged for audit purposes and can be used for downstream reconciliation back to PeopleSoft.

What happens if Oracle PeopleSoft is updated with a new vendor while ml-connector is syncing?

ml-connector maintains a processed-record log to avoid duplicate bill submissions. On the next polling cycle, new vendors are detected and added to Ramp. Because PeopleSoft has no API-level idempotency keys, the log prevents the same invoice from being created twice if the sync is retried.

Oracle PeopleSoftRamp

Oracle PeopleSoft and Ramp integration

Oracle PeopleSoft runs accounts payable, vendors, and general ledger across your enterprise. Ramp runs corporate spend, bill pay, and expense management. Connecting the two keeps your vendor master in agreement and pushes AP bills from PeopleSoft into Ramp for reconciliation and payment. New vendors created in PeopleSoft automatically appear in Ramp, and bill status changes in Ramp feed back to your AP records. ml-connector handles the authentication complexity on both sides and keeps the data flowing on a schedule you set.

How Oracle PeopleSoft works

Oracle PeopleSoft is a self-hosted on-premise ERP running on customer-managed servers or Oracle Cloud Infrastructure. It exposes vendors, invoices, GL accounts, and employees through REST and SOAP endpoints with a base URL pattern specific to each customer's hostname, port, and node name. Authentication is HTTP Basic Auth (OPRID plus password) for all versions, or OAuth2 Bearer token for PeopleTools 8.58 and later. PeopleSoft has no public webhooks, only asynchronous Integration Broker messaging that must be configured per customer, so vendor and invoice polling is the standard approach. Individual service operations must be activated by the PeopleSoft admin, and result sets are filtered by date range or other parameters since pagination is not standardized.

How Ramp works

Ramp is a cloud-hosted corporate spend management platform exposing vendors, bills, purchase orders, GL accounts, and accounting dimensions through REST APIs. It authenticates with OAuth2 using the Client Credentials flow (server-to-server), with tokens valid for ten days. Ramp supports both polling and real-time webhooks with HMAC-SHA256 signature verification. Vendors cannot be created directly; they are created implicitly when bills are submitted. Ramp offers read and write access to bills, transactions, and vendors, and read-only access to GL accounts and purchase orders.

What moves between them

The main flow runs from Oracle PeopleSoft into Ramp. ml-connector polls PeopleSoft's vendor and invoice endpoints on a schedule you define, extracting vendor master records and AP voucher data. Vendors are upserted into Ramp's vendor list, and new invoices are created as Ramp bills mapped to the corresponding GL accounts. Subsequent bill status changes in Ramp (approval, payment, archival) are tracked in audit logs for reconciliation back to PeopleSoft. Reference data such as GL accounts and departments are mapped first, ensuring every bill lands on a valid Ramp accounting dimension.

How ml-connector handles it

ml-connector stores both PeopleSoft and Ramp credentials encrypted. For PeopleSoft, it accepts each customer's self-hosted hostname, port, and node name (since there is no shared URL), and uses HTTP Basic Auth or refreshes OAuth2 Bearer tokens per the customer's PeopleTools version. For Ramp, it refreshes OAuth2 access tokens before they expire and stores the ten-day token lifetime. ml-connector polls PeopleSoft's vendor and invoice REST endpoints at intervals tied to your AP cycle, parsing the JSON responses and filtering by date range to avoid reprocessing. Each vendor extracted from PeopleSoft is matched against Ramp's vendor list; new vendors are queued for creation (implicitly via bill creation, since Ramp has no direct vendor creation endpoint). AP invoices become Ramp bills with GL account and department mappings applied. Because PeopleSoft has no idempotency guarantees at the API level, ml-connector maintains a processed-record log to prevent duplicate bill submissions. All records carry a full audit trail and can be replayed if a downstream Ramp call fails.

A real-world example

A mid-sized professional services firm runs Oracle PeopleSoft on-premise for accounting and AP, and Ramp for corporate cards and centralized bill pay across their offices. Before the integration, the AP team exported vendor and invoice data from PeopleSoft weekly, checked for new vendors, manually created them in Ramp if missing, and uploaded bills to Ramp by hand. Reconciliation was manual and slow, with bills sometimes posted to the wrong GL account. With Oracle PeopleSoft and Ramp connected, vendors and bills flow automatically from PeopleSoft into Ramp on each AP cycle, with GL accounts mapped correctly, eliminating manual data entry and reducing month-end reconciliation time by days.

What you can do

Sync vendor master records from Oracle PeopleSoft into Ramp automatically, creating new vendors as they are added to your AP system.
Poll Oracle PeopleSoft's invoice endpoints on your AP schedule and create Ramp bills with GL account and department mappings.
Authenticate to self-hosted Oracle PeopleSoft instances using HTTP Basic Auth or OAuth2, and refresh tokens as needed.
Maintain a full audit trail of every vendor and bill record, with replay capability if a Ramp API call fails.
Track bill status changes in Ramp and log them back to your audit trail for seamless month-end reconciliation.

Questions

How does ml-connector handle Oracle PeopleSoft's self-hosted architecture?: Each PeopleSoft customer has a unique hostname, port, and node name. ml-connector accepts these values per customer and uses them to construct the correct REST endpoint URL for each polling cycle. There is no shared Oracle-managed sandbox, so integration testing requires access to the customer's own development or test environment.
Which direction does data move between Oracle PeopleSoft and Ramp?: The main flow is from PeopleSoft into Ramp. Vendor master records and AP invoices are polled from PeopleSoft and synced into Ramp as vendors and bills. Bill status changes in Ramp (approval, payment, archival) are logged for audit purposes and can be used for downstream reconciliation back to PeopleSoft.
What happens if Oracle PeopleSoft is updated with a new vendor while ml-connector is syncing?: ml-connector maintains a processed-record log to avoid duplicate bill submissions. On the next polling cycle, new vendors are detected and added to Ramp. Because PeopleSoft has no API-level idempotency keys, the log prevents the same invoice from being created twice if the sync is retried.

Connect Oracle PeopleSoft and Ramp

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started