NirmaanOne Help
ScreenReviewed 2026-09-29

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

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.

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

The page is titled "Book <unit> for <applicant>". This wizard makes the booking. It shows you exactly what the approved estimate contains (unit, charges, parking and payment plan), lets you add the people who will co-own the unit, and books the unit on the date you choose. Nothing is saved until you press Book on the last step.

Where to find it

  • Book in the header of an opportunity whose current estimate is approved.
  • Book on the approved, current estimate.
  • For an allottee's purchase, Book on the allottee's approved estimate; the breadcrumbs then read Estimates › allottee (their page) › Book instead of Opportunities › name › Book.

You need the Create permission on Bookings (otherwise "No access" / "You do not have permission to view booking creation. Ask your administrator.") and the View permissions on Opportunities and Estimates ("You do not have permission to view opportunities and estimates (needed to book). Ask your administrator."). In the default roles the Administrator, Sales Manager and Sales Executive can book.

If the opportunity has no estimate the page reads "This opportunity has no estimate to book. Create and approve an estimate first." with a Back to the opportunity link. If it can't be loaded at all the page reads "Opportunity not found." with Back to opportunities.

Before you start

  • The opportunity's current estimate is Approved and carries a Finalized payment plan.
  • The unit is Available or held for this buyer by the estimate (a sent estimate holds the unit as Reserved For Buyer until its validity runs out), and is Saleable stock. For an allottee's purchase the unit is Allotted to them on their offer.
  • Parking slots, if any, were picked on the estimate; the wizard doesn't add or change them.
  • The project is ready to sell and collect: promoter chosen, books set up, the collection, RERA separate and operative bank accounts with their ledgers (the GST account is optional), and, when your organization requires it, the RERA registration on file. See Project setup wizard.

What you see

"Book <unit> for <applicant>", with "<project> · estimate vN · ₹<total>. Nothing is saved until you press Book on the last step."

Alerts

