Rent Payment Evidence — Workflow Guide
A reliable workflow does not wait for a dispute before collecting receipts. It creates a repeatable monthly cycle that starts before the due date and ends after the transfer has been matched, classified and archived. This reduces disagreements between landlord and tenant and keeps the property file ready for sale, audit or litigation. Article 313 of the Turkish Code of Obligations places the rent-payment duty on the tenant, while Article 315 addresses default. The workflow should also follow the current Revenue Administration rules for documenting rent collections and payments through banks or PTT.
Step 1: Freeze the due schedule
At the beginning of each cycle, extract the current rent, currency, due date, beneficiary and payment account from the controlling lease version. If rent or payment instructions have changed, update the schedule only after preserving the document that supports the change and its effective date. Use one line per rental period so differences are not hidden inside a yearly total.
Step 2: Issue clear payment instructions
When needed, give the tenant written instructions containing the beneficiary name, IBAN and a suggested transfer description identifying the month and property. Do not change the payment account through a casual message with no verification path. If the account changes, preserve the change notice, its source, effective date and evidence that the tenant received the instruction before payment became due.
Step 3: Use a channel that produces evidence
The Revenue Administration’s official rent-payment documentation guide, based on Income Tax General Communiqué No. 328, explains that covered residential and workplace rent collections and payments must be documented through banks or PTT. The previous TRY 500 housing threshold was removed when the communiqué was published on 17 October 2024. Use a payment method that produces a receipt or statement that can later be retrieved.
Step 4: Capture the source evidence immediately
Do not postpone archiving until year-end. When payment arrives, preserve the receipt or statement showing transaction reference, date, amount, payer and beneficiary. If the transfer description is vague, link the transaction manually to the correct rental period in the ledger without altering the original evidence. If a third party paid, record why the payment was accepted and who paid on the tenant’s behalf.
Step 5: Match payment against the due amount
Compare what was received with what was due for that period. Classify the result as full, partial, excess, late or unmatched. Do not allow the system to mark a month “paid” simply because some money reached the account. If one transfer covers more than one month or includes aidat or another charge, allocate the amount using documented support.
Step 6: Resolve differences in the same cycle
If there is a shortfall, request an explanation and preserve the correspondence. If there is an excess, determine whether it is a prepayment or an error requiring refund. For late payments, record the due date, payment date and affected period. Article 315 deals with default in rent and due ancillary expenses; any legal step should be based on a reproducible balance rather than a vague spreadsheet figure.
Step 7: Separate rent from security and other charges
Do not use the rent ledger as a general cash bucket. Create separate fields for security, aidat, utilities or compensation. Security in residential and roofed workplace leases is subject to Article 342 and should not be mixed with rental income. When one transfer includes multiple items, preserve the allocation and its basis.
Step 8: Perform a short monthly review
At month-end, answer five questions: was the due amount correct, was payment received, do payer and beneficiary fit the file, is the payment assigned to the correct period, and is any difference still open? A five-minute monthly review prevents six months of uncertainty from accumulating and appearing only when the property is being sold.
Step 9: Review patterns periodically
Every few months, examine the whole sequence for repeated third-party payers, beneficiary changes, claimed cash payments, chronic delay or unexplained amount changes. A pattern can reveal a problem that one month does not show. If recurring disagreement appears, open a separate dispute log instead of scattering notes throughout the payment ledger.
Step 10: Freeze evidence when a formal dispute starts
If a notice, mediation, lawsuit or enforcement procedure begins, create a dated snapshot of the ledger and the source documents on which the balance was calculated. Do not keep editing one live version until the historical position disappears. Since 1 September 2023, rental disputes within Article 18/B of the Mediation Law are generally subject to mandatory mediation before litigation, subject to statutory exceptions.
Step 11: At sale, update through title-transfer day
Prepare a final statement showing the latest due amount, latest payment, arrears and prepaid rent. State how each item is allocated between seller and buyer and attach the supporting bank evidence. Article 310 places the new owner into the lease relationship when ownership transfers, so the payment file should pass with the tenancy in a form that can be operated from day one.
Step 12: Close with a reproducible reconciliation
At year-end, lease end or ownership transfer, another reviewer should be able to total the due amounts, subtract the evidenced payments and reach the same balance. If that is not possible, the cycle is not closed. Record disputed sums separately and do not present them as confirmed debt or confirmed income until resolved.
Conclusion: A strong workflow makes rent evidence continuous rather than reactive: define the obligation, issue controlled instructions, use an evidential channel, preserve the source, match the payment, resolve differences, review patterns and reconcile. The result is a tenancy file that prevents disputes instead of merely documenting them after they arise.