
Respond after a suspected diverted supplier payment: identify the transfer, contact the institution, preserve evidence and separate bank, IT and order outcomes.
Act on the suspected payment problem before debating blame
The transfer has left your account. A supplier in China now says the invoice carried the wrong bank details, or a colleague notices that the beneficiary changed shortly before payment. There may be a genuine explanation, an administrative error or deliberate diversion. You do not yet know which. What matters immediately is getting the exact transaction in front of the financial institution that handled it, while preserving the records that explain why the payment was made.
Direct answer: contact your originating bank or payment institution through its established official channel, identify the transfer and explain the suspected diversion. In parallel, preserve the original instructions and ask the responsible IT person to assess potentially affected communications. Keep bank actions, supplier statements and confirmed financial outcomes separate. A request to recall funds is not confirmation that money has returned.
The FBI’s BEC guidance advises immediate contact with the financial institution after a suspected fraudulent transfer. Do not postpone that contact until the supplier has completed an internal investigation. This article develops an original incident-file routine for a China purchasing team; it does not promise recovery or determine legal responsibility. For the surrounding order, use the China purchasing and import guides.
Open one incident file and identify the payment
Give the incident a reference that everyone can use. Put the purchase order, supplier’s contractual identity and affected payment reference at the top. Record what triggered the concern in plain language: “supplier denies requesting the new account” is an observation; “supplier stole the funds” is a conclusion that the available evidence may not support. A precise opening note lets the bank, management and technical responder work from the same problem statement.
Identify the actual institution and person who executed the instruction. If a permitted payment arrangement involved another company, establish who holds the transaction record and can contact its provider. Do not assume that a sales representative, intermediary or purchasing coordinator has authority to recall a transfer. The incident owner should know which authorized person is making the request, through which institution and against which transaction.
Keep the transaction’s amount and currency together. Record the execution reference, sending account, beneficiary details used, submission time and any status supplied by the provider. Use the exact record rather than reconstructing the transfer from an invoice total. One invoice may have been paid in several parts; a single transfer may settle several orders. Write down that relationship before a reviewer assumes the whole purchase price is affected.
Reach the bank through a route you can trust
A suspicious message may offer a helpful telephone number or claim that a “recovery department” will handle everything. Establish the contact route separately. Use the institution’s official application, an existing authenticated relationship or contact details obtained from its official website. The UK NCSC’s business payment fraud guidance similarly directs businesses to contact their bank through official details and involve their IT responder.
Describe the issue as a suspected fraudulent diversion when that is the concern. Explain that funds have already been sent, give the exact reference and ask which immediate action is possible for that transfer. A general question about changing future beneficiary details may reach a different process. Record the name or team, time, case reference and next instruction provided, using whatever identification the institution is willing to supply.
Ask how to deliver supporting documents securely and who should send them. Do not broadcast full bank details or identity documents to a large project chat. The working incident summary can refer to a restricted transaction record. If the bank needs additional authorization, identify the authorized signatory promptly. Keep that dependency visible instead of recording the case as submitted when the required request has not actually reached the institution.

