Can You Get Turkish Citizenship by Buying Off-Plan Property, and What Does Tapu “Serh” (Annotation) Actually Need?

Atty. Serkan Kara | Istanbul Bar #53770 | Last updated: March 2026

Off-plan purchases can be eligible for Turkish CBI only if the transaction is structured in a legally registrable way that the citizenship real-estate workflow recognizes, which often means a notarized sales promise (promise-to-sell) contract plus the correct Land Registry annotation (serh) and a fully reconcilable bank payment trail. The most common failure is signing a developer contract and paying installments without securing the registry footprint early; if the registry step is missing or wrong, the investment may be treated as non-qualifying even if you paid the full amount. For the broader CBI legal map (valuation, DAB, rejection cures, E-2 bridge), start with: 2026 Turkish CBI Master Guide.

What does "off-plan" mean legally in Turkey?

"Off-plan" is a marketing term. Legally, your deal usually fits one of these:

• sale of an existing titled independent section (rare for true off-plan)
• notarized sales promise (promise-to-sell) contract to transfer title later
• consumer-facing housing delivery contract (facts can trigger Consumer Protection Law No. 6502)

Your citizenship risk is determined by the legal category and the registry footprint, not by the developer brochure.

Why does the registry footprint (tapu step) matter more than the contract?

Citizenship conformity relies on registry-recognized rights. A private contract that is not registrable or not registered can be:

• enforceable between parties, but
• insufficient for the administrative CBI workflow

In practice, the workflow expects either:

• title deed transfer (tapu devri), or
• an accepted alternative route where your notarized contract is annotated in the Land Registry with correct identifiers and required undertakings/restrictions

What is the difference between title deed transfer and a notarized promise contract + serh?

• Title deed transfer: you become the registered owner; strong and simple for compliance if money trail and valuation are aligned.
• Promise contract + serh: you do not become owner immediately; you register a claim/annotation against the property based on a notarized contract.

The second route is compliance-sensitive. If any identifier or party is wrong, the annotation may not support CBI conformity.

Which laws are the high-confidence legal anchors here?

Without over-claiming sub-article numbers, the core anchors are:

• Turkish Civil Code No. 4721 (property rights framework)
• Turkish Code of Obligations No. 6098 (contract law foundation)
• Title Deed Law No. 2644 and Land Registry practice rules (registry procedure and annotation practice)
• Consumer Protection Law No. 6502 (may apply to consumer housing delivery structures)

What must be in a notarized sales promise contract for it to be enforceable and registrable?

Minimum enforceability/registrability basics (conceptual):

• unambiguous property identity (parcel/block/independent section where available)
• clear parties with verified authority (developer/seller chain)
• price and payment terms (bank-only)
• transfer/delivery milestones and deadlines
• remedies: termination, refund, penalties
• cooperation obligations for registry steps (annotation, later transfer)

If the property identity is not final (common in early off-plan), you must handle that risk explicitly; otherwise, later "unit renumbering" can break the CBI chain.

What if the independent section is not fully formed yet (construction-stage identity risk)?

Many off-plan deals occur at a stage where the unit is described commercially but the official independent section identity is still being finalized. Risk controls:

• require documentary mapping between marketing unit codes and the official registry identity that will exist at transfer/annotation time
• avoid paying large sums before the identity mapping is stable and enforceable
• align valuation timing to the stage where the identity can be recorded consistently

If identity is unstable, your file can fail for reasons unrelated to value or payment amount.

What registry record types are commonly confused, and why does terminology matter?

Developers and non-lawyers often use "serh" as a catch-all. In practice, registry records can reflect different legal effects (annotations, declarations, restrictions) with different enforceability and workflow implications.

For CBI safety, the question is not the label. The question is whether the registry record you plan to rely on:

• is registrable for your exact contract type
• binds the correct property identity and parties
• supports the citizenship workflow posture (including required undertakings/restrictions where applicable)

If your plan depends on a registry record, require a written "what exactly will be recorded, against which unit, and under which party names" memo before you sign.

What is "serh" and what must the annotation contain to be CBI-safe?

Serh is a Land Registry annotation recording certain contractual rights/claims. For CBI risk management, the annotation must match:

• the exact property record (parcel and, where applicable, independent section)
• the correct seller/developer identity that is linked to the registry chain
• the buyer identity matching the citizenship applicant
• notary references (date, notary, contract ID)
• any required investment undertakings/restrictions used in the citizenship workflow (for example, a hold/transfer restriction undertaking where applicable)

If the annotation is recorded against the wrong unit, wrong buyer, or wrong seller, you may have paid but still not have a qualifying footprint.

What is the "double mismatch" risk in off-plan (unit identity + payee identity)?

Off-plan failures often combine two problems:

• unit identity is not final (or later changes), and
• installment payments are made to multiple beneficiary accounts over time

If both drift, cures become expensive: fixing unit identity forces you to rebuild the entire payment mapping, and fixing payee identity may require restructuring payments.

Lawyer rule: lock unit identity mapping and beneficiary logic early, before large payments.

What is the "undertaking / holding restriction" issue and why does it matter?

CBI real estate routes often involve a commitment not to dispose of the asset for a required holding period (commonly described as a three-year no-sale commitment in practice). In ready-title cases, this is typically reflected through a registry annotation/undertaking mechanism.

For off-plan structures, you must ensure:

• you can legally record the required undertaking in a way that is accepted for conformity, and
• your contract does not contain clauses that undermine it (for example, easy reassignment clauses that conflict with "no transfer" posture)

How do you protect against developer insolvency or non-delivery (practical contract levers)?

