RERA-Linked Disbursement: A Practical Guide for HFC Credit Teams

What RERA-linked disbursement means, and why lenders use project status as a release gate

RERA-linked disbursement ties each tranche release to a project's status under RERA rather than to the borrower's word or a single sanction-time valuation. The Act requires most residential projects above a modest threshold — broadly, land over 500 square metres or more than eight units — to register with the state real estate regulatory authority before they can be marketed or sold. Registration produces a public record: the declared plan, approvals, the project's completion timeline, and periodic progress updates.

Because that record is maintained by a regulator and not the developer's sales team, lenders treat it as an independent gate. If a project is not registered when it should be, or its registration has lapsed, that is a reason to pause before releasing funds — long before you reach the narrower question of whether a particular floor has actually been cast.

What to cross-check: registration, validity, quarterly progress and declared milestones

A useful RERA cross-check is more than confirming a registration number exists. For the specific project and the specific unit — not the developer in general — verify:

• Registration and authority — the project is registered with the correct state body (MahaRERA, Karnataka RERA, UP-RERA and so on), and the registered promoter matches the entity in your loan file.
• Validity — registration carries a declared completion date. A project past that date without an extension is a flag, not automatically a stop, but it changes the conversation.
• Quarterly Progress Reports — promoters are required to file QPRs updating construction and financial progress. The declared tower, floors completed, and percentage of work done are the closest thing to an official stage statement you will get.
• Declared milestones and approvals — sanctioned plan, commencement certificate, and the tower or unit your borrower has booked actually existing in the registered inventory.
• Complaints and litigation — many state portals publish complaints and orders against the project. One promoter can run a clean project and a stalled one at the same time.

The gap RERA status alone leaves

Here is the limit. RERA tells you what the promoter has declared and what the regulator holds on file. That is paperwork status — official, useful, and often weeks old. A QPR filed for the quarter might tell you a tower was at the tenth slab in March; it does not tell you whether your borrower's specific unit is at plinth, brickwork, or finishing today. Quarterly reporting lags reality, declared progress is self-reported, and project-level percentages average across towers that may sit at very different stages.

For a lender releasing money against this unit at this draw, that gap is exactly where disbursement risk lives. RERA narrows the universe of acceptable projects; it does not verify the on-ground stage of the asset you are funding.

Pairing the cross-check with verified construction-stage evidence at each draw

This is why disciplined credit teams pair the RERA cross-check with independent, dated evidence of the actual construction stage at every draw. Traditionally that meant a site visit and an engineer's report — accurate, but slow, costly, and hard to standardise across a growing book. The modern alternative is geo-tagged, time-stamped photographs of the unit, assessed against the milestone the tranche is meant to fund.

This is the seam StageBridge is built for. Computer-vision models read the construction-stage photos, classify the stage, and return a confidence score, while the RERA status sits alongside as the independent paper check. The two are complementary: RERA confirms the project is legitimate and broadly on track; the stage evidence confirms that this unit has actually reached the milestone you are about to pay for. Neither leg alone is sufficient — together they make a draw defensible. The AI reads the evidence; a human still makes the call, and that call is what gets logged.

Building the audit trail: RERA data, stage evidence, confidence and the human approval

A disbursement decision is only as good as your ability to reconstruct it later for an NHB or RBI examiner. The defensible record for a tranche links four things in one place: the RERA data pulled (registration, validity, latest QPR) with the date it was retrieved; the stage evidence (the photographs, their GPS and timestamp); the model's stage classification and confidence score; and the name of the human who approved the release, with any notes.

StageBridge keeps this as an append-only log — entries are added, never edited or deleted — so the trail shows not just the final decision but the sequence that produced it. When an examiner or internal auditor asks why tranche three was released on a given date, the answer is a single linked record, not a hunt through email threads and a shared drive.

Common edge cases: loans outside project RERA, and stalled projects

Two situations break the clean RERA-linked flow, and credit teams should hold a written policy for both:

• Loans outside project RERA — self-construction on an owned plot, plotted developments, and small projects below the registration threshold simply will not have a project registration. Do not treat the absence as a red flag by reflex; treat it as a signal to lean harder on the other leg — verified stage evidence, the approved building plan, and local approvals — because the paper gate is not available here.
• Stalled or delayed projects — a project past its declared completion date, with registration lapsed, or with a spike in complaints, needs an explicit decision: pause draws, require a revised timeline or extension, or release against a narrower milestone with closer site verification. What matters is that the policy is written and the decision is logged, so a later reviewer sees a considered call rather than an oversight.

A per-tranche checklist before releasing funds

A practical sequence a credit team can apply to every draw:

• Confirm the project is RERA-registered with the correct state authority and the promoter matches the file.
• Check registration validity and whether the declared completion date has passed.
• Pull the latest QPR and note declared progress for the relevant tower or unit.
• Scan the state portal for complaints, orders, or litigation on the project.
• Obtain dated, geo-tagged evidence of the actual stage of this borrower's unit.
• Confirm the verified stage matches the milestone this tranche is meant to fund.
• Resolve any mismatch between declared (RERA) and observed (site) progress before releasing.
• Record the RERA data, evidence, confidence score, and approver in one append-only log.
• Have a named credit authority make and sign off the final release.

Run that on every draw and your disbursement decisions stop depending on memory or trust. They stand on their own record — which is exactly what an examiner will ask to see.