Oracle PeopleSoft and Cleo integration

What moves between them

Purchase orders, invoices, and vendor records flow from PeopleSoft to Cleo on a daily or weekly schedule aligned to your procurement and payment cycles. ml-connector polls PeopleSoft for new or modified purchase orders and invoices since the last sync, transforms them into EDI 850 and 810 formats, and posts them to Cleo as files or API events. Vendor master records and cost objects sync bidirectionally so Cleo's trading partner profiles match PeopleSoft's approved vendor list. Payment and invoice status flows back from Cleo into PeopleSoft when supplier confirmations and receipts are available.

How ml-connector handles it

ml-connector stores the PeopleSoft OPRID and password encrypted and connects to your unique hostname and port using HTTP Basic Auth or OAuth2 tokens. It retrieves the Cleo tenant URL and OAuth2 credentials (also encrypted) and manages the short-lived Bearer token across API calls. Because PeopleSoft is pull-only, ml-connector polls purchase order and invoice inquiry endpoints on a schedule you define, filters by date or created timestamp to find only new records, and avoids re-posting by tracking processed order numbers and voucher IDs. Each PeopleSoft purchase order maps to a Cleo EDI 850 message, and each invoice becomes an EDI 810 or API payload directed to the matching supplier connection in Cleo. ml-connector retries on HTTP 429 rate limits from Cleo, backs off exponentially, and logs every poll, transform, and post attempt in the audit trail so failed records can be replayed without loss.

A real-world example

A large manufacturing company operates Oracle PeopleSoft for procurement and finance across four regional plants and a central buying office. Purchase orders created in PeopleSoft must flow to 200+ suppliers as EDI 850 documents through Cleo for order transmission, and supplier invoice receipts must be captured as EDI 810 transactions and matched back to PeopleSoft for payment processing. Before the integration, the procurement team exported purchase orders from PeopleSoft weekly, manually formatted them as EDI files, and uploaded them to Cleo. Invoice returns from suppliers were exported from Cleo and re-entered into PeopleSoft's invoice matching module by hand, creating delays and data entry errors. With PeopleSoft and Cleo connected, each purchase order in PeopleSoft automatically flows to Cleo as an EDI 850 message to the correct supplier, and incoming 810 invoices are posted back to PeopleSoft in the same transaction, reducing the invoice matching cycle from days to hours and eliminating manual file handling.

What you can do

• •Sync purchase orders from PeopleSoft to Cleo as EDI 850 messages on a daily or weekly schedule aligned to your procurement cycle.
• •Post invoices from PeopleSoft as EDI 810 or API payloads to Cleo for supplier invoice transmission and trading partner fulfillment.
• •Align vendor master records and cost objects bidirectionally between PeopleSoft and Cleo so trading partner profiles match your approved supplier list.
• •Authenticate PeopleSoft with HTTP Basic Auth or OAuth2 Bearer tokens and handle each customer's unique hostname, port, and node name without re-configuration.
• •Retry Cleo rate limits, track processed records by order number and voucher ID, and replay failed transactions with a complete audit trail.

Questions

How does ml-connector handle PeopleSoft's unique deployment architecture?

Each PeopleSoft customer operates on their own hostname and port. ml-connector stores the full base URL (hostname, port, and node name) for each PeopleSoft instance along with the HTTP Basic Auth credentials or OAuth2 configuration. On every sync, it uses those credentials to connect to the customer's unique PeopleSoft environment, so the same integration code works across any number of customer deployments without re-hardcoding endpoints.

What happens if a PeopleSoft inquiry operation is not activated by the PeopleSoft administrator?

PeopleSoft requires a system administrator to activate each Service Operation in the Integration Broker console before it can be called. ml-connector will receive a 401 or 403 error when attempting to call a deactivated operation. The integration will surface this as a connectivity error in the audit trail, and your PeopleSoft team must activate the required inquiry operations (e.g., purchase order fetch, invoice fetch, vendor lookup) before polling can proceed.

Can ml-connector handle both EDI and API payloads to Cleo, or must I choose one format?

ml-connector can route data to Cleo in either EDI transaction format (850, 810) or as API JSON payloads, depending on how you configure the Cleo connection and action. Most supply chain integrations use EDI for supplier feeds, but API routes are available if your Cleo tenant uses managed file transfers or API-based integrations. Your Cleo tenant administrator defines the action in CIC Studio; ml-connector will post records to the action you specify.