Why developers structure as multi-SPV in the first place
Walk into any mid-sized Indian developer with more than two live projects and you will count Tally companies in double digits. One Special Purpose Vehicle (SPV) per project, sometimes one per tower in a large township. The structure is not accidental and it is not going away.
Three forces drive it. RERA requires project-level ring-fencing of bookings and escrow. Tax planning routes land cost, JV partner economics, and FSI premium through separate entities to keep the assessing officer's job clean. Investor and lender covenants treat each project as a stand-alone risk and demand its own books. The result is a developer with ₹250 Cr of annual sales running 12 companies in Tally, with the owner asking for a consolidated portfolio view at the end of every month.
The owner's question is reasonable. The plumbing to answer it is not. The MIS analyst pulls 12 trial balances, 12 unit-status reports from the inventory system, and 12 sales slices from the CRM, then reconciles common ledgers, common customers, and inter-company entries by hand. By the time the consolidated PDF lands on Friday, the underlying data has already moved on.
What a real consolidated view actually requires
A working portfolio P&L is not just adding twelve numbers. It needs four moving parts to line up cleanly.
- Per-SPV financials, read live. Each SPV's Tally company, with its own chart of accounts, customer master, and vendor master. Twelve companies, twelve trial balances, refreshed without a manual export.
- Cross-SPV entity map. The same vendor selling to three SPVs is one vendor, not three. The customer who booked a flat in Project A and a plot in Project D is one customer. Inter-company entries net out at the portfolio level instead of inflating revenue.
- Project-to-SPV map and unit-to-customer map. The CRM and inventory system identify projects and units differently from how the SPV books them. Without an explicit map, sales velocity and collection do not reconcile to revenue booked in Tally.
- Common cost allocation rules. Head-office overhead, marketing spend, and shared finance cost get apportioned across projects on agreed bases - revenue, area, or built-up cost. The rules need to be encoded once and applied consistently.
Where the data sits, per SPV
| Data domain | Lives in | What gets joined |
|---|---|---|
| Bookings and sales velocity | CRM (Sell.do, LeadRat, Salesforce, custom) | Joined to unit master and revenue booking in Tally |
| Unit status and inventory | Construction ERP or homegrown inventory tool | Joined to bookings (CRM) and possession schedule |
| Collections and escrow | Tally per SPV, plus bank statements | Joined to booking schedule and RERA escrow requirement |
| Construction cost and BOQ | Tally vendor ledger, project engineer's BOQ Excel | Joined to RA bill register and approved budget |
| RERA quarterly progress | State portal data, separate from internal systems | Joined to internal sales, collection, and cost views |
Each row is a join nobody at the developer is paid to maintain. The MIS analyst rebuilds them from exports every cycle and the joins drift the moment a new project comes online or a CRM gets switched.
The AI approach - read each SPV in place
KolossusAI connects to each SPV's stack as a distinct source. Each Tally company is a separate connection. The CRM is a separate connection. The inventory tool is a separate connection. The AI maintains the project-to-SPV map, the unit-to-customer map, and the common entity master in one place and uses them to answer questions across the portfolio.
The owner asks "consolidated revenue this quarter excluding intercompany entries, by project, with collections versus billing" in plain English. The AI runs the query against every SPV in parallel, applies the consolidation rules, and returns a portfolio table in seconds. Every row drills down to the underlying voucher in the relevant SPV's Tally company. AI for Indian real estate developers covers the full pattern across CRM, inventory, and Tally. For developers whose primary system is Tally, AI for Tally Prime users is the right entry point.
Typical scale - what we see at customer plants
The five-day analyst cycle is not just inefficient, it is systematically late. The owner sees consolidated numbers two weeks after month-end, by which time three new launches and a price revision have already happened. A live consolidated view changes the rhythm of the business - the owner is looking at this week's portfolio P&L during this week's launch decision.
The intercompany trap
The single biggest mistake we see in developer consolidation is double-counting intercompany items. The holding company books a management fee from each SPV. Each SPV books the fee as an expense and the holding books the matching revenue. A naive consolidation adds both sides and inflates revenue by 6 to 12 percent. A good MIS analyst nets these manually, but the netting drifts as new SPVs come online.
KolossusAI flags intercompany pairs at onboarding and nets them automatically in every consolidated query. The rule is encoded once - holding charges to SPV X for project management, JV revenue share to SPV Y, land cost transfer to SPV Z - and the consolidation is correct on every cut.
What the owner actually starts asking
The interesting shift is not in the standard consolidated P&L. It is in the questions the owner starts asking once the data is one query away.
- Cross-project channel ROI. 'Of the leads that came from our hoarding spend last quarter, which projects did they actually book in?'
- Customer profitability across projects. 'Show me customers who have booked in more than one project, and the total margin we have made on them.'
- Vendor concentration across SPVs. 'Which civil contractors have outstanding RA bills above ₹50 lakh across multiple projects? What is our negotiating leverage?'
- Cash position by project. 'Net of escrow lock-up, working account, and RA bills due, which projects are cash-positive and which are funding?'
- Launch decision support. 'Should we launch Project H now? Show absorption rates of comparable projects launched in the last 18 months at similar configurations.'
None of these are exotic. All of them require the consolidation to be live and reliable. The MIS analyst doing weekly Excel cuts cannot answer them at the speed the decision needs.