Red alerts list anything that stops the booking; the same reasons are repeated on the grey Continue and Book buttons.

  • "The opportunity is booked; nothing can be booked." / "The opportunity is lost; nothing can be booked."
  • "This opportunity already has a booking."
  • "Estimate vN is <status>; only an Approved estimate can be booked."
  • "Estimate vN is not the current version."
  • "Unit <unit> is <status>." (a buyer's unit that is no longer available) or "Unit <unit> is <status>, no longer allotted to this allottee."
  • "The estimate has no payment plan; draft and finalize one on the estimate first." / "Payment plan vN is <status>; finalize it on the estimate first."
  • "<project> is not ready to sell and collect, so nothing can be booked on it yet." with each blocker and a fix link: Choose the promoter, Set up the books, Add the collection account, Add the RERA separate account, Add the operative account, Record the RERA registration, or a Sync bank ledgers button beside the first missing-ledger blocker. While blockers remain, the card's warnings are listed too, each with its link, for example the missing GST account with Add the GST account. Then "Demands and receipts post to the promoter's books through these bank accounts; without them the money has nowhere to go." This block needs the View permission on Projects to load.

Green notes are good news, not blockers: "Unit <unit> is held for this buyer until <date>. Booking it lifts the hold." and, for an allottee, "Unit <unit> is allotted to <name> on their offer; booking gives it its own booking and agreement, and it stays allotted to them."

Stepper

Review, Co-applicants (marked "Optional") and Book. You can click any other step directly.

Step 1: Review

"Exactly what estimate vN was approved with: the same charges, figures and payment plan as on the estimate. To change anything, make a new version there (it goes back for approval)."

  • Unit ("<unit> · <tower>, floor <n>"), Estimate (version and status badge), Unit pricing plan (or "Manual pricing"), Parking (each parking slot as "<parking area> <number>", comma-separated, or "None") with the parking layout when parking slots were picked.
  • Charges: the grouped charges table with sub-totals, GST and "Grand total · unit <unit>", or "No charges."
  • Payment plan: "vN" with its status badge and the schedule preview, computed by the server from the booking date: "Dated from the booking date (<date>); change it on the Book step."

Step 2: Co-applicants

"The primary applicant is the opportunity's contact; add co-applicants who share ownership." (or "… is the allottee; …"). The primary applicant is shown as a chip with phone and email. For an allottee: "Leave the co-applicants empty to book in the names the allottee already holds: their co-owners become the co-applicants, with their shares."

The co-applicants editor starts with "None. Add anyone who co-owns the unit with the primary applicant; their shares may total up to 100%." Each row ("Co-applicant <n>") has the contact (pick an existing one, with the View permission on Contacts, or enter a new one), Relationship (placeholder "e.g. Spouse") and Share (%). A running line reads "Co-applicant shares total <n>%; the primary applicant keeps <m>%." or "Co-applicant shares total <n>% — more than 100%."

Checks: "The primary applicant cannot also be a co-applicant", "Co-applicant shares add up to <n>%, more than 100%", "Pick a contact", "First name is required", "Enter a phone number (at least 5 digits)".

Step 3: Book

A summary: "Unit <unit> for <name> at ₹<total>, with <n> co-applicants, <n> parking slots."

  • Booking date (required; defaults to today; hint "The down payment (if any) and lumpsum rows fall due on this date."; cleared, it shows "Enter a date").
  • Notes ("Optional").

The token amount, agreement and registration details are not asked here; record them later with Edit on the Booking overview.

What you can do

Continue / Back

Continue checks the current step's fields and moves on; Back (shown from the second step) returns a step. New co-applicant rows are added on top with Add co-applicant, and removed with the trash icon ("Remove co-applicant <n>").

  • Continue is greyed out while any red alert stands; the hover reason lists every reason, joined with " · ".

Cancel

The Cancel link returns to the opportunity without saving anything.

Sync bank ledgers

Shown inside the readiness alert when a bank account has no ledger yet; creates the missing ledgers in the promoter's books so the readiness check can pass.

  • Who: anyone with the Edit permission on Projects. Otherwise it is greyed out with "Creating the ledgers needs permission to edit projects".
  • What happens next: a toast reads "Bank ledgers created: <codes>." or "Every bank account already has its ledger."

Book

Makes the booking. A toast reads "Booked as <booking no>." and the new booking opens.

  • Who: anyone with the Create permission on Bookings.
  • Greyed out for the same reasons as Continue, with the same hover text.
  • If the server refuses, the message appears in the form banner and the wizard jumps to the step it concerns. Reasons you may see: "This opportunity already has a booking.", "This opportunity is closed (booked or lost). Reopen it first.", "Only the current, Approved estimate can be booked.", "The estimate needs a Finalized payment plan before it can be booked", "Unit is <status>", "Unit was booked by someone else moments ago", "Unit <unit> is <designation> stock, not for sale", "Parking slot <no> (<parking area>) was taken after the estimate picked it (it is <status>); pick another on a new estimate version", "That parking slot belongs to a different project.", "Estimate vN was priced on <x> sq ft chargeable; the offer now gives <y> sq ft (entitled <e> of <a>). Reprice it first" and "This unit is no longer allotted to the allottee on this project" (allottee), "<project> is not ready to sell and collect: … Open the project and finish the "Ready to sell and collect?" card.", "This project has no RERA registration number and date on file; record them under Land & RERA before estimates or bookings (organization setting).", and "No active Tax charge component (GST) exists to schedule the GST rows".

What happens when the booking is made:

  • The booking gets a number "BK-<financial year>-<sequence>" (for example BK-2026-27-00001) from the booking date's Indian financial year, the estimate's total as its agreed total, and the payment plan version it was built from.
  • The unit becomes Booked and its hold is lifted; an allottee's unit stays Allotted.
  • The estimate's parking slots are allocated to the booking and become Booked (an allottee's own parking slot stays Allotted).
  • Every other Draft or Sent estimate on the opportunity becomes Cancelled.
  • The termsheet is created in Draft with one line per estimate charge plus the GST lines, and the installment schedule is generated from the plan.
  • The opportunity becomes Booked and is closed.
  • The system rule "Booking created: accounts and legal (system)" notifies Accountants and Legal & Documentation and gives Legal the task "Prepare agreement for booking <booking no>", due in 7 days. The rule "Booking created: welcome mail with allotment letter (system)" can email the allotment letter but ships switched off.

Things to know

  • Why the estimate must be approved and current. The booking copies the estimate's charges, figures and plan without change, so the buyer gets exactly what was signed off. To change anything, make a new estimate version; it goes back for approval.
  • Why the project must be ready. Demands and receipts post to the promoter's books through the project's RERA accounts: every buyer payment enters the collection account, the bank sweeps it to the RERA separate and operative accounts, and refunds are paid from the operative account. Without promoter, books, those three accounts and their ledgers the money has nowhere to go (see RERA accounts and the daily sweep). When your organization has switched on the RERA gate, a project with no RERA registration can't book either.
  • A held unit is the normal case. A sent estimate holds the unit for this buyer until its validity date; booking lifts the hold. A unit reserved for someone else, or taken between the estimate and the booking, blocks the wizard until a new estimate version picks another.
  • Parking comes from the estimate. If a parking slot was taken after the estimate picked it, the booking is refused; pick another on a new estimate version.
  • Allottee purchases (a landowner, PAP tenant or society member buying their allotted unit) skip the Available and Saleable checks, keep the unit Allotted, and can inherit the allottee's co-owners as co-applicants. The estimate must still match the offer's current entitlement split.
  • One booking per opportunity, ever. Cancelling the booking marks the opportunity Lost (reason "Booking cancelled: <reason>") and the system rule "Booking cancelled: cancel its estimate (system)" cancels the booked estimate. Even after reopening, the same opportunity can't be booked again ("This opportunity already has a booking."); start a new opportunity.
  • The booking date drives the schedule. The down payment and any lump-sum installments fall due on it, and it decides the financial year in the booking number.

