NirmaanOne Help
ScreenReviewed 2026-09-29

Demand runs

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 runs

A demand run bills everything that has fallen due on one project in one go: one demand per buyer (or per member offer) holding every open installment due on or before a date you choose. This page lists the runs and is where you draft a new one.

Where to find it

Demand runs in the header of the Demands list. The Runs breadcrumb on a demand run's page brings you back here, and so does Raise demands ("Bill the installments that have fallen due") on the dashboard, which shows with the Create permission on Demands. The notification sent by an automatic run tells finance to "Open Demands > Demand runs to review." There is no sidebar item for it.

You need the View permission on Demands. Without it the page shows "No access" and "You do not have permission to view demands. Ask your administrator."

Before you start

  • The project's promoter company needs active books. A run is refused otherwise ("The project's promoter company has no books yet. Set them up under Books first." or "These books are inactive. Reactivate them under Books to post entries.").
  • Buyers are billed only for installments with a due date. Installments tied to a construction stage get their date when the stage is achieved, so they are picked up in later runs.
  • Members are billed only on offers that are Issued, Accepted or Signed.
  • To issue the run, every charge and GST needs a ledger mapping in the books under Component mappings.

What you see

The header reads "Demand runs" with the breadcrumbs Demands > Runs, and "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."

The Books switcher in the header picks which books' runs are listed, as on the Demands list.

  • Project: Any project, or one project (shown with the View permission on Projects).
  • Status: Any status, Draft, Issued or Cancelled.
  • Search (placeholder "Search by run number"): matches the run number and the run's notes.

Columns

Column What it shows
Run The run number (DR-, the financial year and a running number), which opens the run, with the project and the subjects ("Bookings", "Member Offers" or "Both") underneath.
Dates "due up to …", the date the run collected dues up to; underneath "dated …", the demand date, and "payable by …", the due date.
Demands How many demands the run holds, with "… skipped" and "… failed" underneath when some subjects were skipped or some demands failed to issue.
Payable What the demands ask for after TDS, with the total "before TDS" underneath when they differ.
Status Draft (grey), Issued (green) or Cancelled (red).
(actions) The eye icon (tooltip "Open").

The newest runs come first. When there are none, the grid reads "No demand runs yet".

Automatic demand runs

This card lists the scheduled workflow rules that create demand runs on a timetable: "Workflow rules that create these runs, on a cadence or the moment an event happens. Manual runs stay available; an automatic run is an ordinary run whose notes name the rule." Each rule shows its name (a link to the rule), Active or Inactive, its schedule, its project or "Every project", when it runs next and how its last run went. With no rules it reads "No schedule yet."

The card shows when you have the View permission on Workflow Rules.

What you can do

New demand run

Opens the New demand run dialog: "Every open installment with a due date on or before the as-of date is billed: one demand per buyer (or member offer) holding all its due rows. Demands are drafted first; issuing the run posts them."

  • Who: anyone with the Create permission on Demands. In the default roles that is the Administrator, Finance Lead and Accountant. Without it the button isn't shown.

Fill in:

  • Project (placeholder "Choose a project"). The list needs the View permission on Projects.
  • Bill everything due on or before: today by default. Installments due up to this date are collected.
  • Demand date: today by default. Every demand in the run is dated this day.
  • Due after (days): 15 by default (0 to 365). The demands fall due this many days after the demand date.
  • Subjects: Bookings (buyers) by default, Member offers (charges and GST), or Bookings and member offers.

As soon as a project and a valid date are set, a preview shows who would be billed: a badge with the number "to bill" out of the subjects considered, "Payable" with the total, and a table of Buyer / member (with the booking number, or "Member" and the membership number, and the unit), Due rows (each charge with its row number and due date, or "nothing due" greyed out), Amount, GST, TDS and Payable.

Draft demands

The main button, Draft … demands, creates the run as Draft with one Draft demand per subject that has something due. The message reads "Run … drafted with … demands." and the run's page opens.

  • Who: anyone with the Create permission on Demands.
  • Greyed out: when no project is chosen or the preview finds nothing to bill. No reason is shown on hover.
  • What happens next: nothing is posted yet. Subjects with nothing due are listed on the run's page under Skipped subjects ("No open installment due on or before the as-of date"), as is any subject whose demand couldn't be drafted, with the reason.
  • If it's refused, the reason shows in the dialog, for example "These books are inactive. Reactivate them under Books to post entries."

Close

Closes the dialog without drafting anything.

Open

The eye icon on a row, or a click on the run number, opens the Demand run.

  • Who: anyone who can see this list.

Schedule automatic demand runs

On the Automatic demand runs card. Opens the New rule page with a demand run preset named "Monthly billing: demand run for everything due": on the 1st of every month at 09:00, create the demand run and "Tell finance" (the Finance Leads) when one was created. Adjust the schedule, the project (or every project) and the run's options, then save.

  • Who: anyone with the Create permission on Workflow Rules. In the default roles that is the Administrator. Without it the button isn't shown.

Statuses

  • Draft: drafted; its demands are drafts and nothing has been posted.
  • Issued: every demand of the run has been issued.
  • Cancelled: withdrawn before anything was issued; its draft demands were deleted.

The Demand run article explains each step.

Things to know

  • A run drafts first and posts only when issued. You can open any demand of a draft run, change or delete it, and then issue the run. Issuing needs the Issue permission on Demands, so the person who prepares the billing and the person who posts it can be different.
  • Running twice bills nothing extra. An installment already on a live demand is never picked up again, so a second run for the same date only collects what the first one missed.
  • A partly paid installment is billed in full, not for its open amount.
  • Automatic runs issue by default. A scheduled rule creates the run and issues it in one go unless its "issue" option is switched off, and it creates no run when nothing is due. The user the rule acts as needs the Create and Issue permissions on Demands.
  • A system schedule is available. The workflow rule "Daily demand runs (system)" bills every installment due on each project at 09:00 daily, for bookings and member offers, issues the demands and tells finance. It ships switched off; switch it on under Workflow rules, or clone it to change the cadence.
  • The list follows the books switcher. A run drafted for a project of other books appears once you switch to those books.
  • Your organization can rename the grid's column titles, so your screen may use different words.

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.

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

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

  • Component mappingsScreen

    Which ledger each charge component posts to in the chosen set of books (a main ledger, an optional second tax ledger, an optional cost centre and, for sale and tenant charges, the revenue treatment and contract liability ledger), and the action to copy template additions into the books.

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

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

  • Books, the active books switcher and cost centresConcept

    A set of books is the ledger of one promoter company: every posting for a project lands in its promoter's books, every accounting screen works on the one set chosen in the Books switcher, and cost centres inside the books (usually one per project with a child per tower) let the ledger and reports be cut by project.

  • 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 a whole project with a demand runHow-to

    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.

  • Put demand, payout and revenue runs on a scheduleHow-to

    Have demand runs, payout runs, revenue runs and RERA sweeps prepared on a timetable instead of by hand: start from the ready-made schedule on each runs page, adjust the day, time and options, save the rule, or simply switch on the matching system rule.

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

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

  • NotificationsScreen

    Your in-app inbox: every message the workflow rules sent you, newest first, with links to the records they are about and a way to mark them read.