Project overview

The project's home page. It shows the project's details and site, its land and RERA registration, a summary of the unit inventory, whether the project is ready to sell and collect money, where its money stands across its RERA accounts, and how far its setup has got.

Where to find it

Open a project from the Projects list: click its name or the Open icon. The breadcrumb with the project's name on the edit and setup pages also brings you here.

You need the View permission on Projects. Without it the page shows "No access" and "You do not have permission to view projects. Ask your administrator." If the project can't be found you see "Project not found." with a Back to projects link.

What you see

Header and tabs

The header shows the project name, a project-type badge (New Development or Redevelopment), a property-type badge, and "<city>, <state>", followed by the society name when one is linked. On the right are History and Edit Project. The header stays above every tab of the project, so History is there on each of them.

Under the header, the tabs appear in this order. Each one shows only when you have the permission it needs:

Tab	Shown when you have
Overview	Always
Structure	Any permission on Towers, Floors & Units
Society & Tenants	Any permission on Societies, and only on Redevelopment projects
Amenities	The View permission on Projects
Parking	Any permission on Parking
Construction Stages	Any permission on Construction Stages
Unit Pricing	Any permission on Pricing Plans
Tenant Benefits	Any permission on Pricing Plans
Settings	The View permission on Projects

Your organization can rename the tabs, so yours may carry different names.

Setup banner

While the project's setup is unfinished, a blue banner under the header reads "Setup in progress · N of M steps done." with each setup step and an icon for its state. It shows only to people with the Edit permission on Projects. It disappears once the setup is finished or dismissed, or once no step is left open. A skipped step still counts as open.

Details

Project type, Property type, Promoter (the promoter entity), Society (a link to the linked society), Created, Updated and Description.

Site

Address, City, State, PIN code, Village, District and Registration district.

Land

CTS / survey no.

RERA registration

The registration in force and its history. The badge reads Current, Expiring, Expired, Not yet valid, Validity end not recorded or Not recorded. Under it: Jurisdiction (the state authority, for example Maharashtra (MahaRERA)), Certificate no. (or Extension order no.), Valid from and Valid to with the days left. The history table lists every Registration and Extension, newest validity first, with its number, jurisdiction, date, validity and certificate file (Download, Upload or Replace), and Delete. See RERA registration, its validity and extensions.

Inventory

A summary line: "N towers · N floors · N units · N sellable now", followed by "· N common use (not inventory)" when the project has Common units. With the permission to see the structure, a Structure link opens the Structure tab. A project with no units shows "No units yet. Add towers and generate floors and units from the Structure tab."

Common units (a gym, a refuge area, a society office) are not inventory: they are never allotted or sold, so the unit count, the tiles and the status columns leave them out. They appear only in the summary line, in the Common use row of By designation and in the Common use column of By configuration. A project with 35 flats and 2 common units reads "37 units" nowhere: it reads "35 units · 35 sellable now · 2 common use (not inventory)".

Once there are units, five tiles count them:

Tile	Counts units that are
Units	All Saleable and PAP reserved units (Common units are left out)
Available	Available
Reserved	Reserved For Tenant
Allotted	Allotted
Booked	Booked or Sold

Two tables break the inventory down, each with a Total column and a column per status:

• By designation: a row for each designation the project's units carry: Saleable, PAP reserved or Common use. The Common use row is the only place the status of a Common unit is shown.
• By configuration: a row per unit configuration (No configuration for units without one). Its Total and status columns count the inventory only. When the project has PAP reserved or common-use units, extra columns show how many of each configuration carry those designations, so a 1 BHK used as a gym shows under Common use but not in the row's total.

The status columns use short names: Available, Reserved (Reserved For Tenant), Allotted and Booked always show; On hold (Reserved For Buyer), Sold and Blocked show only once some unit has that status.

Ready to sell and collect?

This card lists what still stops the project from taking bookings and receiving money. Its badge reads Ready in green when nothing is missing, or N to fix in red.

Blockers are listed in red. The messages you may see:

• "No promoter entity: choose the company developing the project"
• "<Promoter> keeps no books yet; set them up under Accounting > Books"
• "<Promoter> has no collection bank account for this project"
• "<Promoter> has no RERA separate bank account for this project"
• "<Promoter> has no operative bank account for this project"
• "The books have no ledger for the collection bank account <bank> ····<last 4 digits>; sync bank ledgers" (also "… for the RERA separate bank account …", "… for the operative bank account …" and "… for the GST bank account …")
• "RERA registration is not recorded; no estimate or booking can be made until it is", or the expired / not-yet-valid messages under Things to know (only when your organization requires RERA before selling)

Warnings don't block anything. They are shown as amber banners at the top of the Overview tab rather than in the card:

• "While not required, <Promoter> can also have a GST bank account for this project; without one a buyer's GST is banked into the operative account or goes into the collection account with the rest and is swept"
• the RERA registration messages when your organization doesn't require RERA before selling, and "RERA registration <number> expires on <date> (<n> days); record the extension once it is granted"

The X on a banner hides it until you open the project again. The GST note also has a Don't show again button (the Edit permission on Projects): it records the choice on the project, so nobody sees that banner again, and confirms "This note is not shown again for <project>. The Readiness card can show it again." The card then reads "1 note hidden with "Don't show again"." with a Show again link that brings it back. The choice is kept as the project setting readiness.dismissed on the Settings tab. The RERA notes change with dates, so they can only be closed for the visit.

Below the messages, the card lists:

• Promoter entity and Books.
• Collection account, RERA separate account, Operative account and GST account (optional): the bank and the last four digits of the account. "(shared)" means the account belongs to the promoter but isn't pinned to this project. Then the ledger code, or "no ledger" in amber.
• RERA registration: the registration in force (number, jurisdiction, "valid to <date>" or "validity end not recorded", and "current", "expiring (<n> days)", "expired" or "not yet valid"), or "Required before selling", or "Not recorded".
• Escrow share in force: "N% of every collection swept to the separate account", followed by "(the organization's rule)" or "(this project's own share; the organization's rule is N%)".

Since 2026-10-12 the card also lists approvals: an approval type ticked required before sale under Settings > Lookups without a Current row on the Approvals tab is a blocker while Require approvals before selling is on under Settings > Organization, and a note otherwise.

RERA accounts

Where the project's money stands across its RERA accounts, the same figures as the dashboard's RERA accounts card and the RERA accounts statement. The card shows to anyone with the View permission on Payments. Its text reads "Every buyer payment enters the collection account; the bank sweeps N% to the separate account and the rest to the operative account. As of <date>.", with "(this project's own share)" after the split when the project overrides the organization's rule.

The badge says how things stand:

• In order (green): every cleared receipt entered the collection account and has been swept.
• Unswept money (amber): cleared receipts into the collection account are waiting for a sweep. Since the sweep is posted the moment a receipt clears, this normally means a sweep could not be posted or receipts were released by a cancel or a reverse. A note reads "₹… collected has not been swept yet (₹… on Draft sweeps). The sweep rule posts it the moment a receipt clears; use Sweep now to catch up."
• Receipts outside the collection account (red): "<n> cleared receipts (₹…) were banked outside the collection account. Under RERA the money should enter the collection account; move it with a Contra voucher if the bank corrected it."
• Accounts missing (red): the project has no collection, RERA separate or operative account yet.
• No receipts yet (grey): nothing has cleared.

The rows: Collected into the collection account; GST banked apart ("never swept"; only when there is any); Swept to the separate account (with the actual share, for example "70%"); Swept to the operative account; Unswept; Withdrawn from the separate account (with "₹… requested" while withdrawals are still Draft or Approved); Separate account balance (on the books); and Banked outside the collection account (only when there is any). The buttons RERA sweeps, Escrow withdrawals and Statement are described below.

Setup checklist

One row per setup step, from Land & RERA to Amenities, parking, stages & pricing, each with its short description and state. The header shows "N/M" steps done, or the Complete badge once the setup is finished. A step marked Skipped was skipped in the wizard. A greyed-out step with a lock is one you have no access to.

What you can do

History

History in the header (hover "Who changed this record, what and when") opens the panel History · <project name>: who changed the project, what they changed and when, newest first.