Related

  • Booking overviewScreen

    A booking's home page: the applicant and unit, parking, dates, money summary, termsheet status and possession, with the buttons to edit the booking, see its history, jump to the opportunity or cancel it.

  • BookingsScreen

    The list of every booking in your organization, with project, status and date filters and a search by booking number, applicant name or phone, to find a booking and open it.

  • Applicants & parkingScreen

    Who owns the booked unit (the primary applicant and the co-applicants with their ownership shares) and which parking slots came with the booking.

  • Termsheet & scheduleScreen

    The buyer's termsheet: the agreed charges and the installment schedule with GST, the TDS the buyer deducts and what is payable to the developer, plus the actions to issue, accept, sign, reopen or regenerate it and to re-date an installment.

  • Opportunity (Overview tab)Screen

    One buyer's enquiry on one project: who they are, what they want, the current estimate, the latest activity, documents and tasks, with the pipeline actions (estimate, assign, book, mark lost, reopen) in the header.

  • EstimateScreen

    One estimate version: its charges by group, payment plan, approvals, unit and parking hold and validity, with the lifecycle actions to send, finalize, request approval, approve or reject, extend, cancel, version and book.

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

  • ParkingScreen

    Set up the project's parking areas (basement, podium, stilt) and their numbered parking slots, see who holds each parking slot, and allocate parking slots to society members.

  • BooksScreen

    The list of every set of books in your organization, one per promoter company, with the actions to set up books for a company, open a set or delete one.

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

  • AllotteeScreen

    One society member, landowner or PAP tenant on a page: who they are, what they hold today, their co-owners, their offers on each project, the letters and files filed for them, their bank accounts and parking.

  • RulesScreen

    Every automation rule in your organization, system and custom, with filters, the switch that turns each rule on or off, and shortcuts to edit, test, clone, see the run history of or delete a rule.

  • Greyed-out buttonsScreen

    Why a button is grey and can't be clicked, where to read the reason, and why some buttons are missing altogether.

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

  • RERA accounts and the daily sweepConcept

    Every buyer payment enters the project's collection account; the bank sweeps it daily, the escrow share (70% under RERA 2016, or the project's own share) to the RERA separate account and the rest to the operative account. NirmaanOne mirrors the sweep as a Contra voucher per receipt the moment it clears, records certified withdrawals from the separate account, warns on receipts banked elsewhere and reports where the money stands; it never moves the money itself.

  • Estimate validity and the unit holdConcept

    A sent estimate holds its unit (and the parking slots it picked) for that buyer until its Valid until date; the hold starts on sending, can be extended with a reason, and an hourly job expires the estimate and frees the unit the day after the date passes.

  • Allottee purchasesConcept

    How an allottee buys the units their offer allots: one purchase per allotted unit, priced only on the area beyond their entitlement, through the same estimate, payment plan, approval and booking chain as any buyer, with the unit staying Allotted throughout.

  • Numbers and series: documents, bookings, demands, payments and vouchersConcept

    How NirmaanOne numbers what it creates: generated documents, bookings, demands, demand runs, payments, payout runs and revenue runs take a prefix, the Indian financial year and a five-digit serial (BK-2026-27-00007), while vouchers are numbered on posting from their voucher type's prefix, padded counter and suffix.

  • Booking: agreed total, applicants and sharesConcept

    A booking is the closed deal on one unit for one opportunity, made from the current Approved estimate: it fixes the agreed total, numbers itself by financial year, books the unit and parking, and names the primary applicant and the co-applicants with their ownership shares.

  • Payment plans: lumpsum, cadence, custom and construction-linkedConcept

    A payment plan says how the buyer's total is collected: all at once, in equal installments on a cadence, on agreed dates, or as construction stages are achieved; it lives on the estimate as numbered versions, is finalized with the price for approval, and becomes the booking's schedule.

  • Book a unitHow-to

    Turn an approved estimate into a booking: review what was approved, add the co-applicants and their shares, set the booking date and book, then record the agreement details and any co-applicant who joins later.

  • Make a project ready to sell and collectHow-to

    Clear every blocker on the project's "Ready to sell and collect?" card: a promoter entity, its books, the collection, RERA separate and operative bank accounts with their ledgers, and the RERA registration when your organization requires it, so bookings and allottee purchases can go through.

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

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

  • Unit or parking slot is not free: held for another buyer, not for sale, or taken before bookingTroubleshooting

    An estimate can be priced, sent or booked only on a Saleable unit that is Available or already held for this buyer, with parking slots that are free or held for this buyer; a unit or parking slot held by another buyer's sent estimate, allotted, booked, blocked, or of PAP or Common designation is refused, including when someone else takes it between the estimate and the booking.

  • "No books yet" or "has no books": set up books for the promoter company firstTroubleshooting

    Every posting follows the project's promoter company into its set of books; until that Promoter Entity company has books, the accounting screens show an empty state and demands, receipts, commissions and cancellations cannot post.