Paid an Invoice After Bank Details Changed? What to Do Next
A practical incident guide for U.S. business owners facing a suspected diverted vendor payment.
Estimated reading time: 8 minutes
Suspected invoice payment fraud needs an immediate bank call before a complete internal investigation. Preserve the payment record while requesting the available recovery steps.
Invoice payment fraud: contact your bank now
If you suspect your vendor payment went to a fraudster, contact the bank that sent it immediately. Request a recall or reversal. Ask what documents its process requires. Recovery isn’t guaranteed. Start this call without waiting for the vendor or finishing a report.
This guide is for U.S. businesses facing suspected diversion of a vendor payment, primarily a wire transfer. It doesn’t decide who bears the loss.
Call the vendor on a known correct number to verify the changed payment instructions.
Coordinate inside the business
Tell colleagues about the suspicious request and follow your incident procedures, including notifying your IT contact. Tell the vendor if someone impersonated them. A suspicious message alone doesn’t establish whose account, if any, was compromised.
- If passwords were compromised, change them immediately.
- If a device is infected with malware, disconnect it from the network.
- If personal information was compromised, notify affected people.
These conditional steps follow FTC guidance; they aren’t a diagnosis of this incident.
File a report
Report the incident to IC3, completing required fields, including banking details. Its analysts review complaints and may refer them to other agencies. Investigation is discretionary. Don’t expect IC3 to contact you.
Prepare and preserve the records
The IC3 FAQ covers these details:
- Your contact details; transaction date, amount, recipient and loss.
- What happened; available suspect identifiers and email headers.
Keep original evidence securely, including wire receipts and emails. IC3 accepts no attachments; you can paste information into the complaint. Investigators may request evidence separately.
Save or print the submitted complaint before leaving the page; IC3 won’t email a copy. For a time sensitive matter, contact local law enforcement directly.
Invoice payment fraud: keep the first call short and actionable
The first bank conversation needs enough information to identify the transfer and explain the suspected diversion. Have the sending business, payment amount, date, transaction reference and intended vendor available. Distinguish the intended recipient from the beneficiary actually shown on the payment record.
Don’t postpone that conversation while assembling a polished incident report. An internal summary can be completed alongside the bank’s response. If a requested detail is unknown, say so and ask how to provide it securely when found.
Record the time of the call, the department reached, the case reference and the next action the bank actually confirmed. A request to investigate, a recall request and recovered money are different statuses.
Ask which documents are needed and how the bank wants them delivered. Use its verified contact channel. The article can’t predict whether another institution can stop or return a particular payment.
Build a timeline without assuming who was compromised
A useful timeline starts with the legitimate invoice and then records the changed instructions, approval, payment submission and discovery. Keep each event’s actual timestamp and time zone where available.
For an invented sequence, the original invoice arrived Monday morning, a replacement instruction arrived Tuesday afternoon and the transfer was sent Wednesday morning. On Thursday the known vendor contact said no payment had been received.
Those events explain the concern, but they don’t establish that the vendor’s mailbox was hacked. An impersonated address, a compromised business account and another explanation require investigation. Preserve what the message shows rather than turning suspicion into a finding.
Keep the actual wording of the changed instructions beside the earlier approved record. Note which details changed, such as beneficiary name or account destination, without circulating complete bank information in an ordinary group discussion.
Invoice payment fraud: separate recovery from the vendor balance
Consider a fictional $12,000 invoice and a $12,000 transfer to a suspected substituted destination. Assume the legitimate vendor confirms it received nothing and no funds have yet been recovered.
The business has a $12,000 disputed outgoing payment. A recall request doesn’t restore $12,000 to its bank balance. The vendor’s unpaid-invoice record also remains a separate issue requiring reconciliation and, where necessary, advice on the parties’ rights.
Don’t silently mark the vendor invoice paid just because the business bank shows an outgoing debit. Equally, the example doesn’t instruct the business to send a second payment. Confirm the actual status and the appropriate authorized response first.
If $3,000 is later actually returned, the unrecovered portion of that original transfer becomes $9,000 before any other adjustments. That receipt doesn’t by itself show that the vendor has received payment or decide who ultimately bears the loss.
Use a cash ledger that distinguishes a request from a receipt
For a separate controlled cash example, begin with $30,000 available before the $12,000 transfer. Ignore all other activity. The outgoing payment reduces the available amount to $18,000.
Submitting a recall leaves the modeled amount at $18,000 until money actually returns. After a confirmed $3,000 recovery, the modeled balance becomes $21,000. Adding both the requested $12,000 and the received $3,000 would invent cash that hasn’t arrived.
If an unrelated $5,000 payment is then made, the modeled available amount falls to $16,000. Retain the order of events: the later receipt shouldn’t be backdated to fund an earlier obligation.
This is an original bookkeeping illustration, not a rule for recording a loss, insurance claim or tax deduction. Ask the business’s accountant which entries and supporting evidence are appropriate for the actual circumstances.
Invoice payment fraud: track three separate response records
Use separate records for the bank recovery process, the verified vendor conversation and the law-enforcement report. Each has a different purpose and may have a different reference number.
For the bank, record what was requested and what was confirmed. For the vendor, record how the contact was independently verified and what it said about the invoice and payment instructions.
For the complaint, retain the submitted version and its reference. A complaint receipt isn’t confirmation that a bank transfer was reversed, that an investigation was opened or that reimbursement was approved.
Where one colleague owns the bank follow-up and another handles records, assign the next action clearly. Avoid duplicate, inconsistent requests that use different amounts or beneficiary details. Correct an internal summary when evidence changes, while retaining the original evidence.
Preserve usable evidence and a separate working summary
Keep the source invoice, the changed instruction, payment confirmation, relevant emails and their headers securely. A screenshot may help explain what someone saw, but it shouldn’t replace the original record where that record is available.
Create a working index naming each item, its date, where it’s held and the question it helps answer. The index can point to a wire receipt without copying the full destination account into every status update.
Label a reconstructed timeline as a summary. Don’t edit the source email to insert comments or overwrite the original invoice with an annotated version. Keep explanatory notes separately so a later reviewer can distinguish evidence from interpretation.
If IT identifies a compromised account or infected device, coordinate the conditional containment steps described above through the business’s incident process. The payment evidence alone doesn’t diagnose a technical cause.
Ask precise questions during follow-up
Useful bank questions include: Has the recovery request been sent? Is another document required? What reference identifies the request? When should the business contact the bank again if no update arrives?
Useful vendor questions include: Which invoice remains outstanding? Did the vendor issue the changed instructions? Which previously verified contact and approved payment record should be used to investigate the mismatch?
Keep unanswered questions visibly pending. A colleague’s expectation that the funds will return shouldn’t replace a bank confirmation. Likewise, a vendor’s promise to investigate doesn’t establish a final allocation of responsibility.
If legal, insurance or accounting questions arise, give the relevant professional the actual chronology and documents. The same factual packet can support those conversations without claiming that a suspected diversion automatically qualifies for a particular remedy.
Invoice payment fraud: improve the next payment check
After the immediate response is underway, examine the point where the changed instructions entered the workflow. Identify whether independent verification occurred and whether the approver could see the earlier approved destination.
A review should distinguish a missing control from a control that existed but wasn’t followed. That distinction helps the business choose a practical correction and train the people who approve changes.
Document a verified contact route for future changes and retain evidence of the confirmation. Urgency in an email shouldn’t substitute for the required approval record. The goal is a repeatable check, not an unsupported accusation about a particular employee or vendor.
Close the incident record only when the actual recovery status, vendor balance and assigned follow-up are clear. An unanswered recovery request can remain open even after the business has completed its internal report.
For future payments, make independent verification of emailed wire requests a written company policy.
Illustrative stock photograph of an office telephone. Photo by Ron Lach on Pexels.
For a separate unauthorized debit, review business ACH reporting and controls. Use your business bank reconciliation to distinguish the disputed transfer from outstanding payments and other timing items.