• Who: anyone with the View permission on Projects, which you need to open the page anyway, or the View permission on Audit Trail.
• What's included: the project's own details and the records that belong directly to it, such as its towers, amenities, parking areas, construction stages, pricing plans, benefit plans and offers. Each of those entries is marked with the kind of record, for example "Tower", "Parking" or "Offer". Floors, units and parking slots aren't included; a unit has its own History in its panel on the Structure tab.
• What each entry shows:
  • a badge, Create, Update or Delete, and a summary: "Created", "Changed <fields>" (up to four field names, then "and N more") or "Deleted";
  • who and when: the person's name, "<name> via AI connector" for a change made through an AI connector, or Workflow or System for a change the app made by itself; then the date and time, and the IP address when one was recorded;
  • for an update, a table of Field, Before and After; for a create or a delete, a Show N values link that opens the values recorded (headed "Value", or "Value when deleted").
• The panel opens with "N changes, newest first. Lines of this record (items, parties, permissions) are included." It loads 25 changes at a time; Load older changes brings the next ones.
• With nothing recorded you see "No history yet" and "Changes are recorded from 28 Sep 2026; nothing has changed on this record since." If the panel can't load: "The history could not be loaded."
• With the View permission on Audit Trail, the panel ends with Open in the audit log, which opens the organization's audit log showing this project's changes. In the default roles, Administrator, Compliance Officer and Auditor have it.

Edit Project

Opens Edit project to change the project's facts (basics, site, land, development agreement). The settings it inherits from the organization are on the Settings tab.

• Who: anyone with the Edit permission on Projects. Otherwise the button isn't shown.

Promoter & bank accounts

On the readiness card. Opens the Promoter & bank accounts step of the Project setup wizard, where you add the collection, RERA separate, operative and GST accounts.

• Who: anyone with the Edit permission on Projects.

Record RERA

On the readiness card, shown only while the RERA number or date is missing. Opens the Land & RERA step of the setup wizard.

• Who: anyone with the Edit permission on Projects.

Sync bank ledgers

Shown beside the first "no ledger" blocker. It creates the missing ledger in the promoter's books for each of the project's collection, RERA separate, operative and GST accounts. One click fixes every missing ledger.

• Who: anyone with the Edit permission on Projects. Without it the button is greyed out, with the reason "Creating the ledgers needs permission to edit projects".
• What happens next: "Bank ledgers created: <codes>." or "Every bank account already has its ledger." The ledgers now appear in the promoter's chart of accounts, and the card updates.
• If it's refused: "Choose the promoter entity first." or "The promoter keeps no books yet; set them up under Accounting > Books."

RERA sweeps

On the RERA accounts card. Opens RERA sweeps filtered to this project, where each sweep mirrors the bank's sweep of the collection account (one per receipt when the rule posts it as the receipt clears, one per clearing date when made by hand), and Sweep now catches up on unswept receipts.

• Who: anyone with the View permission on Payments (the card itself needs it).

Escrow withdrawals

On the RERA accounts card. Opens Escrow withdrawals filtered to this project: the certified drawdowns from the RERA separate account into the operative account.

• Who: anyone with the View permission on Payments.

Statement

On the RERA accounts card. Opens the RERA accounts statement under Reports with this project chosen.

• Who: anyone with the View permission on Reports; the button isn't shown otherwise.

Continue setup

On the setup banner. Opens the setup wizard at the first step that is still open.

• Who: anyone with the Edit permission on Projects.

Dismiss

On the setup banner. Hides the banner for this project for everyone, without finishing the setup. There is no confirmation. The checklist card stays, and you can still open the wizard from it.

• Who: anyone with the Edit permission on Projects.

Add registration

