NirmaanOne Help
TroubleshootingReviewed 2026-09-29

Revenue run cannot be started, posted or reversed: a draft exists, the period is out of order, or the status forbids

Revenue runs on a set of books form a chain: one draft at a time, each run ending on or after the last posted one, and reversals from the latest run backwards; each action fits one status only.

Messages this explains

  • “A Draft estimate already exists for this opportunity. Edit that draft instead of creating another.”
  • “Run <no> already closed <date>; a new run must end on or after it”
  • “Reverse run <no> first: later runs start from this one”
  • “Only a Draft run can be refreshed (this one is <status>)”
  • “Only a Draft run can be posted (this one is <status>)”
  • “Only a Posted run can be reversed (this one is <status>)”
  • “Only a Draft run can be deleted; reverse a posted one”
  • “A draft posts nothing. Posting recomputes it from the books as they stand, then posts one journal per project for the revenue and one for the brokerage released.”
  • “Reversed <datetime>: <reason>. The next run starts again from the run before this one.”
  • “Reversed <datetime>. The next run starts again from the run before this one.”

Revenue run cannot be started, posted or reversed: a draft exists, the period is out of order, or the status forbids

You tried to prepare, recompute, post, reverse or delete a revenue run and the app refused.

What you see

In the New revenue run dialog on Revenue runs, after Prepare draft:

  • "A Draft estimate already exists for this opportunity. Edit that draft instead of creating another." when the books already hold a Draft revenue run. The wording is misleading on this screen (it is the message used for estimates); here it means that a revenue run of these books is still a draft and must be posted or deleted first.
  • "Run <no> already closed <date>; a new run must end on or after it" when the period end you chose is before the period end of the latest Posted run.

On the Revenue run page:

  • The blue note on a draft: "A draft posts nothing. Posting recomputes it from the books as they stand, then posts one journal per project for the revenue and one for the brokerage released."
  • Recompute (in a pop-up notice): "Only a Draft run can be refreshed (this one is <status>)".
  • Post run: "Only a Draft run can be posted (this one is <status>)", or "Run <no> already closed <date>; a new run must end on or after it" when a later run was posted after this draft was made.
  • Reverse <run no>?: "Only a Posted run can be reversed (this one is <status>)", or "Reverse run <no> first: later runs start from this one" when a later run has been posted since.
  • Delete this draft?: "Only a Draft run can be deleted; reverse a posted one".
  • After a reversal the amber alert stays: "Reversed <datetime>: <reason>. The next run starts again from the run before this one." (without the reason when none was given).

Why it happens

Revenue runs on one set of books form a chain. Each run computes what each booking and member offer has earned up to its period end, and posts only the difference from the last posted run that held that booking. That is why the order matters:

  • One draft at a time. A draft is a preview computed from the books as they stand. Two drafts would each claim to be the next link in the chain, so the books hold one until it is posted or deleted.
  • Periods never go backwards. A new run must end on or after the latest posted run's period end; otherwise it would recognise revenue for a period a later run has already closed. The check is repeated at posting time, so a draft made before a later run was posted can no longer post.
  • Reverse from the latest run backwards. Reversing mirrors every journal of the run. A later run started from this run's figures, so the run cannot be pulled out from under it; the later run must be reversed first. After a reversal the chain continues from the run before the reversed one.
  • One action per status. A run is Draft (recompute, post, delete), Posted (reverse) or Reversed (final: no delete, no re-post). The message names the status the run really has, usually because someone else acted on it after you opened the page.

A run also needs active books and an open fiscal year covering the period end with its period unlocked (see No fiscal year covers that date and These books are inactive).

How to fix it

  1. A draft already exists: open it from Revenue runs (status Draft). Either Post run (the Approve permission on Revenue Recognition; Administrator and Finance Lead by default; without it the button is greyed out) or Delete draft (the Delete permission on Revenue Recognition), then press New revenue run and Prepare draft again. Preparing a run needs the Create permission on Revenue Recognition (also the Accountant).
  2. Period before the last run: in the New revenue run dialog choose a period end on or after the date in the message. If the later run itself was wrong, reverse it first (step 4) and then run the earlier period.
  3. A stale draft cannot post ("Run <no> already closed <date>"): a later run was posted after this draft was made. Delete draft and start again with a period end on or after that date.
  4. Reverse later runs first: on Revenue runs find the latest Posted run, open it, press Reverse, give a Reason (and a Reversal date if it should not be the run's own date) and confirm with Reverse run (the Approve permission on Revenue Recognition). Repeat until the run you want to reverse is the latest posted one. Every reversal posts mirror journals; nothing is deleted from the books.
  5. The status does not match: refresh the page. The buttons follow the run's real status: Recompute, Delete draft and Post run on a draft, Reverse on a posted run, nothing on a reversed one.
  6. To recognise the reversed period again, create a new run for it. It starts from the run before the reversed one, as the alert says, and picks up any policy change made in between (see Revenue policy cannot be changed or deleted).

Related

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

  • 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 policy cannot be changed or deleted: a posted run used it, or the settings do not fit the frameworkTroubleshooting

    A revenue policy that a posted revenue run has used stays as history and is changed by adding a new policy from a later date; a set of books always keeps one policy, two cannot start on the same date, and the significant financing component is only available under Ind AS 115 and needs a rate.

  • Posting refused: no open fiscal year or period for the dateTroubleshooting

    Every posting, manual or automatic, needs a fiscal year of the books that covers its date, with the year open and the month's period unlocked; open the next year, unlock the period or reopen the year under Books, or move the document's date.

  • "These books are inactive": nothing posts until the books are reactivatedTroubleshooting

    Posting a voucher, issuing a demand, recording a payment, starting a run or cancelling a booking is refused because the promoter's books are inactive; what is blocked and how to reactivate them.

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