The Noida developer and the quarterly RERA reconciliation

He has two children, a fifteen-year mortgage on the family flat in Sector 95, and a reputation in the Noida real estate circle: not flashy, not part of the scandal generation of the 2010s, but steady. He does not advertise. Most of his buyers come through referrals from earlier buyers or through the site office. He has delivered twelve projects to date — none late by more than six months, all units sold at promised specifications, no litigation. He is not large; he is reliable. Noida's market knows the difference.

His current portfolio sits at 347 units across two RERA-registered projects: Phase 1 (190 units, launched 2021, 86% sold, completion targeted for July 2026), and Phase 2 (157 units, launched 2024, 34% sold, completion targeted for December 2027). Both projects are on land he owns in Bisrakh Village, just off the Yamuna Expressway — approximately 6.5 acres, with approvals from the Noida Authority, the UP government, and the Environmental Clearance board. He has a standard project finance loan of ₹58 crores from ICICI Bank, drawn in tranches against construction milestones and unit sales. Monthly bank audits confirm his project costs and cash flow.

What is unusual is what nearly happened in Q3 of 2025, and what did not happen in Q4 — which is to say, a compliance near-miss that an agent on a spreadsheet prevented from becoming a scandal.

🗓️ The annual ritual

The Uttar Pradesh Real Estate (Regulation and Development) Act, 2016 — UPRERA — transformed how builders report finances. Under UPRERA Section 4, every registered project must maintain a separate bank escrow account, segregated from the developer's general account. Funds from unit sales flow into the escrow account and can only be released for construction expenses and statutory approvals — not for developer salaries, office rent, or loan repayment. The developer must file quarterly financial statements on the RERA portal (Form 4 filing), certified by an independent auditor, showing: (a) opening escrow balance, (b) inflows from unit sales, (c) releases against invoices, (d) closing balance, (e) construction progress percentage, (f) homebuyer grievance count.

The quarterly deadline is thirty days after the quarter closes. Miss it once, and the RERA authority issues a notice. Miss it twice, and RERA can suspend the project registration, triggering a flood of homebuyer complaints. Violate Section 37, and the developer faces a penalty up to ₹5 lakh per violation per quarter. Violate Section 38, and RERA can order the refund of all homebuyer units and seize the escrow account.

By law, the filing is the developer's responsibility. In practice, it is distributed across three people: the company secretary (CS), who handles the board resolutions and auditor coordination; the chartered accountant (CA), who prepares the financial statement; and the independent auditor, who certifies the numbers. In a tightly run firm, these three coordinate. In most firms, they do not — each assumes the other is managing the deadline, until the deadline passes.

Rohan had hired an independent auditor in November 2023, months after Amrapali's collapse made the news nationwide. Her name was Neelam Sharma, a senior CA with twenty years of real estate audit experience and a boutique practice in Noida specializing in RERA compliance. She charged ₹4.5 lakhs per annum for quarterly audits plus spot checks. Her engagement letter was clear: she would verify the escrow bank statements, cross-check unit-sale vouchers against escrow inflows, and certify the Form 4 filing. Rohan's in-house CA, Arun Joshi, would prepare the draft financials; Rohan's CS, Vikram Singh, would coordinate. All three understood the quarterly deadline.

⚠️ What very nearly happened

In late September 2025, Neelam sent Rohan an email asking for the Q3 (July–September) escrow bank statements and the unit-sale summary. She needed them by September 30th to audit and certify by October 15th. Rohan asked Arun, the in-house CA, to gather the documents. Arun assumed Vikram Singh, the CS, had already sent them to Neelam. Vikram assumed Arun had prepared the consolidated unit-sale report. Rohan, busy with Phase 2 construction delays (a contractor payment dispute with the ready-mix concrete supplier), did not follow up.

By October 10th, Neelam had heard nothing. She sent a second email, more formal, copying Vikram Singh. Vikram replied on October 12th saying the bank statements were being gathered. What he did not say was that the SBI account where the escrow was held had four transactions in July that were still unreconciled — they appeared in the bank statement but were not in Arun's unit-sale voucher log. The amounts were small: ₹4.2 lakhs, ₹1.9 lakhs, ₹6.1 lakhs, ₹2.8 lakhs. The total was ₹15 lakhs — roughly 0.3% of the quarterly inflow. But they were unaccounted for. The bank had posted them as "NEFT to ACC NUM 3627" and "NEFT to ICICI" without invoice reference.