Record what the institution has actually acknowledged
The IC3’s BEC resource describes contacting the originating institution about recall or reversal and relevant documentation. The available process depends on the transaction. Ask the institution what applies; do not treat a foreign authority’s terminology as a universal form or a guarantee that a particular mechanism exists for your payment route.
In your own file, separate the request from the response. “We asked for action” records something your team did. “The bank opened case B” records an acknowledgement. “The bank reports that the receiving institution has been contacted” describes a further reported step. None of these alone establishes that funds are secured or returned. Retain the institution’s actual wording alongside your internal status label.
Set the next follow-up from the instruction you receive, not an invented industry deadline. If the provider asks for a signed statement or transaction evidence, note who will supply it and whether receipt was acknowledged. If there is no substantive update, record that honestly. Repeatedly opening new cases without cross-referencing the existing one can make the internal history harder to follow, even when several legitimate contacts are needed.
| Internal record | Evidence to attach | What remains open |
|---|---|---|
| Concern raised | Triggering message and transaction reference | Nature and extent of the problem |
| Action requested | Request, time, authorized sender | Whether the institution accepted the request |
| Case acknowledged | Provider case reference and response | Disposition of the funds |
| Return reported | Institution’s written update | Actual credit and reconciliation |
| Return reconciled | Confirmed credit, currency, amount and reference | Any residual loss, fees or order obligation |
Preserve the instruction trail without rewriting it
Save the original payment instruction, the earlier approved details and the message that introduced the change. Include attachments in their original form, the surrounding conversation and available message metadata. Ask the technical responder how to preserve potentially malicious material safely. Do not open a suspicious attachment merely to make the incident folder look complete, or delete a message because it is embarrassing.
Create a working copy for annotation and keep the original distinct. Mark the exact field that changed: beneficiary name, account, bank, currency, contact route or payment reference. The fact that the grand total stayed the same can hide a consequential instruction change. A reviewer should be able to compare the two versions without relying on somebody’s memory of what was visible on a phone.
Also preserve the approval record. Who saw the changed instruction, what did they approve and which version was used for execution? This is initially an evidence question, not a disciplinary interview. Avoid retrospectively adding approval language to an old message. If a colleague explains an earlier decision now, date that explanation now and identify it as a later recollection.
Build a timeline that survives a handover
Record events with dates, times and time zones. A buyer, China supplier, payment provider and technical responder may be working in different locations. “Yesterday afternoon” will become ambiguous quickly. Keep the original timestamp and, if useful, a separate normalized time for comparison. Do not silently change a source record’s time to make the sequence appear cleaner.
A practical timeline has four columns: event, source, observation and next dependency. For example, the invoice arrived; a changed-account message followed; finance submitted the transfer; the supplier disputed the instruction; the bank acknowledged the report. The event sequence can reveal which records need examination without proving who controlled an account or why the transfer was redirected.
Where times conflict, leave the discrepancy visible. A screenshot may show a device’s local time, while a provider receipt records another zone. A forwarded message may display the forwarding time rather than the original send time. Ask the appropriate record holder to explain the difference. Do not invent a missing event just because it would make the story plausible.

Verify the supplier’s position outside the questioned conversation
Use contact information established before the disputed request or obtained through an independently checked company route. Rejoining the same email thread may put the question back in front of the person controlling it. State the transaction reference and ask the supplier’s authorized representative whether the changed instruction originated with them. Record how you established the route and the scope of the answer.
A statement that the account is not theirs is relevant, but it does not complete a forensic investigation. A statement that the new account is legitimate does not automatically establish the beneficiary’s contractual role or the provider’s acceptance of the arrangement. Keep authenticity of the request, suitability of the beneficiary and status of the sent transfer as separate questions.
Ask for a factual response rather than a general reassurance. Which instruction do they recognize? Who was authorized to issue it? Which invoice and purchase order are affected? Do not request passwords or remote access to their systems. If the supplier needs to involve its own IT or bank contacts, identify the person coordinating that work and agree a trusted channel for updates.
Give the technical responder a bounded investigation task
Purchasing should supply the incident references, affected addresses, relevant times and original messages through the responder’s approved method. The technical question is whether communications or accounts may have been compromised and what needs containment. It is not for the purchaser to infer account security from a familiar logo, successful login or apparently normal reply.
Microsoft’s compromised-account guidance covers administrator investigation and remediation, including account activity and forwarding. It applies to the stated Microsoft environment; another mail service requires its own official process. Ask the responsible specialist to preserve useful evidence while securing access, rather than improvising technical changes from a purchasing checklist.
Keep the technical disposition separate from the financial one. Restored access does not show where the money is. A bank case does not show that the mailbox is secure. Ask the responder what was examined, what remains unknown and which communication route is now suitable for use. A short, dated handover is more useful to finance than an unexplained statement that IT has fixed it.
Limit further exposure without losing control of the order
Identify other queued or pending instructions that relied on the same questionable details. Refer those specific items for authorized review. Do not assume that every payment in the business is fraudulent, and do not allow an affected instruction to be resubmitted simply because the first transaction has not reached the intended supplier. A duplicate transfer can create a second unresolved problem.
List the affected payment references and purchase orders individually. Where the same beneficiary version was reused, show that connection. Where a transaction used independently approved details, record that difference. The purpose is to scope the review from evidence. Broad guesses about all suppliers or all payments obscure which decisions need immediate attention.
The order itself needs a separate owner. Production, collection and delivery may still have contractual consequences. Ask purchasing and the appropriate advisers to handle those obligations while finance pursues the transfer. The supplier purchase-contract guide explains the wider contract file; an incident note does not by itself amend payment terms or decide which party bears a loss.
Use reporting channels that fit the actual transaction
Determine the relevant bank, organizational and official reporting routes from the countries and parties involved. The language of this article does not choose a jurisdiction. IC3 is a US reporting resource; the NCSC and Australian resources have their own contexts. Check the current official instructions before submitting sensitive material, and preserve the report reference where one is issued.
The Australian recovery guidance emphasizes recording incident actions and reviewing account security. Use that general organization principle while keeping Australian reporting arrangements within their actual scope. Your organization may also need legal, privacy or insurer advice. Ask the responsible professional which obligations apply instead of assuming that one foreign web form closes every requirement.
Keep reports consistent with the evidence available at submission. Say that an account change is disputed when that is what you know; distinguish an estimated exposure from a confirmed loss. If new information arrives, retain the earlier report and record the update through the relevant route. Avoid copying speculation about a named individual into several official reports as though it were an established finding.

