Vendor management

Handle a bank detail change request without a fraud loss

A verification process for vendor bank-detail changes that uses a known contact, a callback, and a second approval.

Handle a bank detail change request without a fraud loss workflow illustration

Handle a bank detail change request without a fraud loss

How to approach: Handle a bank detail change request without a fraud loss

A bank detail change is a high-risk request, even when the email looks ordinary. Verify the request through a known contact and a callback to a number on file. Do not use the number in the request. Record the date and the source so the next reviewer can repeat the check.

Keep the verification evidence with the vendor record. A change that cannot be explained later is a liability. The process should be the same for every vendor, not only the large ones. Keep the original note beside the corrected version.

Verify the requester

Confirm the name, the role, and the authority of the person requesting the change. Compare the request with the vendor master and the contract. A new contact with no history should be treated as a question. Ask whether a new reviewer could act on the record without a conversation.

Use a known channel to reach the vendor. A reply to the same email thread is not verification. The attacker may control the mailbox. A control that depends on memory is not yet a control.

Call back to a known number

Call the vendor at the number already on file, not the number in the request. Ask the contact to confirm the change independently. Record the name, the number, and the time. Use the same format for every handover so the next reader can scan it.

If the vendor cannot be reached, hold the change. A delayed payment is better than a fraudulent one. The hold should be recorded and reviewed. Review the first few notes together before the process expands.

Require a second approval

Require a second approver who did not receive the request. The approver should see the verification evidence. A single person should not be able to change the bank details and release the payment. Name the owner in the same line as the action.

Record the approval and the date. A change without a second approval should be reversed or held. The audit trail is the evidence that the control worked. Use the same format for every handover so the next reader can scan it.

Update the record and notify

Update the vendor master only after the verification and the approval. Record the old and new details. Send a confirmation to the vendor through the known channel. Record the exception and the person who approved it.

Notify the payment team before the next run. A change that is not communicated may be missed or applied to the wrong payment. The notification should name the effective date. Keep the evidence with the record rather than in a separate log.

Review the attempt for patterns

Record every bank-detail change request, including the ones that were rejected. Look for a pattern in the sender, the timing, or the language. Share the pattern with the security owner. Update the template when the same question appears twice.

Train the team on the process at least annually. A process that is not practiced will be skipped under pressure. The goal is a change that is verified, not a change that is fast. Write the deadline as a date and a local time.

This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.