NirmaanOne Help
ScreenReviewed 2026-09-29

Booking overview

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.

Booking overview

This is the booking's home page. It shows who bought which unit, the parking that came with it, the agreed money and what has been paid, the state of the termsheet, and how far possession has got. From here you edit the few details that can change after booking, hand the unit over, and cancel the booking if the deal falls through.

Where to find it

Open a booking from the Bookings list. You also land here from Open booking on the opportunity, from the Booking field on demand, voucher and commission pages, from an allottee's page, from the ledger report, and straight after Book in the booking wizard. The Booking button on a demand, payment or commission page opens the Demands & money tab instead.

You need the View permission on Bookings. Without it the page shows "No access" and "You do not have permission to view bookings. Ask your administrator." If the booking can't be loaded, the page reads "Booking not found." with a Back to bookings link.

What you see

  • The title is the booking number, with the breadcrumbs Bookings › <booking no>.
  • Three badges: the booking status (Active or Cancelled), the opportunity's stage (Lead, Estimate, Approval, Booked or Lost) and the project name, which opens the project.
  • A line "<applicant> · unit <unit>, <tower> · ₹<total> agreed".
  • The header buttons: History, Workflows, Opportunity, Edit and Cancel booking (see below).

On a cancelled booking a warning banner reads "Cancelled on <date>: <reason>" followed by "The unit and parking slots were released." and, when the cancellation wizard recorded money, "Forfeited ₹…; refund ₹…" with a "refund payout" link to the refund payment (the link shows only when a refund payout exists and you have the View permission on Payments).

Tabs

The booking has eight tabs, in this order:

Applicant & unit card

Primary applicant, Phone, Email, Co-applicants (a count, or "None"), Unit (with its status badge), Tower / floor ("<tower>, floor <n>"), Project (a link), Parking slots ("<parking area> <parking slot no>, …" or "None") and Channel partner.

For an allottee's purchase (a landowner, PAP tenant or member buying their allotted unit) three more rows appear: Allottee purchase (the tenant category, linking to the allottee's page), Entitled (free) and Chargeable area ("<chargeable> of <total>").

Parking card

Shown only when the booking holds parking slots: the project's parking layout in view mode with the booked parking slots highlighted.

Dates & notes card

Booking date, Agreement date, Agreement no., Registration date, Created, Updated and Notes. Agreement and registration details are empty until you record them with Edit.

Money card

  • Agreed total: the approved estimate's total including GST, fixed at booking.
  • Scheduled: the total of the payment schedule.
  • Paid: money received against the booking's demands.
  • Token: the token amount, if one was recorded with Edit.
  • Estimate: "Version <n> · ₹<total>", linking to the estimate when you have the View permission on Estimates (otherwise just "Version <n>").

Termsheet card

The termsheet Status, Issued and Signed dates, and the Payment plan ("v<n> · <plan summary>"). The Schedule link opens the Termsheet & schedule tab. "No termsheet." appears when the booking has none.

Possession card

Tracks the handover of the unit. A badge next to the title reads Offered once possession is offered and Handed over once the unit is handed over. The rows are:

  • Occupation certificate: "<date> · <number> (tower)" or "(project)", whichever OC covers the unit, or "Not recorded".
  • Possession offered, Handed over and Conveyance registered: each date once set, with a small clear icon beside it for users who can edit the booking.
  • Revenue recognised on: the trigger the promoter's books use to recognise revenue, or "<n> days after the offer" when the books deem possession handed over after a set number of days. The policy is looked up on the offer date or, before an offer, the OC date, so the row stays empty until one of those exists, and while the promoter has no books or no revenue policy applies.

Two alerts can appear: "No occupation certificate covers this unit yet, so possession cannot be offered." (on an active booking that needs an OC) and "Revenue on this booking is recognised; its possession dates stay as posted."

Agreement for sale card

The agreement's state (No agreement yet, Signed, not registered, Registration overdue, Over the advance cap, Registered), when it was signed and registered, the register-by date (four months from signing), what was taken before registration against the organization's advance cap, and the stamp duty and registration facts. Edit (the Edit permission on Bookings, active bookings) opens the form for all of them. See Agreement for sale compliance.

Tasks card

