Every real estate project, whether in Mumbai or Dubai, runs on trust. Homebuyers pay upfront. Developers build over years. Somewhere in between sits a RERA escrow account, the legal mechani...
Every real estate project, whether in Mumbai or Dubai, runs on trust. Homebuyers pay upfront. Developers build over years. Somewhere in between sits a RERA escrow account, the legal mechanism meant to protect that trust.
The model shows up under different names across markets. India’s Real Estate Regulatory Authority runs it under the RERA Act, 2016. Dubai’s Real Estate Regulatory Agency, also called RERA, enforces its own version under Law No. 8 of 2007. Other Gulf and global markets are moving toward similar buyer-protection frameworks. The name is the same. The underlying risk to banks is nearly identical too.
But here’s the uncomfortable truth. The bank holding that account often carries more risk than it realizes. Not credit risk. Not market risk. Operational risk that hides in plain sight.
This is the RERA escrow account blind spot. And it’s time banks, in India, the Middle East, and beyond paid attention.
In India, the Real Estate (Regulation and Development) Act, 2016, changed how developers collect and use buyer money. Under Section 4(2)(l)(D), developers must deposit 70% of funds collected from buyers into a separate RERA escrow account. This money can only be used for construction and land costs of that specific project. Not for other projects or corporate expenses. Not for debt repayment elsewhere. The remaining 30% goes into a regular account, usable more freely.
In Dubai, the structure differs slightly but the intent is identical. Developers must open a dedicated project escrow account with a RERA-approved bank before selling a single unit off-plan. Withdrawals are tied to construction milestones, certified and monitored by the regulator’s appointed engineer and auditor, rather than a fixed percentage split.
Across markets, the core idea stays constant: buyer money gets ring-fenced, and a bank sits in the middle as custodian.
Sounds simple. It isn’t.
RERA puts the compliance obligation on developers. But banks become the gatekeepers by default. Every escrow account needs a banking partner. And that partner inherits a set of duties the Act never fully spells out.
Here’s where the blind spot begins.
RERA frameworks require withdrawals from the escrow account to be certified by qualified professionals, an engineer, an architect, and a chartered accountant in India; a project engineer and registered auditor in Dubai. These certificates confirm that construction has progressed enough to justify the withdrawal.
The bank’s job? Release funds only after verifying these certificates exist and match the withdrawal request.
But most bank branch staff aren’t trained construction auditors. They’re not equipped to judge whether a certificate is genuine, whether the percentage of completion claimed is accurate, or whether the same certificate has been reused across multiple withdrawal requests.
Banks end up performing a quasi-regulatory function without the tools, training, or legal mandate to do it well.
Each RERA-registered project needs its own separate escrow account. A developer running five projects needs five distinct accounts, each governed independently.
In practice, developers sometimes maintain overlapping banking relationships, similar account naming conventions, and shared signatories across projects. A single lapse in internal controls at the bank, a wrong account tagged during a transfer, a signatory approved for the wrong project, creates a compliance breach that isn’t easily reversed.
Cross-contamination of project funds is one of the most common and least discussed risks in this system.
RERA expects that money in the escrow account is used strictly for construction and land cost of that project. But banks typically monitor transactions after the fact, not in real time.
By the time a suspicious pattern is flagged, repeated large withdrawals, transfers to unrelated vendors, or payments that don’t match typical construction cash flow, the funds may already be diverted.
This delay between disbursement and detection is where real damage happens. A bank isn’t just processing a transaction. It’s the last checkpoint before buyer money leaves its intended purpose.
Unlike core banking compliance areas like KYC or AML, RERA escrow account management doesn’t have a uniform, standardized operating framework across banks. Different banks interpret “withdrawal certification,” “project completion percentage,” and “fund utilization proof” differently.
This inconsistency creates two problems. First, developers can shop for banks with looser interpretation of compliance steps. Second, when disputes arise, a delayed project, an angry homebuyer association, a RERA authority inquiry, the bank’s own process becomes a liability if it can’t demonstrate consistent due diligence.
If an engineer or CA issues a fraudulent completion certificate, and the bank releases funds based on it in good faith, who bears the consequence?
Legally, the bank followed procedure. Practically, buyers and regulators often view the bank as complicit, especially if red flags were visible and ignored. This reputational exposure rarely shows up in a risk register, but it’s very real.
Behind every RERA escrow account is a family that paid its life savings for a home. When funds get diverted, or a project stalls because money that should have been available wasn’t tracked properly, the fallout isn’t abstract.
Homebuyers file complaints with RERA authorities. Developers face project delays or blacklisting. Banks face regulatory scrutiny, reputational damage, and sometimes litigation.
The irony? The RERA escrow account was designed specifically to prevent this outcome. When operational gaps exist at the banking layer, the very safeguard meant to protect buyers becomes a false sense of security.
Most banks treat RERA escrow accounts as a documentation exercise. Open the account. Collect the registration certificate. File the paperwork. Move on.
But escrow accounts under RERA aren’t static. They require ongoing verification tied to construction milestones, a process that spans years per project. Bank staff turnover, inconsistent training, and lack of dedicated RERA compliance teams all widen the gap between what the law requires and what actually happens on the ground.
Add to this the sheer volume. A single mid-sized bank can be the escrow banker for dozens of real estate projects simultaneously, across different cities, each with different milestones, certificates, and withdrawal schedules. Without dedicated systems, this becomes an operational maze.
The good news: this blind spot is fixable. It requires intent, not reinvention.
Build a dedicated RERA compliance desk. A specialized team, even a small one, that understands construction certification, RERA rules, and red flags in fund utilization, changes the game. Generalist branch staff shouldn’t be the last line of defense on high-value withdrawal approvals, whether the currency is rupees or dirhams.
Digitize certificate verification. Manual certificate checking is slow and error-prone. Digital verification workflows, cross-referencing engineer and CA registration numbers, and flagging duplicate or reused certificates reduce fraud risk significantly.
Set up real-time transaction monitoring for escrow accounts. Rule-based alerts for unusual withdrawal patterns, mismatched vendor payments, or withdrawals exceeding certified construction progress should trigger immediate review, not a monthly audit.
Standardize internal SOPs across branches. Every branch handling a RERA escrow account should follow the same checklist. Consistency protects the bank legally and operationally.
Maintain project-level audit trails. Clear, timestamped records of every certificate received, every withdrawal approved, and every query raised protect the bank if a dispute or regulatory inquiry arises later.
Train relationship managers on RERA fundamentals. They don’t need to become engineers. But they need to recognize red flags: a completion certificate that seems disproportionate to the construction timeline, or a withdrawal request pattern that doesn’t match typical project cash flow.
RERA escrow accounts exist because real estate sectors worldwide needed a trust mechanism. Buyers needed assurance their money wouldn’t vanish into unrelated projects or corporate debt. Regulators, from Mumbai to Dubai, needed a lever to enforce discipline in off-plan sales.
Banks became the custodians of that trust, almost by accident of their role in the payment chain. That role comes with responsibility that goes beyond opening an account and processing transfers.
The operational risk isn’t hypothetical. It’s structural, built into how the system currently works. Every unmonitored withdrawal, every unverified certificate, every inconsistent process is a small crack. Enough cracks, and the entire purpose of the RERA escrow account collapses.
The RERA escrow account was never meant to be a passive holding account. It’s an active compliance instrument. Banks that treat it as paperwork inherit risk they don’t fully see, until something goes wrong.
The fix isn’t complicated. It’s disciplined. Dedicated teams, digital verification, real-time monitoring, and standardized processes turn a blind spot into a strength.
Because in the end, the RERA escrow account isn’t just about money sitting in a bank. It’s about keeping a promise made to thousands of families who trusted the system to protect their savings.
Banks that recognize this responsibility early won’t just avoid risk. They’ll build the kind of credibility that developers and regulators actively seek out.
Have questions about RERA escrow account compliance for your bank or developer entity? A structured audit of your current withdrawal and certification process is often the first step toward closing the gap. Schedule a free consultancy with RERA Escrow accounts experts now.
