ERP Integration

Auxtri + Oracle PeopleSoft

Auxtri is the inbox layer for Oracle PeopleSoft. Four products, one integration through Integration Broker REST, and your vendors never change a thing.

PeopleSoft Runs Your Health System. The Inbox Burden Is Heavier, Not Lighter.

PeopleSoft powers some of the largest and longest-running health systems in the country. It is deeply configured, deeply trusted, and not going anywhere. Your AP team knows it cold.But PeopleSoft's vendor communication tooling hasn't evolved at the same pace as newer cloud ERPs. When a vendor emails asking "Where's my payment?" someone still navigates the voucher and payment screens by hand, then composes the reply. For PeopleSoft shops the inbox burden is heavier, not lighter.You don't need a full ERP migration to fix that. Auxtri brings the same modern inbox automation to PeopleSoft that newer cloud ERPs get, reading your data through Integration Broker REST and leaving your PeopleSoft configuration exactly as it is.

Lead Product

Vendor Inquiry Automation on Oracle PeopleSoft

Vendor inquiry automation is the daily fire AP managers feel first. When a "Where's my payment?" email lands, Auxtri reads it and pulls the voucher status, scheduled and actual payment dates, check or ACH references, and vendor identity from PeopleSoft using Integration Broker REST through Query Access Services. The reply is built from your live data.This flow is read-only. Auxtri looks up what your team would have looked up by hand and never writes back to PeopleSoft for an inquiry response.

What Auxtri reads

Voucher status, scheduled and actual payment dates, check and ACH references, PO references, and vendor identity, queried from PeopleSoft through Integration Broker REST (Query Access Services) when the email is processed.

SetID-based vendor lookups

PeopleSoft organizes vendors by SetID. Auxtri resolves the inquiry against the correct SetID so a vendor shared across business units returns the right records.

GPO inquiry routing

Healthcare vendors often bill through group purchasing organizations with several subsidiary IDs. Auxtri matches the right vendor records so the response references the correct vouchers.

Nothing is written back

Inquiry responses are read-only. Auxtri pulls data and drafts a reply; your team approves and sends. No part of this flow changes a record in PeopleSoft.

A vendor emails "What's the status of invoice 78432?" Here is what happens.

1

Classification

Auxtri reads the email, recognizes a payment status inquiry, identifies the vendor, and extracts invoice number 78432.

2

PeopleSoft lookup through Integration Broker REST

Auxtri queries PeopleSoft for the matching voucher: its status, scheduled payment date, and any check or ACH reference, scoped to the correct SetID.

3

Draft with real data

A reply is composed with the actual status and payment date from PeopleSoft and lands in your review queue.

4

Human review

An AP staffer confirms the draft matches and edits anything they want to change.

5

Send

The approved reply goes back to the vendor in seconds instead of a manual lookup.

Statement Reconciliation on Oracle PeopleSoft

Vendor statements arrive as PDFs with dozens of line items. Auxtri OCR-extracts every line, then matches each one against your PeopleSoft voucher and payment records through Integration Broker REST. What used to take one to two hours of manual cross-referencing per statement comes back in about 15 minutes.Partial payments, credit memos, and unapplied credits are categorized rather than dropped, so the reconciled summary reflects what actually happened in PeopleSoft.

Line-item OCR extraction

Every line on the statement PDF is extracted into structured invoice references and amounts, so the match runs against data instead of a scanned image.

Matched against PeopleSoft records

Each line is compared to the voucher and payment records in PeopleSoft through Integration Broker REST, reflecting your live ledger.

Partial payments and credits handled

Partial payments, credit memos, and unapplied credits are categorized in the reconciliation rather than forced into a match or ignored.

Reconciled output in the review queue

The summary groups lines as matched, unmatched, or discrepancy, so your team scans the exceptions instead of re-keying the statement.

A vendor sends a 40-line month-end statement. Here is the reconciliation.

1

Extraction

Auxtri OCR-extracts all 40 lines from the PDF into structured invoice references and amounts.

2

Match through Integration Broker REST

Each line is matched against PeopleSoft voucher and payment records, including partial payments and credits.

3

Reconciled summary