Vikram did not want to flag this to Neelam until he had figured out what they were. He suspected they were legitimate unit refunds (buyers backing out, their money returned) or construction cost releases that had been approved in a board meeting he had not attended. But he could not find the board minutes. Rather than escalate, he told the team to wait for Arun to reconstruct the records.

October 15th came and went. Neelam sent a formal notice to Rohan, Arun, and Vikram: the Q3 audit could not be completed without the bank statements and unit-sale reconciliation. The RERA filing deadline was October 30th. There were now two weeks left.

What nearly happened was this: on October 18th, Rohan received a call from an ICICI Bank relationship manager asking about a ₹6.1-lakh NEFT transfer from the RERA escrow account to the project's main construction loan account in early July. The bank relationship manager was flagging it for compliance reasons — RERA rules forbid escrow-to-main-account transfers without explicit RERA approval. The July transfer had no RERA Form 5 (escrow release approval) attached to the project file. Under Section 37 of UPRERA, any escrow transfer without RERA approval is a violation. If the RERA authority discovered it during the Q3 audit, Rohan faced a penalty.

He called Vikram immediately. Vikram confessed: the transfer was supposed to be a unit refund, but the vouch had been recorded incorrectly. A buyer had backed out in late June; Vikram had processed the refund by moving ₹6.1 lakhs from escrow to the main account as a transit point before returning it to the buyer's bank. But the return to the buyer had not happened — the money had sat in the main account for six weeks while the buyer disputed the refund amount. Vikram had not documented it because he was waiting for the dispute to close. Meanwhile, the RERA escrow rules did not care about the dispute — the rule was: no escrow transfer without prior RERA Form 5 approval. The violation was now in the bank statement, unreconciled, and thirteen days from a RERA filing deadline.

Rohan did not lose his temper. He had been in the business long enough to know that this was fixable, but only if it was fixed quietly. He called Neelam Sharma immediately.

🌗 What changed

What Rohan did next was unusual. Instead of asking Neelam to cover the mistake in the audit (which would have compromised her certification), he asked her to help him reconstruct what had happened, create a complete paper trail, and then file a remediation notice with RERA before the Q3 audit submission. This is not the standard playbook — the standard playbook is to hope the auditor doesn't notice, or to delay the filing indefinitely. Rohan did the opposite.

Over the phone, Neelam told him: "The real issue is not the ₹6.1 lakhs — it is that your CS and CA are not talking to each other. You need a system where every escrow transaction is logged in real time, and someone checks it every week. An agent could do that."

Rohan called Vikram and Arun into his office. He said: "From tomorrow, we hire an agent — a tool running on a spreadsheet in the cloud, monitoring the escrow account. Every transaction the bank posts gets flagged. Every unit-sale voucher gets logged. Every board resolution approving an escrow release gets uploaded. The agent cross-checks them daily. On Fridays, I get a reconciliation report." He gave them until Monday to set it up.

Vikram, who had never heard the word "agent" in a software context, asked if Rohan meant to hire a consultant. Rohan said no — a software agent, the kind that reads government documents and spreadsheets the same way Neelam read bank statements. Rohan's daughter Anya, who spent her days coding in Python and Excel, offered to set it up. By Monday, October 21st, Anya had created a Google Sheet that pulled daily NEFT transactions from the SBI escrow account (manually copied from the online statement, but that would be automated later), and an AI agent scanning the sheet for:

1. Any transaction not matched to a unit-sale voucher, board resolution, or construction invoice.
2. Any board resolution older than two weeks without a corresponding escrow release.
3. Any gap of more than ₹5 lakhs between consecutive weekly balances not explained by a unit sale or release.

Anya set it to run every Thursday evening, generating a one-page reconciliation summary for Rohan.

