Payment Release Gate — DASK Earthquake Insurance
Define the relationship between insurance and the payment
DASK is legally checked in specified procedures for covered buildings, but a private payment-release condition in a property transaction remains contractual. The parties need to know which payment depends on obtaining a correct and valid policy. Do not use the label “DASK” to retain money without a written reason and do not let the condition expand automatically to every insurance or property risk.
Establish compulsory scope first
Before evaluating the policy, confirm whether the unit falls within compulsory earthquake insurance under Law No. 6305. If an exemption is claimed, resolve and document it before marking the gate ready. A payment condition is not satisfied merely because somebody buys a policy for the wrong unit or a property that does not match the transaction.
Evidence for a ready-to-release status
A practical minimum is a verifiable policy number, matching address, validity period covering the required transaction date, and correctly linked owner or right holder. Add evidence of issuance/premium where relevant and any available verification reference. If the contract requires another document, list it explicitly instead of hiding it inside a vague phrase such as “insurance documents.”
Do not rely on yesterday's validity
DASK is renewed annually. A policy checked weeks earlier may expire if the title appointment is delayed. The gate therefore needs the coverage end date and a final revalidation before funds move or before the insurance-dependent milestone specified in the contract. A prior “pass” cannot override expiry.
Separate DASK from voluntary building insurance
If a lender or buyer requires additional building insurance, create a separate condition. DASK has its own statutory scope and terms and is not equivalent to comprehensive property insurance. Combining them can lead parties to believe that a DASK check also proves fire, liability, contents or additional building-value cover when those may be separate products.
Look for obviously inconsistent underwriting data
The current tariff uses factors including risk group and construction type, with adjustments for certain building-age and floor-count characteristics. A payment gate does not need to become a full actuarial audit, but if policy data clearly contradict the property, stop release and seek correction. A paid policy based on evidently wrong property data should not be treated as comfortable evidence simply because a document exists.
Predefine the cure for each failure
Address mismatch means correction and reissuance/reconfirmation; expiry means renewal; an unverified number requires confirmation from the issuing channel; a claim of non-applicability requires evidence of registered use or legal category. Each failure should have a known cure before the closing date so that the transaction team does not improvise under time pressure.
Align the gate with payment timing
If the payment coincides with title transfer, make the DASK recheck part of the closing-day checklist. If payment occurs earlier, state clearly that early confirmation does not remove the need for valid DASK at a later legally controlled procedure. An early release should never be interpreted as proof that insurance remains valid months later.
Record the release and exceptions
At release, preserve the policy number, validity dates, verified address, source of confirmation, review time and approver. If the transaction accepts a minor exception that does not undermine validity, record it and its rationale. A material mismatch should not be downgraded to a post-payment note.
Closure standard
The gate closes when the contractual condition is precise, scope or exemption is documented, and the current policy can be verified, matched to the property and shown valid on the required date. The gate does not determine whether voluntary insurance is adequate and does not replace reading the DASK general conditions.