RERA compliance means meeting the registration, disclosure and other obligations that apply under India’s Real Estate (Regulation and Development) Act and the relevant authority’s rules and directions. For a builder, it is an ongoing project process: maintain accurate records, review required updates and retain evidence of submissions. The applicable authority and project circumstances matter.
RERA establishes a regulatory framework for covered real estate projects and promoters. The central Act provides the foundation, while the relevant state or Union territory authority administers registration and reporting. Use the current Act alongside that authority’s current rules, forms and orders.
Build a project compliance register with the registration reference, responsible promoter entity, reporting periods and source documents. Identify who prepares each update, who verifies technical or financial information and who authorises submission. The administrative workflow should make these responsibilities visible rather than leaving them with whoever last used the portal.
Section 3 addresses project registration and exemptions, including the central threshold language concerning land area not exceeding 500 square metres or not more than eight apartments, inclusive of all phases. Authorities may reduce the threshold. Other exemptions and project facts also matter, so obtain a project-specific applicability assessment before advertising or selling.
Record the basis of the assessment and the version of the rules reviewed. A contractor working for a promoter should clarify which obligations belong to the promoter and what evidence the contractor must supply. A project name alone does not identify the legal entity responsible for a filing.
Treat each reporting period as a controlled close. Collect approved progress information, relevant sales or booking information, approvals and other documents required by the authority. Reconcile source records before data reaches the portal. Maintain a list of missing inputs with owners and internal review dates.
Keep the submitted version, acknowledgement and supporting evidence together. A prepared report is not the same as a submitted report, and a submitted report may still receive a query. Track preparation, review, submission and follow-up separately. Do not copy one state’s deadline or form into every project’s calendar.
MahaRERA publishes project-update guidance and operates a financial-quarter-based progress reporting framework. Use its current guidance for Maharashtra projects. UP-RERA also monitors quarterly progress reporting; use its portal and applicable directions for Uttar Pradesh. For Tamil Nadu, consult TNRERA’s current registration and reporting requirements.
Create one compliance profile per authority instead of one generic national checklist. Record portal links, applicable circulars, responsible roles and required professional certificates. Where a form changes, keep a migration note explaining which old fields map to the new ones and which records need additional information.
Section 4 requires the specified 70% of allottee realisations to be deposited in a separate scheduled-bank account for land and construction costs, with conditions on withdrawals and certification. Treat the exact statutory provisions and current authority directions as the controlling reference, not the informal phrase “escrow account”.
Operationally, keep bank references, receipts, project allocation and supporting certificates connected. Maintain a controlled register of buyer communications, approvals and handover records. Reconcile records before responding to a query. A dashboard can point to missing evidence but cannot replace the responsible professional’s certification.
Consequences depend on the breach and applicable provision. Section 59 provides for a penalty that may extend to 10% of estimated project cost for non-registration; other provisions address other failures. This is not a flat state-by-state price list. Check the current law and any case-specific order with qualified counsel.
When a notice arrives, record the service date, response deadline, allegations, responsible reviewer and response evidence. Escalate it through a defined process. Do not close a notice merely because someone uploaded a document; preserve the authority’s acknowledgement and the actual resolution status.
Software can organise source evidence, responsibilities and reminders. It can make incomplete records visible and help teams prepare a consistent submission pack. Any claimed portal integration should be demonstrated against the actual authority workflow, including error handling and acknowledgement storage.
Ask the BUILDX team which project, financial and document records can support your compliance process. Confirm the implementation scope in writing. Automated reminders are useful, but the promoter’s responsibility, professional review and portal submission requirements remain part of the process.
Use clear definitions so another reviewer can follow the decision.
Identifies the regulator and exact project or phase.
Prevents a date from being applied without its governing direction.
Connects a reported value to an accountable check.
Distinguishes preparation from completed submission.
Illustrative example; not a customer result or statutory calculation.
A developer operates one Maharashtra project and one Uttar Pradesh project. The same operations team supplies site progress, but each project has its own authority profile and submission checklist. The coordinator records missing inputs separately, routes the packs for review and stores each acknowledgement against the correct project. No state deadline is inferred from the other project.
Bring a representative project record and one exception to discuss the workflow with the BUILDX team.
Use these checks to prepare a review with the responsible team.
Practical answers to common questions about this topic.
Sources checked on 1 October 2026. Apply current requirements to the relevant transaction or project.
Discuss your project, current records and review responsibilities. Agree a focused demonstration and confirm the scope your team needs.