The first report, on Thursday October 24th, flagged six items: the ₹6.1-lakh NEFT (match it to board resolution from early July for disputed refund), the four other unmatched transfers from July, two unit-sale vouchers from August that had not yet appeared in the escrow account (the payment was in the buyer's cheque draft, awaiting clearance), and one invoice from the contractor that had been approved for escrow release but not yet submitted to the bank. The agent provided the exact date range and amount for each, and estimated that a full reconciliation would take six hours of manual work.

Rohan and Vikram spent those six hours on October 25th and 26th. They found the July board resolution approving the disputed refund. They found the contractor invoices for the other four July transfers. They found one duplicate unit-sale voucher that Arun had mistakenly recorded twice. They found the two August cheques in a file Arun kept but had not yet processed.

On October 27th, Rohan called Neelam with a complete reconciliation. He also told her about the ₹6.1-lakh July transfer without RERA Form 5 approval. Neelam's response was: "That is a violation under Section 37. But because you are disclosing it voluntarily before the audit, and you are fixing it before the RERA filing, I can document it in the audit opinion as a 'noted and remedied control deficiency.' You will not face a penalty if you file a remediation letter to RERA with the Q3 submission, explaining the mistake, the root cause, and your new reconciliation process."

Rohan drafted the remediation letter with Neelam's guidance. He wrote:

"We acknowledge that a ₹6.1-lakh escrow account transfer in July 2025 occurred without prior RERA Form 5 approval. The transfer was authorized in a Board resolution for disputed homebuyer refund processing, but was not submitted to RERA as a separate Form 5 application. The transfer has been matched to Board minutes and supporting documentation. We have implemented a weekly escrow reconciliation agent to prevent recurrence and flag escrow transactions for RERA pre-approval going forward."

(We acknowledge the mistake, explain it, and show what we fixed. This is disclosure without panic.)

Rohan submitted the Q3 audit on November 8th — nine days before the deadline — with Neelam's certification and the remediation letter attached. Three weeks later, RERA acknowledged the submission and the remediation. No penalty.

What changed, in the span of eight days, was the visibility of a problem that had been invisible to three different people working in the same organization. An agent on a spreadsheet became, for Rohan, what a pension-welfare officer is for a government retiree — someone who sits at the table with the documents and says: that transfer doesn't match that vouch, and here is why.

1. ⚠️

   September 30 – October 10 — The gap widens

   Rohan asks Arun (CA) for Q3 escrow statements. Arun assumes Vikram (CS) is handling it. Vikram assumes Arun has the documents. The deadline passes without anyone noticing the four unreconciled July transfers in the bank statement.

2. 🛑

   October 15 — Audit stalls

   Neelam sends a formal notice: no bank statements, no unit-sale reconciliation, no audit certification possible. The RERA filing deadline is now fifteen days away.

3. ⚖️

   October 18 — The violation is discovered

   ICICI Bank calls about a ₹6.1-lakh July transfer from escrow to the main account without RERA Form 5 approval. Section 37 violation: potential ₹5-lakh penalty.

4. 🔍

   October 21 — Agent deployed

   Rohan deploys an agent on a Google Sheet to flag unmatched escrow transactions. Daily SBI transactions cross-checked against board resolutions and unit-sale vouchers. First report: six items need reconciliation.

5. 📋

   October 25–26 — Manual reconciliation

   Rohan and Vikram spend six hours matching July transfers to board resolutions. Find contractor invoices, duplicate vouchers, unprocessed cheques. Complete paper trail reconstructed.

6. ₹

   November 8 — Filing submitted

   Q3 audit submitted with remediation letter disclosing the Section 37 violation and new escrow reconciliation process. RERA acknowledges nine days later. No penalty.

🧭 Why we built it

By RERA law, Rohan's situation is not unique — it is structural. There are 15,000+ RERA-registered projects in Uttar Pradesh alone. Most are managed by developers with in-house teams smaller than Rohan's. Many have the same three-person handoff: CS, CA, independent auditor. The gap that trapped Rohan — where each person assumes the other is managing the deadline — is baked into the architecture.

The Amrapali collapse in 2017 was, in part, a reconciliation failure at scale. The builder had four projects, thousands of buyers, and financial statements that did not match the escrow bank accounts. RERA had no real-time visibility into the escrow accounts — they only found the fraud when homebuyers began filing complaints in 2018, years after the money had been diverted. The 2023 amendments to UPRERA strengthened Section 4 (escrow account rules) and introduced Section 4A (independent auditor certification) precisely to prevent this. But the law cannot prevent what happens in the gap between the SBI statement and the spreadsheet where the CS writes down unit-sale vouchers by hand.

There are approximately 2,000 CS professionals in UP managing real estate projects. Many work part-time across three or four developers simultaneously, juggling RERA filings, board meetings, and MCA regulatory updates. They are not indifferent to the deadlines — they are invisible to each other. The SBI escrow account knows the truth; the unit-sale voucher log knows a shadow of it; the board resolutions know another shadow. None of them talk. An agent bridges that silence.

What it does

• 🔍Scans the SBI escrow account statement daily and flags every transaction not matched to a unit-sale voucher, board resolution, or construction invoice reference.
• 🗂️Matches board resolutions approving escrow releases to the actual NEFT transfers posted to the bank account, identifying timing gaps and missing documentation.
• 📞Generates a weekly reconciliation report (Friday evening) showing opening balance, inflows, releases, closing balance, and a list of items awaiting documentation — so the CS, CA, and auditor see the same picture.

What it does not do

• 🔒Never enters the bank account password or SBI credentials — Rohan manually copies the weekly statement from SBI NetBanking into the sheet each Friday morning.
• 💳Never submits RERA Form 4 filings or board resolutions without explicit human sign-off — it flags missing items and generates a pre-audit checklist, but Rohan approves every submission.
• ✅Never decides which documents are 'good enough' — if a transaction is unmatched, it remains flagged until a human provides the explanation or document.

For a developer like Rohan, the agent costs nothing — it runs on a spreadsheet. For a CS managing three projects, it saves the cognitive load of tracking three separate sets of deadlines and three separate sets of board resolutions. For the independent auditor, it means arriving to a project where the escrow account is already reconciled, reducing audit time from four days to one. For the RERA authority, it means fewer late filings, fewer Section 37 violations, and more real-time visibility into escrow compliance.

Rohan's remediation letter to RERA mentioned the new escrow reconciliation agent. Six weeks later, a RERA official reached out informally, asking if the system was available for other developers. Rohan realized that what had started as a spreadsheet on his daughter's laptop might be useful beyond Sector 62.

"RERA को डर नहीं — कागज़ का डर है। सब कागज़ है। अगर कागज़ सीधा है, सब सीधा है।"

— RERA is not scary — paperwork is scary. Everything is paperwork. If the paperwork is straight, everything is straight.

🌱 What we hope happens

Jignesh Sharma, Rohan's relationship manager at ICICI Bank, mentioned the escrow reconciliation system to his loan officer team. Within a month, three other Noida-based developers asked Rohan if they could use the same agent. Rohan asked Anya to formalize the system — move it off Google Sheets, automate the SBI statement import (via secure API if possible), and add NCLT case-law lookup so developers facing insolvency disputes could see how homebuyers had ranked in similar cases. By April 2026, the system was running for six projects across the Yamuna Expressway corridor.

What we hope is that the agent becomes, for real estate developers and their CS teams, what it became for Rohan: not a replacement for the auditor, not a submission service, but a mirror held up to the escrow account three times a week, saying: here is what the bank knows, here is what you have documented, here is the gap.

The gap is expensive. The developer risks a Section 37 penalty (₹5 lakhs), a Section 38 refund order (all homebuyers, all units), or a suspension of project registration. The CS risks being blamed for missing a deadline that was nobody's job explicitly. The auditor risks certifying numbers that do not match the bank. The homebuyer risks having their deposit trapped in legal limbo. The gap is where Amrapali lived. It is where most real estate collapses live — not in the laws, which are strict, but in the sixty-day window between when the bank posts a transaction and when someone human finally notices that the spreadsheet does not match the statement.

If we can shrink that window to seven days, with an agent that flags the gap on Friday evening, then three people can coordinate instead of panic. The RERA filing stays on track. The remediation letter, if needed, is written from a position of clarity, not damage control. And Rohan can spend his Tuesday mornings not in his office waiting for Vikram to find the missing board resolution, but on the Phase 2 site, watching the concrete get poured, which is what he built the company to do.

The product is free for projects with fewer than 500 units. For larger developments, we charge a monthly subscription based on project size and filing complexity. We do not sell data to RERA, to banks, or to anyone else. We do not submit filings on the developer's behalf — the developer always decides what goes to RERA. If an auditor asks, we generate a clean report showing the reconciliation methodology so the auditor can verify our work. We hold the silence between the SBI statement and the spreadsheet, and we break it, on purpose, three times a week.