What RERA quarterly progress reporting actually requires
The Real Estate Regulation Act mandates that every registered project file a quarterly progress update on the state authority's portal. The filing is not a single number. It is a structured pack with at least five components per project, due within 15 days of the quarter end, and the format varies meaningfully across states.
- Booking status per inventory unit. Total units in the project, units booked this quarter, cumulative bookings, units cancelled and re-released. Required at unit-block level for towers and at unit-by-unit level in some states.
- Collection summary. Total amount collected this quarter, cumulative collection, split between consideration value and statutory dues like GST and stamp duty. Reconciled to the booking amount due as per the agreement schedule.
- Escrow account movement. Opening balance, deposits this quarter, withdrawals against approved RERA-permitted heads, closing balance. Bank statement copy attached.
- Construction expenditure. Cumulative spend by approved BOQ head, with the construction completion percentage certified by the project architect or engineer.
- Project-cost reconciliation. Approved project cost at registration versus current cost forecast versus cumulative spend. Variances explained where they exceed the threshold the state authority has set.
Five components, every quarter, for every active project. A developer with 12 SPVs files this 48 times a year. Most of the work is data assembly, not professional judgement.
The CA pain - why the prep takes a week
Talk to any developer's CA about the RERA quarter close and the same story comes back. Two weeks of email back-and-forth with the developer's MIS team and project managers. Booking status from the CRM in one format. Unit status from the inventory tool in another. Collection data from Tally per SPV. Bank statements pulled from the escrow bank's portal manually. Construction certificates chased from the project engineer who is busy on site.
The CA then spends three to four days reconciling these inputs against each other - booking value in CRM should match revenue booked in Tally, collection in Tally should match deposits in the escrow bank statement, construction spend in Tally should align with the BOQ heads approved at RERA registration. Mismatches surface that need to be chased back to the source. By the time the filing pack is assembled, the 15-day window is usually half gone.
How AI changes the prep workflow
The AI does not replace the CA. It eliminates the data assembly week. KolossusAI reads bookings from the CRM, unit status from the inventory tool, and collections, escrow movement, and construction spend from Tally per SPV. The same project-to-SPV map and unit-to-customer map used for portfolio P&L is reused for the RERA filing pack.
The output is a structured filing pack per project, in the format your CA actually needs - the spreadsheet template they have been using for years, populated end-to-end. The CA reviews, applies professional judgement to anything that needs explaining, and uploads to the state portal. The week-long data hunt becomes a two-hour review. AI for Indian real estate developers covers the full multi-SPV pattern that makes this work.
State-by-state format quirks
| State | Where the format differs | What changes for the filer |
|---|---|---|
| Maharashtra (MahaRERA) | Most detailed - unit-by-unit booking and collection schedule | Highest data prep burden, strongest case for automation |
| Karnataka (K-RERA) | Block-level booking summary, escrow narrative more open-ended | Less granular but escrow narrative needs CA judgement |
| Gujarat (GujRERA) | Construction certificate format prescribed by authority | Architect or engineer certificate template is mandatory |
| Tamil Nadu (TNRERA) | Quarterly versus half-yearly cadence varies by project size | Cadence rule built into the filing reminder logic |
| Telangana (TS-RERA) | Land cost reconciliation requirement at every filing | JV economics need explicit per-quarter restatement |
A developer with projects in three states is filing in three formats every quarter. The CA usually has a template per state. KolossusAI maintains the same per-state format profile and produces the right pack per project, so the CA opens one workbook per project instead of stitching one together.
What AI handles versus what the CA still owns
- AI handles - data assembly across CRM, inventory, Tally, and bank. Booking status, collection summary, escrow movement, construction expenditure, all reconciled and presented in your CA's working template.
- AI handles - validation rules built in. Booking value matches revenue booked. Collection matches deposits. RERA escrow ratio is computed and flagged. Mismatches are surfaced with drill-down to source voucher.
- AI handles - state-specific format output. Maharashtra unit-by-unit, Karnataka block-level, Gujarat with engineer certificate slot. The right format per project, every quarter.
- CA owns - professional judgement on variance. Why is the project cost forecast above approved cost. Why was a particular escrow withdrawal made. The narrative the authority expects from a qualified professional.
- CA owns - portal upload and signature. RERA portals require digitally signed filings by the developer or their authorised representative. This is regulatory, not technical, and stays a human step.
Time savings per project per quarter
On a 12-SPV portfolio, that is 60 CA-days a year today versus 24 CA-hours a year with the assembly automated. The CA bills the saved time as advisory work the developer actually wants - structuring, planning, audit support - instead of as data hunting that nobody pays well for.
The honest constraint - portal upload stays human
We are deliberately not automating the final upload to the RERA portal. There are two reasons. First, every state portal requires a digitally signed filing by the developer or their authorised representative. The signature carries legal weight; we do not want an AI to be the signatory of record. Second, portal interfaces change frequently and unpredictably as state authorities iterate. A bot that breaks in the last hour of the filing window is worse than no bot at all.
The CA opens the portal, pastes the values from the AI-prepared pack, attaches the bank statement and engineer certificate, signs, and submits. Twenty minutes per project instead of half a day. The accountability chain stays clean: the developer signed, the CA prepared, the AI assembled the data with full drill-down to source for audit. That is the right division of labour for a regulated filing.
See our pricing for how the 14-day POC validates the RERA pack against your last filed quarter before you commit.