A channel partner walks in with a buyer. The unit is good, the price works, the booking closes the same evening. Everyone shakes hands. Three months later the authority asks a simple question during a routine check — what is the registration number of the agent who facilitated this sale? — and nobody in the room has an answer. That silence has a price, and increasingly it is the builder, not the broker, who pays it.

What Section 9 actually says

The Real Estate (Regulation and Development) Act, 2016 — RERA — is a central law implemented by each state's authority, GujRERA and MahaRERA among them. Section 9 is blunt: no real estate agent may facilitate the sale or purchase of any plot, apartment, or building in a RERA-registered project without first being registered with the authority. Registration produces a number, and that number is meant to travel with the agent — quoted in dealings and recorded against the transactions they broker.

It is not a one-time formality that sits in a drawer. The point of the number is traceability: the authority wants to know that every person putting a buyer into a regulated project is themselves accountable to the regulator.

And what Section 62 costs

Section 62 attaches the penalty. If an agent contravenes Section 9 — operating without registration — the liability is ten thousand rupees for every day the default continues, and it can cumulate up to five per cent of the cost of the plot, apartment, or building for which the sale or purchase was facilitated. Read that twice. It is not a flat fine. It compounds daily, and the ceiling is tied to the value of what was sold.

  • Agents facilitating deals in registered projects without their own RERA registration.
  • Builders paying commissions to whoever brought the buyer, without recording whether that partner is registered.
  • Sales teams handing 99acres and MagicBricks leads to informal sub-brokers who close in the builder's name.
  • Projects where the same partner's number is quoted on one booking and missing on the next.

Here is the part builders underestimate: you cannot fully hide behind "that was the broker's problem." When an unregistered agent facilitates a sale in your registered project, the transaction is on your project record. The authority's scrutiny starts with your bookings and works outward to the people who made them. If your books cannot show a valid registration number against each externally-sourced booking, you are the one explaining the gap.

Every booking in a registered project should trace back to a registered agent. On a busy channel-partner network, that is a data problem before it is a legal one.
Every booking in a registered project should trace back to a registered agent. On a busy channel-partner network, that is a data problem before it is a legal one.

Why builders get caught

Almost nobody sets out to break this rule. They get caught because the commission follows the buyer, and the paperwork follows the commission — loosely. A 1-to-3 project builder running fifteen or twenty channel partners rarely has a clean, current list of which partner holds a valid RERA number and which one lapsed. The number lives in a WhatsApp forward, or a scanned certificate in someone's email, or nowhere at all.

  • Commissions are approved on trust because the partner "always brings good buyers."
  • No single place captures each partner's RERA number, its validity, and the bookings tied to it.
  • Lead sources — portals, walk-ins, referrals — are not linked to the registered agent who eventually closed.
  • When the quarterly project update or a scrutiny lands, the reconciliation is done by hand, from memory.
Construction moves on schedule. Compliance records usually don't — until you make capturing them part of the booking itself.

What a RERA-aware system does

The fix is not another folder of certificates. It is making the registration number a required field of doing business, captured once and enforced everywhere.

  • Stores each channel partner's RERA registration number and its validity, and flags the ones that have lapsed before a payout goes out.
  • Ties every booking to a registered agent, so no unit is sold in your project by someone the record cannot account for.
  • Keeps channel-partner commissions structured — earned, approved, paid — against the right registered partner.
  • Links portal and referral leads to the agent who actually closed, so the source and the registration line up.
  • Keeps booking and collection records in a shape you can hand to the authority without a week of reconstruction.

Where the CRMs fit — and where they don't

There is good software in this space, and it is worth naming fairly. Sell.Do is genuinely built for real estate and does a lot well — but at roughly ₹20,000 to ₹60,000 a month it is priced for large developers with big sales engines, not a builder running two or three projects. Zoho is affordable and endlessly flexible, but that flexibility is the catch: it is a generic CRM that knows nothing about RERA numbers, construction-linked demand letters, or a co-buyer part-payment split until you build all of it yourself. LeadRat is sharp on lead capture and speed-to-call, which matters, but a fast lead funnel is only the front half of the job.

The gap is the mid-market: the builder too big for spreadsheets and too small for Sell.Do. That is exactly where BizRevolt sits. It captures each partner's RERA registration number, keeps channel-partner commissions clean, generates construction-linked demand letters, handles co-buyer part-payment splits, and shows live unit availability — built around how Indian real estate actually transacts, at ₹999, ₹1,599, and ₹2,499 per user per month. One avoided Section 62 exposure pays for years of it.

If your channel-partner list is really a pile of screenshots, that is worth fixing before the next scrutiny, not after. Message us or call +91 91 0657 4865 and we will map it to your own projects and partners, not a generic demo.

Image credits: cover by Moheen Reeyad, CC BY-SA 4.0; skyline by Vyacheslav Argenberg, CC BY 4.0; both via Wikimedia Commons.