NirmaanOne Help
TroubleshootingReviewed 2026-10-04

No estimate or booking allowed: the project's RERA registration is missing, expired or not yet valid

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.

Messages this explains

  • “RERA registration is not recorded; no estimate or booking can be made until it is”
  • “RERA registration is not recorded”
  • “RERA registration <number> expired on <date>; record the extension; no estimate or booking can be made until it is”
  • “RERA registration <number> expired on <date>; record the extension”
  • “RERA registration <number> is valid only from <date>; no estimate or booking can be made until it is”
  • “RERA registration <number> is valid only from <date>”
  • “RERA registration <number> expires on <date> (<n> days); record the extension once it is granted”
  • “RERA registration <number>: the validity end date is not recorded”
  • “<project> has no RERA registration recorded; record it under RERA registration before an estimate can be made (organization setting: RERA required before selling)”
  • “<project> has no RERA registration recorded; record it under RERA registration before a booking can be made (organization setting: RERA required before selling)”
  • “<project>'s RERA registration <number> expired on <date>; record the extension under RERA registration before an estimate can be made (organization setting: RERA required before selling)”
  • “<project>'s RERA registration <number> expired on <date>; record the extension under RERA registration before a booking can be made (organization setting: RERA required before selling)”
  • “<project>'s RERA registration <number> is valid only from <date>; an estimate cannot be made before that (organization setting: RERA required before selling)”
  • “<project>'s RERA registration <number> is valid only from <date>; a booking cannot be made before that (organization setting: RERA required before selling)”
  • “Your organization requires a valid RERA registration before selling: no estimate or booking can be made on this project until a registration whose validity covers today is recorded below. You can skip for now and come back.”
  • “RERA registration is not recorded yet; under RERA a project cannot be marketed before it is registered.”
  • “Required before selling”
  • “An extension needs an earlier registration on this project; record the registration first”
  • “Valid to must be on or after valid from.”
  • “The certificate date cannot be after the validity starts.”
  • “<number> valid from <date> is already recorded”
  • “Record the registration first; an extension continues it.”

No estimate or booking allowed: the project's RERA registration is missing, expired or not yet valid

Creating an estimate or booking on a project is refused, or the project's readiness card lists the RERA registration as a blocker, because no registration whose validity covers today is recorded and your organization requires one before selling.

What you see

  • On the Project overview, the Ready to sell and collect? card lists one of these in red: "RERA registration is not recorded; no estimate or booking can be made until it is", "RERA registration <number> expired on <date>; record the extension; no estimate or booking can be made until it is", or "RERA registration <number> is valid only from <date>; no estimate or booking can be made until it is". Its RERA registration line reads "Required before selling" when nothing is recorded, or the number with "expired" or "not yet valid"; the button reads Record RERA or Record RERA extension. The RERA registration card's badge reads Not recorded, Expired or Not yet valid.
  • In amber, as warnings only: "RERA registration <number> expires on <date> (<n> days); record the extension once it is granted" (the badge reads Expiring) and "RERA registration <number>: the validity end date is not recorded" (a registration carried over from before validity was kept). Nothing is blocked by these.
  • On New estimate and in the booking wizard the RERA line is listed with the project's other blockers and Book is greyed out; the server's refusal names the project: "<project> has no RERA registration recorded; record it under RERA registration before an estimate can be made (organization setting: RERA required before selling)", "<project>'s RERA registration <number> expired on <date>; record the extension under RERA registration before a booking can be made (organization setting: RERA required before selling)", or "… is valid only from <date>; an estimate cannot be made before that …".
  • On step 2, Land & RERA, of the Project setup wizard: "Your organization requires a valid RERA registration before selling: no estimate or booking can be made on this project until a registration whose validity covers today is recorded below. You can skip for now and come back." (or, with the switch off, "RERA registration is not recorded yet; under RERA a project cannot be marketed before it is registered.").
  • When your organization does not require RERA before selling, every one of these appears as an amber warning and nothing is blocked.
  • While recording: "An extension needs an earlier registration on this project; record the registration first", "Valid to must be on or after valid from.", "The certificate date cannot be after the validity starts.", "<number> valid from <date> is already recorded"; Record extension greyed out with "Record the registration first; an extension continues it."

