RERA Broker Registration: What to Verify Before Onboarding

Before a channel partner submits a single lead to your project, there is one box you should not skip: confirming their RERA broker registration status. Under the Real Estate (Regulation and Development) Act and state-level RERA rules, broker registration is a key compliance requirement for property agents involved in registered projects. A developer who onboards an unverified broker may create avoidable compliance, audit, payout, and customer-dispute risk. This guide explains what to verify operationally and where legal review should define the exact rule for each state.

Verifying registration is the compliance gate within channel partner management — and it belongs at the very start of your broker onboarding flow, not after a booking.

What RERA broker registration is

RERA requires real estate agents — the brokers and channel partners who introduce buyers to projects — to register with the RERA authority of the state where they operate. Once registered, the agent receives a RERA registration number that’s valid for a defined period and must be renewed. The registration exists to bring the broking layer into the same accountability framework as developers: registered agents are expected to deal honestly, not misrepresent projects, and maintain records.

For you as a developer, the agent’s registration number is the single proof that the broker can legally transact your registered inventory.

Why developers should verify, not assume

It’s tempting to take a broker’s word that they’re registered. Don’t. The cost of an unregistered broker surfaces at the worst possible time — at booking or payout:

A booking facilitated by an unverified or ineligible agent may create avoidable dispute risk
Commission paid to an unregistered agent creates a compliance and audit exposure
Enforcement risk may arise depending on the state, project, facts, and how the relationship was documented
A later commission dispute becomes far messier if the broker’s standing is in question

Verification is cheap compared with cleaning up a disputed booking, payout, or audit trail later. Make the check part of the process rather than a judgement call left to the sales team.

What to capture and check at onboarding

Build verification into the registration form so it’s impossible to onboard a broker without it. Capture and confirm:

Item	Why
RERA agent registration number	The core proof of eligibility
State of registration	Must cover where they’ll transact your project
Validity / expiry date	Lapsed registration = not eligible
Registered firm name	Must match the CP’s KYC and bank details
RERA certificate (upload)	Documentary evidence for your records

Then check the number against the state RERA authority’s public agent register. Most state RERA portals (MahaRERA, UP-RERA, K-RERA, TG-RERA and others) publish a searchable list of registered agents. The match has to be active — a number that exists but has expired doesn’t count.

State variation is real

RERA is a central act, but implementation is state-level, so the registration number format, validity period, fee and renewal cycle differ by state. A broker registered in Maharashtra is not automatically cleared to transact a project in Karnataka. If your project spans markets, or your brokers operate across state lines, capture the state explicitly and confirm the registration covers the relevant jurisdiction. Don’t treat “they have a RERA number” as a universal pass.

This state-by-state nuance is part of the wider compliance picture for developers, covered in the RERA compliance guide for developers.

Keep legal review in the loop

This article is an operational checklist, not legal advice. RERA implementation, broker-registration obligations, document formats and enforcement practice can vary by state and project type. Your legal or compliance team should define the exact acceptance rule for each market you operate in: which certificate is valid, whether an individual or firm registration is acceptable, how renewals are handled, and what happens when a broker’s status changes mid-year.

The CRM process should then enforce that rule consistently. Sales teams should not be deciding case by case whether a broker is acceptable; they should see a clear status such as verified, pending review, expired or rejected.

Wire verification into your records

A verified registration is only useful if it’s stored and re-checkable. Three things make the check durable:

Store the certificate and number on the CP’s record, not in someone’s email.
Flag expiry so a broker whose registration lapses is paused before they submit new leads.
Keep the trail auditable, so if a booking is ever questioned you can show the broker was verified and active at the time.

This feeds directly into your audit-ready sales records: the registration evidence sits alongside the booking and commission trail, so a RERA or financial audit is a lookup, not a scramble.

A pre-onboarding verification checklist

RERA registration number captured
Number verified active on the state RERA register
State of registration covers the project’s jurisdiction
Validity/expiry date recorded and flagged for renewal
Registered firm name matches KYC and bank details
RERA certificate uploaded and stored on the CP record

Only after all six should a CP code be issued and the broker allowed to submit leads.

The takeaway

RERA broker registration verification is one of the simplest risk controls in a channel partner program. Verify the number against the state register where applicable, confirm it is active and covers the right jurisdiction, store the evidence, and flag it for renewal — all before the broker submits their first lead. A real-estate CRM like ExeLoop can store and flag RERA status on each CP record, but the discipline of verifying up front is what actually protects your process.

Next step: With your brokers verified and registered, build the rest of the onboarding flow around it — see how to onboard channel partners at scale.