Oracle PeopleSoft and Cin7 integration

What moves between them

The primary flow moves GL journals, cost centers, and supplier master records from Oracle PeopleSoft into Cin7. GL journals are read from PeopleSoft via REST polling and loaded into Cin7 as chart of accounts entries, mapped to the matching cost centers. Supplier master records including vendor names, addresses, payment terms, and tax IDs flow from PeopleSoft into Cin7 suppliers on a daily or weekly schedule. Purchase orders and invoices created or modified in Cin7 can be written back to PeopleSoft via SOAP Component Interface calls, keeping the procure-to-pay process synchronized. The sync direction depends on where authoritative changes originate: if GL journal maintenance is done in PeopleSoft, that direction is primary; if new suppliers are onboarded in Cin7, those flow back to PeopleSoft.

How ml-connector handles it

ml-connector stores the PeopleSoft hostname, port, node name, and OPRID credentials encrypted, and presents HTTP Basic Auth on every REST call or an OAuth2 bearer token if PeopleTools 8.58 is running. It similarly stores the Cin7 API key pair and presents the custom headers on every request. Because PeopleSoft has no webhooks and no standard pagination, ml-connector polls at a cadence you set, using date-range filters to retrieve only new or changed records since the last sync. For write operations, ml-connector uses SOAP Component Interface calls with the supplied credentials to post purchase orders and invoices back into PeopleSoft's AP module. Cin7 imposes rate limits per application key, so ml-connector backs off and retries on 429 responses. GL journals are mapped from PeopleSoft GL accounts to Cin7 chart of accounts by account number, and supplier codes are mapped by vendor ID. Since PeopleSoft is self-hosted, there is no sandbox environment; testing is done against the customer's own development or PUM (Patch Update Manager) instance via Oracle Cloud Manager. All records carry a full audit trail, timestamps, and can be replayed if a downstream call fails.

A real-world example

A mid-sized manufacturing company runs Oracle PeopleSoft on-premise for general ledger and supplier management, and uses Cin7 Core for inventory, purchase orders, and accounting. Before integration, the finance team manually exported GL account structures from PeopleSoft and re-entered new accounts into Cin7 whenever the chart of accounts changed, and the procurement team re-keyed new vendors from PeopleSoft into Cin7 every time onboarding was completed. Purchase orders were created in both systems separately, creating duplicate records and reconciliation headaches at month-end close. With Oracle PeopleSoft and Cin7 connected, new GL accounts and cost centers sync automatically from PeopleSoft to Cin7, new suppliers flow from PeopleSoft into Cin7 on a daily schedule, and purchase orders created in Cin7 post back to PeopleSoft's AP module without manual intervention. The finance team now spends month-end close reconciling balances instead of chasing duplicate records.

What you can do

• •Sync GL journals and cost centers from Oracle PeopleSoft into Cin7's chart of accounts on a schedule you control.
• •Keep supplier master records aligned between Oracle PeopleSoft and Cin7, including vendor names, addresses, and payment terms.
• •Write purchase orders and invoices from Cin7 back into Oracle PeopleSoft via SOAP Component Interface calls.
• •Authenticate both systems encrypted: HTTP Basic Auth or OAuth2 for Oracle PeopleSoft, custom API keys for Cin7.
• •Poll Oracle PeopleSoft on your cadence with date-range filters and handle retries when Cin7 rate limits are reached.

Questions

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

Every PeopleSoft installation has a unique hostname, port, and node name. ml-connector accepts those parameters per customer and stores the HTTP Basic Auth credentials (OPRID and password) encrypted, or uses OAuth2 bearer tokens if PeopleTools 8.58 or later is running. Write operations use SOAP Component Interface calls with the same credentials.

Why does the integration poll instead of using webhooks?

Oracle PeopleSoft has no standard webhook system. It offers Integration Broker asynchronous pub/sub, but that requires customer configuration. ml-connector uses REST polling with date-range filters, which works across all PeopleTools versions and does not require additional setup in PeopleSoft. You control the sync schedule.

Which GL accounts and suppliers should be synced from Oracle PeopleSoft to Cin7?

Typically, active GL accounts, cost centers, and vendors marked as suppliers in PeopleSoft are synced. Cin7's chart of accounts is read-only via API, so accounts are created as reference entries. Suppliers are synced with all master data including vendor IDs, names, addresses, and payment terms, and matched by vendor ID on future updates.