Why it happens

Under the Real Estate (Regulation and Development) Act a project may not be marketed or sold before it is registered with the state authority, and the registration runs for a fixed period that has to be extended. NirmaanOne turns that into an organization-wide switch, Require RERA registration before selling on the Projects card under Settings > Organization, on by default. With it on, a project counts as registered only when its RERA registration history holds a row whose Valid from has passed and whose Valid to has not: a certificate that expired without a recorded extension, or an extension that only starts next month, does not count (see RERA registration, its validity and extensions).

The gate stops the two acts of selling: pricing a unit for a buyer (an estimate) and booking it. Opportunities and leads can still be recorded; an allottee's purchases are held back by the same rule. The wizard deliberately lets you skip the step, so a project can be set up before its certificate arrives.

How to fix it

  1. Nothing recorded: open the project and click Record RERA on the Ready to sell and collect? card (or use the RERA registration card directly). Click Add registration, pick the RERA jurisdiction, enter the Certificate no., Valid from and Valid to, and save. Needs the Edit permission on Projects; in the default roles the Administrator and the Project Manager. See Record land, RERA and the project's sales settings.
  2. Expired or expiring: click Record RERA extension (or Record extension on the card) and enter the extension order's number and dates; attach the order with Upload. See Record a RERA extension. If the extension has not been granted yet, nothing can be sold on the project until it is, which is what the Act requires.
  3. Not yet valid: the only registration starts in the future. If the certificate is in fact effective already, open the row and correct Valid from.
  4. Validity end not recorded: open the row and enter Valid to from the certificate, so the reminders and the gate can work.
  5. Check the card. The blocker disappears, the badge reads Current, and the RERA line shows "<number> · <jurisdiction> · valid to <date>". Then create the estimate or open the booking wizard again.
  6. If your organization sells before registration (for example a project exempt from RERA), an administrator can switch off Require RERA registration before selling on Organization (the Edit permission on Organization Settings); every RERA finding then shows as a warning only.

Related

  • RERA registration, its validity and extensionsConcept

    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.

  • 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.

  • Project setup wizardScreen

    Set up a project step by step, from the land and RERA details and bank accounts to towers, society, members, offers, amenities, parking, stages and pricing; each step saves as you go.

  • New estimateScreen

    Price a unit for a buyer: pick the unit and optional parking slots, load a unit pricing plan or add charges by hand, override rates with a reason, set the validity, and save the draft before moving on to the payment plan.

  • Book <unit> for <name> (booking wizard)Screen

    The three-step wizard that turns an approved estimate into a booking: review exactly what was approved, add co-applicants and their shares, set the booking date and book the unit.

  • OrganizationScreen

    Your organization's profile and policies: name and invitation expiry, the two-factor requirement, the AI connectors switch, the help-assistant recording switch, the project defaults every project inherits (RERA gate, estimate validity, the two chargeable areas, carpet area offered, revenue method and trigger) and the effective-dated rules: the RERA escrow share that splits every sweep of a project's collection account, TDS on sales and booking cancellation.

  • 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.

  • "Not ready to sell and collect": the project's readiness card still has blockersTroubleshooting

    A booking, or an allottee's purchases, cannot go ahead while the project lacks a promoter entity, the promoter's books, its collection, RERA separate and operative bank accounts with ledgers in those books, or (when the organization requires it) the RERA registration; the Ready to sell and collect? card lists what is missing and where to fix it.

  • "Purchases cannot start yet": the offer, its split or the project is not readyTroubleshooting

    An allottee's purchases of their allotted units open only from an issued, accepted or signed offer that allots units, records the entitled area with a split that adds up, carries no Differential Area Cost, and sits on a project that is ready to sell and collect; a purchase then stays tied to its allotted unit and the allottee as buyer.