What a payment exception register is for
A payment exception register is not merely an accounting error list. It is a transaction-control tool that records any gap between what the contract says has been paid and what the banking evidence actually proves. Property transactions can contain reservation fees, deposits, instalments and a closing balance, sometimes across different currencies and accounts. Without a structured register, a file can appear complete even though a material amount is unexplained, a beneficiary differs from the seller, or a receipt cannot be tied to the property.
Fields to reconcile for every payment
For each movement record the amount, currency, value date, payer, beneficiary, IBAN or account identifier, bank reference, payment narrative, contractual stage and the document showing how it is credited against the purchase price. For a foreign-buyer transaction, link any applicable DAB or foreign-exchange evidence to the same payment trail rather than storing it in isolation. TKGM lists DAB among foreign-buyer documents and, in procedures such as citizenship-by-property, requires bank-approved transfer evidence, illustrating why the banking trail must be reproducible.
Classify exceptions by impact, not by how easy they are to fix
A minor difference in transfer wording can be low risk where amount and parties match and the bank can explain the reference. A payment to a different beneficiary, a personal account, a materially short amount or a manually altered receipt is different. Use practical severity levels such as missing information, explainable mismatch, material mismatch blocking the next payment, and potential fraud requiring immediate escalation.
Do not close an exception with an oral explanation
Every exception needs closure evidence. If a beneficiary name is abbreviated, a bank statement or bank letter may establish the account holder. If several obligations are settled through one transfer, a signed allocation schedule and bank evidence may be needed. If a third party pays on behalf of the buyer, the legal and contractual basis should be documented so that the payment does not create a later dispute over who discharged the obligation. A broker saying “this is normal” is not a substitute for evidence.
Connect the register to the payment-release gate
The register only becomes an effective control when it changes decisions. Adopt a rule that open material exceptions block the next significant payment or closing until they are resolved, or until a named authorised decision-maker accepts the residual risk in writing. Sales pressure should not be the sole basis for overriding a banking discrepancy. High-value exceptions should receive independent review.
Examples requiring special attention
Common cases include a card-paid reservation fee that was never credited against the price, a transfer from a relative’s account, a mismatch between the contracted seller and the bank account holder, two transfers carrying the same reference, payment in a different currency without a documented conversion basis, a partial refund missing from the schedule, or a screenshot of a receipt that cannot be authenticated. Each should be converted into a precise question, required document and deadline.
Preserve the history when a payment is corrected
If a transfer was wrong, do not rewrite the historical register so that the error disappears. Keep the original evidence and record the reversal, refund or corrected transfer as a separate movement. This preserves the audit trail and prevents confusion in later accounting or legal review. If money was returned and paid again, both flows should remain visible rather than showing only the final net position.
What belongs in the closing file
Keep unaltered payment receipts, relevant bank statements or confirmations, DAB where applicable, the payment schedule, the exception register, the closure evidence for each exception, and the contract or amendment explaining how each amount is treated. Give every exception a unique identifier, opening date, owner and closing date. The result should be reviewable by an accountant, lawyer or internal auditor without relying on memories of the transaction.
Limits of the register
The exception register does not by itself determine whether a transaction is legally valid and it does not replace title, seller-authority, tax, encumbrance or technical checks. Its role is narrower but important: it prevents the file from stating “paid” unless a consistent evidence chain supports that conclusion. International transfers, third-party payment structures and large unexplained differences may require input from the bank, Turkish counsel or a financial adviser.
Additional questions and context
What is a material payment exception?
A mismatch that can change whether payment was validly made, such as a different beneficiary, unexplained amount or account unrelated to the seller.
Can a broker’s explanation close an exception?
No. Closure should rely on verifiable bank or contractual evidence.
Should an erroneous transfer be deleted after correction?
No. Preserve the original movement and record the refund or correction separately.
When should an exception block the next payment?
When it is material or affects beneficiary identity, payment validity or fraud risk.
Does a DAB replace the payment register?
No. DAB is one item of evidence where applicable; the register reconciles the entire payment history.