Oracle PeopleSoft and AvidXchange integration

What moves between them

Vendor masters and GL account and dimension lists flow from Oracle PeopleSoft into AvidXchange so AP staff can route and code invoices correctly. Approved AP vouchers move the same direction for payment. After AvidPay executes a payment, ml-connector pulls the settled check number, ACH trace, or virtual card detail from AvidXchange and posts it against the PeopleSoft general ledger through the JOURNAL_ENTRY_CI SOAP service. Reference data is synced first so every invoice lands on a vendor and GL code that already exists. Payment instructions are never written back into PeopleSoft, since AvidXchange owns execution.

How ml-connector handles it

ml-connector stores both credential sets encrypted. On the PeopleSoft side it accepts the customer base URL, node name, and OPRID and password, or an OAuth2 token where an IDP is configured, and it reads inquiry data over REST while creating vouchers and posting journals through SOAP Component Interfaces. On the AvidXchange side it sends the Company Token and User Token on every AvidConnect call. Because neither system offers usable push events, both are polled on a schedule, conservatively for PeopleSoft to avoid loading the self-hosted application server. Vendors and GL codes are synced before invoices so coding never fails on a missing payee. Voucher creation uses the PeopleSoft invoice number as a natural idempotency key, since PeopleSoft rejects a duplicate that already exists, and AvidXchange batch IDs are tracked to avoid resubmitting a batch. PeopleSoft returns HTTP 401 on bad credentials and cryptic 500 errors under load, so ml-connector backs off and retries with a full audit trail and error replay.

A real-world example

A mid-market property management firm with roughly 600 employees runs Oracle PeopleSoft Financials for its general ledger and payables across dozens of managed properties, and adopts AvidXchange to automate a high volume of vendor invoices. Before the integration, staff exported vendor and GL data into AvidXchange by spreadsheet and keyed settled payments back into PeopleSoft by hand each week, which delayed close and left the ledger out of step with what AvidPay had actually paid. With Oracle PeopleSoft and AvidXchange connected, vendors and GL codes sync automatically, approved vouchers flow out for payment, and settled payment detail posts back to the general ledger. The weekly re-keying is gone and the cash accounts reconcile on their own.

What you can do

• •Sync Oracle PeopleSoft vendor masters into AvidXchange so invoices route to a valid payee.
• •Push PeopleSoft GL accounts and accounting dimensions into AvidXchange for accurate invoice coding.
• •Send approved AP vouchers from PeopleSoft to AvidXchange for payment execution.
• •Post settled check, ACH, and virtual card detail back to the PeopleSoft general ledger via JOURNAL_ENTRY_CI.
• •Bridge PeopleSoft Basic Auth or OAuth2 with AvidXchange company and user tokens, polling both on a schedule with retries and a full audit trail.

Questions

Which direction does data move between Oracle PeopleSoft and AvidXchange?

Vendors, GL codes, accounting dimensions, and approved AP vouchers move from Oracle PeopleSoft into AvidXchange. Settled payment detail moves the other way, from AvidXchange back into the PeopleSoft general ledger. AvidXchange owns payment execution, so ml-connector never writes payment instructions back into PeopleSoft.

How does the integration handle PeopleSoft being self-hosted with no webhooks?

Each customer provides their own PeopleSoft base URL and Integration Broker node name, which ml-connector stores per connection. Because PeopleSoft has no conventional webhooks and only pushes XML when an admin configures Integration Broker routing, the connector polls PeopleSoft inquiry endpoints on a conservative schedule. This avoids loading the on-premise application server while keeping AvidXchange current.

How are AvidXchange payments written back into PeopleSoft?

AvidXchange has no GL write endpoint and runs approval and payment inside AvidSuite, so it returns only settled payment status. ml-connector pulls that status after AvidPay executes a payment and posts the check, ACH, or virtual card detail into PeopleSoft using the JOURNAL_ENTRY_CI SOAP Component Interface, since PeopleSoft exposes no delivered REST endpoint for journal entry.