A familiar vendor asks you to change its bank details. What next?
Do not update the payment record from the email alone. Verify the request through a separate, trusted channel before changing where the money goes. The FBI specifically recommends verifying changes to account numbers or payment procedures and independently obtaining the phone number used for verification. (fbi.gov)
For a small business, the goal is a repeatable procedure—not asking the bookkeeper to decide whether an email feels suspicious. Use the workflow below as a starting point, then agree on responsibilities with your owner, finance lead, and payment provider.
The governing rule should be simple: a request to change payment details starts a review; it does not authorize the change.
Why checking the sender is not enough
Business email compromise can involve a lookalike address or a legitimate account that an attacker has taken over. Criminals can use information from business correspondence to make fraudulent payment instructions convincing. A familiar name and an accurate invoice therefore do not establish that new banking instructions are authorized. (fbi.gov)
Watch for urgency, changed contact details, and instructions to avoid telephone verification. However, make verification mandatory for every banking change—not just requests containing obvious mistakes. The FBI recommends verifying payment changes through a known telephone number and including contact-information changes in verification policies. (ic3.gov)
Build a five-step bank-change procedure
The following is a suggested small-team implementation of independent verification and approval controls. Adapt the administrative details to your accounting system rather than treating this as a prescribed compliance standard.
1. Pause the change and assign an owner
Create a review task before editing the vendor record. Identify the affected supplier, the requested change, and any payment approaching its due date.
Give the task one named owner. Their job is to coordinate verification, not necessarily to approve or release payment. Use a clear status such as “Banking change awaiting verification.”
Do not let an approaching deadline replace the review. North Carolina’s Department of Justice advises businesses to check invoices before paying and resist pressure to pay before verification. (ncdoj.gov)
If a payment is due, ask your finance lead to resolve timing with the supplier through an established contact. Do not assume either the old or new account is appropriate until the situation is understood.
2. Retrieve contact information independently
Use a trusted contact number already held in your vendor records, rather than the number supplied with the change request. J.P. Morgan’s guidance calls for callbacks using a number retrieved from a system of record, including when contact information itself changes. (jpmorgan.com)
For your internal procedure, record where that number came from. “Existing vendor record verified during onboarding” is more useful than “called supplier.”
If the existing contact is unavailable, mark the task unresolved and escalate it. Do not substitute an unverified number simply to finish the checklist. For a new supplier without an established contact, use a separate onboarding review rather than pretending a trusted relationship already exists.
3. Confirm authority, intent, and the actual details
During the independently initiated call, establish that the person is authorized to request the change, that the supplier initiated it, and that the requested banking information is correct. These are explicit elements of North Carolina’s Office of the State Controller guidance. It also advises against leading questions that disclose the answer you want confirmed. (ncosc.gov)
A suggested opening is: “We received a request to change your payment instructions. Before we act, please explain the change your organization requested and who authorized it.”
Then follow your approved secure process for comparing the actual payment details. A general acknowledgment that the business has changed banks is not the same as confirming the destination account. J.P. Morgan recommends confirming all account details during the callback. (jpmorgan.com)
If anything remains inconsistent, leave the request unresolved. Do not turn a partial answer into an approval.
4. Separate the update from approval
Use a second authorized person to review the completed verification before the changed destination is used. Separation of duties and dual controls are among the operational safeguards identified in NCUA guidance on wire-transfer fraud. (ncua.gov)
A practical two-person arrangement is for the bookkeeper to prepare the change and the owner or finance lead to approve it. Ask your accounting and banking providers which permissions can enforce that arrangement.
If you work alone, do not describe a second look by the same person as independent approval. Ask your accountant and bank about controls suited to your situation.
5. Keep a concise decision record
Use a restricted review log containing:
- Supplier identifier and date of the request.
- Employee responsible for the review.
- Source of the trusted callback number.
- Verification date and the supplier representative’s role.
- Result: approved, rejected, or unresolved.
- Approver and approval date.
- Reference to the controlled accounting record.
This is a suggested record layout, not an official form. Avoid duplicating full banking details in general-purpose task boards. Keep the review record focused on who checked what and where the approved information is maintained.
DIY checklist for your next payment run
Use this checklist to apply the verification, limited-authority, and dual-control principles above. North Carolina DOJ recommends limiting who can place orders and pay invoices; federal guidance supports independent verification and separation of duties. (ncdoj.gov)
- Identify every supplier with a pending banking change.
- Confirm that none has been approved solely by replying to an email.
- Check that callback numbers came from independently trusted records.
- Confirm both the supplier’s authority and the destination details.
- Review any simultaneous changes to telephone or contact information.
- Obtain the required second-person approval.
- Keep unresolved requests out of the changed-destination payment run.
- Assign a backup approver for absences.
- Record the decision where authorized staff can find it.
Choose a named person to own the checklist. Avoid making “everyone should check” the operating procedure.
A North Carolina reference for Triangle businesses
Owners in Raleigh, Durham, Cary, and Chapel Hill have a useful state-level reference: the North Carolina Office of the State Controller publishes supplier payment and banking-change guidance. It says verification should not depend solely on an email, written request, or supporting documents. It also warns against using recently changed contact information that has not been independently verified. (ncosc.gov)
That guidance addresses the state’s supplier-payment process; this article does not present it as a blanket requirement for private businesses. For a Triangle company writing its own procedure, it is a relevant regional example of separating a payment-change request from its verification.
Make email security support the process
Ask your IT administrator to review multifactor authentication, unexpected external forwarding, suspicious sign-ins, and mailbox rules that hide or delete messages. Federal guidance identifies these as relevant defenses or investigation areas for business email compromise. (ic3.gov)
Keep the financial approval step even when technical protections are in place. The FBI recommends both account protections and independent verification of payment changes. (fbi.gov)
If you automate invoice intake, make the design requirement explicit: extracted bank details should create a review task, not silently overwrite approved payment instructions. Treat that as a workflow requirement to test before enabling the automation.
When professional help is sensible
Start with your own written procedure and a dry run. Bring in your accountant or finance adviser when responsibilities, payment authority, or exceptions are unclear. Involve your bank when you need to understand available approval controls or investigate a transaction.
Technical help is sensible when you cannot determine who can edit supplier records, when automated workflows bypass approval, or when an email account may be compromised. EverpineLab’s cybersecurity and automation services are relevant to reviewing the technical side of that process; finance leadership should retain responsibility for approving payment policy.
If money has already been sent
Contact the sending bank immediately and explain that you suspect business email compromise. Ask about a recall or reversal and the documentation it needs. File a detailed complaint with the FBI’s Internet Crime Complaint Center. These are the immediate steps recommended by the U.S. Department of Justice. (justice.gov)
Engage your IT or security support promptly to investigate possible account compromise. Do not wait for that investigation before contacting the bank. J.P. Morgan’s response guidance calls for immediate bank notification alongside reporting and technical investigation; recovery should not be assumed. (jpmorgan.com)
Test the procedure before a real request arrives
Run a tabletop exercise using a fictional supplier. Ask one employee to submit a banking-change request and another to walk through verification without modifying live records or sending money.
Can they locate a trusted number, identify the approver, handle an absence, and document an unresolved result? Fix any gaps you find. The finished procedure should tell a busy employee exactly what to do next—not merely remind them to be careful.
Sources and further reading
- FBI: Business Email Compromise
- NC Office of the State Controller: Best Practices for Supplier Payment and Banking Information Setup & Changes (Agency Perspective)
- North Carolina Department of Justice: Tips for Small Businesses
- FBI: Business Email Compromise Actors Targeting State, Local, Tribal, and Territorial Governments, Straining Resources
- J.P. Morgan: Defending Against Business Email Compromise
- NCUA: Business Email Compromise through Exploitation of Cloud-Based Email Services
- U.S. Department of Justice: United States Recovers $2.4 Million Obtained In Business Email Compromise
Ready to improve the next bottleneck?
We will help you identify the most practical next step for your business—without turning it into a giant technology project.