Encumbrance Certificate Fraud Patterns: Odisha Advocates' Field Guide

A NIL Encumbrance Certificate (Form 25) confirms one specific thing: no encumbrances were registered at the searched Sub-Registrar office for the searched property over the searched period. It does not confirm ownership, freedom from court orders, or absence of unregistered charges. Five fraud patterns repeatedly surface in Odisha property files even when the EC reads clean. This guide is a field reference for advocates.

Pattern 1: Multi-SRO splitting

A property's transactions are deliberately registered at different Sub-Registrar offices to fragment the audit trail. A search at the property's jurisdictional SRO returns NIL because the offending registrations were filed at an adjacent SRO.

How it works. The seller registers a mortgage at SRO Bhubaneswar Sadar instead of the property's actual jurisdiction (SRO Bhubaneswar). An EC search filtered to the actual jurisdiction misses the mortgage entirely.

How to detect. Pull EC searches at all SROs within the District. Some Districts have 3 to 5 SROs; checking only one is incomplete. Bhubaneswar District alone has 6.

Corroboration. Cross-reference the registered Sale Deed with its SRO of registration. If the SRO of registration is not the jurisdictional SRO, expand the EC search to all SROs the property could have been registered at.

{{EDUCATION_CTA}}

Pattern 2: Backdated discharge entries

A subsisting mortgage is recorded on the EC. The seller produces a release deed dated within the EC search window but the release deed is not visible on the EC. The release deed is then claimed to have been "filed late."

How it works. Either the release deed is forged with a backdated date, or the release deed is genuine but unregistered (and therefore legally ineffective for clearing the mortgage).

How to detect. Compare the release deed registration number against the EC chronology. A genuine release deed will appear on the EC at its registration date. A backdated forgery will not appear at all on the EC. An unregistered release deed exists only on paper and does not discharge the mortgage.

Corroboration. Pull the certified copy of the release deed directly from the SRO using the deed's registration number. If the SRO has no record, the deed is forged or unregistered. Either way, the mortgage subsists and the property is not transferable.

Pattern 3: Pre-EC-window encumbrances

The EC is searched for 12 years. A mortgage registered 13 years prior is not on the EC. The seller represents the property as encumbrance-free.

How it works. Sellers commission narrow EC searches deliberately to surface only the most recent activity. Pre-window mortgages, especially long-term equitable mortgages or government dues, do not appear.

How to detect. For high-value transactions, always request a 30-year EC at minimum. For properties acquired more than 12 years ago, the EC must cover the seller's entire tenure plus a buffer.

Corroboration. Read the chain of Sale Deed Certified Copies. Any mortgage encumbrance recorded in a prior Sale Deed but absent from the EC indicates either a pre-window encumbrance or a missing EC search.

Pattern 4: Fake Tahasildar mutation entries

The seller produces a mutation order receipt that does not exist in the Tahasildar's records. The Khatiyan on Bhulekh has been informally updated to show the seller as current owner via insider data entry, despite no order having been actually issued.

How it works. Insider corruption at the Tahasil office. The Bhulekh display can be manipulated by data entry operators with sufficient access; the underlying paper Settlement file remains in the predecessor's name.

How to detect. Pull the certified Khatiyan from the Tahasildar in person. The certified copy is signed by the Tahasildar; the data entry version on Bhulekh is unsigned. A mismatch between certified copy and Bhulekh display indicates manipulation.

Corroboration. Match the mutation case number on the seller's order receipt against the Tahasildar's case register. A genuine order has a register entry; a fake one does not.

{{FEAR_CTA}}

Pattern 5: Lis Pendens not filed at the SRO

A civil suit is pending against the property at the District Court. A Lis Pendens notice was filed at the court but not at the SRO. The EC, which only reflects SRO-registered entries, is silent on the litigation.

How it works. Section 52 of the Transfer of Property Act creates Lis Pendens by operation of law when a suit is filed; formal filing at the SRO is not mandatory in Odisha. So a property under active litigation can show a clean EC.

How to detect. A separate court records search at the District Court, the High Court, and any consumer forums. Search by the seller's name and by the property address.

Corroboration. A Lis Pendens search is a paid service from court record agents or can be self-conducted at the court's filing cell. For high-value transactions, this search is mandatory regardless of EC status.

Combining the EC with the Khatiyan and the Sale Deed

A title verification report that reads only the EC misses all five patterns above. The standard advocate workflow combines:

• Khatiyan: Confirms current owner per the Tahasildar's record, including the mutation register
• EC: Confirms registered SRO entries within the search window and at the searched SRO
• Sale Deed CCs: Confirms the chain of registered transfers and historical encumbrances

Each artefact answers a different question. A clean EC plus a contradictory Khatiyan signals Pattern 4. A Sale Deed mortgage entry absent from the EC signals Pattern 3 or 1. A mortgage on the EC without a discharge entry signals Pattern 2.

Real Odisha cases where pattern detection saved the file

A buyer in Cuttack received a 12-year NIL EC and a Sale Deed showing the seller's father had taken a mortgage in 2007. The EC search began in 2014, missing the 2007 mortgage. A 30-year EC pulled subsequently showed the mortgage subsisted because no release deed was registered. Pattern 3 caught.

A buyer in Khordha relied on a clean EC and a Bhulekh display showing the seller as current owner. An advocate-pulled certified Khatiyan from the Tahasildar showed the predecessor still listed; the Bhulekh display had been manipulated. Pattern 4 caught.

A buyer in Bhubaneswar saw a clean EC. A separate court search revealed an active partition suit filed by the seller's brother. Pattern 5 caught. The transaction was abandoned.

What to ask of any tool that automates EC reading

Four questions:

1. Does the tool flag SROs within the District where the property could have been registered, beyond the primary jurisdictional SRO?

2. Does the tool flag any mortgage entry without a paired discharge entry?

3. Does the tool recommend (or refuse to certify completeness) when the EC search window is shorter than the seller's tenure?

4. Does the tool decline to certify clear title on the EC alone, requiring Khatiyan and Sale Deed CCs as inputs?

Tools that compress the EC into a single "encumbrance free" verdict cannot detect any of the five patterns above.

{{FINAL_CTA}}