Channel partner management software for real estate gives a builder one system to register channel partners (CPs), share live inventory with them, record which partner brought which buyer, accept their booking requests and pay brokerage against collection milestones. The software is the easy half. The hard half is the operating rules: who owns a lead when two partners claim it, when a payout becomes due, and what happens to brokerage when a booking is cancelled. This playbook sets out those rules and shows where the system should enforce them so the CP desk stops running on WhatsApp screenshots and memory.
Key takeaways
- Treat the CP programme as five linked records: partner master, inventory access, lead registration, booking request and payout ledger. Each one closes a specific gap where money or goodwill leaks.
- Write the attribution rules before you sign the first partner. Most disputes come from a rule that was never written down, not from a rule that was broken.
- Pay brokerage in legs tied to collection milestones, and void unpaid legs automatically on cancellation.
- Lock the source and sub-source on a lead the moment it is registered, and never silently drop a duplicate.
- Keep an audit trail on assignments, bookings and commission payments so a dispute is settled by looking at the log, not by who shouts louder.
What does channel partner management actually cover for a builder?
A builder working with 40 to 400 partners needs more than a spreadsheet of names and phone numbers. The programme has five moving parts, and each one exists to stop a specific failure.
| Part of the programme | What it records | Failure it prevents |
|---|---|---|
| Partner master | Legal entity, RERA number, PAN/GST, bank details, commission %, allocated projects, status | Paying an unregistered or blacklisted partner; wrong % applied |
| Inventory access | Which partner can see which project's live unit status | Partners selling units that were sold last week |
| Lead registration | Which partner tagged which buyer, when, for which project, with what validity | Two partners claiming the same buyer; a direct walk-in later claimed as a CP lead |
| Booking request | Partner's request to book a specific unit with token proof, accepted or rejected by the builder | Double bookings; unit price negotiated outside the agreed list |
| Payout ledger | Agreed brokerage, legs due, legs paid, voided legs, deductions | Paying twice, paying on a cancelled deal, paying before the buyer has paid |
If your current system handles only the first and the last, you have a payout tool, not channel partner management. The checklist in CRM for builders: 25 features to check covers how this fits with the rest of a builder's stack.
How should you onboard and register a channel partner?
The partner master: fields that matter
Set up every partner as a master record before they bring a single lead. Keep the record light enough that a CP manager can create it in ten minutes, but complete enough that finance never has to chase basics at payout time.
- Legal name and trade name, with the authorised signatory and the person who will actually call your site.
- RERA agent registration number and its validity date. Under the Real Estate (Regulation and Development) Act, 2016, real estate agents must register with the state authority before facilitating sales in registered projects. Rules and portals differ by state; the Ministry of Housing and Urban Affairs is the official starting point, and our plain-English explainer on RERA covers the basics.
- PAN and GST registration. Brokerage invoices from a GST-registered partner carry GST; an unregistered partner is a different accounting case. Confirm the treatment with your CA rather than improvising per partner.
- Bank account and cancelled cheque, verified once, then locked. Changes should require a fresh document and an audit entry.
- Commission formula per project: usually a percentage of agreed value, sometimes a fixed amount per unit for plots or inventory you want cleared.
- Project allocation: which projects the partner is empanelled for. A partner empanelled for Project A should not be able to register a buyer for Project B without being added.
- Payout milestones agreed in the empanelment letter (see the payouts section below).
- Status: Active, On hold, Exited. Put the reason on every status change.
Tiering and the empanelment letter
Tier partners on a simple rule you can defend: number of site visits and bookings in the last two quarters. Tiers can change the percentage, the hold window on units, or early access to a new tower launch. Whatever you promise, write it into a one-page empanelment letter that also carries the attribution rules and the cancellation clause. Partners who have read the rules first raise far fewer disputes.
How do you share inventory with partners without losing control?
The commonest complaint from partners is stale stock: they pitch a unit from last month's PDF, the buyer visits, and the unit is gone. The commonest complaint from builders is the reverse: a partner "blocks" three units on WhatsApp for a client who never shows up.
The access-request model
Run inventory access as a request-and-approve flow, project by project. The partner asks for access to a project's stock, your CP manager approves, and from then on the partner sees live status (Available, Hold, Booked, Sold) for that project only. They do not see the buyer behind a booked unit, and they do not see projects they are not empanelled for. Live status removes the stale-PDF problem without a weekly email.
Holds with an expiry and a history
A hold is a promise with a clock. Set a standard hold window (24 to 72 hours is typical; pick one and apply it to everyone) and require a token amount or at least a KYC document to place it. Every hold and release should carry who placed it, for whom, and when it expired. When a partner says "I had that unit blocked", the history answers the question. For the mechanics of unit status and double-booking prevention, see unit tracking system in real estate.
Partner-tagged microsites instead of forwarded brochures
Give each partner a project microsite link or QR code tagged to their name. A buyer who enquires through it is attributed to that partner at the moment of enquiry, which settles a lot of "I sent them the brochure first" arguments. It also keeps the price and the amenities list current for every partner at once. More on this in how real estate microsites improve lead quality.
How do you attribute leads and settle duplicate conflicts?
Attribution is where CP programmes go wrong. Write these rules down, put them in the empanelment letter, and configure the CRM to apply them.
Lead registration before site visit
A partner registers a buyer by name, phone number and project before the buyer visits the site. The registration is time-stamped and the lead's source is set to "Channel partner" with the partner name as sub-source. Lock both so that nobody on the sales floor can quietly change a CP lead into a direct lead or vice versa.
Validity window
A registration is valid for a defined period, commonly 30 to 90 days, with renewal if the partner has brought the buyer to site or logged a documented follow-up. Unrenewed registrations lapse. Choose a window and apply it uniformly.
Duplicates are flagged, never dropped
When a second registration arrives for a phone number already in the CRM, the system should create it, flag it as a duplicate and link it to the original rather than silently discarding it. A dropped duplicate is a dispute with no evidence. A flagged, linked duplicate shows both time stamps, both sources and the full history, which is exactly what the CP manager needs to apply the rules below. Lead consolidation explains why this matters across all sources, not just partners.
The attribution matrix
| Situation | Rule |
|---|---|
| Two partners register the same buyer | Earlier valid registration wins, provided the site visit happens within the validity window |
| Buyer was already a direct lead in the CRM before the partner's registration | Stays direct, unless the direct lead was marked lost more than the validity window ago |
| Direct lead enquires, then a partner brings the same buyer to site | Direct wins if the builder team logged contact within the SLA; otherwise partner wins |
| Buyer books a different unit or project than the one registered | Registration carries over within the same builder for the validity window |
| Family member (spouse, parent) of a registered buyer books | Treated as the same buyer when the address or co-applicant matches |
| Partner's registration lapsed, buyer books later through another partner | Second partner wins; first partner gets nothing |
How should booking requests from partners flow?
A booking request is the partner's formal ask to book a specific unit for a registered buyer. Make it a request, not a booking, so the builder keeps the final say.
- The partner raises the request on a unit with the buyer's details, token proof and KYC documents.
- The CP manager checks three things: the buyer is validly registered to this partner, the unit is still available at list price, and the token has reached the builder's account.
- Acceptance converts the request into a booking, moves the unit to Booked and creates the brokerage entry in the ledger. Rejection carries a reason the partner can see.
- Both sides see the same status: Pending, Accepted, Converted or Rejected. Nobody has to call to ask "did it go through?".
The system should refuse a booking on a unit that is already Booked, Allotted or Sold, whoever raises it. That one rule removes the most expensive class of CP dispute, the double sale.
How do you calculate and pay brokerage?
Define the base, the legs and the triggers
Brokerage disputes rarely concern the percentage. They concern the base (is it agreed value, or value plus parking plus club charges?), the legs (how many instalments) and the triggers (what collection milestone releases each leg). Define all three in the empanelment letter.
Illustrative example (figures are made up for clarity): a partner's buyer books a 2 BHK at an agreed value of ₹85 lakh, excluding GST, stamp duty and registration. Brokerage is 2%, so the agreed commission is ₹1,70,000. The letter splits it into two legs: 50% when the buyer has paid 10% and signed the agreement, 50% when collections cross 30%. The first leg, ₹85,000, becomes due the day the agreement is executed. The partner raises a GST invoice; the builder deducts TDS on commission as required and pays the net. If the buyer cancels after the first leg but before the second, the second leg is voided automatically and the recovery clause for the first leg applies.
On tax, keep it general and current: TDS on commission or brokerage is governed by the Income-tax Act (Section 194H), and GST applies on brokerage from registered partners. Rates and thresholds change; confirm them with your CA or on the Income Tax Department portal before you set the deduction in the ledger.
The ledger view every CP manager needs
- Agreed vs paid per booking and per partner.
- Legs due this month, by milestone reached.
- Voided legs with the cancellation reference.
- Payable (to partners) and receivable (reference commissions owed to the builder, if any) side by side.
Tie payouts to the same collection data your finance team already runs; post-sales automation shows how collection milestones can drive downstream actions without manual chasing.
Voiding on cancellation
Cancellation handling must be automatic for unpaid legs and contractual for paid ones. When a booking is cancelled, any due-but-unpaid commission is voided in the ledger with a link to the cancellation. For legs already paid, the empanelment letter should state whether the partner refunds, forfeits it against the next deal, or keeps it if the cancellation was the builder's fault.
The CP dispute-resolution rule set
Publish these to partners and to your own sales team. They work because they are mechanical.
- The log decides. Registration time stamp, site-visit record and booking request time stamp are the only evidence. Screenshots of chats are not.
- Earlier valid registration wins. Validity means within the window and with a logged site visit.
- Direct lead precedence requires contact. A direct lead beats a later partner registration only if the builder team logged a call or visit within the first-response SLA.
- One buyer, one partner, one project cycle. A buyer cannot be split between two partners; brokerage is never divided to end an argument.
- Unit status is final. A booking request on a Booked or Sold unit is rejected automatically, and no partner is compensated for it.
- Holds expire. A lapsed hold gives no claim on the unit.
- Brokerage follows the ledger, not the conversation. Legs are due when the milestone is recorded in collections, not when the partner says the buyer paid.
- Cancellation voids unpaid legs. Paid legs follow the clause in the letter.
- Appeals go to one person. The sales head decides within a fixed number of working days, and the decision is recorded on the booking with the reason.
- Repeated misregistration costs tier. A partner who registers buyers who were already direct leads, or who registers lists without consent, drops a tier; a third instance ends empanelment.
How Homelead handles channel partners for builders
Homelead's Builder panel includes a Channel Partners master where each partner is recorded with their commission percentage and project allocation, so the CP manager controls which partner sells which project. Partners request access to a builder's stock through Shared Inventory; once the builder approves, the partner sees live unit status (Available, Hold, Temporary Booked, Booked, Allotted, Sold) in their own Shared Inventory grid. Holds and releases keep a history, and a booking on a Sold or Allotted unit is refused, which blocks double bookings at the system level.
Partners raise booking requests that the builder sees as Pending, Accepted, Converted or Rejected; an accepted request converts into a sale that appears on both the builder's and the broker's side. Every lead carries a source and sub-source that can be locked, duplicates are created but flagged and linked to the original rather than dropped, and merging keeps the full history. A partner API key lets outside tools or call centres post leads with attribution intact, and every project, property and plot gets a shareable microsite link and QR code whose enquiries land as leads.
Commission uses one formula everywhere, percentage of deal or fixed amount, with three separately payable legs (owner, lead/buyer, reference). The Finance → Commission tab shows agreed vs paid, lets finance mark legs as paid or refunded, and separates receivable from payable. Cancelling a booking voids its due commission. The Audit Logs screen records who changed what on leads, assignments, bookings and commission payments with before-and-after values, and role scopes limit each user to My, Team or All records. Broker management, commissions and payouts are included in every plan; see pricing or book a demo with your own partner list and inventory sheet.
Which mistakes do builders make with CP programmes?
- Paying on the partner's word. Brokerage released on "client ne 10% de diya" without checking collections. Tie legs to recorded receipts.
- One percentage for everything. Plots, ready units and launch stock deserve different formulas. Keep them per project in the master.
- No validity window. Registrations that never lapse let a partner claim every buyer they ever messaged.
- Letting the floor change sources. If telecallers can flip a lead from CP to direct, incentives follow. Lock the source.
- Silent duplicate handling. Dropping the second registration destroys the evidence you need later.
- No exit process. Partners leave; their registered buyers should be reassigned under a documented rule, not forgotten.
Frequently asked questions
What is channel partner management software in real estate?
It is the part of a builder's CRM that registers channel partners with their commission and project allocation, shares live inventory with them, records which partner brought which buyer, processes their booking requests and tracks brokerage legs from agreed to paid or voided.
How do builders avoid two partners claiming the same buyer?
By requiring registration (name, phone, project) before the site visit, time-stamping it, giving it a validity window, and applying a written rule that the earlier valid registration wins. Duplicates should be flagged and linked, not deleted, so the evidence survives.
When should brokerage be paid to a channel partner?
In legs tied to collection milestones recorded in the builder's ledger, for example part on agreement signing after 10% collection and the balance after 30%. Paying on the partner's claim rather than on recorded receipts is the most common cause of overpayment.
What happens to brokerage if the booking is cancelled?
Unpaid legs should be voided automatically in the ledger with a link to the cancellation. Already-paid legs follow the clause in the empanelment letter: refund, adjust against the next deal, or retain if the cancellation was the builder's fault.
Do channel partners need RERA registration in India?
Under the Real Estate (Regulation and Development) Act, 2016, real estate agents must register with the state authority before facilitating sales in registered projects. Store the registration number and its validity in the partner master and check it at onboarding and renewal; state rules differ, so refer to your state RERA portal.
Should partners see which buyer booked a unit?
No. Partners need live unit status (available, hold, booked, sold) for the projects they are empanelled on, not buyer identities. Limiting visibility protects buyer data and removes an incentive to poach.