NirmaanOne Help
How-toReviewed 2026-09-29

Bill a whole project with a demand run

Draft one demand per buyer (or member offer) for every installment due on a project up to a date, review the batch, and issue all of it in one action.

Bill a whole project with a demand run

Instead of raising demands booking by booking, a demand run bills everything that has fallen due on a project in one action: one demand per buyer (or per member offer) holding every open installment due on or before a date. The run drafts the demands first so you can review them, then issues them together; each demand is then an ordinary demand.

Before you start

  • The project's bookings have issued termsheets whose installments carry due dates. Installments linked to a construction stage get a due date only when the stage is achieved; until then a run never picks them. Installments already on a live demand are skipped.
  • The project promoter's books exist and are active with a fiscal year covering the demand date (Set up the books), and every charge component billed is mapped to a ledger (Map a charge component to a ledger).
  • You need the Create permission on Demands to draft a run, the Issue permission on Demands to issue it and the Edit permission on Demands to cancel it: in the default roles the Administrator, the Finance Lead and the Accountant. Picking the project in the dialog needs the View permission on Projects, which those roles hold.
  • The runs list shows the runs of the books chosen in the header switcher; a run drafted for a project of other books appears once you switch to those books. The dialog itself offers every project and bills each in its own promoter's books.

Steps

  1. Open Demands in the sidebar and click Demand runs in the header (Demand runs). The page reads "Bill everything that has fallen due on a project in one action: one demand per buyer (or member offer) with every open installment due on or before the as-of date. Draft, review, issue; each demand is then an ordinary demand." It lists earlier runs (Run, Dates, Demands, Payable, Status) and, below, the Automatic demand runs card. The dashboard's "Raise demands" launcher brings you here too.
  2. Click New demand run. In the dialog "New demand run", choose the Project, set Bill everything due on or before (today by default), Demand date (today), Due after (days) (15) and Subjects: "Bookings (buyers)", "Member offers (charges and GST)" or "Bookings and member offers". A preview loads as soon as the project and date are set: a badge "<n> to bill" of "<m> subjects", "Payable <amount>" (no ₹ sign), and a table with Buyer / member (booking number or "Member <no>", the unit), Due rows ("<charge code> #<n> (<due date>)", or "nothing due" with the row greyed), Amount, GST, TDS and Payable.
  3. Click Draft <n> demands (greyed out while no project is chosen or nothing is due). You see "Run <no> drafted with <n> demands." and the run page opens (Demand run) with a Draft badge, the project and the scope. The Run card shows the dates, Due date "<date> (<n> days)" and the Books; the Totals card shows Demands, Total incl. GST, Payable (after TDS) and Skipped subjects; Demands in this run lists the drafts; Skipped subjects names each buyer left out with the reason ("No open installment due on or before the as-of date" in grey, or an error in amber).
  4. Review the batch. Open any demand from Demands in this run: it is an ordinary Draft demand with its own DM- number (Demand); use Edit to change its dates or rows, or Delete to take it out of the batch, then return to the run. The run's counts and totals are recalculated only when the run is issued or cancelled.
  5. Click Issue <n> demands. The dialog "Issue the run?" reads "Every Draft demand of <run no> is issued: one Sales voucher each (buyer debited the full total, revenue and GST credited; the TDS the buyer deducts arrives later as a TDS credit). A demand that cannot post is reported and the others still go through." Click Issue. You see "Run <no> issued: <n> demands posted." The badge reads Issued, Issued on the Run card shows the time, and every demand in the grid reads Issued with its sales voucher number.
  6. If the toast reads "<n> demands could not be issued; see the failures below.", the run stays Draft and a red card "<n> demand(s) failed on the last attempt" lists each demand with its message and the advice "Fix the cause (a missing ledger mapping, inactive books) and run the action again; documents already posted are not touched." Fix the cause (see below) and click Issue <n> demands again for the remaining drafts; the run turns Issued once no draft is left.
  7. To drop the batch before issuing, click Cancel run and confirm with Cancel run in "Cancel the run?" ("The draft demands of <run no> are deleted; nothing was posted."). You see "Run cancelled; its draft demands were deleted." and the banner "Cancelled on <date time>; its draft demands were deleted." The installments are open again.

What happens next

  • Each issued demand posts its own Sales voucher dated the demand date, with the buyer's bill for the full total due on the run's due date. Nothing is posted to TDS Receivable: a booking demand's 194-IA deduction is shown as expected TDS and reaches the books when the buyer's deposit is recorded as a TDS credit (TDS under section 194-IA). The demands appear under Demands and on each booking's Demands & money tab; from there the flow is the same as for a single demand: Record and clear a buyer's receipt, appropriation, Record a TDS credit. A wrong demand is cancelled on its own page with a credit note: Cancel or correct a demand.
  • Running the same run again bills nothing extra: rows on a live demand are skipped, so a second run for the same date only picks up installments that became due or were freed since.
  • To bill on a cadence without opening the dialog, click Schedule automatic demand runs on the Automatic demand runs card (the Create permission on Workflow Rules). The New rule page opens with the preset "Monthly billing: demand run for everything due" (every month on day 1 at 09:00, create the run and tell finance); adjust the schedule, the project and the options and click Create rule. The rule issues the run it creates unless you switch that option off; its owner needs the Issue permission on Demands. Alternatively switch on the seeded "Daily demand runs (system)" rule under Rules. Automatic runs list "Automatic: rule "<name>"" under Notes and notify the Finance Leads.

