What Is a DAB (Foreign Exchange Purchase Certificate) and How Do You Avoid DAB Mistakes in Turkish CBI?

What does “DAB” prove in a citizenship-by-investment real estate file?

The conformity workflow must be able to answer, using documents, a simple question:

“Did the applicant invest eligible funds into the eligible asset, through the banking system, with a traceable and compliant chain?”

The DAB/conversion record is the bridge between:

• foreign currency source (incoming transfer / account history)
• TRY payment (seller/developer receipts)
• the transaction that is registered (tapu transfer or eligible annotation)

If that bridge is missing or inconsistent, the file is exposed to deficiency notices or a negative conformity assessment.

Where does this requirement come from (what laws and processes are in the background)?

The citizenship framework is anchored in Turkish Citizenship Law No. 5901 and its implementing regulation (as amended to include investment routes). The real estate route is operationalized through:

• TKGM / land registry workflows (property identity and registry steps)
• banking and AML compliance expectations (Law No. 5549 practice)
• administrative document checklists that require a coherent payment narrative

Practical takeaway: even if different offices phrase the evidence list differently, the same principle is enforced: the money trail must be clean, bank-based, and reconcilable.

Which bank issues the DAB/conversion record and what details must match?

The bank handling the conversion/payment path issues the relevant conversion evidence. The high-risk fields that must match other documents are:

• applicant identity (name + passport/ID references)
• currency in, TRY out, and conversion rate details
• conversion date/time (often becomes the “anchor date” in reconciliation)
• bank transaction references that can be mapped to receipts
• payer/payee names on the outgoing TRY transfer

If a developer, agent, or third party “handles” the funds, you must assume extra scrutiny and design the beneficial-owner narrative carefully.

When must conversion happen relative to payment and registry steps?

The safest sequence (design your file around it):

1. source funds are documented and enter the banking system (in a way that matches your story)
2. FX is converted (documented)
3. TRY is paid to the correct seller/developer (documented)
4. the registry step is completed (tapu transfer or eligible annotation)
5. the conformity application is submitted with a single coherent reconciliation pack

Common failure sequences:

• payment happens first; conversion evidence appears later with no clean linkage
• conversion exists but payments are split across accounts without mapping
• payer/payee identities drift (different people/entities)

What is the fastest way to “de-risk” DAB before you pay anything?

Build a one-page reconciliation table before the first transfer. Your table should tie every number to a document.

Example (simplified):

If you cannot produce this table, you are not ready to file.

What are the most common DAB mistakes that trigger rejection or long delays?

High-frequency failure modes:

1. Wrong payer: spouse/relative/company pays, but the applicant is different.
2. Wrong payee: payment to an intermediary, “collection account,” or group company that is not the seller in registry/contract.
3. Timing mismatch: conversion after payment, or conversion far from payment with no mapping.
4. Split flow with no mapping: multiple conversions + multiple receipts without a clear table.
5. Currency mismatch: receipts in a different currency than valuation/contract without conversion evidence.
6. Identity mismatch: name spelling and passport references differ across documents (transliteration errors).
7. Cash-like flows: multiple internal transfers that weaken the beneficial-owner story.

What happens if you need to refund and re-pay (cancellation, unit change, developer restructure)?

Refunds are a hidden DAB risk because they create “broken chains” in bank records. Risk controls:

• keep refunds in the same banking ecosystem (avoid cash withdrawals)
• document why the refund occurred (contract addendum, termination letter)
• re-build the reconciliation table for the new payment path
• avoid mixing refunded funds with unrelated account flows before re-paying

If a unit change occurs (new unit identity), assume you may need a refreshed valuation and a fully updated compliance binder.

How should you handle installment payments (off-plan schedules) without breaking DAB reconciliation?

Installments are compatible with compliance only if you structure them intentionally:

• create a mapping for each installment (conversion event -> receipt)
• avoid mixing personal accounts and third-party senders
• keep payer/payee constant (or document why any change is unavoidable)
• maintain a “running reconciliation” that you update after each payment

If the developer changes the beneficiary account mid-project, treat that as a red flag and re-check compliance before sending any further funds.

Can you use multiple banks or multiple accounts?

You can, but every additional account is a new place for mismatch to occur. Best practice:

