Oracle PeopleSoft and Square integration

What moves between them

Vendor records flow from PeopleSoft into Square's vendor endpoint, so accounts payable teams see all PeopleSoft suppliers in Square for payment processing. Customers and customer segments flow from PeopleSoft to Square's customer directory. Payment and invoice data move from Square back into PeopleSoft so finance can reconcile cash and match Square transaction records to PeopleSoft invoices and payments. The sync runs on a schedule you define, typically daily or weekly, to keep reference data current without overwhelming PeopleSoft's polling capacity.

How ml-connector handles it

ml-connector stores PeopleSoft credentials (OPRID and password, or OAuth2 token) encrypted and connects to each customer's unique PeopleSoft instance using the full hostname and node name provided at setup. It polls PeopleSoft for vendors, customers, and recent invoices using date-range filters to manage load, then reads the resulting REST or SOAP responses and transforms them into Square's expected JSON schema. On the Square side, ml-connector uses Bearer token authentication and automatically refreshes expired tokens before they cause call failures. Vendor and customer records are matched by external ID or natural key on both sides to avoid duplicates. Square's 30-day token expiry and PeopleSoft's lack of rate-limit headers mean ml-connector tracks token refresh timing and monitors PeopleSoft polling load to avoid service degradation. Every record carries a full audit trail, and failed syncs can be replayed once the underlying issue is resolved.

A real-world example

A mid-sized retail holding company runs Oracle PeopleSoft for financial consolidation, accounts payable, and HR across multiple operating companies, each with its own Square account for point-of-sale and online payments. Before the integration, the accounts payable team manually entered new vendors from PeopleSoft into each company's Square account, and the finance team exported Square payment reports daily to match them to PeopleSoft invoices and payments. With PeopleSoft and Square connected, new vendors from PeopleSoft automatically appear in Square ready for payment, and daily payment summaries flow back into PeopleSoft so the daily bank reconciliation process starts with all transactions already matched.

What you can do

• •Sync vendor records from Oracle PeopleSoft to Square's vendor endpoint so accounts payable teams see all suppliers available for payment processing.
• •Keep customer records and segments aligned between PeopleSoft and Square so customer credit terms and tax treatment stay consistent across systems.
• •Pull payment and invoice data from Square into PeopleSoft daily so finance can reconcile cash and match ecommerce transactions to AP and AR records.
• •Authenticate PeopleSoft with HTTP Basic Auth or OAuth2 and Square with Bearer token, managing token refresh and PeopleSoft's unique instance configuration.
• •Poll PeopleSoft on a schedule with date-range filters to manage load, match records by external ID to avoid duplicates, and maintain a full audit trail of every sync.

Questions

How does ml-connector handle PeopleSoft's requirement for a unique hostname and node name?

PeopleSoft is self-hosted, so every customer operates their own instance at a unique hostname with a unique Integration Broker node name. ml-connector accepts the full REST service URL and node configuration per customer during setup and uses those credentials for every request. No shared base URL is required, and ml-connector stores the configuration encrypted for each customer's cell.

Can ml-connector write journal entries from Square payments back into PeopleSoft's general ledger?

No. Square is a commerce and payments platform and does not expose a chart of accounts or GL posting interface. ml-connector syncs transaction summaries and invoice matching data so finance can reconcile, but actual journal entries for payments must be created in PeopleSoft based on the Square transaction data, either through a downstream ERP process or manual review and posting.

What happens when the Square access token expires or PeopleSoft becomes temporarily unreachable?

ml-connector tracks Square's 30-day token expiry and automatically refreshes using the refresh token before a call can fail. For PeopleSoft outages, ml-connector retries failed syncs with exponential backoff and surfaces the error in the audit trail so finance can replay the sync once the instance is available again.