Booking: agreed total, applicants and shares
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.
Booking: agreed total, applicants and shares
A booking is the closed sale of one unit to one buyer. It is made from the opportunity's current Approved estimate, and from that moment the price, the unit, the parking slots and the payment plan are fixed on the booking: everything that happens next (the termsheet, demands, receipts, possession) hangs off it. The primary applicant is the buyer on the opportunity; co-applicants are the other people who will own the unit, each with a share of ownership.
How it works in NirmaanOne
How a booking is made
The Booking wizard (Book on the opportunity or the estimate; the Create permission on Bookings) reviews exactly what was approved, takes optional co-applicants, then a Booking date and notes, and books. "Nothing is saved until you press Book on the last step." The checks, in order: the RERA gate and project readiness (see Project readiness and the RERA gate); no booking yet on the opportunity; the opportunity not Lost; the estimate is this opportunity's current Approved version; the unit is Available or held for this buyer, and Saleable; the estimate has a Finalized payment plan; every parking slot the estimate picked is still free for this buyer.
On success:
- the booking gets its number BK-<financial year>-<serial>, for example BK-2026-27-00007: the Indian financial year of the booking date (April to March) and the next number in that year;
- the agreed total is copied from the estimate's grand total, GST included, and never changes;
- the unit becomes Booked and its hold is cleared; the parking slots on the estimate are allocated to the booking and become Booked (an allottee's own unit and parking slot stay Allotted);
- every other Draft or Sent version of the opportunity is Cancelled;
- a Draft termsheet is created with the full payment schedule built from the finalized plan and dated from the booking date;
- the opportunity moves to Booked; the seeded rule tells Accountants and Legal and gives Legal the task "Prepare agreement for booking <number>".
One opportunity can have one booking, ever; one unit can have one Active booking at a time ("Unit was booked by someone else moments ago" if two people race for it).
What the booking carries
- Agreed total: the estimate's grand total. The booking's Money card also shows Scheduled (the sum of every schedule row), Paid (money received against the booking's demands) and Token. On the Demands & money tab, Balance is agreed − received; on a deal with TDS it never quite reaches zero, because the TDS is deposited with the Income Tax department rather than paid to you.
- Dates and notes: Token amount, Agreement date, Agreement no. (unique across the organization's bookings: "Agreement number <no> is already on another booking"), Registration date and Notes are recorded later from Edit (the Edit permission on Bookings, Active booking only). "The unit, applicant, agreed amount and payment plan are fixed; regenerate the schedule from the Termsheet tab or cancel the booking to change them."
- Statuses: Active from creation; Cancelled only through the cancellation wizard. The unit becomes Sold when possession is handed over.
Applicants and shares
- The primary applicant is the opportunity's contact (for an allottee purchase, the allottee). It cannot be changed on the booking.
- Co-applicants are added in the wizard's Co-applicants step or later on the Applicants & parking tab (Add co-applicant; the Edit permission on Bookings, Active booking). Each has a contact (existing, or a new one, which gets the Customer contact type), a Relationship to the primary ("e.g. Spouse", up to 50 characters) and a Share in percent, 0 to 100, which may be left blank.
- The primary applicant's share is always 100% less the co-applicants' shares; it is worked out, never typed. The tab's heading reads "The primary applicant holds <x>%; co-applicants share the rest."
- The co-applicants' shares may add up to at most 100%: "Co-applicant shares add up to <n>%, more than 100%". The primary applicant cannot also be a co-applicant, and the same contact cannot be listed twice.
- On an allottee's booking, leaving the co-applicants empty books the unit in the names the allottee already holds: their co-owners become the co-applicants with their shares.
Shares are recorded so the agreement, the allotment letter and later documents name every owner with the right proportion; they do not split demands or receipts, which stay on the booking as one account with the primary applicant's ledger.
Example
On 5 October 2026 Priya Nair books unit A-1203 for Rakesh Shah from estimate v1, approved at ₹1,36,94,683.00 with a finalized construction-linked plan and parking slot P-14.
- The booking is BK-2026-27-00007 (financial year 2026-27, the seventh booking of that year), Active, agreed total ₹1,36,94,683.00. A-1203 and P-14 are Booked; the opportunity is Booked; the termsheet is Draft with its schedule dated from 5 October.
- In the Co-applicants step she adds Meera Shah (Spouse, Share 40) and Mahesh Shah (Father, Share 10). The running line reads "Co-applicant shares total 50%; the primary applicant keeps 50%."
- A month later the family asks to add a brother at 55%. Add co-applicant refuses it: "Co-applicant shares add up to 105.00%, more than 100%". Editing Meera to 30% first makes room.
- The agreement is registered on 20 October: Edit records Agreement no. MH/2026/10/4471, Agreement date and Registration date 20 October 2026, and a Token amount of ₹5,00,000.00 that was taken at booking.
Where you see it
- Booking wizard: the checks, the Co-applicants step and Book.
- Bookings: booking number, applicant, unit, Agreed, Paid and status.
- Booking overview: the Applicant & unit, Dates & notes, Money and Termsheet cards, and Edit.
- Applicants and parking: the shares and the allocated parking slots.
- Termsheet and schedule: the schedule the booking created.
- Demands and money: what has been billed and received against it.
- Cancel booking: how a booking ends.
- Structure and Parking: the Booked status.
Related
- Estimate versions, price lock, overrides and the approval gate
- Estimate validity and the unit hold
- Payment plans: lumpsum, cadence, custom and construction-linked
- Project readiness and the RERA gate
- Booking cancellation, forfeiture and refund
- Demands, demand runs and the GST split
- Opportunity stages, lead sources and system activities
Related
- 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.
- 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.
- 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.
- Demands & moneyScreen
The booking's demands, receipts and payouts, and channel-partner commission in one place, with shortcuts to raise a demand, record a receipt and accrue commission.
- Booking documentsScreen
The letters and agreements generated for one booking, such as the allotment letter, together with the receipts of its payments and the letters of its demands, with the button to generate another from a published template and the icons to preview, download, email, void or delete each one.
- Cancel bookingScreen
The four-step wizard that cancels a booking: it shows the demands and receipts that will be reversed, suggests the forfeiture and charges from the rule in force, sets the refund and posts everything in one go, releasing the unit and parking and marking the opportunity lost.
- 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.
- StructureScreen
Build and maintain a project's towers (wings), floors and units, generate them in bulk, and see every unit's status and designation at a glance.
- 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.
- Estimate versions, price lock, overrides and the approval gateConcept
Every priced offer to a buyer is a numbered version of the opportunity: a Draft is edited in place, any later price change is a new version that supersedes the current one, the price is locked when finalized, and every estimate must be approved before it can be booked.
- 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.
- 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.
- 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.
- Booking cancellation, forfeiture and refundConcept
Cancelling a booking reverses its demands with credit notes, posts the forfeiture and any charges against the buyer's ledger by the rule in force, creates the refund as a pending payout for the credit that is left, and frees the unit and parking; with nothing billed or received it only frees them.
- Demands, demand runs and the GST splitConcept
A demand is the bill raised on a buyer's installments (or a member's offer charges): numbered by financial year, billing the full total with the buyer's expected 194-IA TDS shown apart, posted as a sales voucher with GST split as CGST + SGST or IGST by place of supply; a demand run raises one demand per buyer for everything due by a date.
- Opportunity stages, lead sources and system activitiesConcept
An opportunity moves through Lead, Estimate, Approval and Booked (or Lost) only through the actions taken on it; every move is written to its stage history and its timeline, where locked system activities sit beside the calls and visits the team logs.