NovAsia
Payments and bank evidence

Property payment ledger and instalment reconciliation

A practical system linking the contractual obligation, authorised recipient, bank movement, receipt and updated balance without confusing bank debit with performance of the SPA.

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

A property-purchase payment is controlled only when the record can be reconstructed from contractual basis to a confirmed remaining balance. Create a separate ledger line for every reservation fee, deposit, instalment, final balance, refund or credit: what made it due, when it became payable, who owed it, who was authorised to receive it, what amount had to be credited, what was actually debited, what the recipient received and how the contractual balance changed.

A bank debit alone does not prove performance of the buyer’s obligation to the seller. A seller receipt does not explain fees, conversion or a difference from the bank statement. A strong chain links the SPA or signed amendment, invoice or payment request, verified details, bank instruction, trace or reference, account statement, credit confirmation, official receipt and updated seller statement. Any mismatch remains an open exception until documentary evidence closes it.

What the payment ledger should deliver

A payment ledger shows not only how much has been sent, but to whom, on what basis, for which milestone and what remains unconfirmed. It connects the agreement, invoice, bank evidence, schedule, seller statements and later handover or title steps.

Use it as a working reconciliation between party records. It does not replace the bank statement, seller acknowledgment or legal review of the beneficiary.

Start with a transaction identity

A ledger should not exist as an anonymous spreadsheet. Its header should record the buyer, project, phase or tower, unit number, contractual seller, contract currency, SPA date and version, and a permanent file identifier. If several people buy or a third party pays, show each role separately.

This prevents similar units, obsolete price lists and payments by different family members from being mixed. A project or brand name is not enough: the legal seller and money recipient may differ, but the relationship between them must be documented.

  • permanent transaction ID and file name
  • buyer, co-buyers and actual payer
  • project, phase, tower, floor and exact unit code
  • SPA seller, licence or project company and authorised payee
  • currency, contract version and signed amendments
  • responsible contact and independently verified channel

Convert the contract into a calendar of cash events

Do not copy only dates and percentages from a marketing payment plan. For every event, record its legal basis, exact amount formula, trigger and evidence that the trigger occurred. An instalment ‘on 30% construction completion’ differs from one ‘six months after the SPA’: the first requires milestone evidence; the second is calendar-based.

Enter the reservation fee, SPA deposit, regular instalments, balloon payment, handover balance, contractual assignment charge, applicable late amounts and permitted retentions separately. Costs outside the price—registration, service charge, furnishing or tax—must not be mixed with the purchase-price balance even if they are paid in the same period.

  1. Extract the obligation

    Contract clause, schedule, signed addendum or other basis.

  2. Identify the trigger

    Date, construction milestone, signature, handover or registration event.

  3. Calculate the amount

    Fixed amount, percentage of a defined base, adjustment or balance.

  4. Assign evidence

    Invoice, notice, progress evidence, acceptance record or filing receipt.

  5. Set status

    Not due, due, initiated, debited, credited, receipted, reconciled or disputed.

Fields for every payment record

Record the obligation number and date; project, phase and unit; payer; contractual payee and actual bank beneficiary; currency; amount due and amount debited; bank charges; send date; bank reference or UETR; credit date; seller acknowledgment; linked milestone; discrepancy status; evidence and owner.

Do not turn an unknown fee, credit date or balance into zero. Leave it open and assign a check.

Field

Purpose

fieldpurpose
Contract basis and due eventShows why and when the amount became due.
Required credited amountKeeps the obligation separate from the bank debit.
Payer / source accountLinks funds to the buyer and source-of-funds file.
Legal payee / account holderShows authority to receive and any difference in names.
Debited / credited / feesExplains the arithmetic difference.
Bank reference / UETR where availableAllows banks to trace the specific transaction.
Receipt and seller balanceConfirms recognition and the new remaining balance.
Exception owner and deadlinePrevents an exception from disappearing unresolved.

One instalment — one closed evidence chain

For every instalment, link records in a single sequence. Start with the SPA clause and payment schedule. Add the invoice or authorised request, verified bank details and payment approval. After initiation, attach the bank instruction, debit confirmation, transaction reference, charges and, where needed, the trace. Close the chain with credit confirmation, seller receipt and a statement showing the new balance.

