The payment file can matter after the keys are handed over

Why the banking record of an international property purchase should remain a coherent file after handover, rather than a collection of old screenshots.

2026-09-09

This article reflects the named expert’s practical perspective. See NovAsia’s editorial policy for how material is prepared and reviewed.

Handover feels like the natural end of a purchase. The buyer has the keys, the seller has acknowledged payment and the banking documents suddenly look like history. A short organising pass is still worthwhile before closing the folder. A payment record can remain useful long after the transfer itself is complete because it explains how each contractual obligation was actually settled.

The purpose is not to retain every message forever. It is to keep a compact chain that connects the contract, the bank and the recipient. Months later, the owner should be able to answer a simple question without reconstructing an old chat: what was due, what was sent, where it was sent, and what did the seller recognise as paid?

Organise around obligations, not around apps

A folder called “Bank” and another called “Developer” reflect where documents came from, not what they prove. For a purchase paid in stages, I find it more useful to organise the file by reservation, first instalment, second instalment and final settlement. Each stage can then contain material from different parties while still telling one story.

For an individual payment, that story might include the invoice or contractual schedule, the payment instruction used at the time, the sending bank’s confirmation, the transaction reference and the seller’s acknowledgement. If the seller issues an updated balance or receipt, that belongs with the same stage.

Version history matters. If bank details changed during the purchase, the earlier instruction should not be overwritten by the newer one. The archive should show which version applied to which transfer and how the change was verified. Otherwise a perfectly legitimate payment can look inconsistent when somebody later compares it with the latest set of bank details.

Keep evidence from both sides of the transfer

A sender’s bank receipt and the seller’s confirmation do different jobs. The first records the bank transaction from the payer’s side. The second shows that the recipient recognised the money as payment for the relevant obligation. Neither is automatically a substitute for the other.

This difference can matter when fees, timing or intermediary banks create a mismatch between the amount debited and the amount credited. It also matters when one payment has to be investigated later. A bank reference, including a UETR where the bank makes it available for a Swift transfer, gives the financial institution a much better search point than a screenshot saying “successful.”

Swift uses the Unique End-to-End Transaction Reference to identify and track a payment transaction across the chain. The owner does not need access to the underlying institutional systems. Keeping the bank’s transaction reference simply preserves a durable handle for any later enquiry.

Handover does not eliminate every future payment question

A later issue may have nothing to do with a dispute. The owner may be reconciling a final balance, documenting a refund, explaining the acquisition to a bank or professional adviser, or preparing records for a future transaction. It would be wrong to claim that one particular document will always be required; retention requirements vary by jurisdiction, bank and circumstance. The practical value is the ability to reconstruct a significant cross-border payment accurately if somebody legitimately asks about it later.

Joint ownership makes this especially visible. If one person made the reservation payment and another made the final instalment, the property should not depend on two old phones and two private inboxes for its financial history. A shared, controlled archive lets either owner understand the settlement without guessing.

Refunds deserve their own branch in the file. A refund may relate to an earlier payment, but it is a new movement of money with its own date, amount, currency, fees and bank reference. Linking it to the original obligation is useful; merging the documents as though one simply erased the other is not.

Original records are stronger than screenshots alone

Screenshots are convenient during a live transaction, but they are fragile as the only archive. They can omit account details, references or status information and often lack the context of a downloadable bank confirmation. Where the bank provides a formal receipt or transaction document, that original file is worth keeping as well.

The same applies to the seller’s side. A short message from a salesperson saying “received” may help in the moment, but a formal receipt, statement or updated balance is a stronger long-term record when available. The right document depends on the seller’s process; the principle is to preserve what the organisation itself uses to recognise the payment.

Security matters too. A payment file contains bank and personal information. It should not be copied into every messaging thread or left under a public link simply because it is convenient. Access and retention should be appropriate to the owner’s situation and the relevant legal or institutional requirements.

The archive should answer the question without the original participants

A good test is to imagine that the salesperson, banker and buyer who handled the transaction are all unavailable. Could another competent person open the file and understand the sequence without an oral explanation?

The answer does not require a huge dossier. It requires a coherent one. Each obligation has an amount and basis. Each transfer has the instruction and bank evidence. Each receipt has a link to the corresponding payment. Changes are visible rather than overwritten. Refunds sit beside, but do not erase, the original movement.

That is why I see the payment archive as part of the ownership record rather than a temporary collection of transaction screenshots. The keys mark the start of using the property. They do not remove the value of a clear record showing how the purchase price moved and how the seller confirmed it.

Sources

• NovAsia Estate — “Payments and banking when buying property in Cambodia”: sender confirmation, UETR, recipient acknowledgement and updated balance as distinct payment evidence; accessed 6 October 2026.
• Swift — Payments / Tracking: UETR and end-to-end payment tracking; accessed 6 October 2026.
• Swift — About ISO 20022: structured information and reconciliation in payment records; accessed 6 October 2026.