ERP Integration

Auxtri + Workday

Auxtri is the inbox layer for Workday Financial Management. Four products, one integration through the Workday REST API, and your vendors never change a thing.

Workday Modernized Your Invoice Processing. Vendor Inquiries Didn't Change.

Your health system moved to Workday Financial Management for faster invoice processing, better reporting, and modern cloud infrastructure. The migration delivered on those promises.But vendor communication still arrives in the same shared AP mailbox and still requires manual effort. The "Where's my payment?" emails, the statement reconciliation requests, the remittance inquiries. Someone on your team still logs into Workday, looks up each invoice, and composes a response by hand.Faster invoice processing often creates higher vendor expectations for equally fast inquiry responses. Workday has no tooling for that conversation layer. It tracks the invoice, not the communication around it. That's a structural gap, not a configuration problem.

Lead Product

Vendor Inquiry Automation on Workday

Vendor inquiry automation is the daily fire AP managers feel first. When a "Where's my payment?" email lands, Auxtri reads it through the Workday REST API and pulls the invoice status, scheduled and actual payment dates, check or ACH references, and the supplier identity from Workday Financial Management. The reply is built from your live data.This flow is read-only. Auxtri honors Workday's worker-based security model, so it only sees what the integration security group permits, and it never writes back to Workday for an inquiry response.

What Auxtri reads

Invoice status, scheduled and actual payment dates, check and ACH references, PO references, and supplier identity, queried from Workday through the Workday REST API when the email is processed.

Worker-based security model

Auxtri only sees what your Workday integration security group permits. Reads are scoped by the same security model you already administer.

Multi-entity company lookups

Health systems run Workday across multiple companies and cost centers. Auxtri resolves vendor inquiries across your entire organizational structure so the answer is complete.

GPO inquiry routing

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

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 supplier, and extracts invoice number 78432.

2

Workday lookup through the REST API

Auxtri queries Workday for invoice 78432: its status, scheduled payment date, and any check or ACH reference, scoped by the integration security group.

3

Draft with real data

A reply is composed with the actual status and payment date from Workday 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 Workday

Vendor statements arrive as PDFs with dozens of line items. Auxtri OCR-extracts every line, then matches each one against your Workday invoice and payment records through the Workday REST API. 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 Workday.

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 Workday records

Each line is compared to the invoice and payment records in Workday Financial Management through the Workday REST API, 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 the REST API

Each line is matched against Workday invoice 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 Workday data for the discrepancies, ready to approve and send.

AP Invoice Intake on Workday

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 supplier and company and flags likely duplicates against your existing Workday invoice records through the Workday REST API.Auxtri handles intake and structuring only. PO matching, GL coding, approval routing, and payment execution all stay in Workday. Once the packet is approved, it is ready for Workday's existing invoice 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.

Supplier and company suggestions

Auxtri suggests the matching supplier and company so the reviewer starts from a populated packet instead of a blank form.

Duplicate detection

Auxtri checks the extracted invoice against existing Workday invoice records through the Workday REST API and flags likely duplicates before they reach your team.

What stays in Workday

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

The Approval Layer

Vendor Master Manager on Workday

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 Workday tenant, each workflow is shaped to how Workday Financial Management actually validates a supplier change. 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. After the write, Auxtri checks the Supplier Bank Account Review Status before any subsequent payment-related read.

W-9 collection and tax ID updates

Auxtri auto-requests a fresh W-9 and runs an IRS TIN match before any write. Workday stores a W-9 Date field on the supplier record, and Auxtri updates it natively in the same write so your Workday record is the record of truth.

COI tracking

Workday stores a Certificate of Insurance Date field, and Auxtri updates it natively. It 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 current terms from Workday surfaced for comparison. Workday stores terms at the supplier header, so one approved change writes once and applies to all future invoices.

BPF bypass option per tenant

Workday's Business Process Framework can route bank changes for internal approval. Tenants that want Auxtri to be the single approval layer can configure a BPF bypass; tenants that want both can run them in series. The choice is documented in your tenant configuration.

Remittance advice requests

The most automatable module. Auxtri queries Workday 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.

Implementation: Four to Six Weeks, Low Disruption

Auxtri connects to your existing Workday environment without modifying your business processes or security configuration. The integration is pre-built on the Workday REST API.

Scoped permissions

Read access for invoice and payment data through your integration security group. Writes only on the Vendor Master Manager workflows you enable, behind dual approval.

No Workday rebuild

Your Workday configuration, Business Process Framework, and security groups stay as they are. Auxtri sits next to your existing setup and only writes through workflows you turn on.

Pre-built REST API integration

Our implementation team works with your Workday administrators to configure REST API access, integration security, BPF behavior 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 Workday Data

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