Would You Spot the Fake Vendor Payment Email?

Could you spot a vendor email redirecting your payment? Test your judgment with two fictional examples and learn how to verify bank changes before money leaves your account.

The most consequential detail in a vendor email may not be a spelling mistake, a suspicious attachment, or an unfamiliar sender. It may be a routine-looking instruction about where to send the money.

For accounts payable teams, the challenge is separating a plausible request from an authorized one. A familiar company name and a matching invoice reference can make a message feel trustworthy. Neither establishes who is directing the payment.

The following exercise tests that distinction. Both messages are fictional training examples, not actual correspondence. Read them as if they arrived during a busy workday, with other invoices waiting for approval.

The Challenge: Which Message Requires a Callback?

Imagine your company already purchases supplies from the fictional Harbor Supply. An invoice is awaiting processing, and you receive one of these messages.

Fictional Message A: Scheduled Payment

Subject: Invoice HS-1048 — scheduled payment

Hello Accounts Payable,

Please process invoice HS-1048 through your usual approval workflow. Our payment instructions remain unchanged. If your records do not match the invoice, please hold payment and contact your established account representative.

Thank you,
Harbor Supply Billing

Fictional Message B: Updated Payment Instructions

Subject: Invoice HS-1048 — updated payment instructions

Hello Accounts Payable,

We have moved our receivables to a new bank. Please replace the account details on file with those in the attached instructions and send payment today to avoid a shipping hold. Our regular billing line is unavailable; use the new number in my signature if you need confirmation.

Thank you,
Harbor Supply Billing

Which message requires a callback before you change anything or release payment—and which number should you use?

Pause and make your choice before reading the answer.

The Answer: B Requires Independent Verification

Hold both the banking change and the payment. Call an established vendor contact using a previously verified number—not the number supplied in Message B.

The decisive issue is the request to redirect funds. The FBI’s guidance on business email compromise recommends verifying changes to account numbers or payment procedures. The FTC’s phishing guidance advises using a phone number you know is correct, rather than one provided in the message.

This does not prove that Message B is fraudulent. Legitimate vendors change banks. It establishes that the request needs independent verification before action.

Message A contains no explicit payment-change trigger, but it is not automatically genuine or approved. Continue your normal invoice matching, authorization, and payment-verification procedures. The FBI also recommends independently verifying payment and purchase requests.

A callback is not a verdict on whether an email is fake. It is a control over where your money goes.

The Clues That Matter More Than Appearance

A New Destination for the Money

Message B asks the recipient to replace banking details already on file. That is the critical trigger, even without the shipping threat or the unavailable billing line.

A useful operating rule is simple: any request to change payment instructions requires verification outside the requesting message. Apply that rule consistently, including when the request appears to come from a long-standing vendor.

Pressure to Skip the Pause

“Send payment today” links immediate action to avoiding a shipping hold. That creates a conflict between keeping operations moving and following the approval process.

The FBI identifies pressure to act quickly as a warning sign. Urgency may justify prompt attention, but it should not justify bypassing verification. Escalate a time-sensitive request internally while keeping the payment on hold.

An Attempt to Choose the Verification Channel

Message B does more than provide new banking information. It also tells the recipient how to confirm it: ignore the regular line and use a new number.

Calling that number would keep the entire exchange inside a channel supplied by the unverified sender. Even a convincing conversation would not independently establish the request’s legitimacy.

Retrieve the number from your approved vendor record or another previously verified source established before this request. Do not copy it from the new email, its signature, or its attachment.

Familiar Details That Can Create False Confidence

A recognizable signature, an existing email thread, and a plausible bank document can all make a request easier to accept. They are not substitutes for verification.

The Department of Commerce Office of Inspector General’s fraud alert warns that criminals can hijack payment conversations and provide convincing supporting documents. The practical lesson: assess the requested action, not just the message’s presentation.

A Simple Callback Script Using a Known Number

First, open the approved vendor record and retrieve the previously verified contact number. Call your established contact rather than anyone identified only in the new message.

The following is suggested training language, not a quotation from an actual conversation:

“Hi, this is [name] from [company]. We received a request to change payment instructions for invoice HS-1048. I’m calling the number we already have on file. Did your team request this change? Please confirm the approved payment instructions through our established verification process. We’ll hold payment until verification and our required approvals are complete.”

The script identifies the request, establishes why you are calling, and makes clear that payment depends on completed verification—not merely a reassuring response.

If the contact confirms that a change is legitimate, complete your approved banking-change process. If the contact denies it, preserve the message and notify your finance lead and security team. If you cannot reach the contact, keep the change and payment on hold and escalate internally.

Turn the Callback Into a Repeatable Control

A callback should be part of a defined workflow, not an improvised favor performed only when someone feels suspicious.

Separate Confirmation From Approval

Confirmation answers whether the vendor requested the change. Internal approval determines whether your organization has met its requirements for implementing it. Both matter.

The Commerce inspector general recommends dual approval and separation of duties for payment setup and banking changes. A practical implementation is to have one authorized employee collect and document the verification, then have another review the change before it takes effect.

Document What Was Verified

Record the contact’s name, the previously verified number used, when the conversation occurred, and the outcome. Document the required internal approval as well. A note saying “vendor confirmed” leaves important questions unanswered.

Apply the Rule Even When the Request Looks Ordinary

Consider a fictional variation: Harbor Supply requests a bank change without urgency, uses polished language, and invites questions. The independent-verification requirement remains the same. Removing obvious warning signs does not remove the risk of redirecting a payment.

Similarly, a shipping deadline should not create an exception. A consistent process protects employees from having to decide, under pressure, whether a convincing email deserves special treatment.

A Vendor Payment Verification Checklist

Before implementing new payment instructions, confirm that your team has completed these steps:

  • Pause: Hold the requested banking change and affected payment.
  • Identify the change: Determine exactly what payment information or procedure would be different.
  • Use a trusted number: Retrieve contact information verified before the request arrived.
  • Call independently: Speak with an established vendor contact rather than relying on the requesting email thread.
  • Complete verification: Confirm the request and approved instructions through your established process.
  • Require review: Obtain the necessary second-person authorization before implementing the change.
  • Keep a record: Document the verification and approvals before releasing funds.

Make Verification the Default, Not a Judgment Call

The goal is not to turn every accounts payable employee into an email-forensics specialist. It is to give the team a reliable response when a message asks the business to send money somewhere different.

Message B requires a callback because it changes the payment destination. Message A still requires normal controls because ordinary-looking correspondence is not proof of authorization.

Use this exercise with your finance team. Ask employees where they would find a trusted vendor number, who can approve banking changes, and what happens when the contact cannot be reached. Resolve those questions before the next urgent request arrives.

A convincing email should never be enough to redirect a payment.

Browse all insights · Contact Bart McDonough