The tasks linked to this booking ("No tasks yet for this record." when there are none), with Add task. The card shows only with the View permission on Tasks; Add task needs the Create permission on Tasks. See Tasks.

What you can do

History

The History button (clock icon, tooltip "Who changed this record, what and when") opens the History panel for the booking, titled "History · <booking no>": every change to the booking and its lines (co-applicants and the like), newest first.

  • Who: anyone with the View permission on Bookings or on Audit Trail. With the View permission on Audit Trail the panel also offers Open in the audit log, which opens Settings › Audit log filtered to this booking.

Workflows

Runs a manual workflow rule against the booking.

  • Who: anyone with the View permission on Workflow Runs. The menu is hidden when no manual rule exists for bookings; none is provided by default, so you'll see it only if your organization has added one under Rules.

Opportunity

Opens the opportunity this booking came from.

  • Who: anyone with the View permission on Opportunities. Without it the button isn't shown.

Edit

Opens the panel "Edit <booking no>" with the only fields that stay editable after booking:

  • Token amount (₹, hint "Optional").
  • Agreement date ("Optional").
  • Agreement no. (hint "As registered; unique across the organization's bookings"; up to 100 characters).
  • Registration date ("Optional").
  • Notes ("Optional"; up to 2,000 characters).

The panel explains: "The unit, applicant, agreed amount and payment plan are fixed; regenerate the schedule from the Termsheet tab or cancel the booking to change them."

Save changes stays greyed out until you change something. On success a toast reads "Booking <no> updated." If the agreement number is already on another booking the form shows "Agreement number <no> is already on another booking".

  • Who: anyone with the Edit permission on Bookings, and only while the booking is Active. In the default roles that is the Administrator, the Sales Manager and Legal & Documentation. On a cancelled booking the button isn't shown, and the app refuses the change anyway ("This booking is cancelled and can no longer be changed.").

Cancel booking

Opens the Cancel booking wizard.

  • Who: anyone with the Edit permission on Bookings, on an Active booking only. Finishing the cancellation needs more than that; see the wizard's article.

Offer possession

