Oracle PeopleSoft and Stampli integration

What moves between them

Approved invoices flow from Stampli into Oracle PeopleSoft. ml-connector polls Stampli's SFTP directory at a regular interval (e.g. every 15 minutes) for new invoice export files in CSV or XML format. Each file contains approved invoice records with vendor, amount, GL account coding, and cost center allocation. ml-connector parses the files, transforms them into Oracle PeopleSoft AP_VOUCHER component format, and posts them via SOAP Component Interface write operations. Deduplication prevents the same invoice from posting twice if a polling cycle detects the file again before it is archived.

How ml-connector handles it

ml-connector stores both credential sets encrypted: SFTP credentials for Stampli and HTTP Basic Auth (OPRID plus password) or OAuth2 bearer token for Oracle PeopleSoft. For each polling interval, ml-connector connects via SFTP to Stampli's outbound directory, downloads new invoice files, and parses the CSV or XML format per the Stampli template. Each invoice is transformed into a PeopleSoft AP_VOUCHER component request, mapping Stampli's vendor code and GL account fields to PeopleSoft's VENDOR_CI and JOURNAL_ENTRY_CI references. ml-connector then posts the voucher via SOAP Component Interface to the customer's unique PeopleSoft hostname and port. Because both systems support polling only and neither has webhooks, ml-connector deduplicates by tracking processed file names and invoice IDs in its audit log. Network requirements: the PeopleSoft instance must be reachable (usually behind firewall or reverse proxy requiring whitelisting), and the Stampli SFTP server must allow outbound connections from the ml-connector host. Retries handle transient SFTP or SOAP timeouts, and every invoice carries a complete audit trail.

A real-world example

A mid-sized manufacturing company uses Oracle PeopleSoft on-premise for finance and procurement, and Stampli in the cloud for invoice capture and AP automation. Before the integration, the AP team printed Stampli approval reports, manually re-keyed vendor names, amounts, and GL coding into PeopleSoft AP vouchers, and hand-matched invoices to purchase orders in PeopleSoft. With Stampli and Oracle PeopleSoft connected via ml-connector, each approved invoice flows directly into PeopleSoft's AP module on a schedule tied to the company's approval cycle. The AP team now spends its time resolving exceptions and managing vendor relationships rather than re-keying data, and PeopleSoft's AP aging and payment records reflect Stampli's ground truth.

What you can do

• •Move approved invoices from Stampli into Oracle PeopleSoft AP_VOUCHER components via SOAP, mapped to the correct vendors and GL accounts.
• •Poll Stampli's SFTP directory on a schedule you control, retrieving CSV or XML invoice export files as they become available.
• •Authenticate SFTP connections to Stampli and SOAP Component Interface calls to PeopleSoft (HTTP Basic Auth or OAuth2 bearer token).
• •Deduplicate invoices across polling intervals by tracking file names and invoice IDs in the audit log.
• •Handle the unique per-customer hostname and port configuration of self-hosted Oracle PeopleSoft instances.

Questions

How does ml-connector handle the different transports between Stampli and PeopleSoft?

Stampli publishes data only through SFTP file exports; it has no public REST API. Oracle PeopleSoft accepts writes through SOAP Component Interface calls and reads through REST Skills endpoints. ml-connector connects to Stampli via SFTP, downloads invoice files, parses them, transforms the data into PeopleSoft AP_VOUCHER component format, and posts via SOAP to PeopleSoft's unique instance URL and port.

What happens if an invoice file appears in the Stampli SFTP directory more than once?

ml-connector tracks processed file names and invoice IDs in its audit log and compares each polling cycle against the log. If the same invoice ID appears in a new or re-uploaded file, ml-connector detects the duplicate and skips posting the voucher again. The audit entry shows the original post date and the duplicate detection event.

Does ml-connector require the PeopleSoft instance to be on the public internet?

No. Most PeopleSoft instances are on-premise behind a corporate firewall. ml-connector can reach PeopleSoft if the customer whitelists the ml-connector IP address on their firewall or if PeopleSoft is exposed through a reverse proxy. Credentials (OPRID and password or OAuth2 token) are stored encrypted by ml-connector.