Demand run: some demands could not be issued, or the run holds nothing
A demand run issues each demand on its own, so one that cannot post is listed under "failed on the last attempt" while the others go through; a run whose demands were all cancelled or deleted, or a subject with nothing due, is reported rather than issued.
Messages this explains
- “<n> demands failed on the last attempt”
- “1 demand failed on the last attempt”
- “Fix the cause (a missing ledger mapping, inactive books) and run the action again; documents already posted are not touched.”
- “<n> demands could not be issued; see the failures below.”
- “1 demand could not be issued; see the failures below.”
- “The booking is cancelled”
- “A <status> offer cannot be billed; issue it first”
- “The run holds no demand to issue.”
- “No open installment due on or before the as-of date”
Demand run: some demands could not be issued, or the run holds nothing
You pressed Issue <n> demands on a demand run and not every demand posted, or the run had nothing to issue in the first place.
What you see
On the Demand run page:
- After Issue, the red toast "<n> demands could not be issued; see the failures below." ("1 demand could not be issued; …" for a single one). The run stays Draft, and a red card "<n> demands failed on the last attempt" lists each demand number with its reason, followed by "Fix the cause (a missing ledger mapping, inactive books) and run the action again; documents already posted are not touched." The reasons are the server's own wording, for example "Charge component <code> has no ledger mapping in books <name>", "Books <name> are inactive", "No fiscal year of these books covers <date>; open it first", "Period <n> of <FY> is locked", "Fiscal year <name> is closed", "The booking is cancelled" or "A <status> offer cannot be billed; issue it first".
- The Issue <n> demands button shows only while the run still holds a Draft demand. On a page opened before someone else cancelled or deleted every demand of the run, Issue the run? fails with "The run holds no demand to issue."
- The Skipped subjects card lists buyers or members the run drafted nothing for, with "No open installment due on or before the as-of date" in grey, or another reason in amber (the same texts as above when drafting itself failed).
On Demand runs, the Demands column shows "<n> skipped, <n> failed" under the count, and Draft <n> demands in the New demand run dialog stays greyed out while the preview finds nothing to bill.
Why it happens
A run is a batch of ordinary demands: one Draft demand per buyer (or member offer) holding every open installment due on or before the as-of date. Issuing posts one Sales voucher per demand, and each demand is posted in its own step. If one cannot post, it is recorded with its reason and the loop goes on, so a single unmapped charge or a buyer in another state does not hold up the rest. The run turns Issued only when no Draft demand remains, which is why it stays Draft after a partial failure. Issuing again touches only the demands still in Draft.
The failures come from the same checks a single demand goes through: the promoter's books must exist and be active, every charge component on the demand must be mapped in those books, the standard ledgers (1300 TDS Receivable, 2230 IGST) must be there, and a fiscal year must cover the demand date with its period unlocked. The booking must still be Active (or the offer still Issued, Accepted or Signed).
A run holds nothing to issue when every demand of it was cancelled or deleted one by one on its own page. (If the remaining demands were all issued one by one instead, issuing the run simply marks it Issued.) A subject is skipped with "No open installment due on or before the as-of date" when its schedule has no Pending or Partially Paid receivable row dated on or before the as-of date that is not already on a live demand. Rows without a due date, typically installments tied to a construction stage not yet achieved, are never picked.
How to fix it
- Read the reason beside each failed demand and fix it:
- "Charge component <code> has no ledger mapping in books <name>" or "These books have no active ledger copied from template <code>; sync templates": see Posting stopped: a charge component or standard ledger is missing (the Edit permission on Chart of Accounts).
- "No fiscal year of these books covers <date>; open it first", "Period <n> of <FY> is locked" or "Fiscal year <name> is closed": see No fiscal year covers that date (the Edit permission on Books).
- "Books <name> are inactive": reactivate the books, see These books are inactive (Edit on Books).
- "The booking is cancelled" or "A <status> offer cannot be billed; issue it first": that demand can't issue; open it and Delete the draft (the Delete permission on Demands) or Cancel demand (Edit on Demands).
- Back on the run, press Issue <n> demands again. You need the Issue permission on Demands; in the default roles that is the Administrator, the Finance Lead and the Accountant. Only the demands still in Draft are attempted; the ones already posted are not touched. Or open a failed demand from Demands in this run and press Issue there.
- When the run turns Issued, the failures card disappears. If you would rather not issue the remaining drafts, delete or cancel them one by one; Cancel run is refused once any demand of the run is issued (see Demand or commission cannot be cancelled).
- For "The run holds no demand to issue.", nothing is pending: reload the page, check Demands in this run to see what happened to each demand, then draft a new run if anything is still due.
- For subjects skipped with "No open installment due on or before the as-of date", nothing is wrong. To bill them, draft a new run with a later date under Bill everything due on or before, or give the installment its due date: mark the construction stage achieved on the project's Construction Stages tab (the Edit permission on Construction Stages) or check the schedule on the booking's Termsheet & schedule tab.
Related
- Demand run
- Demand runs
- Demand
- Termsheet & schedule
- Construction Stages
- Posting stopped: a charge component or standard ledger is missing from these books
- Posting refused: no open fiscal year or period for the date
- "No books yet" or "has no books": set up books for the promoter company first
- "These books are inactive": nothing posts until the books are reactivated
- Demand or commission cannot be cancelled, edited or approved
Related
- Demand runScreen
One demand run: its dates and totals, the demands it drafted, the subjects it skipped and the demands that failed to issue, with the actions to issue or cancel the run.
- Demand runsScreen
Every demand run of the chosen books, the dialog that previews and drafts a run billing everything due on a project, and the scheduled rules that create runs automatically.
- 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.
- 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.
- Construction StagesScreen
Plan the project's construction stages (plinth, slabs, possession…) with their shares and dates, record commencement and completion, and keep the certificates and photos for each stage.
- Posting stopped: a charge component or standard ledger is missing from these booksTroubleshooting
A demand, payout, commission, cancellation or revenue run could not post because a charge component has no ledger in the promoter's books, or a template ledger or group the posting needs was never copied into them; map the component or sync the templates, then retry.
- 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.
- "No books yet" or "has no books": set up books for the promoter company firstTroubleshooting
Every posting follows the project's promoter company into its set of books; until that Promoter Entity company has books, the accounting screens show an empty state and demands, receipts, commissions and cancellations cannot post.
- "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.
- Demand or commission cannot be cancelled, edited or approved: payments are against it, or its status forbidsTroubleshooting
A demand with receipts, or a commission with payouts, cannot be cancelled until that money is bounced, cancelled or reallocated; and once issued or approved, the document's figures are fixed, so only a Draft demand or an Accrued commission can be edited or deleted.