NirmaanOne Help
TroubleshootingReviewed 2026-09-29

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

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.

Messages this explains

  • “Record the occupation certificate on the tower or the project first”
  • “No occupation certificate covers this unit yet, so possession cannot be offered.”
  • “<tower/project> has no occupation certificate on or before <date>; record the OC on the tower or the project first”
  • “Offer possession first”
  • “A possession date cannot be before the booking date”
  • “Offer possession before handing the unit over”
  • “The handover cannot be before the offer of possession”
  • “Revenue on this booking is recognised; its possession dates stay as posted.”
  • “Revenue on this booking is already recognised; its possession dates stay as posted”
  • “A cancelled booking has no possession”
  • “This booking is cancelled and can no longer be changed.”
  • “No occupation certificate on or before the trigger date”
  • “Waiting for: <trigger>”

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

The Possession card on the booking will not let you offer possession or hand the unit over, a date you picked is refused, or a revenue run leaves the booking at 0% with a note about possession or the occupation certificate (OC).

What you see

On the Possession card of the Booking overview:

  • An amber alert "No occupation certificate covers this unit yet, so possession cannot be offered.", and Offer possession greyed out with "Record the occupation certificate on the tower or the project first" on hover. The card's Occupation certificate row reads "Not recorded".
  • Hand over greyed out with "Offer possession first".
  • A blue alert "Revenue on this booking is recognised; its possession dates stay as posted.", and no possession buttons at all.

In the Offer possession, Hand over or Register conveyance dialog, after you pick a date:

  • "<tower or project> has no occupation certificate on or before <date>; record the OC on the tower or the project first", for example "Tower B has no occupation certificate on or before 2027-03-01; record the OC on the tower or the project first".
  • "A possession date cannot be before the booking date"
  • "Offer possession before handing the unit over"
  • "The handover cannot be before the offer of possession"
  • "Revenue on this booking is already recognised; its possession dates stay as posted"
  • On a booking cancelled in the meantime, the server's "A cancelled booking has no possession" is shown as "This booking is cancelled and can no longer be changed."

On a Revenue run, under a booking's Progress:

  • "Waiting for: <trigger>", for example "Waiting for: possession handed over".
  • "No occupation certificate on or before the trigger date".

Why it happens

A buyer can only be offered possession of a building the municipal authority has certified fit to occupy. NirmaanOne records the OC on the tower (Occupation certificate no. and OC date on the tower in Structure) or, for the whole project, on the project's Settings tab under Possession. A tower's own OC wins for its units; a tower without one is covered by the project's.

  • The OC rule. The promoter's books carry a revenue policy with the switch Occupation certificate required (on by default). While it is on, possession can be offered only when the unit's OC is dated on or before the offer date. The card greys out Offer possession whenever no OC is recorded at all; the dialog also refuses an offer date earlier than the OC date.
  • The order of events. Possession is offered, then handed over, then the conveyance is registered. No date may be before the booking date, and the handover cannot come before the offer. Handing over makes the unit Sold; clearing the handover date puts it back to Booked.
  • Revenue locks the dates. For a point-in-time policy, the possession event the books name (Recognise on: possession offered, handed over, deemed handed over or conveyance registered) is when the sale becomes revenue. Once a posted revenue run has recognised revenue on the booking, its possession dates are part of the books and cannot be changed or cleared.
  • The revenue run waits for the same facts. "Waiting for: <trigger>" means the booking has no date yet for the event the policy names (or it falls after the period end). "No occupation certificate on or before the trigger date" means the policy requires an OC and the tower's (or project's) OC is missing or later than that event.

How to fix it

  1. Record the OC. For one tower: the project's Structure tab, open the tower, fill in Occupation certificate no. and OC date, and save (the Edit permission on Towers, Floors & Units). For the whole project: the project's Settings tab, section Possession, Occupation certificate no. and OC date, then Save settings (the Edit permission on Projects). Use the date printed on the certificate.
  2. Offer possession on the booking's Possession card with a date on or after both the OC date and the booking date. This needs the Edit permission on Bookings (in the default roles the Administrator, the Sales Manager and Legal & Documentation) and an Active booking.
  3. Hand over once the offer is recorded, with a date on or after the offer date; then Register conveyance when it is registered. See Hand over a unit.
  4. If a date was entered wrongly before any revenue was recognised, clear it with the x next to it on the card and set it again. The offer date cannot be cleared while a handover date is set; clear the handover first.
  5. If revenue is already recognised and a possession date is wrong, the CA reverses the revenue run that recognised it (Reverse on the Revenue run, the Approve permission on Revenue Recognition), you correct the date, and the next run picks it up.
  6. For a revenue run at 0%, record the missing possession date on the booking or the OC on the tower or project (steps 1 to 3), then recompute or prepare the next run.
  7. Whether an OC is required at all is the CA's choice on the books' revenue policy (Revenue policy, the Approve permission on Revenue Recognition). Recording the OC is the usual fix; turning the switch off does not by itself ungrey Offer possession on a booking that has no possession date and no OC.

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.

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

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

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

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

  • Reverse a posted revenue runHow-to

    Undo the latest posted revenue run of a set of books: every journal it posted is mirrored, the run becomes Reversed, and the next run starts again from the run before it.

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