Payments and bank evidence

Delayed, held or returned property payment

A post-initiation route covering first response, UETR and bank trace, compliance requests, short credit, return, recall, suspected fraud and written protection of the contractual deadline.

Bank status, contractual performance and the recipient’s entitlement are separate questions. Check the actual contract, bank details, bank evidence and current requirements.

Updated 24 July 2026

In short

If an international property payment was debited but not credited, do not send a second transfer or accept ‘it is probably on the way’ as a status. Establish the exact state: instruction accepted, debited, awaiting compliance information, held by an intermediary, credited to the beneficiary bank, credited to the beneficiary account, rejected, returned, recalled or potentially misdirected. Each state requires different actions and evidence.

The sending bank is the primary contact because it accepted the instruction and can initiate a trace, request chain status, correct permitted data, issue a recall or investigate. The beneficiary should simultaneously check with its bank and provide precise incoming-payment details. The seller should receive a written notice of the banking incident and should not alter the contractual ledger until the outcome is confirmed.

Identify the last confirmed point first

Start with evidence rather than an assumption. Record debit date and amount, currency, sending bank, beneficiary, bank reference or UETR, payment narrative and the last confirmed event: debited, accepted by a correspondent, delivered to the receiving bank, held for review, rejected, returned or credited.

Do not send a duplicate payment until the first chain has been traced and the seller has confirmed non-receipt in writing.

First actions: do not compound the problem

Preserve the original instruction, debit confirmation and all correspondence. Check amount, currency, value date, account holder, account number, BIC or Swift code, payment purpose and transaction reference. Do not edit screenshots or send records through an unverified contact.

If there is any suspicion of changed instructions or an unintended beneficiary, tell the bank explicitly rather than describing an ordinary delay. Request immediate fraud escalation, recall or hold where possible, and a timestamped case record. Speed matters because misdirected funds may be moved onward quickly; recovery is never guaranteed.

Stop a second payment
Do not duplicate the amount until the first transfer is classified.
Open a bank case
Obtain case number, timestamp and team name.
Notify the counterparty
State the facts without admitting an unverified default.
Freeze the ledger
Use pending trace, not paid or failed.
Set the next check-in
Set a specific response deadline for each participant.

Use precise payment statuses

**Pending** means the normal window has not yet closed but the bank should confirm status. **Held** means a bank has requested review or documents. **Rejected** means one participant did not accept the payment. **Returning** means funds are on the way back but not yet credited. **Credited** means the receiving bank reports credit, followed by seller reconciliation.

Each status needs its own evidence and owner; “stuck” does not identify the next action.

Status

Meaning

status	meaning
Initiated / accepted	Bank accepted the instruction; not yet proof of debit or credit.
Debited	Payer account was charged; funds may still be in the chain.
On hold / information required	A bank is awaiting information or conducting review.
Credited to beneficiary bank	Funds reached the bank but may not be available to the beneficiary.
Credited to beneficiary account	Bank side confirms credit to the stated account.
Rejected / returned	Payment was not completed or is returning; obtain reason and amount.
Recall requested	A return request was sent; success is not confirmed.
Potentially misdirected	Requires fraud or error escalation, not an ordinary trace.

Collect the identifiers banks use

A bank should not be asked to find ‘USD 30,000 to Cambodia’. Provide exact date and time, amount, currency, ordering account, beneficiary name and account, BIC or Swift code, payment reference, bank transaction number and UETR where present. Terminology and available records vary by institution and message format.

The UETR supports end-to-end tracking in a Swift chain. A buyer should not claim direct access to the full Tracker; practical access is generally through a participating bank. Request a trace or status record from the ordering bank and never expose real references on the public website.

initiation date, value date and actual debit time
amount instructed, amount debited and currency
ordering account and legal payer
beneficiary name, account and beneficiary bank
BIC or Swift and intermediary details where disclosed
payment purpose or reference as originally entered
bank reference, UETR or another unique transaction identifier
case number and written bank status

What to request from the ordering bank

Ask for more than a generic ‘transfer sent’ confirmation: request investigation against the specific reference. The bank may check network status, contact an intermediary or beneficiary institution, identify missing information and provide the rejection or return reason. Capabilities and response form depend on the institution.

Clarify which action has actually been opened: trace, amendment, cancellation, recall, fraud case or compliance response. These are not interchangeable. A recall is a request to return funds, not unilateral cancellation of a completed credit. An amendment may be unavailable after a certain stage and should not be used to legitimise an originally unauthorised beneficiary.

What the beneficiary and its bank should check

The seller or developer should give its bank the exact amount, currency, expected date, payer name, reference and UETR where available. ‘Nothing is in the account’ is not enough: an incoming payment may await compliance review, clarification, conversion, manual repair or internal allocation.

The beneficiary should distinguish credit to the bank, credit to the account and allocation to the specific buyer or unit. Even after bank credit, the seller’s accounting team may post funds to the wrong contract. Bank confirmation therefore needs an official receipt and updated seller statement.

When the bank requests compliance documents

Answer the bank’s specific request and keep names, addresses, payment purpose and transaction facts consistent across documents. The bank normally identifies what it requires, such as identity, source of funds, agreement, invoice, relationship to the beneficiary or economic purpose.

Use a verified banking channel. Do not send more personal data than required or provide conflicting explanations without a written correction.

If less arrived: locate the deduction

A short credit may result from ordering, intermediary or beneficiary-bank charges, conversion, an incorrect charging instruction, or the beneficiary comparing the payment with a different obligation. Obtain bank records rather than using a typical fee. The difference should be arithmetically reproducible.

