Practical perspectives
Supplier Bank Change: An Approval Checklist Before Payment
A practical control record for a supplier bank-detail change, from requester identity to payment-system release.
An approved supplier can ask to change its bank details at any time. The change should start a fresh verification and approval record, especially when an invoice is about to be paid. This checklist uses invented details and should be adapted to the buyer’s treasury and AP policy.
The supplier bank-detail change software guide explains how to evaluate supporting tools. This article shows the operational handoff those tools must preserve.
1. Record the change without replacing the old instruction
Keep the legal supplier entity, current payment instruction reference, proposed change, request channel, named requester and time. Do not copy full bank details into general-purpose notes or email. Flag invoices in flight and prevent an unapproved new account from becoming the payment default.
| Field | Record | Reviewer question |
|---|---|---|
| Supplier identity | Existing legal entity and ERP ID. | Is this the entity on the contract and invoice? |
| Requester | Named person and independently verified role. | May this person change payment details? |
| Change | Masked new account reference and effective date. | Was the prior instruction preserved? |
| Open payment | Invoice in AP queue. | Is a hold required until verification? |
2. Test identity and account ownership separately
A reply from the same email thread is weak independent evidence. Use a trusted contact path and account-ownership check appropriate to the country and payment rail. A routing-number or IBAN format check can catch malformed data, but does not by itself establish that the supplier owns the account.
- Contact: verify the requester through an existing trusted supplier record or approved callback process.
- Entity: compare the account holder with the contracted legal entity or authorized payee.
- Result: retain the verification method, outcome, source date and unresolved discrepancy.
- Escalation: hold an inconclusive or mismatched request for a separate reviewer.
3. Separate approval from entry and reconcile systems
The person who enters the new detail should not alone approve it. Record the approver, policy basis, accepted verification and effective date. Apply the authorized change to the system of record, verify the downstream AP or ERP acknowledgment and inspect the next payment before closing the case.
Graphite Connect describes verified supplier users and change tracking ↗; Certa describes live banking checks during onboarding ↗. In a demo, test whether those controls apply to a later change and what remains in the buyer’s own approval workflow.
4. Close only after the payment instruction is consistent
| Check | Proof to retain |
|---|---|
| Independent verification complete | Outcome and reviewer, including any exception. |
| Approval complete | Authorized decision with timestamp. |
| ERP and AP agree | Acknowledged masked account reference and effective date. |
| Open invoices handled | Hold released, canceled or retained with reason. |
If an approved change later proves wrong, the record must show the previous instruction and the route to stop further payment. Closing a workflow task before the payment system reflects the approved value creates a false sense of control.