NirmaanOne Help
How-toReviewed 2026-09-29

Book a unit

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.

Book a unit

Booking closes the deal on a unit. It takes the buyer's approved estimate exactly as approved (unit, charges, parking and payment plan), records who will own the unit and on what date it was booked, and creates the booking with its number, termsheet and payment schedule. From then on the money is billed through demands. The same wizard books an allottee's purchase of extra area.

Before you start

  • The opportunity's current estimate is Approved and carries a Finalized payment plan: Approve an estimate. Only the current version can be booked.
  • The unit is Available or held for this buyer by the sent estimate (Reserved For Buyer), and is Saleable stock. For an allottee's purchase the unit is Allotted to them on their offer (Split the entitlement and start the allottee's purchases).
  • Parking slots, if any, were picked on the estimate; the wizard neither adds nor changes 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, and the RERA registration when your organization requires it. See Make a project ready to sell and collect.
  • You need the Create permission on Bookings and the View permissions on Opportunities and Estimates: in the default roles the Administrator, the Sales Manager and the Sales Executive. Recording the agreement and adding co-applicants afterwards needs the Edit permission on Bookings (the Administrator, the Sales Manager and Legal & Documentation).

Steps

  1. Open the opportunity from the Opportunities list, or open its approved estimate. The header of the opportunity shows the current estimate as Approved, and Book has replaced New version as the main button.
  2. Click Book (the estimate page has the same button on an approved, current version). The wizard "Book <unit> for <name>" opens on the Review step, under "<project> · estimate vN · ₹<total>. Nothing is saved until you press Book on the last step." A green note reads "Unit <unit> is held for this buyer until <date>. Booking it lifts the hold." or, 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." Red alerts list anything that stops the booking (see below). See booking wizard.
  3. Review the step: "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)." Check the Unit, Estimate, Unit pricing plan, Parking (each parking slot, or "None"), the Charges table with its "Grand total · unit <unit>", and the Payment plan preview ("Dated from the booking date (<date>); change it on the Book step."). Click Continue. The Co-applicants step opens.
  4. Add the co-owners, if any: click Add co-applicant for each, pick an existing contact (with the View permission on Contacts) or enter a new one (first name and phone at least), fill Relationship (for example "Spouse") and Share (%). The line reads "Co-applicant shares total <n>%; the primary applicant keeps <m>%." The primary applicant is the opportunity's contact and keeps whatever share is left. 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." Click Continue. The Book step opens with "Unit <unit> for <name> at ₹<total>, with <n> co-applicants, <n> parking slots."
  5. Set the Booking date (today by default; hint "The down payment (if any) and lumpsum rows fall due on this date.") and any Notes.
  6. Click Book. You see "Booked as <booking no>." and the new booking's overview opens: the unit is Booked, the Termsheet card shows Draft, and the opportunity is Booked.
  7. Record the paperwork when you have it: on the booking overview click Edit ("Edit <booking no>"), fill Token amount, Agreement date, Agreement no. ("As registered; unique across the organization's bookings"), Registration date and Notes, and click Save changes. You see "Booking <no> updated." Everything else on the booking is fixed: "The unit, applicant, agreed amount and payment plan are fixed; regenerate the schedule from the Termsheet tab or cancel the booking to change them."
  8. To add a co-owner after booking, open the Applicants & parking tab (Applicants & parking) and click Add co-applicant. Pick or enter the person, fill Relationship and Share, and click Add co-applicant. You see "<name> added as co-applicant." and the card reads "The primary applicant holds <x>%; co-applicants share the rest." The pencil changes a co-applicant's relationship or share; the bin removes one ("Remove co-applicant?").

What happens next

  • The booking gets its 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; the estimate's parking slots become Booked. An allottee's unit and their own parking slot stay Allotted.
  • Every other Draft or Sent estimate on the opportunity becomes Cancelled, and the opportunity is closed as Booked.
  • The termsheet is created in Draft with one line per estimate charge plus the GST lines, and the installment schedule dated from the booking date. Next: Issue, accept and sign the buyer's termsheet, then raise demands from the Demands & money tab.
  • The system rule "Booking created: accounts and legal (system)" notifies the 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.
  • Shares record ownership for the agreement only; demands and receipts are raised on the booking as a whole. To book in a different primary name, cancel and book again from a fresh opportunity (Cancel a booking).

