NirmaanOne Help
TroubleshootingReviewed 2026-09-29

Booking cannot be cancelled yet: pending payments, or revenue already recognised

The cancel wizard stops on its first step while a receipt or payout on the booking is still Pending, while revenue on the booking is recognised under a policy that does not allow cancelling, or when the booking is already cancelled.

Messages this explains

  • “The booking cannot be cancelled yet; clear or cancel the pending payments first.”
  • “Receipt <no> is Pending; clear or cancel it first”
  • “Payout <no> is Pending; clear or cancel it first”
  • “The booking is already cancelled”
  • “This booking is already cancelled.”
  • “Revenue on this booking is recognised and the revenue policy does not allow cancelling it; the CA can switch the policy to a sales return”

Booking cannot be cancelled yet: pending payments, or revenue already recognised

You opened Cancel booking and the wizard lists a problem in red on its first step, and Next stays greyed out.

What you see

On step 1, Entries reversed, of the Cancel booking wizard, a red alert lists each blocker:

  • "Receipt <no> is Pending; clear or cancel it first"
  • "Payout <no> is Pending; clear or cancel it first"
  • "Revenue on this booking is recognised and the revenue policy does not allow cancelling it; the CA can switch the policy to a sales return"
  • "The booking is already cancelled"

Next is greyed out while any blocker is listed (no reason on hover), and so is Cancel booking on the last step. If a blocker appears between opening the wizard and confirming, the final step shows the same messages, or "The booking cannot be cancelled yet; clear or cancel the pending payments first."

On a booking that is no longer Active, the page also shows the warning "This booking is already cancelled."

Why it happens

Cancelling posts everything in one go: credit notes for the demands, the forfeiture and charges, and a refund worked out from the money actually received. Those figures have to be final.

  • A Pending payment is money in transit. A receipt that is still Pending (a cheque not yet cleared, say) has posted nothing and may still bounce; a pending payout may still be cancelled. If the booking were cancelled around them, the refund would be worked out on the wrong amount, or money would arrive against a cancelled booking. Every pending receipt and payout recorded against the booking must first be settled one way or the other.
  • Recognised revenue follows the CA's policy. Once a revenue run has recognised revenue on the booking, cancelling it is a sales return in the accounts. The books' revenue policy says whether that is allowed: under Cancelling after revenue is recognised = Not allowed (the default), the booking "cannot be cancelled once its revenue is in the books". The policy in force on the cancellation date decides.
  • Already cancelled. Cancellation is final; there is no way back to Active and nothing to cancel twice. This usually means someone else finished the cancellation while your page was open.

How to fix it

  1. Open each pending payment. The number in the blocker is the payment number; find it on the Receipts and payouts card of the booking's Demands & money tab and open its Payment page.
  2. Settle it, with the Edit permission on Payments:
  3. For recognised revenue, the CA (the Approve permission on Revenue Recognition) opens the books' Revenue policy and sets Cancelling after revenue is recognised to Sales return on the policy in force on the cancellation date. A policy a posted run has used is locked, so add a new policy (New policy from a date) instead, starting after the locked policy's own start date and on or before the cancellation date, so that it is the one in force. The next posted run then reverses the booking's revenue and cost of sales.
  4. Go back to the wizard (reload it, or open Cancel booking again from the Booking overview). The blockers are worked out afresh from the books and the Cancellation date on step 1.
  5. "Already cancelled": nothing to do. Open the booking to see who cancelled it and when.

Related

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

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

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

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

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

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

  • Receipts and payouts: allocation, clearing and the UTRConcept

    A receipt is recorded as Pending and settles the payer's open demands by itself, oldest due first; a payout is allocated to commissions or member rows by hand. Both post their voucher only when cleared and can be bounced afterwards; the UTR is the bank's transfer reference, typed on NEFT-style payments and per payout when a payout run is cleared.

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

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

  • Bounce a returned payment or correct a pending oneHow-to

    Mark a cheque or transfer the bank returned as bounced so its voucher is reversed and the demand reopens, and fix, cancel or delete a payment that is still pending.

  • Cancel booking fails on the last step: it needs Edit on Demands and Create on PaymentsTroubleshooting

    Opening the cancel wizard needs only the Edit permission on Bookings, but posting the cancellation also writes credit notes and a refund payout, so it needs the Edit permission on Demands and the Create permission on Payments as well. With the default roles only the Administrator holds all three.