A fictional order with three different open questions
Consider a teaching example called Order K-17. The buyer receives an ordinary invoice, then a message in the same conversation supplies replacement beneficiary details. Finance sends the payment using the replacement. Later, a representative reached through an older verified company number says that the supplier did not request the change. The example contains no real transaction, customer, account or recovery result.
The first open question concerns the transfer. Finance identifies the executed reference and contacts its provider. The file records the concern and the provider’s acknowledgement. It does not say that money has been frozen unless the institution provides an appropriately specific confirmation. Any additional request from the supposed recovery team is verified through the already established provider route.
The second question concerns communications. IT receives the original message trail and determines the appropriate account review. Purchasing asks the supplier to confirm its recognized instruction through the checked contact route. Neither side’s claim is silently converted into a finding about who caused the problem. The case can proceed while the cause remains unresolved.
The third question concerns the order. The supplier says production is ready but payment is not credited to its recognized account. Purchasing records that commercial position and seeks an agreed next step with the relevant advisers. It does not send another transfer merely to clear the shipping schedule. Bank follow-up, technical containment and contractual decisions have separate owners, even in a small team.
Work through the outcome branches before closing the case
If the provider confirms that the instruction never executed, reconcile that confirmation with the sending-account record. An unsuccessful instruction is different from returned funds. If the supplier subsequently confirms receipt through the verified route, match that statement to the transaction and the purchase-order ledger. Do not treat either branch as proof that the earlier account-change process was sound.
If a return is confirmed, record the amount and currency actually credited, the transaction reference and any remaining difference. A partial return does not close the residual exposure. A fee or currency difference should remain visible for review, rather than being hidden by marking the original invoice paid. The incident’s financial result and the supplier’s commercial balance may require separate accounting decisions.
If the outcome remains unknown, keep it unknown. Record the last institutional response, the outstanding request and the person following up. A case can have completed evidence collection while recovery remains open. Equally, a financial credit can arrive before the technical investigation finishes. Close each workstream from its own evidence instead of forcing the whole incident into one misleading green status.
Reopen payment only against a new controlled decision
Before any replacement or subsequent payment, establish which beneficiary instruction is current, who verified its origin and who approved its use. Link the new decision to the incident without overwriting the earlier record. The supplier payment milestone guide owns the ordinary evidence and approval process; return to that process after the incident-specific questions have been addressed.
The reopening note should state the scope. It may authorize review of a particular next payment while leaving recovery of the earlier transfer open. It may identify a new trusted communications route without approving a beneficiary account. It may confirm that finance has corrected a duplicate queue item without resolving a supplier dispute. Specific wording prevents one approval from travelling further than intended.
Keep goods-quality problems separate as well. If an unrelated discrepancy is discovered after delivery, use the post-delivery discrepancy case guide. A damaged product is not evidence of payment diversion, and a suspicious payment is not proof that the goods are defective. Distinct files can cross-reference the same order while preserving their different evidence and decisions.