If something goes wrong

  • "Charge component <code> has no ledger mapping in books <name>" in the failures card: map the component under Chart of Accounts > Component mappings and issue again. See Component not mapped (trouble.accounting.component-not-mapped) and Demand run issue failed (trouble.accounting.demand-run-issue-failed).
  • "These books are inactive. Reactivate them under Books to post entries." when drafting, or "Books <name> are inactive" in the failures card when issuing. See Books inactive (trouble.accounting.books-inactive).
  • "The project's promoter company has no books yet. Set them up under Books first.": create the promoter's books. See No books yet (trouble.accounting.no-books-yet).
  • "No fiscal year of these books covers <date>; open it first", "Fiscal year <name> is closed" or "Period <n> of <year> is locked" in the failures card: open the fiscal year, or open the failed draft and Edit its Demand date, then issue again. See Fiscal year missing (trouble.accounting.fiscal-year-missing).
  • "The run holds no demand to issue.": every draft was deleted or cancelled one by one; draft a new run. See Demand run issue failed (trouble.accounting.demand-run-issue-failed).
  • "Some demands of this run are already issued; cancel those individually with credit notes." on Cancel run: after a partly failed issue the run holds issued demands. Cancel each of them on its own page (Cancel or correct a demand) and delete the remaining drafts. Same article (trouble.accounting.demand-run-issue-failed).
  • The Project list in the dialog is empty: your role lacks the View permission on Projects. See No permission (trouble.common.no-permission).

Related

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

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

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

  • DemandsScreen

    Every demand raised in the chosen books, on bookings and on society members' offers, with filters for status, subject, project and dates, and the way into demand runs.

  • New ruleScreen

    Build an automation rule on a full page: which records it watches, what starts it, which records qualify, and the ordered actions it carries out.

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

  • Raise and issue a demand on a bookingHow-to

    Bill one or more installments of a booking's payment schedule: draft the demand from the booking, check its GST and TDS, issue it to post the sales voucher, and send the demand letter.

  • Record and clear a buyer's receiptHow-to

    Record the money a buyer paid against an issued demand as a consideration receipt (and the GST they paid as its own GST receipt), clear it to post the receipt voucher, give the buyer their receipt, and hand the TDS they deducted to a TDS credit.

  • Cancel or correct a demandHow-to

    Fix or remove a draft demand, or cancel an issued one with a credit note so its installments are free to be billed again.

  • TDS under section 194-IAConcept

    When a flat's consideration reaches the threshold, the buyer withholds 1% of every installment and deposits it with the Income Tax department instead of paying it to the developer; NirmaanOne bills the buyer the full total, shows the expected TDS and what is payable in money, and books the withheld tax only when the buyer's deposit (Form 16B / 26QB) is recorded as a TDS credit.

  • Bill and collect a member's chargesHow-to

    Raise and issue a demand on the charge and tax rows of a society member's redevelopment offer, record the member's receipt against it, and place the money on the charges.

  • Set up the books for a promoter companyHow-to

    Create the set of books a promoter company keeps, mirror its projects as cost centres, check the voucher numbering series and the component mappings, and connect the project's bank accounts to their ledgers so demands, receipts and payouts can be posted.

  • Map a charge component to a ledgerHow-to

    Tell a set of books which ledger each charge component posts to (with its tax leg, cost centre and, for sale and tenant charges, the revenue treatment), so demands, benefit accruals, payouts and commissions can be posted automatically, and give future books the same default through a template mapping.

  • Demands, demand runs and the GST splitConcept

    A demand is the bill raised on a buyer's installments (or a member's offer charges): numbered by financial year, billing the full total with the buyer's expected 194-IA TDS shown apart, posted as a sales voucher with GST split as CGST + SGST or IGST by place of supply; a demand run raises one demand per buyer for everything due by a date.

  • Demand run: some demands could not be issued, or the run holds nothingTroubleshooting

    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.

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

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

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

  • CollectGuide

    Map charges to ledgers, raise and issue demands on bookings and member offers (singly or in runs), record and clear receipts, appropriate them, handle bounces, chase overdue demands, mirror the bank's daily RERA sweeps and watch the RERA accounts.

  • DashboardScreen

    The page you land on after signing in: shortcuts to common jobs, a queue of what is waiting on you, the headline figures and one card each for projects, sales, stock, receivables, construction and the RERA accounts.