Operations · Process breakdown
Automate the paperwork around supplier changes, and keep approval of bank details, addresses and prices a deliberate human step.
Vendor master data management sounds like housekeeping: a supplier moves, changes a bank account or sends a new price list, and someone updates the record. But vendor master data management is also the door that invoice fraud walks through, and a wrong price list quietly changes every order after it. So the process splits. Receiving requests, preparing the change and logging it are rule work. Reading the attachments is a fair job for AI. Verifying who asked and approving the change stay with people. The first thing to fix is the intake: no changes from a reply-all email.
Suppliers submit changes through a portal or form with fixed fields and required attachments. Emails asking for changes are answered with a link to that channel, which stops informal requests from becoming data entry.
AI extracts the new values from the attachments, such as a bank letter or a price list, and presents a side-by-side of the current record and the proposed change with the source highlighted.
A person confirms the change through a channel you already trust, such as a call to a known contact number on file, never the number in the request. This is the step that catches impersonation.
Someone other than the person who prepared the change approves it, with the evidence in view. High-impact changes, such as bank accounts or contract prices, can require a second approver.
The approved values are written to the ERP with the effective date, the approver and the evidence attached. Downstream systems receive the update from the master record, not from a copy.
A new price list or payment term is a negotiation, not a data update. Procurement reviews the proposal against the contract and decides whether to accept, push back or escalate.
Route only bank-detail and address changes through the new flow for one month. Count requests that arrive with incomplete evidence, the time from request to approval, and any change stopped by the call-back. Add price lists once the verification habit holds.
Treating an emailed “we changed our bank account” as a data-entry task. That is the classic route for invoice fraud, and speed makes it worse.
AI can flag signals: a bank account in a different country than before, a request from a new email domain, urgency in the wording, or a letterhead that does not match earlier documents. Those flags are useful, but the control that actually stops fraud is a person calling a known contact. Use AI to prioritise verification, not to replace it.
Someone who did not request or prepare the change and who can see the evidence. For low-risk fields, one approver in procurement or finance is enough. For bank details, tax numbers and contract prices, many companies require two approvers and a documented call-back. Write the rule down and let the system enforce it rather than relying on habit.
Vendor management covers selecting, contracting, evaluating and offboarding suppliers. Master data changes are the operational core underneath it: if the record is wrong, evaluations, payments and compliance checks are wrong too. Getting the change process right is usually the cheapest improvement in the whole vendor management chain.
Illustrative workflow guidance by Arcgent. Each business needs its own assessment. No integration or savings claim has been verified for your systems.
Get an assessment based on your own steps, systems, and constraints.
Audit my process See an example report ↗