Oracle PeopleSoft and Basware integration

What moves between them

The main flow runs from Basware into Oracle PeopleSoft. When an invoice clears coding and approval, Basware fires an AccountingDocuments webhook, and ml-connector reads the full document and posts it as an AP voucher into PeopleSoft through the AP_VOUCHER Component Interface, mapped to the matching business unit, vendor, GL accounts, and cost centers. In the other direction, PeopleSoft vendor master records and GL account and dimension data are imported into Basware so the coding panel only offers valid accounts and suppliers. Once PeopleSoft records a payment, ml-connector calls the Basware paymentResponses endpoint so the invoice status closes out. Cadence is event-driven from Basware webhooks for invoices, with scheduled polling for master data and payment status.

How ml-connector handles it

ml-connector stores both credential sets encrypted, requesting a fresh Basware OAuth2 bearer token before the one-hour token expires and sending PeopleSoft Basic Auth against the customer hostname and node name on every call. It accepts the full PeopleSoft base URL and Integration Broker node name per customer because PeopleSoft publishes no shared address. Basware webhooks are verified by recomputing the HMAC-SHA256 over the raw UTF-8 body using the webhookAuthenticationToken and checking the timestamp to reject replays, and the endpoint returns HTTP 200 only after a valid signature. Approved AccountingDocuments are mapped field by field into the AP_VOUCHER schema, so the invoice number acts as the natural key and PeopleSoft rejects a duplicate voucher on retry. Master data imports into Basware paginate with the continuation token returned in the response header, which must be sent back as a request header on the next page. Because PeopleSoft is pull-only for status, payment confirmation is polled from the eSettlements payment inquiry endpoints and then written back to Basware. ml-connector backs off on Basware 429 responses and PeopleSoft 500 or 503 errors, never updates the same record within a few seconds to avoid Basware locking, and every record carries a full audit trail with replay if a downstream call fails.

A real-world example

A mid-sized regional healthcare provider runs Oracle PeopleSoft Financials on its own servers for the general ledger and accounts payable, and uses Basware to capture and approve supplier invoices across several facilities. Before the integration, the AP team approved invoices in Basware, then a clerk keyed each one into PeopleSoft as a voucher, copying the coding by hand and reconciling vendor codes that did not always match. With Oracle PeopleSoft and Basware connected, each approved invoice posts straight into PeopleSoft against the correct business unit and cost center, vendor and GL master data stays aligned so coding is valid, and payment status flows back to Basware automatically. The re-keying step disappears and month-end close starts with AP already in agreement.

What you can do

• •Post approved Basware invoices into Oracle PeopleSoft as AP vouchers through the AP_VOUCHER Component Interface.
• •Import PeopleSoft vendor, GL account, and dimension data into Basware so the coding panel stays valid.
• •Confirm payments back to Basware through the paymentResponses endpoint once PeopleSoft records them.
• •Bridge Basware OAuth2 client credentials with PeopleSoft Basic Auth against the customer hostname and node name.
• •Verify Basware HMAC-SHA256 webhooks and poll PeopleSoft status, with retries and a full audit trail on every record.

Questions

Which direction does data move between Oracle PeopleSoft and Basware?

The main flow is Basware into Oracle PeopleSoft. Approved invoices move from Basware and post as AP vouchers in PeopleSoft, while PeopleSoft vendor and GL master data is imported into Basware to keep coding valid. Once PeopleSoft records a payment, ml-connector confirms it back to Basware so the invoice closes out.

How does the integration handle the different authentication on each side?

Basware uses OAuth2 client credentials and returns a bearer token valid for about an hour with no refresh token, so ml-connector requests a new token before each expiry. PeopleSoft uses HTTP Basic Auth with an OPRID and password against the customer hostname and Integration Broker node name. Both credential sets are stored encrypted and applied automatically on every call.

Does Basware push invoices, or does the connector poll PeopleSoft?

Basware supports real webhooks and fires an AccountingDocuments event when an invoice is ready for transfer, signed with HMAC-SHA256 in the X-BWAPI-Signature-256 header. ml-connector verifies that signature, then posts the voucher to PeopleSoft. PeopleSoft has no self-service webhooks, so payment status and master data are read by scheduled polling instead.