RERA registration, its validity and extensions
A project's RERA registration is a history of certificates and extension orders, each with the state authority that issued it and the dates it is valid for; the one in force today decides whether the project may sell, and an expiry is a new row, never an edit.
RERA registration, its validity and extensions
Under the Real Estate (Regulation and Development) Act a project is registered with the RERA authority of its state before it may be advertised or sold, for a fixed period. When the period runs out the promoter applies for an extension, which comes as a new order with its own dates. In NirmaanOne a project's RERA registration is therefore a history, not a single number.
How it works in NirmaanOne
- One row per certificate or extension order. Each row records the RERA jurisdiction (the state whose authority issued it, from the RERA jurisdictions lookup: Maharashtra / MahaRERA, Gujarat / GujRERA …), the Certificate no. (for example P51800049852), the date on the certificate, Valid from, Valid to, notes, and the certificate file itself when you attach it. Rows are Registration or Extension. Valid to is required on every new row.
- The registration in force is the latest row whose validity has started. Its state is Current, Expiring (it ends within 90 days), Expired (it ended and no extension has been recorded), Not yet valid (the only rows start in the future), or Validity end not recorded (a row carried over from before validity was kept). The project's own RERA fields (number, date, jurisdiction, valid from and to) always mirror that row, so documents, lists and searches show it without you doing anything.
- An extension is a new row. Record it with Record extension; it starts the day after the previous validity ends (you can change the dates) and the earlier row stays in the history. A letter generated last year under the earlier certificate keeps that number.
- Selling depends on it. When the organization's Require RERA registration before selling switch is on, a project whose registration is missing, expired or not yet valid cannot have an estimate or a booking made: the readiness card shows the blocker and the button is greyed out with the reason. An expiring registration is only a warning. With the switch off, all of these are warnings. See Project readiness and the RERA gate.
- Reminders. Two system rules run every Monday: "RERA registration expiring (system)" notifies Project Managers and Administrators about projects whose registration ends within 90 days, and "RERA registration expired (system)" about projects whose registration has ended without an extension. Both ship switched on; they are rules, so you can edit the recipients or switch them off under Settings > Workflows.
- The promoter's own RERA number (on the promoter entity) is a single field and is not part of this history.
Example
Sunrise Heights was registered with MahaRERA as P51800049852 on 15 Jan 2024, valid to 31 Dec 2026. On 3 Oct 2026 the readiness card reads "RERA registration P51800049852 expires on 31 Dec 2026 (89 days); record the extension once it is granted", and the Monday reminder goes to the project manager. The extension order P51800049852/EXT-1 arrives in December, valid 1 Jan 2027 to 31 Dec 2027; the project manager clicks Record extension, enters it, and attaches the order. From 1 Jan 2027 the project's RERA number reads P51800049852/EXT-1 and the state is Current; the allotment letters generated in 2025 still show P51800049852. Had nobody recorded the extension, from 1 Jan 2027 the card would read "RERA registration P51800049852 expired on 31 Dec 2026; record the extension; no estimate or booking can be made until it is", and Book would be greyed out on every opportunity of the project.
Where you see it
- The RERA registration card on the project overview and on the wizard's Land & RERA step: the current certificate, the history, Add registration, Record extension.
- The Ready to sell and collect? card: the RERA line shows the number, jurisdiction, valid to and state.
- RERA jurisdictions under Settings > Lookups.
- The project's RERA fields in document templates and on the project list search.
Related
Related
- Project readiness and the RERA gateConcept
A project is ready to sell and collect once it has a promoter entity with books, the collection, RERA separate and operative bank accounts with their ledgers, and, when the organization requires it, a RERA registration whose validity covers today; bookings and allottee purchases wait for all of it, estimates only for RERA.
- Record land, RERA and the project's settingsHow-to
Fill in the land survey details and expected possession, record the RERA registration (jurisdiction, certificate and validity) that lets the project be sold, and override the settings the project inherits from the organization on its Settings tab only where it differs: estimate validity, the chargeable areas for buyers and for members and tenants, carpet area offered, RERA escrow share, revenue method and trigger, plus its occupation certificate.
- Record a RERA extensionHow-to
When a project's RERA registration is about to expire or has expired, record the extension order as a new row on the RERA registration card, attach the order, and check that the readiness card reads Current again.
- Project overviewScreen
A project's home page: its details, site, land, RERA registration, inventory summary, whether it is ready to sell and collect, where its money stands across its RERA accounts, and the setup checklist.
- LookupsScreen
The dropdown lists every form draws on: contact types, lead sources, activity types, company types, bank account purposes, parking types, amenities, unit types and unit configurations.
- No estimate or booking allowed: the project's RERA registration is missing, expired or not yet validTroubleshooting
With the organization's "Require RERA registration before selling" switch on, no estimate or booking can be made on a project unless a RERA registration whose validity covers today is recorded on its RERA registration card; an expiring one only warns, and opportunities can still be logged.
- System rules and starter templatesConcept
The 53 automation rules, six email templates and six draft document templates every organization starts with: which ship switched on, why the customer-facing ones ship off, what is locked, and how to switch, clone or customise them.