Give every bank change a traceable approval path
A supplier bank detail change should remain pending until the company verifies it through a trusted channel, approves it separately from the request, and confirms which account the next payment run will select. In an SAP Ariba supplier management workflow, the request, verification evidence, change approval, ERP update, and payment result may sit in different places. Design the process to make those boundaries visible and assign ownership for handoffs.
SAP’s late-2026 Ariba Supplier Management and Risk release notes offer a timely reason to review supplier workflows [1]. Supplier registration and update capabilities vary by configuration and release. The operating question applies across designs. A successful portal submission or an approved request is useful evidence for its own stage. Finance still needs to know whether the trusted verification happened and whether the downstream payment record changed as intended.
The FBI’s guidance on business email compromise describes attempts to impersonate trusted business contacts and redirect payments [2]. A strong process helps teams verify genuine requests as well as identify suspicious ones. It also gives suppliers a predictable route for submitting changes. Build the workflow around ordinary operating realities such as month-end volume, mergers, and the occasional urgent request.
Decide which events should open a bank verification case
Map how a supplier asks to change payment details today. Requests may come through a portal, a procurement contact, a shared mailbox, or an employee who received an update while working on an order. Set a preferred route and document the exceptions. Give procurement a consistent response for requests received elsewhere. The request should enter a governed workflow with a reference before anyone edits the payment record.
Determine what qualifies as a material change. A new bank account or beneficiary can affect payment directly. A supplier name change or a merger can make verification more complex even when some identifiers remain the same. Confirm which company codes, payment methods, and organizational areas would be affected. A change may apply to one remittance arrangement without replacing every existing account.
Assign someone to check whether payments are already scheduled. The business can then decide which items require a review or temporary hold according to its policies. Give procurement and accounts payable a shared view of the request’s status so neither group must infer next steps from a message chain. The process should tell users what must happen before a request becomes eligible for the next payment cycle.
Establish independent verification and a clear evidence standard
Independent verification should use a trusted contact or channel already established by the company. A phone number, link, or contact name supplied with the change can be part of the submitted information. Resolve the authoritative source according to company procedure. If verification is inconclusive, route the request to the person empowered to investigate rather than making the pending status look like approval.
The evidence should show who verified the request, which established method they used, when it took place, and what was confirmed. Restrict sensitive details to the roles that need them. A support administrator may need to see that approval is pending. They may have no reason to see the full account number. Agree on record retention and where underlying documents can be inspected under appropriate access controls.
Separate the person requesting or entering the change from the person approving it according to the organization’s control design. If a small team needs a backup approver, designate the authority before the next payment window. NIST’s security and privacy controls catalog offers general reference points for access control and audit evidence [3]. Adapt the design to the actual financial controls and responsibilities in the organization.
Follow the request from Ariba to the payment system
Give applications a common supplier reference and a linked change record. One team should be able to see that a request was received and independently verified. Another should be able to see whether the corresponding update was accepted by the system that maintains payable records. In a hybrid architecture you may have several receiving systems, and a successful update in one does not establish success in another.
Walk an illustrative case through the process. A supplier finishes an acquisition and requests a new account for one business unit. Procurement opens the case. A separate reviewer verifies the request. The change is approved for the relevant entity. The ERP accepts one organizational update while another is pending review because its supplier record has a different owner. The operating team should be able to tell exactly which invoices and payments fall into each situation.
Use acknowledgments and business reconciliation intelligently. Determine whether the interface message reached its destination, which fields changed, and whether the payment proposal reflects the allowed effective date. If a delivery fails, preserve the case and use approved checks before retrying. A repeated message may be harmless in a well-controlled design, but the team should prove that its own process can tell the difference between repeat delivery and a new approved update.
Exercise the controls before the next urgent request arrives
Start with a straightforward case. Run a normal change through initiation, verification, approval, downstream update, and a nonproduction payment proposal. Ask the reviewer to retrieve evidence using the tools and access they typically have. Then run a change submitted just before a payment cutoff and ask what happens when verification is incomplete. The response should name the person who can decide whether to hold or defer payment and how to tell the supplier.
Test a correction after approval. Suppose a verified bank change for one entity is accidentally routed to two company codes. Confirm that the unexpected update is detected and that the team knows who can authorize a correction. Record the existing payment position before taking action. If a payment already moved, follow the organization’s incident and banking procedures. NIST’s incident response guidance discusses preparation, response, and recovery as related phases [4].
Bring AP, procurement, treasury, and internal controls into the exercise. Establish what each group needs to see. Separate evidence that a request passed verification from evidence that a payment was released. A good drill gives a controller a coherent record without expecting them to search multiple unrelated tickets.
Track signals that protect suppliers and reduce rework
Measure how long requests wait for verification and how often submitted data must be corrected. Add a view of aging requests that could affect a scheduled run. Ask whether requests stall because suppliers have unclear instructions, trusted contacts are out of date, or organization-specific rules are difficult to find. Give the operational team a way to identify recurring sources of delay.
Keep review evidence that can be linked to downstream changes. A sample may show requests approved without a confirmation from a receiving system, or payments waiting on a case no one owns. Record those patterns and act on the highest-impact gap. Keep privacy in view when designing reports and queue access. NIST’s Privacy Framework can help teams identify overcollection and access risks [5].
The supplier experience matters too. Clear status information reduces repeated submissions and requests to bypass the normal process. Give suppliers a way to know that the change is received, pending confirmation, or applied to a defined scope. Communicate through established channels and provide a contact for questions without exposing verification details.
Put the first payment scenario in the design session
Bring procurement, AP, treasury, and integration owners together around one supplier case. List how the request arrives, who verifies it, who approves it, which record is updated, and what the payment team can check. Give a person responsibility for an unresolved case and set a point when treasury or controls should be notified. Identify one improvement you can make in the next release.
Use the result to define GBSI’s SAP GRC services requirements around approval and evidence and SAP integration design requirements around status and reconciliation. A stronger workflow makes it easier for suppliers to submit valid changes and easier for finance to know which changes have been verified.
Decide how temporary holds end
A payment hold can protect an item while verification is incomplete. It can also create a late payment if the team forgets to remove it after the decision. Define which roles may place or release the hold, where the reason appears, and who checks that the intended invoices are available for the next run. Give the supplier a reliable way to learn that the case is still pending.
Review a sample of holds after the first operating cycle. Compare the time spent waiting for verification with the time spent moving the result across systems. If the verified decision reaches AP too late, the problem may be queue visibility or unclear handoff ownership. Document which change the team will test and how it will verify the result.
Frequently asked questions
Does submitting bank details through a supplier portal complete verification?
Treat submission as a distinct stage. Verify the organization’s procedures for establishing the identity and authority behind a change. Maintain that evidence with the case before a downstream payment record is updated.
Who should own a supplier bank change case?
Give the request one operational owner and define the other roles explicitly. Procurement, AP, treasury, and integration teams may own different steps. Give the case owner visibility into those steps without automatically granting authority to perform every action.
What should be tested before a new workflow goes live?
Test a normal change, a late change, a changed scope, and a failed downstream update. Verify the approval record and the expected result for a payment proposal or another approved test artifact. Include an exercise with someone responsible for the next shift or payment cycle.
References
1. SAP Community · SAP Ariba Supplier Management and Risk 2611 highlights
2. FBI · Business Email Compromise
3. NIST · Security and Privacy Controls for Information Systems
4. NIST · Incident Response Recommendations



