Vendor Master Manager is one of three Auxtri products on a single AP inbox intake layer. When a vendor onboarding packet, bank change notice, tax ID update, payment term request, remittance request, or compliance document arrives in your AP mailbox, Auxtri assembles the verified packet and lets your team take the right action in a single approval click, with the full audit trail attached to the original email.
Six modules, independently toggled per organization. Each workflow is molded to the ERP that owns it (Workday Financial Management, Infor CloudSuite FSM, or Oracle Fusion Cloud Financials), so the approval packet, the field map, and the write payload match how that ERP actually validates a vendor master change.
No AP team prioritizes vendor master cleanup as a primary initiative. It is a known mess that gets accepted as a risk because the hospital keeps running and the urgent fires keep burning. The bank change requests, the new vendor packets, the expired COIs, and the EIN updates pile up in the background while the team handles the inquiry queue and the month-end statement pile.
Your AP team verifies a bank change request by reading the email, eyeballing the sender domain, and then making the call. A new vendor onboarding packet sits in the inbox for two weeks while someone chases a W-9 and a COI. A tax ID change comes in and the team has to remember whether IRS TIN matching has been run for this vendor in the last twelve months. The work is real, the stakes are real, and none of it is in your ERP.
Workday, Infor CloudSuite FSM, and Oracle Fusion each have their own change controls for vendor records, but those controls only fire when someone initiates the change inside the ERP. Vendors who email AP directly never touch any of it. Vendor Master Manager closes that gap and gets the cleanup work done at the same time as the urgent fires, with each workflow shaped to the ERP that actually validates the write.
Five steps, every one of them logged. Your approver opens a complete packet, not a half-finished email thread.
A vendor emails your AP mailbox with an onboarding request, bank change notice, tax ID update, payment term proposal, or compliance document.
Auxtri identifies the change type, checks the sender against the vendor's known domains, runs a domain mismatch and lookalike check, and assigns the right approver and approval policy for the module (single approver, dual approver, or out-of-band confirmation required).
Auxtri requests anything missing from the vendor (W-9, certificate of insurance, banking form) using your templated emails, tracks responses, and assembles a complete change request without manual chasing.
The completed request lands in the approver queue with the full context surfaced: prior values, proposed values, supporting documents, domain check result, and out-of-band call log. Every state change is audit-logged.
On final approval, Auxtri writes the change to your ERP through the vendor master adapter for Workday, Infor CloudSuite FSM, or Oracle Fusion. The audit log records exactly what hit the ERP and any payment hold that was applied.
Enable the modules your team is ready to automate. Leave the rest in your existing process. Every module is configured per tenant from the Workflows tab in your ERP Config admin page.
Auxtri collects the W-9, banking form, certificate of insurance, and any other documents you require, chases the vendor on a configurable cadence, deduplicates against existing records, and presents a complete packet to the AP supervisor for approval. On approval, the new supplier is created in your ERP through the native adapter.
Bank account and payment detail change requests carry the highest fraud risk in the inbox. Auxtri runs a sender domain mismatch check against the vendor's known domains, requires dual approval, requires an out-of-band confirmation call to be logged before the change can complete, and applies a one-cycle payment hold by default after the write. The write goes to Workday Supplier Bank Account, Oracle Supplier Bank Accounts, or Infor vendor bank fields with the change recorded in audit log.
Auxtri classifies the request as name-only, EIN-only, or combined, auto-requests a fresh W-9, flags IRS TIN match before any ERP write, and routes EIN changes through dual approval with tax department notification. On Workday, the W-9 Date field is updated in the same write. On Oracle, the duplicate taxpayer ID check runs before submission to avoid a rejected write.
The most automatable of the six modules. Auxtri extracts the requested invoice numbers, queries your ERP for payment date, amount, and check or ACH reference, and generates the remittance response. Above the configurable confidence threshold it can auto-send with a copy to your team; below the threshold it lands in the review queue. No ERP writes are required for this module.
Payment term change requests route to the configured approver (procurement or AP leadership) with the current terms from your ERP surfaced for comparison and the proposed terms extracted from the email body. On Oracle, payment terms are written at the supplier site level; on Workday and Infor, terms are written at the supplier header level.
Auxtri tracks the document types you care about per vendor (W-9, COI, diversity certifications), extracts the expiration date from each incoming document, and runs proactive outreach on a 90 / 60 / 30 day cadence. Expired documents can trigger a payment hold automatically. For Workday, the W-9 Date and COI Date fields are updated natively. For Infor, Auxtri remains the record of truth for compliance dates because Infor has no native fields. For Oracle, dates land in descriptive flexfields when configured, otherwise Auxtri is the record of truth.
The controls healthcare AP needs to trust a workflow that writes to the ERP.
Configurable per module. Bank changes and EIN updates require two approvers by default. Single-approver modules can be elevated to dual approval per tenant.
For bank changes and any other module you configure, an out-of-band call log is required before the change can complete. The call note becomes part of the approval audit record.
Inbound change requests are scored against the vendor's known email domains. Lookalikes and free-email senders surface as a flag on the approval, not as a silent pass-through.
Every ERP write records the exact structured payload sent, the response from the ERP, the approver IDs, the out-of-band confirmation reference, and any payment hold applied. Built for compliance review, not retrofit for it.
The same approval workflow targets Workday, Infor CloudSuite FSM, or Oracle Fusion through a single capability interface. ERP-specific nuances (Workday Review Status, Oracle site-level terms, Infor missing COI field) are handled in the adapter, not in the workflow code.
Bank changes apply a configurable payment hold by default. Compliance document expirations can trigger a payment hold per document type. Holds are released by the same approval workflow that applied them.
The other Auxtri workflows that share data and approvals with Vendor Master Manager.
The peer product on the same intake layer. Vendor Inquiry Automation reads the inbox, classifies each request, and drafts the response. Where it drafts a reply, Vendor Master Manager assembles a verified change packet and writes it to your ERP after approval.
Read more→When vendors send statements listing dozens of invoices, Auxtri extracts every line item, matches them against your ERP, and summarizes paid, pending, and missing invoices in minutes.
Read more→Bring a sample bank change request, a vendor onboarding email, or an expired COI to a live demo. We will walk through the approval packet and the ERP write end to end.