Oracle PeopleSoft and ServiceTitan integration

What moves between them

The main flow reads ServiceTitan invoices and payments and posts them into Oracle PeopleSoft as journal entries or vouchers on a daily or weekly schedule. Vendor records flow from Oracle PeopleSoft into ServiceTitan to keep the two systems aligned, with any new vendors created in Oracle PeopleSoft appearing in ServiceTitan within the sync window. Tax information and business unit data are mapped between the two systems so service invoices post to the correct general ledger accounts and cost centers in Oracle PeopleSoft. ServiceTitan can push invoice and payment events via webhooks where enabled, allowing near-real-time synchronization of completed transactions back to Oracle PeopleSoft.

How ml-connector handles it

ml-connector stores both credential sets encrypted and polls Oracle PeopleSoft on a schedule to read vendor records using REST endpoints with date-range filters, since Oracle PeopleSoft has no webhook push capability. ServiceTitan webhooks are received and verified using HMAC-SHA256 signatures for real-time job and invoice notifications. On the Oracle PeopleSoft side, ml-connector uses the customer's unique hostname and validates that required Integration Broker service operations are activated before attempting reads. OAuth2 tokens are cached for both systems and refreshed when expired. Vendor records are mapped to ServiceTitan's vendor entity, and ServiceTitan invoices are mapped to Oracle PeopleSoft journal entry or AP voucher formats with the correct general ledger accounts and business units. Because Oracle PeopleSoft write operations require SOAP Component Interface services, ml-connector uses authenticated SOAP calls to post vouchers and journal entries, with natural object keys to prevent duplicate posting if a network retry occurs. ServiceTitan AP bills are read-only, so no write-back occurs on the invoice side. All records carry a full audit trail and can be replayed if a downstream write fails.

A real-world example

A regional mechanical contractor with offices in three cities runs ServiceTitan for field dispatch, scheduling, and job invoicing, and uses Oracle PeopleSoft on-premise for accounting and vendor management. Before the integration, the accounting team exported ServiceTitan job invoices weekly and manually entered them into Oracle PeopleSoft's general ledger by business unit and location, a process that took 4-6 hours and frequently had re-keying errors. New vendors added to Oracle PeopleSoft did not sync to ServiceTitan, forcing dispatchers to maintain a parallel vendor list. With ServiceTitan and Oracle PeopleSoft connected, each completed ServiceTitan job invoice flows into Oracle PeopleSoft automatically on the correct general ledger account and cost center for that location, and vendors created in Oracle PeopleSoft appear in ServiceTitan within one polling cycle, eliminating the manual entry step and keeping both systems current.

What you can do

• •Sync vendor records from Oracle PeopleSoft to ServiceTitan so field service teams see the same vendor list.
• •Read ServiceTitan invoices and payments via webhooks or polling and post them to Oracle PeopleSoft as journal entries or AP vouchers on the correct general ledger accounts.
• •Map ServiceTitan jobs and invoices to Oracle PeopleSoft business units and cost centers so labor and material charges land on valid accounts.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer tokens, handle tenant-unique hostnames and port numbers, and activate required Integration Broker service operations.
• •Poll Oracle PeopleSoft on a custom schedule, receive ServiceTitan webhook events, verify signatures, retry failed writes to Oracle PeopleSoft using SOAP Component Interface calls, and maintain a full audit trail on every record.

Questions

Which direction does data move between Oracle PeopleSoft and ServiceTitan?

Vendors move from Oracle PeopleSoft into ServiceTitan so the contractor's service team sees the same vendor list. ServiceTitan invoices and payments move back into Oracle PeopleSoft as journal entries or AP vouchers on the correct general ledger accounts and business units. ServiceTitan AP bills are read-only, so ml-connector does not write invoice data back into ServiceTitan.

Why does Oracle PeopleSoft need to be polled if ServiceTitan supports webhooks?

Oracle PeopleSoft is self-hosted on-premise and has no outbound webhook capability. Integration Broker can push XML messages to external endpoints via manual configuration, but most integrations rely on polling with date-range filters instead. ServiceTitan does push webhook events for invoices and jobs, so ml-connector can receive those events in real time while polling Oracle PeopleSoft on a schedule you control.

What happens if an Oracle PeopleSoft write fails partway through a sync?

ml-connector tracks which ServiceTitan invoices have been successfully posted to Oracle PeopleSoft and can replay any failed write operation. SOAP write calls use natural object keys (vendor ID, date, amount) so a network retry does not create a duplicate posting. The full audit trail lets you see exactly which records succeeded and which need manual review.