Lines are grouped as matched, unmatched, or discrepancy and presented in the review queue.

4

Vendor response

The draft reply references the actual PeopleSoft data for the discrepancies, ready to approve and send.

AP Invoice Intake on Oracle PeopleSoft

When a vendor emails an invoice PDF, Auxtri reads it from the inbox, OCR-extracts the fields, and lands a structured review packet. It extracts the invoice number, date, amount, PO reference, vendor identity, and line items, then suggests the vendor and business unit and flags likely duplicates against your existing PeopleSoft voucher records through Integration Broker REST.Auxtri handles intake and structuring only. PO matching, GL coding, approval routing, and payment execution all stay in PeopleSoft. Once the packet is approved, it is ready for PeopleSoft's existing voucher build and approval workflow.

Fields extracted

Invoice number, invoice date, amount, PO reference, vendor identity, and line items are pulled from the emailed PDF into a structured packet.

Vendor and business unit suggestions

Auxtri suggests the matching vendor and business unit so the reviewer starts from a populated packet instead of a blank form.

Duplicate detection

Auxtri checks the extracted invoice against existing PeopleSoft voucher records through Integration Broker REST and flags likely duplicates before they reach your team.

What stays in PeopleSoft

PO matching, GL coding, approval routing, and payment execution all remain in PeopleSoft. Auxtri prepares the structured packet; PeopleSoft runs the voucher lifecycle.

The Approval Layer

Vendor Master Manager on Oracle PeopleSoft

Vendor Master Manager handles the maintenance work that piles up in the background: W-9s, bank change requests, COIs, payment term changes, remittance requests, and tax ID updates. On a PeopleSoft tenant, reads run through Integration Broker REST Query Access Services and approved writes go through Component Interfaces. Every write is approval-gated and audit-logged end to end.

Bank change requests

A banking update triggers domain mismatch detection, dual approval, and a logged out-of-band confirmation call, with a one-cycle payment hold while the change is verified. The approved write goes through a PeopleSoft Component Interface so your existing vendor security and audit trail apply.

W-9 collection and tax ID updates

Auxtri auto-requests a fresh W-9 and runs an IRS TIN match before any write. Tax ID and legal name changes are batched into a single approved Component Interface transaction so the vendor record never sits half-updated.

COI tracking

Auxtri tracks COI expirations in its own compliance store, extracts the expiration date, runs a proactive 90, 60, and 30 day outreach cadence, and can trigger a payment hold when a certificate lapses.

Payment term changes

A term change routes to your configured approver with the current terms from PeopleSoft surfaced for comparison, then writes through a Component Interface scoped to the correct SetID.

Remittance advice requests

The most automatable module. Auxtri queries PeopleSoft for the payment date, amount, and check or ACH reference. Above your confidence threshold it can auto-send with a copy to the team; below it, the draft lands in the review queue. No ERP writes are required.

Audit-logged writes

Every write records the structured payload sent to PeopleSoft, the response, the approver IDs, the out-of-band confirmation reference when required, and the approval policy that fired. Built for compliance review, not retrofit for it.

Implementation: Four to Six Weeks, Low Disruption

Auxtri connects to your existing PeopleSoft environment without a migration, without reconfiguring your ERP, and without retraining your team. The integration is pre-built on Integration Broker REST.

Scoped permissions

Read access for voucher and payment data through Query Access Services. Writes only on the Vendor Master Manager workflows you enable, through Component Interfaces, behind dual approval.

No PeopleSoft customization

Your PeopleSoft configuration, vendor security, and SetID structure stay as they are. Auxtri sits next to your existing setup and only writes through workflows you turn on.

Pre-built Integration Broker REST integration

Our implementation team works with your PeopleSoft administrators to configure Integration Broker REST access, the Component Interfaces for vendor master writes, and data mapping.

BAA executed during onboarding

Auxtri is built for healthcare. We execute a Business Associate Agreement as part of onboarding and maintain the technical safeguards required to handle data adjacent to ePHI.

See Auxtri Work with Your Oracle PeopleSoft Data

Bring sample vendor emails to a live demo. We'll query your Oracle PeopleSoft system and show you exactly how Auxtri drafts responses using your real data.