If the contract requires a net credited amount, a top-up may be needed, but responsibility depends on the SPA and bank terms. Create a separate top-up line and preserve the original payment unchanged. If the deduction is unexplained, keep the exception open and request a trace of charges.

Rejection, return and recall are different processes

For a rejection, obtain the code or written reason and correct only the confirmed error. For a return, trace the route back, fees, conversion and actual credit to the sender. A recall is a request by the sending bank, not a guaranteed recovery; it depends on stage and participant decisions.

Independently verify any new seller instructions, especially after a failed transfer.

Event

Practical action

event	action
Rejected before credit	Obtain reason, correct permitted data or choose another agreed route.
Returned after part of the chain	Trace return amount, charges and actual destination account.
Recall requested	Do not treat return as complete until confirmed and credited back.
Cancellation before execution	Obtain bank confirmation that funds did not leave.
Duplicate credit risk	Do not resend until the first transaction is documented as closed.

Unintended beneficiary or suspected fraud

If account details differ from those previously verified, an email came from a lookalike domain, the counterparty denies the instruction or funds may have reached a third party, report suspected fraud or error to the bank immediately. Request the fraud team, recall or hold, and preservation of all information. Then contact law-enforcement or other authorities in the relevant jurisdiction as directed by the bank and lawyer.

Do not continue only through an address that may be compromised. Use a previously known number, official website or separately verified channel. Never promise recovery: after credit, funds may move quickly and the result depends on banks and jurisdictions.

one-character domain change or new email thread
urgent account change just before deadline
personal or unrelated corporate account
instruction not to call the previous contact
counterparty denies sending the details
recipient asks to disguise purpose or split the amount

Protect the contractual position during the bank investigation

A bank case does not automatically suspend the due date, late charges, cancellation right or handover process. Notify the seller in writing with confirmed facts: when the instruction was accepted, when funds were debited, which reference applies, what the bank requested and when the next update is due. Do not admit unverified fault or conceal the issue.

Request written agreement on treatment: extension, standstill, unit preservation, non-application of penalties during the trace or another mechanism. The terms depend on the SPA and negotiation. A sales manager should not alone promise a change of obligations without authority.

Maintain linked bank and contract logs

The bank case log records network status, requests, responses, references and bank actions. The contract log records the due date, notices to the seller, agreed extensions, receipt, seller allocation and remaining balance. They share one transaction ID but are not merged.

For example, the bank may confirm credit to the beneficiary account while the seller has not allocated funds to the unit. The banking incident is closed but the accounting exception remains open. Or the payment is returned while the parties extend the due date in writing: bank status failed or returned, contractual status protected. This model prevents false conclusions.

Evidence pack for tracing and reconciliation

Assemble the payment order, debit statement, SWIFT copy or bank confirmation, UETR or other reference, invoice, SPA, verified instructions, bank correspondence, compliance requests and responses, seller confirmation, and dated notes of calls.

After the outcome, update the ledger with the credited amount, fees, exchange rate, date, balance and linked milestone.

SPA, schedule, invoice and authorised payment instruction
original and changed bank-detail versions
bank instruction, debit advice and full statement
transaction reference, UETR and case number where available
trace, amendment, recall or return correspondence
compliance requests and submitted responses
seller receipt and updated account statement
contract extension, standstill or dispute notice
call chronology, names and timestamps

Who to contact for each problem

Do not send the same generic question to every participant. Assign a primary owner to each exception and request a verifiable output. NovAsia or an agent may coordinate records but does not replace the bank or legal adviser.

On mobile, render the matrix as cards: problem, primary contact, expected evidence and next step.

Issue

Primary contact

Expected output

issue	owner	output
Unclear network status	Ordering bank	Trace or status and reference.
Incoming hold	Beneficiary and beneficiary bank	Information request or release status.
Short credit	Both banks through trace	Actual deductions and credited amount.
Seller misallocation	Seller finance team	Corrected receipt or statement.
Suspected fraud	Bank fraud team and competent authorities	Case, recall or hold action and incident record.
Contractual default risk	Seller and independent lawyer	Written extension, standstill or legal position.

When the incident can be treated as closed

‘The money was found’ is not enough. Record final bank status, credit or return amount and date, all charges, contractual allocation, remaining balance and timing consequences. If there was an attempted fraud, close the security incident separately: change credentials, review domains, restore trusted contacts and notify affected participants.

If some facts remain unknown, use resolved with residual unknowns rather than clean. For example, the seller recognises full payment but an intermediary-fee breakdown is unavailable. The relevant party or adviser decides whether that result is sufficient.

final bank status and source of confirmation
credited or returned amount, currency and value date
fees, FX and unexplained difference
seller receipt, allocation and remaining balance
contractual extension, penalties or waiver
fraud or security remediation where applicable
residual unknowns and risk owner

When not to resend or remove stop status

Do not resend if the first transfer is not confirmed as cancelled, rejected, returned or otherwise incapable of later credit. Do not use new details received in the same suspect correspondence. Do not rely on an oral seller promise that a double credit will be refunded later.

Keep the stop status if the bank requests records that conflict with the contract, the beneficiary refuses to contact its bank, the return amount does not match, no fraud case has been opened, or due-date protection remains unresolved while SPA consequences may apply.

first transfer has an unknown or contradictory status
new payee is not confirmed through an independent channel
bank has not received the complete identification pack
seller statement does not show treatment of the first payment
return or recall was requested but not completed
possible fraud was reported only as an ordinary delay

Who owns the next step

The sending bank opens the trace and provides the available status. The receiving bank acts through its customer and internal process. The seller confirms receipt and the contractual balance. A lawyer assesses deadlines, breach, duplicate payment, refund or a changed beneficiary. NovAsia can organise the pack and action log but does not control the banking chain.

Hub materials