On the Possession card. Opens the dialog "Offer possession" with a Date (defaults to today; it can't be before the booking date) and the note "Workflow rules can send the possession letter when possession is offered." Confirm with Offer possession (greyed out until a date is chosen) or close with Cancel. A toast reads "Possession offered on <date>."

  • Who: anyone with the Edit permission on Bookings, on an Active booking whose revenue has not yet been recognised. The button disappears once a date is set.
  • Greyed out with "Record the occupation certificate on the tower or the project first" whenever no occupation certificate is recorded on the tower or the project (the card can only read the revenue policy once an OC or an offer date exists, so without an OC the button is always greyed out). The app also refuses an offer date earlier than the OC when the books' revenue policy in force on that date requires one, or no policy is set: "<tower or project> has no occupation certificate on or before <date>; record the OC on the tower or the project first".

Hand over

Opens the dialog "Hand over", which warns "Unit <unit> becomes Sold. Revenue follows at the next revenue run when the books recognise it on handover." Pick the Date and confirm with Hand over. A toast reads "Handed over on <date>." The unit's status becomes Sold.

  • Who: as for Offer possession.
  • Greyed out with "Offer possession first" until an offer date is set. The app also refuses a handover dated before the offer ("The handover cannot be before the offer of possession") or before the booking ("A possession date cannot be before the booking date").

Register conveyance

Opens the dialog "Register conveyance" with a Date; confirm with Register conveyance. A toast reads "Conveyance registered on <date>."

  • Who: as for Offer possession. It is never greyed out, but the date can't be before the booking date.

Clear a possession date

The small cross beside a set date (labels "Clear possession offered", "Clear handed over" and "Clear conveyance registered") removes it. A toast reads "… cleared." Clearing the handover date sets the unit back to Booked.

  • Who: as for Offer possession. The offer date can't be cleared once the unit is handed over.

Schedule

The link on the Termsheet card opens the Termsheet & schedule tab.

Statuses

  • Booking: Active from the moment it is made; Cancelled only through the Cancel booking wizard. There is no way back to Active.
  • Opportunity stage: Booked when the booking is made, Lost when it is cancelled.
  • Unit: Booked at booking (an allottee's unit stays Allotted), Sold on handover, Available again on cancellation (an allottee's unit leaves their offer and returns to the status it had before the offer took it).
  • Termsheet: see Termsheet & schedule.

Things to know

  • Once revenue is recognised, the possession dates are frozen. The promoter's books post revenue on the booking through a revenue run, and after that the dates that triggered it can't move; the card says "Revenue on this booking is recognised; its possession dates stay as posted."
  • Possession needs an occupation certificate first. The Offer possession button stays greyed out until an OC is recorded on the tower or, failing that, the project; the tower's OC is used when both exist. The date check behind it comes from the books' revenue policy: when the policy requires an OC, or no policy has been set, an offer dated before the OC is refused.
  • Handing over marks the unit Sold so the inventory shows it as gone for good; clearing the handover puts it back to Booked.
  • "Paid" here and "Paid" on the termsheet tab are different figures. The Money card counts money received against the booking's demands; the termsheet tab counts what has been placed on individual installments by hand. They match only once every receipt has been appropriated.
  • The agreement number is unique across the organization, so a mistyped number that belongs to another booking is refused rather than silently duplicated.
  • Cancelling releases everything. The unit, its parking slots and the schedule are freed, the opportunity is marked lost, and the cancelled banner keeps the reason and the money outcome for the record.
  • Clearing the handover always sets the unit to Booked, even for an allottee's unit, which was Allotted before the handover.

Related

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

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

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

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

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

  • PaymentScreen

    One receipt or payout: its details, amounts and allocations, and the actions to clear it, bounce it, cancel it, edit it or delete it.

  • History panelScreen

    See who changed a record, what they changed and when, including the record's lines, newest first, and jump to the full audit log.

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

  • Audit logScreen

    The organization-wide change log: every create, change and delete, every sign-in (including refused ones), sign-out and downloaded file, with who did it, when, from where and what changed.

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

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

  • Revenue policyScreen

    The CA's effective-dated choices on how the books recognise sale revenue and the costs that go with it: framework, method, possession trigger, OC rule, cost treatments and judgement areas.

  • Revenue runScreen

    One period close: what each booking and member offer recognises, the journals and cost moves it posts, the subjects it left out, and the actions to recompute, post, reverse or delete it.

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

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

  • Possession: offer, handover, conveyance and the occupation certificateConcept

    Possession of a booked unit is recorded as three dates on the booking (possession offered, handed over, conveyance registered); the occupation certificate on the tower or project is what allows the offer, the handover marks the unit Sold, and the books' revenue policy names which of these dates is the moment sale revenue is recognised.

  • Revenue recognition: policy, point in time vs over time, and revenue runsConcept

    Each set of books carries an effective-dated revenue policy (framework, method, possession trigger, cost and brokerage treatments, judgement areas) chosen by the CA; a revenue run is the period close that computes every booking's and member offer's progress under it, recognises the catch-up revenue, cost of sales and brokerage, and posts the journals.

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

  • Record the occupation certificate and hand over a unitHow-to

    Record the OC on the tower or the project, then on the booking offer possession, hand the unit over (it becomes Sold) and register the conveyance; the books recognise the revenue at the next revenue run.

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

  • Possession cannot be offered or handed over: no occupation certificate, wrong dates or revenue already recognisedTroubleshooting

    Possession is offered only once an occupation certificate (the tower's, else the project's) dated on or before the offer is recorded, when the revenue policy requires one; the handover must follow the offer, no date may precede the booking, and once a revenue run has recognised the booking its possession dates are locked.

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

  • DemandScreen

    One demand: the installments it bills, its amounts with GST, the expected TDS and what is payable in money, the receipts and TDS credits against it and how the money is placed on the charges, with the actions to edit, issue, cancel or delete it.

  • VoucherScreen

    One voucher with its lines and bill allocations, its reversal links, its history, and the actions to post, reverse, cancel or delete it.

  • CommissionScreen

    One channel-partner commission: the partner, the brokerage with GST and TDS, the payouts against it, and the actions to edit, approve, cancel or delete it.

  • Ledger reportScreen

    The ledger of one account between two dates: opening balance, every posting with a running balance, and closing balance, with CSV export.