The file is not closed if it contains only an app screenshot, a manager message saying ‘funds received’, or a receipt that is not tied to a specific instalment. The payment purpose should distinguish the buyer, project and unit. If the bank truncates the reference, preserve the original instruction and obtain written seller confirmation identifying the contractual debt discharged.

Match the seller, account and authority to receive funds

The bank beneficiary must connect to the SPA seller or another party with documented authority to receive the payment. Reconcile the legal name, account, bank, currency, payment purpose and source of the instruction.

Verify changed details through an independent channel using a previously known contact. A new email address, chat message or urgency does not authenticate the change.

Separate obligation, debit, credit and charges

The amount debited by the bank may differ from the amount the seller must receive. Charges may be taken by the sending, intermediary or beneficiary bank; OUR, SHA, BEN or equivalent terms depend on the institution and route. Do not assume that a selected charging option guarantees an exact credit: obtain the actual bank terms and instruction, then record the realised result.

Keep at least four figures in the ledger: contractual amount due, amount instructed, amount debited including fees and amount credited. Record currency conversion separately with source currency, rate, date and evidence. If the seller requests a top-up after a short credit, create a separate documented line rather than erasing the history of the original payment.

Third-party, split and partial payments

When the payer is not the buyer, the banks and seller need an explanation of the legal and economic relationship. Clear the third party, source of funds, payment purpose and recognition of the buyer’s obligation in advance. Likewise, splitting one obligation across several transfers or accounts should be authorised and fully traceable.

Do not combine several partial payments into one row. Each has its own reference, charges, date and status. The parent obligation may show the sum of the parts and the open balance. If the seller asks for a premium, tax, commission or booking fee to be paid to another party, treat it as a separate money flow with separate documentary authority.

  • unknown third-party payer without bank clearance
  • several unrelated recipients without a signed allocation
  • cash later presented as if it were a banked instalment
  • generic reference without project, unit or buyer
  • set-off across different contracts without a signed statement

Discounts, credits, refunds and price changes

Do not overwrite the original price or schedule as if the earlier version never existed. A discount, cashback, furniture credit, waiver, deferral, reservation refund or partial termination should rely on a signed record and appear as a separate adjustment entry. The ledger should show the original obligation, authority for the change and resulting balance.

A refund is not simply a negative payment. Record who owes it, the triggering event, destination account, due date, deductions and whether it settles all claims. If a different legal entity returns the money, add its authority and an explanation of the chain.

Reconcile the ledger to the seller statement

Obtain a seller statement and match each obligation date, amount sent, amount credited, deduction, credit note, refund and balance. Record a variance separately instead of silently editing history.

After reconciliation, both sides should be able to identify the milestone covered by each payment and every open item.

  1. Freeze versions

    Save dated copies of your ledger and the seller statement.

  2. Match line by line

    Do not rely only on the grand total.

  3. Create an exception

    Record amount, cause, evidence and owner.

  4. Obtain a corrected record

    Close the difference with a new statement or signed confirmation.

  5. Preserve the audit trail

    Do not delete the incorrect version or correction correspondence.

Payment status and contractual default are not the same

An initiated or debited status does not necessarily mean the seller received funds by the due date. At the same time, a banking delay does not automatically make the buyer contractually in default: the result depends on the SPA wording, agreed payment method, point of performance, notices and conduct. Before a material instalment, agree what counts as timely payment and which evidence is accepted.

If a transfer is delayed, notify the seller immediately through a documented channel, attach instruction evidence and request a written standstill, extension or other agreed treatment where needed. Do not backdate the due date without a signed amendment. The ledger should show both bank status and a separate contractual status.

Confirm the event before a milestone payment

Do not pay only because an expected calendar date has arrived. Check the contractual milestone definition, seller notice, required document or result, coverage of the correct phase or unit, and authority to invoice.

Where evidence is incomplete, record the question and response date. A marketing photograph or internal seller message should not be treated as proof of a legal or construction milestone.

Control points before handover, assignment, title and refund

Before final settlement, reconcile the balance, handover conditions, defects, access, charges and the document triggering payment. For an assignment, check consent, fee, new-party identity and treatment of prior payments. Before title, match the unit and registration route. For a refund, record the basis, amount, currency, payee, deadline and actual receipt.

  • official seller or developer account statement
  • buyer ledger with closed exceptions
  • signed price and adjustment schedule
  • separate list of fees, taxes, service charge and deposits
  • confirmation of remaining balance and next action
  • who may sign the reconciliation and under what authority
  • list of disputed amounts not treated as agreed

