Reconciling competing versions of a lease file
Lease due diligence becomes unreliable when the file contains more than one contract, an unsigned amendment, a tenant copy that differs from the seller’s copy, or a rent schedule that cannot be traced to a signed change. The correct response is not to choose the newest-looking PDF. A document-version reconciliation reconstructs how the lease evolved and identifies which terms are currently supported by executed documents and by the parties’ actual performance.
Create a document lineage before interpreting the terms
List every version chronologically: original lease, renewals, protocols, rent-change letters, deposit receipts, handover records and later settlements. For each item record its date, signatories, page count, referenced property and whether it refers to an earlier document. Do not merge two files into a “clean” composite until their relationship is proven. A later protocol may amend only the rent while leaving the rest of the original agreement in force; another document may replace the entire agreement. The text and signatures, not the filename, determine the relationship.
Reconcile the identity fields first
Before comparing economic clauses, check whether all versions describe the same lessor, tenant and independent unit. Address changes caused by municipal renumbering should be supported by an explanation that still connects the unit to the title-deed record. A change of owner does not necessarily require a new lease because Article 310 of the Turkish Code of Obligations provides that the new owner becomes a party when ownership changes after the lease is formed. Therefore an older contract showing the former owner may remain relevant, but the ownership transition must be documented rather than silently editing the landlord name in a copy.
Build a clause-by-clause change table
Compare commencement date, term, monthly rent, payment day, bank account, permitted use, common-expense allocation, security, maintenance obligations and any special termination provisions. Mark each item as unchanged, amended, superseded or unclear. This is particularly important for security because Article 342 limits agreed security in residential and roofed workplace leases to three months’ rent. If one version states a different amount, identify whether it is a lawful later arrangement, a separate advance or simply an error.
Use performance records to test which version was actually followed
Bank payments can show whether a later rent amount was put into practice, but payment history does not by itself validate every clause in an unsigned draft. Likewise, a tenant paying to a new bank account may prove an operational change without proving that all other contractual terms changed. Compare payment amounts, narratives and dates with the purported amendment. Where the parties’ conduct conflicts with the written versions, record the conflict explicitly and obtain legal advice before treating one source as controlling.
Keep termination and eviction documents in their own branch
A notice, mediation minute, court settlement or written evacuation undertaking is not merely another “version” of the lease. It may create or evidence a separate legal step affecting possession. Article 352 addresses written undertakings to vacate made after delivery, while other termination routes are governed by different provisions. Preserve these documents with their own dates and status instead of folding them into a rewritten lease summary.
Produce one reconciled index, not one artificial contract
The safest output is a document map identifying the current lease base, every amendment that remains relevant, the evidence of performance and every unresolved inconsistency. If the file must be used for a purchase decision, financing or handover, the map should state the exact version set relied on and the date of review. This gives the buyer a defensible record without manufacturing a document the parties never signed.