If something goes wrong

  • The wizard shows "<project> is not ready to sell and collect, so nothing can be booked on it yet." with its reasons and fix links (Choose the promoter, Set up the books, Add the collection account, Add the RERA separate account, Add the operative account, Add the GST account, or Sync the bank ledgers; "Demands and receipts post to the promoter's books through these bank accounts; without them the money has nowhere to go."), or booking is refused with "<project> is not ready to sell and collect: … Open the project and finish the "Ready to sell and collect?" card.": finish the project's readiness. See Project not ready (trouble.projects.project-not-ready).
  • "Record the RERA registration" in that list, or "This project has no RERA registration number and date on file; record them under Land & RERA before estimates or bookings (organization setting).": see RERA required (trouble.projects.rera-required).
  • "Unit <unit> is <status>.", "Unit is <status>", "Unit was booked by someone else moments ago", "Unit <unit> is <designation> stock, not for sale" or "Parking slot <no> (<parking area>) was taken after the estimate picked it (it is <status>); pick another on a new estimate version": the unit or a parking slot is no longer free. See Unit taken before booking (trouble.sales.unit-taken-before-booking).
  • "Estimate vN is <status>; only an Approved estimate can be booked." or "Only the current, Approved estimate can be booked.": get the estimate approved first. See Estimate not current or in the wrong status (trouble.sales.estimate-not-current).
  • "Estimate vN is not the current version.": a newer version exists; book that one. See Estimate not current (trouble.sales.estimate-not-current).
  • "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." or "The estimate needs a Finalized payment plan before it can be booked": finalize the plan on the estimate. See Finalize in order: pricing, plan, approval, booking (trouble.sales.cannot-finalize-plan-pricing-first).
  • "Co-applicant shares add up to <n>%, more than 100%" or "The primary applicant cannot also be a co-applicant" (after booking: "The primary owner cannot also be a co-owner."): fix the shares or the person. See Co-owner or co-applicant shares over 100% (trouble.societies.co-owner-shares-over-100).
  • "This opportunity already has a booking." or "This opportunity is closed (booked or lost). Reopen it first.": the opportunity was booked or lost meanwhile; open the booking from the header, or reopen the opportunity.
  • "Estimate vN was priced on <x> sq ft chargeable; the offer now gives <y> sq ft (entitled <e> of <a>). Reprice it first", "Unit <unit> is <status>, no longer allotted to this allottee." or "This unit is no longer allotted to the allottee on this project" on an allottee's purchase: the offer changed after pricing; see Split the entitlement and start the allottee's purchases.
  • Book isn't shown, or "You do not have permission to view booking creation. Ask your administrator.": your role lacks the Create permission on Bookings. See No permission (trouble.common.no-permission).

Related

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

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

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

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

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

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

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

  • TasksScreen

    Follow-ups for you and your team: add tasks by hand or let workflow rules raise them, link each to the record it is about, assign it, and mark it done.

  • Approve or reject an estimateHow-to

    Find an estimate that is awaiting approval from the approvals inbox or your task, review its price and payment plan, and approve it so it can be booked or reject it with comments for the team to revise.

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

  • Issue, accept and sign the buyer's termsheetHow-to

    Take the booking's termsheet from Draft to Issued, Accepted and Signed on the Termsheet & schedule tab, optionally emailing the term sheet document through the seeded workflow rule.

  • Record the token, agreement and registrationHow-to

    Note the token amount, the agreement date and number and the registration date on an active booking from its Edit panel, once the paperwork with the buyer is done.

  • Cancel a bookingHow-to

    Cancel a booking with the four-step cancellation wizard: see which demands are reversed, set the forfeiture and charges the rule suggests, set the refund, and confirm, which releases the unit and parking slots, marks the opportunity Lost and posts every entry in one go.

  • Split the entitlement and start the allottee's purchasesHow-to

    Decide how the entitled area falls on each allotted unit and how much of the extra area the allottee pays for, then open a purchase per unit and price it through the usual estimate, approval and booking.

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

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

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

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

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

  • Estimate action refused: not the current version, or the wrong statusTroubleshooting

    Estimate actions apply only to the current (highest live) version and only in certain statuses: a Draft is edited, a Draft or Sent version is finalized, a Pending Approval one is approved, the current Approved one is booked; anything else is refused and usually means the page is stale or an older version is open.

  • Payment plan cannot be finalized, or the estimate cannot be approved or booked: finalize in orderTroubleshooting

    An estimate goes price first, plan second: the pricing is locked, then a payment plan whose shares add up to 100% is finalized, which requests approval; only an Approved estimate with a Finalized plan can be booked.

  • Co-owner or co-applicant shares refused: over 100%, or the primary listed againTroubleshooting

    Co-owners of an allottee and co-applicants on a booking share ownership with the primary person: their shares together may not pass 100%, the primary cannot also be listed as a co-owner or co-applicant, and the same person cannot be added twice.

  • "No access" or "You do not have permission": your role lacks a permissionTroubleshooting

    Every screen, button and picker is gated by a permission on a module; your role decides which you hold, so a missing one shows as a No access card, a refused action, a greyed-out button with a hover reason, or a picker that explains which permission it needs.

  • SellGuide

    The sales flow from lead to handover: readiness, opportunities, estimates and payment plans, approval, booking, termsheet, schedule changes, possession, and email campaigns.