Keep the payment archive for ownership and exit

Payment records remain useful after keys are delivered. A bank, tax adviser, future buyer, heir or registrar may later ask for evidence of original cost, source of capital, payment to the seller, expenses and title history. Preserve original formats, full statements, Swift or equivalent messages, receipts, signed amendments and correspondence.

Each record should have document date, receipt date, language, issuer, version, status and original location. A screenshot can be useful operational evidence but should not be the sole archive. Personal and bank data require role-based access; the public site must never expose real account numbers, passports or transaction references.

When to stop reconciliation and escalate

A ledger exposes problems but does not replace a bank, lawyer, accountant or technical specialist. Stop the next irreversible payment if the payee is unverified, an invoice conflicts with the SPA, a payment trigger is disputed, the seller refuses to provide a statement, the balance changes without signed authority, a refund is directed to a different payer without explanation or bank details may have been compromised.

Do not close an exception with an average exchange rate, assumed fee or intermediary message. A banking difference needs bank evidence; a contractual adjustment needs signed authority; a tax amount needs a current calculation by a competent adviser; a construction milestone needs appropriate evidence and, where necessary, professional review.

  • recipient is not documented as connected to the SPA seller
  • bank debited funds but seller does not recognise the credit
  • remaining balance was manually changed without authority
  • payment milestone is disputed
  • two seller statements conflict
  • refund or credit depends on an unsigned promise

The final payment record

Retain the contractual basis, verified instructions, invoice, bank evidence, UETR or other reference, credit acknowledgment, seller statement, milestone evidence, variances and their resolution.

A reviewer should be able to reconstruct the payment path without one manager’s inbox. Keep passport details and full account numbers out of public or shared files; use a controlled archive and redacted copies.

  • obligation, amount, currency and due event
  • contract version and supporting request
  • payer, payee and verified account
  • open banking, contractual and tax unknowns
  • reconciliation result and remaining balance
  • decision: proceed, conditional, pause or escalate
  • approver, date and next review point

When to pass the issue to the bank, lawyer or seller

NovAsia may help organise document requests, build the ledger, compare SPA, invoice, bank-detail and statement data, and frame questions for the parties. NovAsia is not a bank, payment system, auditor, tax agent or law firm and does not certify final performance without records from the responsible parties.

The actual contract, official Khmer text, bank rules on the transfer date and professional opinions take priority. If a live transaction reveals a conflict, the master package requires the conflict to remain visible rather than forcing the data into a template.

Directive on Customer Due Diligence Measures

Publisher: Cambodia Financial Intelligence Unit, National Bank of CambodiaChecked 24.07.2026
Open source →

Directive on Remittance and Wire Transfer

Publisher: Cambodia Financial Intelligence Unit, National Bank of CambodiaChecked 24.07.2026
Open source →

Revised Recommendation 16 and explanatory note on payment transparency

Publisher: Financial Action Task ForceChecked 24.07.2026
Open source →

Business Email Compromise and Real Estate Wire Fraud report

Publisher: Federal Bureau of InvestigationChecked 24.07.2026
Open source →

Brand name vs project company in Cambodia

Publisher: NovAsiaChecked 24.07.2026
Open source →

Property buyer document pack in Cambodia

Publisher: NovAsiaChecked 24.07.2026
Open source →

How to pay for an apartment in Cambodia from abroad

Publisher: NovAsiaChecked 24.07.2026
Open source →

Money transfers and payment safety

Publisher: NovAsia EstateChecked 23.07.2026
Open source →

Ready property and resale checklist

Publisher: NovAsia EstateChecked 23.07.2026
Open source →

Reservation agreement in Cambodia: checklist before booking

Publisher: NovAsiaChecked 24.07.2026
Open source →

How to transfer rental or property sale proceeds out of Cambodia

Publisher: NovAsia EstateChecked 24.07.2026
Open source →

Source of funds and payment trail

Publisher: NovAsia EstateChecked 23.07.2026
Open source →

What is a Unique End-to-end Transaction Reference (UETR)?

Publisher: SwiftChecked 24.07.2026
Open source →

Next step

Share only the minimum necessary records through an approved secure channel. Full account details and personal data are not published on the page.