Leave a compact handover for the next responsible person
A useful handover states the incident reference, affected transaction, current institutional case reference, verified communication route and outstanding dependencies. Add links to the restricted original records, the next action owner and the latest dated response. A colleague should be able to continue the work without asking the whole team to retell a stressful conversation.
Keep access proportionate. Management may need the exposure and decision status, while the bank needs the full transaction details through its secure process. The supplier may need the disputed instruction and order reference, while IT needs original technical evidence. Sending the same unrestricted folder to everyone does not make the incident more transparent; it can spread sensitive material without helping a decision.
After the immediate response, review the specific control that failed or remained uncertain. Did a beneficiary revision bypass approval? Was an old contact route unavailable? Did finance have no way to distinguish recall requested from return credited? Assign a concrete improvement and verify that it works. Avoid closing the review with an instruction to be more careful, which gives the next employee little usable protection.
For a China order, the supplier-verification service and purchasing and payment-coordination service describe their respective commercial scopes. Any enquiry should begin with a redacted description of the order and the coordination question. Urgent banking or cyber-incident reports belong with the relevant institution or responder; this article does not offer a fund-recovery service.
Questions buyers ask after a disputed transfer
Should I wait for the supplier to investigate before contacting the bank?
No. Report the suspected diversion to the institution that handled the transfer promptly while the supplier inquiry continues. Identify the exact transaction and explain what is known and uncertain. The supplier’s investigation and the institution’s response are separate workstreams, so one should not be mistaken for completion of the other.
Does a recall request mean the funds are safe?
No. It records a requested action. Keep the institution’s actual response and any subsequent confirmation. Do not record recovery until the relevant credit or other financial disposition has been confirmed and reconciled. The available options and outcome depend on the actual transfer; this guide provides no success guarantee.
Can a familiar email address prove that the new instructions are genuine?
No. Familiar correspondence is a reason to preserve the message carefully, not a substitute for independently checking a disputed request. Use a trusted route established outside the questionable message. A technical responder must assess any suspected compromise; the purchasing team should avoid declaring an account secure from its appearance.
What if the transfer status is simply unclear?
Ask the provider to clarify the specific instruction rather than inferring fraud from delay alone. Record the response and the reason for your concern separately. If evidence suggests diversion, explain that concern directly. If it remains an ordinary reconciliation issue, keep the record accurate instead of forcing it into a fraud conclusion.
Should I pay the supplier again to avoid delaying shipment?
A replacement payment needs its own authorized commercial and financial decision. First establish the original transaction’s position, the supplier’s recognized account and the applicable obligations. Preserve both decisions if a new payment is eventually approved. Shipping pressure should not silently create a duplicate instruction or erase the unresolved earlier transfer.
Do I send the entire evidence folder to every participant?
No. Share the information each authorized participant needs through an appropriate route. Preserve original records centrally with controlled access. Use references or redacted working copies for wider coordination, while delivering full details securely when the bank or responsible authority requires them. Keep a record of what was supplied and to whom.
When is the incident ready to close?
Close defined workstreams against evidence: the financial result is reconciled, technical findings and remaining limits are recorded, commercial decisions have owners, and follow-up controls are assigned. A bank acknowledgement alone is not closure. If recovery or a dispute remains unresolved, keep that part visibly open while documenting the work already completed.
Sources and scope
This is an original buyer coordination workflow, supported by the limited official guidance linked near the relevant claims: FBI BEC guidance, IC3’s BEC resource, NCSC business payment fraud, Australian BEC recovery guidance and Microsoft’s account-response documentation. The fictional case and suggested worksheets are educational. They establish no legal liability, provider availability, completed investigation or recovery outcome for a real transaction.




[…] Related guide: responding after a suspected diverted supplier payment […]