• keep the number of accounts minimal
• keep the beneficial owner consistent
• maintain a single table mapping conversion and payments across all accounts
• obtain bank confirmations when funds move between banks so the trail does not look like “unexplained hopping”

If you use multiple banks, your file must be even more disciplined about transaction IDs and mapping.

How do gifts and intra-family transfers affect DAB compliance?

Family money is one of the most common sources of “quiet mismatch.” If funds are gifted or transferred from a family member:

• document the gift/transfer basis in a way that is consistent with the source-of-funds narrative
• keep the banking path simple (avoid multiple hops that look like layering)
• ensure the final payer identity and the contract/title structure match the applicant strategy

If the spouse or parent is the payer but the applicant is different, you need a defensible bridge (and you should assume scrutiny). The safest pattern is to align the payer to the applicant unless counsel designs a documented alternative.

What if the seller asks you to pay to a third-party account?

Assume high risk. Third-party payment creates three problems:

• beneficial owner ambiguity (AML)
• payee mismatch with the seller in registry
• difficulty proving the investment was made into the eligible asset

If a third-party payment is unavoidable, you need a lawyer-led structure with written justification, corporate chain evidence, and bank-confirmed mapping. Otherwise, your safest choice is to walk away.

What if your funds come from crypto or multiple jurisdictions?

You can still build a compliant trail, but do not improvise:

• document lawful acquisition and conversion to fiat
• show exchange records + bank deposits
• keep a straight bank trail from fiat deposit to conversion and seller payment

If your story requires five different platforms and accounts, expect scrutiny. Simplicity is a compliance asset.

Can you fix a DAB mistake after it happens (and what fix options exist)?

Yes, but your cure depends on the failure mode.

Option A: bank correction pack (best when the underlying flow is compliant).

• corrected certificate / letter referencing transaction IDs
• bank letter confirming payer identity and conversion mapping
• consistent translations and identity matches

Option B: supplemental reconciliation pack (works only when the flow is truly reconcilable).

• reconciliation table
• sworn explanation + supporting bank confirmations
• proof of beneficial ownership

Option C: restructure (required when the underlying flow is not compliant).

• new compliant conversion + payment trail
• re-align the investment evidence (may require redoing registry steps)

Avoid “paper fixes” that contradict bank data. If your bank records do not support the story, more PDFs usually increase risk.

A bank letter template outline your counsel can request (conceptual)

Ask the bank for a letter that:

• identifies the applicant and account
• references specific incoming transfer(s)
• references the conversion transaction ID(s)
• references the outgoing TRY transfer(s) to the seller
• confirms the applicant is the payer/beneficial owner

The letter should not contain legal conclusions, only factual confirmations tied to transaction IDs.

What if the bank refuses to issue a confirmation letter?

Some banks will not issue customized letters. Alternatives:

• request standard transaction confirmations that show transaction IDs clearly
• obtain official account statements showing incoming transfer, conversion, and outgoing payment in a continuous time window
• ensure receipts contain full payer/payee legal names and references

If the bank’s documentation is too thin, consider switching to a bank that supports the documentation needs before you execute the critical transfers.

What should you do before you sign if you are buying jointly with spouse or business partners?

Joint structures multiply mismatch risk. Do this before paying:

• decide the ownership shares and confirm how they will appear in registry/contract
• decide who will be the payer(s) and ensure each payer maps to their share
• prevent “one pays, another owns” unless you have a defensible documented structure

Evidence discipline: what should you save to keep the bank trail provable?

For conformity and later audits, prioritize bank-issued documents that carry transaction identifiers:

• official bank statements covering the relevant time window
• bank receipts/transfer confirmations showing payer and payee legal names
• conversion evidence that references transaction IDs and dates

Screenshots can be useful for quick internal tracking, but they are not a substitute for bank PDFs or official confirmations when a file is challenged.

Why using an agent or friend to “simplify transfers” usually backfires

Intermediaries create payer/payee mismatch and weaken beneficial owner clarity. If an intermediary is unavoidable, the structure must be designed intentionally (document basis, authority, and mapping), otherwise you are building a rejection-ready money trail.

Disclaimer (DAB)

Informational only; not legal advice. Document expectations can vary by bank compliance practice and by operational interpretation at the time of filing.