Update a supplier record in Coupa from an approved change
Automatically update a Coupa supplier record from an approved change in Slack with Stepwork. Apply new banking, contacts, or payment terms and log the reason.
- Use case
- Vendor & renewal managementProcurement
- Best for
- Procurement Analyst, AP Specialist
- Applications used
Coupa
Slack
- Business outcome
- Data quality
The problem
The supplier changed banks. Coupa still has the old one.
Suppliers send new banking details, a new remittance contact, or revised payment terms. The change gets approved, then waits in a queue behind whoever owns Coupa admin.
Until it lands, payments go to old details and invoices reach the wrong person. When it finally does, the record rarely says why it changed or who approved it.
The outcome
The supplier master stays current, with the reason on file
Stepwork applies the approved change to the supplier record in Coupa and documents the change reason. The run records who asked, which approval it came from, and the old and new values.
- The request names the supplier and the approved change.
- A supplier that does not match the request stops the run.
- The Slack reply shows the old and new values.
The process
From approved change to an updated supplier
Procurement posts the approved supplier change in Slack. Stepwork applies it in Coupa, in the same order every time.
- Step 1
Request it in Slack
A teammate posts the supplier, the approved change, and the approval reference in the procurement channel. That message starts the flow, and Stepwork records who asked and when.
- Step 2
Open the supplier
Stepwork signs in to Coupa and opens the supplier record. If there is no match, or more than one, the run stops instead of guessing.
- Step 3
Apply the change
Stepwork updates the banking, contact, or payment term fields named in the request and documents the change reason on the record.
- Step 4
Confirm and reply in Slack
Stepwork checks the saved record against the request, then posts the old and new values back in Slack.
Why Stepwork
Supplier changes stop waiting on one admin
Stepwork runs the supplier update path you recorded in Coupa. It applies the change your team approved, writes the reason, and never approves a change on its own. Credentials stay in 1Password.
Similar use cases
Similar use cases
- Create a requisition in Coupa from an approved requestCreates the requisition in Coupa with supplier, line items, cost center, and justification from the approved intake.
Create a vendor record in NetSuite from approved onboardingCreates the vendor in NetSuite with legal name, payment terms, banking details, and tax classification from the approved onboarding packet.
Update request approvers in Zip after a re-orgUpdates approval chain assignments in Zip to match the new org structure after a re-org or role change.
FAQ