Ask any sales head at a mid-market developer how many of their bookings are in a single name, and the honest answer is: fewer every year. A flat today is bought by a husband and wife on a joint home loan, by two brothers pooling savings, by a parent and a working child. One unit, two or three people putting in money. It is completely normal — and almost every builder's collection system still quietly assumes there is one buyer who pays one demand. That gap is where money and hours leak.
Why co-buying is the default, not the exception
There are good reasons buyers come in pairs. A joint home loan lets both applicants claim the interest and principal deductions, so couples split ownership to split the tax benefit. Several states offer a lower stamp duty rate when a woman is a co-owner. And for a lot of families, one person simply cannot fund the whole thing, so the down payment is genuinely pooled. The result is that the ledger for a single flat now has two or three contributors, each with their own share, their own bank account, and their own idea of when they will pay.
Where the demand letter breaks
Under a construction-linked plan — which RERA effectively pushes you toward, because you can only raise a demand as a genuine construction milestone is reached — you send one demand per stage, per unit. Plinth complete, raise a demand. Slab cast, raise the next. But the demand is for the unit, and the unit has two payers who agreed to split it 60/40. One pays on time. The other is three weeks late. Now your ageing report shows the unit as 'part paid', and nobody can tell you at a glance which co-buyer is behind, how much of this stage is still due, or who to follow up with.
Multiply that by a hundred units across two projects and the collections desk stops being a system and becomes a set of WhatsApp threads and a personal spreadsheet that lives on one person's laptop. The realities that generic tools handle badly:
- One demand that must be split across two or three payers by an agreed ratio
- Part-payments that arrive out of order — buyer B pays before buyer A
- A single unit that is simultaneously 'fully demanded' and 'partly received'
- Follow-ups that must go to the specific co-buyer who is behind, not both
- Interest on delayed payment that should apply only to the late party's share
Receipts, TDS and the 1% problem
It gets sharper at tax time. Any property sold for 50 lakh rupees or more attracts 1% TDS under Section 194-IA, and the buyer, not the builder, has to deduct it and file Form 26QB. When there are two co-buyers, each deducts and files for their own share of the consideration. If your receipts only record 'payment received against Unit 704' and not who paid which portion, matching those TDS credits at the time of registration turns into a reconciliation puzzle you solve under deadline pressure. A receipt that names the paying co-buyer and their share is not bureaucracy — it is what makes the 26QB math trivial later.
GST does not care how many names are on the agreement
GST on an under-construction home is 5% for a standard unit and 1% for an affordable one (carpet area within limits and priced under 45 lakh), both charged without input tax credit. Those rates have held since April 2019, and the September 2025 GST revision left the property scheme untouched. Crucially, GST is levied on the supply of the unit, not per buyer — so the tax on each demand has to be computed once and then split in your books along the same ratio as the payment. Do that inconsistently and your GST workings and your collection records stop agreeing, which is exactly the kind of mismatch that turns a routine query into a long one.
Generic CRMs were built for one lead, one deal, one payer. Indian real estate is one flat, two loans and three opinions on when to pay.
What a co-buyer-aware collection system actually does
The fix is not exotic. It is a collections model that treats a unit as one ledger with named contributors underneath it. Each construction-linked demand is raised once and split automatically by the agreed ratio. Every rupee that comes in is receipted against a specific co-buyer and their share. Ageing is tracked per buyer, so a reminder goes to the person who is actually late. Interest on delay is calculated only on the delayed share. And the unit still rolls everything up into one clean number for your MIS. It sounds obvious; it is also exactly what spreadsheets and single-payer CRMs fail to do.
Where BizRevolt fits
We will name the field fairly. Sell.Do is a capable, real-estate-native platform, but it is priced and scoped for large developers — often twenty to sixty thousand rupees a month — which is heavy for a builder running one to three projects. Zoho is affordable and flexible, but it is a general CRM you have to bend into a real-estate shape, and co-buyer collections is precisely the kind of thing you end up building by hand. LeadRat and others sit mostly on the lead-capture side. BizRevolt's Real Estate workspace is built for the mid-market builder who needs lead capture and RERA-aware, co-buyer-aware collections in one place, without the enterprise price tag.
It is priced per user — 999 rupees, 1,599, or 2,499 depending on the tier — so a small sales and collections team can run the whole booking-to-collection cycle without a five-figure monthly commitment. If you want to see how your current demand and receipt process would map into a co-buyer model, the quickest path is a real conversation, not a canned demo. Message the founder on WhatsApp, or call +91 91 0657 4865, and we will look at your actual payment plans and tell you honestly whether it helps.
Image credit: Moheen Reeyad, CC BY-SA 4.0, via Wikimedia Commons.