NirmaanOne Help
How-toReviewed 2026-09-29

Record the occupation certificate and hand over a unit

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.

Record the occupation certificate and hand over a unit

Possession is recorded in three dated steps on the booking: the office offers possession, the buyer takes the unit over, and the conveyance is registered. Handing over makes the unit Sold, and the promoter's books recognise the sale revenue at the next revenue run on whichever of these dates their revenue policy names. Before possession can be offered, the occupation certificate (OC) that covers the unit must be on record, on the tower or, failing that, on the project.

Before you start

  • The booking is Active (Book a unit) and no posted revenue run has recognised revenue on it yet; once it has, the possession dates are part of the books and stay as posted.
  • The OC. The books' revenue policy has Occupation certificate required switched on by default ("No possession can be offered, and no revenue recognised, before the tower's (or project's) OC date."). A tower's own OC wins for its units; the project's OC covers towers without one.
  • Permissions: the Edit permission on Towers, Floors & Units to record a tower's OC; the Edit permission on Projects for the project's OC; the Edit permission on Bookings for the possession steps (in the default roles the Administrator, the Sales Manager and Legal & Documentation).

Steps

  1. Record the OC on the tower: open the project, choose the Structure tab and click the pencil on the tower's card (hover "Edit <name>"). In the panel fill Occupation certificate no. ("Optional. This tower's own OC; blank = the project's OC covers it.") and OC date ("Possession can be offered on this tower's units from this date.") and click Save changes. You see “Tower "<name>" updated.” See Structure.
  2. Or record one OC for the whole project: open the project's Settings tab, and under Possession ("The occupation certificate lets possession be offered on the whole project.") fill Occupation certificate no. ("For the whole project. A tower with its own OC (Structure > tower) uses that one.") and OC date ("Blank until the OC is received."), then click Save settings. You see "Project settings saved." See Project settings.
  3. Open the booking from the Bookings list. On its overview the Possession card now shows Occupation certificate as "<date> · <number> (tower)" or "(project)", the empty rows Possession offered, Handed over and Conveyance registered, and Revenue recognised on with the trigger the books use (for example Possession handed over, or "<n> days after the offer"). Offer possession is no longer greyed out.
  4. Click Offer possession. The dialog "Offer possession" notes "Workflow rules can send the possession letter when possession is offered." Set the Date (today by default; it can't be before the booking date) and confirm with Offer possession. You see "Possession offered on <date>." The card shows the badge Offered and the date, with a small cross to clear it.
  5. Click Hand over. The dialog "Hand over" warns "Unit <unit> becomes Sold. Revenue follows at the next revenue run when the books recognise it on handover." Set the Date and confirm with Hand over. You see "Handed over on <date>." The badge reads Handed over and the unit's status on the project's structure is Sold.
  6. When the conveyance deed is registered, click Register conveyance, set the Date and confirm with Register conveyance. You see "Conveyance registered on <date>." This step is never greyed out and can be recorded before or after the handover; the date can't be before the booking date.

What happens next

  • The unit is Sold. Clearing the handover date with its cross ("Handed over cleared.") puts the unit back to Booked; the offer date can't be cleared once the unit is handed over.
  • Each date fires an event for workflow rules (possession offered, handed over, conveyance registered), so a rule you set up can send the possession letter or notify the team; none of the rules NirmaanOne ships listens to these events. See Rules.
  • At the next revenue run of the promoter's books, revenue on the booking is recognised on the date named by the policy's Recognise on (Possession offered, Possession handed over, the default, Deemed handed over after the set number of days, or Conveyance registered), or by the organization's default or the project's own Recognise revenue on on its Settings tab. Until the trigger date is reached the run's line reads "Waiting for: possession handed over" (or the trigger in force). See Revenue runs.
  • Once a posted run has recognised the revenue, the card shows "Revenue on this booking is recognised; its possession dates stay as posted." and the buttons disappear.
  • Charges the pricing plan collects at possession are already on the termsheet under "At the time of possession", dated on the project's expected possession date; bill them through demands as usual.

If something goes wrong

  • Offer possession greyed out with "Record the occupation certificate on the tower or the project first", the card's warning "No occupation certificate covers this unit yet, so possession cannot be offered.", or the dialog's "<tower or project> has no occupation certificate on or before <date>; record the OC on the tower or the project first": do steps 1 or 2, or pick an offer date on or after the OC date. The card only reads the policy once an OC or an offer date exists, so without an OC the button stays greyed out even under a policy that doesn't require one. See Possession needs an OC (trouble.sales.possession-needs-an-oc).
  • Hand over greyed out with "Offer possession first", or "Offer possession before handing the unit over": record the offer of possession (step 4) first. See Possession cannot be offered or handed over (trouble.sales.possession-needs-an-oc).
  • "A possession date cannot be before the booking date" or "The handover cannot be before the offer of possession": the dates are out of order; correct the date. See Possession cannot be offered or handed over (trouble.sales.possession-needs-an-oc).
  • "Revenue on this booking is already recognised; its possession dates stay as posted" or the card's "Revenue on this booking is recognised; its possession dates stay as posted.": a posted revenue run already carries this booking. The CA would have to reverse that run before the dates can change. See Possession cannot be offered or handed over (trouble.sales.possession-needs-an-oc).
  • "This booking is cancelled and can no longer be changed.": the booking was cancelled while your screen was open (on a Cancelled booking the possession buttons aren't shown). See Booking is cancelled or its schedule rows are no longer Pending (trouble.bookings.booking-locked).
  • The buttons aren't shown on an active booking, or the pencil on the tower card is missing: your role lacks the Edit permission on Bookings, Towers, Floors & Units or Projects. See No permission (trouble.common.no-permission).

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.

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

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

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

    The revenue runs (period closes) of the chosen books, the dialog that prepares a new draft run, and the scheduled rules that draft runs automatically.

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

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

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

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

  • Set the revenue policy and prepare the chart for itHow-to

    Record the CA's revenue recognition choices for a set of books as an effective-dated policy, set an organization-wide default or a project override where needed, and prepare the chart, cost centres, cost budgets and construction stages the revenue runs read.

  • Prepare, review and post a revenue runHow-to

    The monthly revenue close: prepare a draft revenue run for a period end, read what each booking and member offer would recognise, fix what holds lines back, post the run's journals, and check the contract balances and the balance sheet.

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

  • Expected possession date and charges at possessionConcept

    The project's expected possession date is when the charge groups a pricing plan collects "at time of possession" fall due: one undivided row per charge, owed from booking, outside the buyer's payment plan, re-dated on every open booking when the date changes.

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

  • Booking is cancelled or its schedule rows are no longer Pending: the change is refusedTroubleshooting

    A cancelled booking accepts no edits, demands, receipts, commissions or reschedules, and on a live booking only Pending schedule rows can be re-dated; paid, partly paid, waived and cancelled rows stay as they are, and the payment plan of a booked estimate is changed by regenerating the termsheet, never by cancelling the plan.

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