On the RERA registration card. Opens Add a RERA registration: RERA jurisdiction (from the RERA jurisdictions lookup, pre-filled from the project's state), Certificate no., Certificate date (optional), Valid from, Valid to (required; "Reminders go out 90 days before this date.") and Notes. "RERA registration recorded." adds the row and refreshes the badge and the readiness card.

• Who: anyone with the Edit permission on Projects.
• Greyed out: never; the picker is disabled without the View permission on Lookups ("Needs the Lookups permission").

Record extension

On the RERA registration card. Opens Record a RERA extension with the jurisdiction and Valid from (the day after the previous validity ends) filled in; enter the Extension order no., Order date and Valid to. "Extension recorded." The earlier row stays as history. See Record a RERA extension.

• Who: anyone with the Edit permission on Projects.
• Greyed out until a registration exists: "Record the registration first; an extension continues it."

Upload / Replace / Download / Delete (RERA registration)

On a history row. Upload or Replace attaches the certificate or order (PDF, image, Word; "File type .<ext> is not allowed." otherwise; "Certificate attached."), Download fetches it, Delete asks "Delete this RERA record?" and removes the row and its file; the project's current registration is worked out again from what remains ("Registration removed.").

Go / View

On each checklist row. Go (or View once the step is done) opens the tab or page where that part of the setup is kept:

• Land & RERA: Edit project for the survey details; the RERA registration itself is the card on this page.
• Promoter & bank accounts: the overview itself.
• Towers & units: the Structure tab.
• Society, Existing members and Offers: the Society & Tenants tab.
• Amenities, parking, stages & pricing: the Parking tab.

Locked steps have no link.

Open setup wizard / Reopen setup wizard

At the foot of the checklist. Opens the setup wizard at the next open step. The link reads Reopen setup wizard once the setup has been finished.

• Who: anyone with the Edit permission on Projects. Otherwise the link isn't shown.

Statuses

• Readiness: Ready (nothing blocks selling and collecting) or N to fix. It updates as soon as the missing item is added: nothing needs to be "approved".
• Setup: in progress, finished (the Complete badge; set by Finish setup in the wizard) or dismissed (banner hidden; set by Dismiss).
• Unit statuses are only counted here, never changed. They follow the unit's estimates, offers and bookings.

Things to know

• What "ready" actually gates. A booking is refused while any blocker remains: "<Project> is not ready to sell and collect: <blockers>. Open the project and finish the "Ready to sell and collect?" card." An estimate is checked only for the RERA registration. Without the promoter's books and the three bank accounts a booking has nowhere to raise demands or receive money, so it is stopped up front. The GST account is optional: without one a buyer's GST receipt goes into the operative account (never swept either); a GST receipt banked into the collection account is swept with the rest.
• RERA before selling is an organization setting. The Require RERA registration before selling switch on the Projects card under Settings > Organization is on by default. While it is on, a registration whose validity covers today must be recorded, or no estimate or booking can be made: "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". A registration ending within 90 days is a warning: "RERA registration <number> expires on <date> (<n> days); record the extension once it is granted". With the switch off, all of these are warnings.
• Which bank accounts count. The promoter's active accounts pinned to this project are used first. If there are none for a purpose, the promoter's unpinned (shared) accounts are used. This lets one promoter run several projects from shared accounts, or keep separate accounts per project.
• The escrow share is the organization's rule under Settings > Organization > RERA escrow share (a start date for each rule; 70% to begin with), unless the project's own RERA escrow share is set on its Settings tab. It is the split the bank applies to every sweep of the collection account: that share to the RERA separate account, the rest to the operative account. NirmaanOne records the sweeps; it moves no money. See RERA accounts and the daily sweep.
• "Unswept money" normally clears itself within seconds. The system rule "Receipt cleared into the collection account: post its RERA sweep (system)" posts each receipt's own sweep the moment it clears into the collection account, dated the clearing date. Money that stays unswept means a sweep could not be posted or receipts were released by a cancel or a reverse: Sweep this receipt on the payment sweeps one receipt, Sweep now under RERA sweeps catches up a project by clearing date, and the 09:00 catch-up rule "Daily RERA sweeps (system)" (off by default) can be switched on.
• Missing books have no button on the card. Set up the promoter's books under Accounting > Books, then come back.
• Estimate validity, chargeable area, the RERA escrow share, the occupation certificate, the revenue overrides and the carpet area offered are not shown here: see the Settings tab, where each one shows the value in force and where it comes from. Expected possession is on Edit project.
• Budget cost sits on the Settings tab. Its card records the project's estimated total cost for cost of sales and over-time revenue recognition, so it shows to everyone with a permission on Revenue Recognition, which in the default roles includes the Project Manager, Sales Manager, Compliance Officer, Auditor and Rehab Officer as well as the finance roles. See Budget Cost.

Related

• Edit project
• Project settings
• Project setup wizard
• Structure
• Society & Tenants
• Amenities
• Parking
• Construction Stages
• Unit Pricing
• Tenant Benefits
• Budget Cost
• Projects
• RERA sweeps
• Escrow withdrawals
• RERA accounts
• RERA accounts and the daily sweep