Off-plan risk is not only timing. Depending on facts and bargaining power, practical levers can include:

• objective delivery milestones and remedies (termination/refund triggers)
• explicit obligations to cooperate for registry steps (annotation and later transfer)
• documented mortgage-release mechanics if the land/project is encumbered
• payment milestones tied to deliverables and registrable steps

No clause is a magic shield, but contract engineering is how you reduce catastrophic risk in an off-plan CBI plan.

What are the developer risks unique to off-plan CBI (beyond normal real estate risk)?

Off-plan multiplies compliance failure modes:

• Delay risk: your timeline can exceed valuation staleness expectations.
• Identity drift: the promised unit changes or is renumbered; registry mapping breaks.
• Encumbrance risk: developer financing creates mortgages/encumbrances.
• Authority risk: the contracting entity is not the title holder or lacks authority.
• Payment mismatch risk: installments paid to different accounts/entities over time.

CBI files are "document truth" files. Developers optimize for sales velocity; you must optimize for evidence consistency.

How should you structure installment payments to stay CBI-safe?

Best practice rules:

• every payment must be bank-to-bank and receipted
• payer identity must match the applicant strategy (or be defensibly bridged)
• payee must match the seller entity that will support conformity (avoid third-party accounts)
• FX conversion evidence must map to each installment (or to grouped installments with a clean table)

If the payee changes, stop and re-check; do not "keep paying and fix later."

Should you sign with a power of attorney (POA) for off-plan deals?

POA can be practical for foreign buyers, but it increases risk:

• POA scope can be too broad or too narrow
• identity mismatches can occur if the POA holder signs inconsistent documents
• fast developer timelines can push signatures before legal review

If you use POA, control it: limit scope, require pre-approval of final documents, and keep the payment and registry plan consistent.

Can you assign an off-plan contract to someone else (and why is it a CBI risk)?

Some off-plan contracts allow assignment. For CBI planning, assignment is risky because it can conflict with:

• the required undertaking/holding posture
• the identity consistency across valuation, bank trail, and registry footprint

If your goal is citizenship compliance, treat assignment clauses as high-risk and get legal review before relying on them.

What due diligence is non-negotiable before signing any off-plan deal?

Minimum due diligence pack:

• registry record for the land and the project ownership chain
• encumbrances (takyidat) and developer financing posture
• zoning and permit status (municipality)
• developer corporate docs: signatory authority, trade registry extracts
• contract legal review (including termination/refund enforceability)
• annotation plan: what, when, and how will be registered at the Land Registry
• banking plan: compliant payer/payee + conversion evidence strategy

If a developer refuses to provide documents or pushes "sign first," treat it as a stop signal.

A CBI-safe off-plan timeline (conceptual)

If you want a low-friction file, plan backward:

1. pre-sign: due diligence + registry feasibility memo
2. signing: notarized structure executed in registrable form
3. before large payments: record the correct registry annotation where applicable
4. payments: bank-only and mapped to conversion evidence with beneficiary consistency
5. identity stabilization: ensure official unit identifiers are locked
6. final registry step: title transfer or completion of required registry footprint
7. conformity submission: one coherent pack (valuation + bank trail + registry steps match)

The earlier you lock registry footprint and identity, the less likely you are to pay into a non-qualifying story.

What are the most common off-plan failure scenarios (and what should you do)?

Scenario A: "We signed a contract, paid 30%, but there is no annotation."

• risk: non-qualifying footprint
• action: counsel reviews whether a notarized contract can be executed and annotated now, and whether payments can be reconciled to the eligible structure

Scenario B: "Payments went to a group company, not the seller entity."

• risk: money trail mismatch
• action: determine whether the payee can be legally tied to the seller and whether a cure pack is defensible; otherwise restructure

Scenario C: "Unit numbering changed; valuation and contract now conflict."

• risk: identity mismatch
• action: re-verify official unit identity and repair every document link (valuation refresh may be required)

Disclaimer (Off-plan / serh)

Informational only; not legal advice. Eligibility depends on exact contract language, registry record content, and current administrative acceptance practice.

FAQ (for FAQPage schema)

Q1: Can I qualify for Turkish CBI with an off-plan purchase?
A: Potentially, but only if the deal creates the registry-recognized footprint required by the workflow (often via notarized promise contract + correct annotation) and your bank payment trail is fully reconcilable.

Q2: What is "serh" at the Land Registry?
A: A registry annotation recording a claim/right against the property. For off-plan CBI structures, the annotation must match exact property identifiers and parties and align with the conformity workflow.

Q3: Is a developer contract enough by itself?
A: Often not. Private contracts that are not properly notarized/registered may not produce the qualifying footprint expected in the conformity process.

Q4: What is the biggest off-plan risk for citizenship applicants?
A: Paying money before securing a compliant registry step and a reconcilable money trail, leading to non-qualifying status or long delays.

Q5: Can I fix a missing or wrong annotation later?
A: Sometimes, but it can require contract amendments, re-annotation, and evidence restructuring. Prevention is far cheaper.

Q6: Do installment payments increase compliance risk?
A: Yes, because each payment must map to conversion evidence and the correct payee; installment structures amplify mismatch risk.

Q7: If the developer delays delivery, does that affect eligibility?
A: Delays can push you outside operational validity expectations for supporting documents and can make identity and registry steps harder. Off-plan CBI plans should include timing buffers and contingency options.

Q8: Can I rely on a verbal promise that the annotation will be done later?
A: No. If the registry footprint is a qualifying element of your strategy, it should be executed and documented as a formal, scheduled step, not as an informal future promise.