Demand run
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 run
This page shows one demand run: what it collected, the demands it drafted, who was skipped and why, and any demand that couldn't be issued. It is where you review the batch and issue it, or cancel it before anything is posted.
Where to find it
- The run number or the eye icon on the Demand runs list.
- Drafting a run opens its page straight away.
- A link in a notification, a task or the audit log.
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." If the run doesn't exist, the page shows "Not found" and "That item could not be found."
What you see
The header shows the run number with the breadcrumbs Demands > Runs > the run number, the status badge, a blue project badge (a link to the project) and a grey badge with the subjects (Bookings, Member Offers or Both). The line underneath reads "… demands · … payable · installments due up to …".
When the run is cancelled, an alert reads "Cancelled on …; its draft demands were deleted." If the last issue or cancel attempt was refused, its reason shows in a red alert.
Run
| Field | What it shows |
|---|---|
| Installments due on or before | The as-of date: installments due up to this date were collected. |
| Demand date | The date on every demand of the run. |
| Due date | When the demands fall due, with the number of days after the demand date in brackets. |
| Books | The books the demands post to: those of the project's promoter company. |
| Issued | When the run was issued. |
| Notes | The run's notes. A run created by a scheduled rule reads Automatic: rule "…". |
Totals
- Demands: how many demands the run holds.
- Total incl. GST: the sum of the demands' charges and GST.
- Payable (after TDS): what the buyers and members have to pay.
- Skipped subjects: how many bookings or offers were left out.
… demands failed on the last attempt
A red card that appears after an issue attempt in which some demands couldn't post. It lists each demand number with the reason, and reads "Fix the cause (a missing ledger mapping, inactive books) and run the action again; documents already posted are not touched."
Demands in this run
The demands the run drafted, in the same grid as the Demands list, with its search and columns. Each demand number opens the Demand.
Skipped subjects
A card with a count badge, listing each booking (by booking number) or offer ("offer to …") the run left out and why. "No open installment due on or before the as-of date" is shown in grey; any other reason, such as a drafting error, in amber.
What you can do
The header buttons show only while the run is Draft and you hold the permission; they are hidden, not greyed out, otherwise.
Issue demands
Issue … demands issues every Draft demand of the run. The confirmation "Issue the run?" reads "Every Draft demand of … 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.
- Who: anyone with the Issue permission on Demands. In the default roles that is the Administrator, Finance Lead and Accountant.
- When: while the run is Draft and at least one of its demands is still Draft.
- What happens next: each draft demand is issued on its own, exactly as Issue on the demand's page does: a Sales voucher dated the demand date, the buyer's or member's ledger debited with a new bill, TDS to TDS Receivable, each charge and GST credited to its mapped ledger. A charge whose revenue treatment is With the unit is credited to its contract liability ledger (2100 Contract Liability - Sale of Units, or 2110 Contract Liability - Differential Area) rather than revenue, to be recognised by a later revenue run, unless the books' revenue policy in force on the demand date is Revenue on billing. When every demand goes through, the message reads "Run … issued: … demands posted." and the run turns Issued.
- If some demands fail, the message reads "… demands could not be issued; see the failures below." The demands that posted stay Issued; the ones that failed stay Draft and are listed in the red card with the reason in the app's own words, for example "Charge component … has no ledger mapping in books …", "Books … are inactive" or "No fiscal year of these books covers …; open it first". The run stays Draft. Fix the cause and click Issue … demands again: only the remaining drafts are issued, and the run turns Issued once none is left.
- If it's refused outright: "The run holds no demand to issue." when the run has no demand left to issue.
Cancel run
Withdraws a draft run. The confirmation "Cancel the run?" reads "The draft demands of … are deleted; nothing was posted." Click Cancel run.
- Who: anyone with the Edit permission on Demands. In the default roles that is the Administrator, Finance Lead and Accountant.
- When: while the run is Draft and none of its demands has been issued. After a partly failed issue the button is still shown, but the app refuses: "Some demands of this run are already issued; cancel those individually with credit notes."
- What happens next: "Run cancelled; its draft demands were deleted." The run turns Cancelled, its draft demands are removed and their installments are free to be billed again.
Open
A demand number in Demands in this run opens the Demand, where you can edit, issue, cancel or delete that one demand.
- Who: anyone who can open this page.
Statuses
- Draft: drafted. Issue … demands moves it to Issued once every demand has posted; Cancel run moves it to Cancelled.
- Issued: every demand has been issued. Final.
- Cancelled: the draft demands were deleted. Final.
Things to know
- Each demand is issued on its own, so one buyer's problem (a charge without a ledger mapping, for example) doesn't hold up the others. That is why a run can end up half issued: fix the cause and issue again rather than cancelling.
- The demands are ordinary demands. Anything you can do on a demand's page, you can do to a demand of this run: edit or delete a draft before issuing, cancel an issued one with a credit note, record receipts. The demand's page doesn't mention the run.
- The run's counts and totals are refreshed only when it is drafted, issued or cancelled. If you delete, edit or cancel one of its demands from the demand's page, the figures here catch up at the next issue.
- A run can't be cancelled once a demand of it is issued, even one. Cancel the issued demands one by one (each gets a credit note) and delete the remaining drafts from their pages.
- Payable is after TDS. For buyers whose deal reaches the section 194-IA threshold, the demand asks for the total less the TDS they deduct; the run's Payable (after TDS) adds those up.
- Automatic runs created by a scheduled rule are usually already Issued when you open them, unless the rule's "issue" option is off or some demands failed.
Related
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.
- 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.
- 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.
- VoucherScreen
One voucher with its lines and bill allocations, its reversal links, its history, and the actions to post, reverse, cancel 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 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.
- Project overviewScreen
A project's home page: its details, site, land, RERA registration, inventory summary, whether it is ready to sell and collect, where its money stands across its RERA accounts, and the setup checklist.
- 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.
- 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.
- 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.
- 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.
- 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.
- TasksScreen
Follow-ups for you and your team: add tasks by hand or let workflow rules raise them, link each to the record it is about, assign it, and mark it done.
- Audit logScreen
The organization-wide change log: every create, change and delete, every sign-in (including refused ones), sign-out and downloaded file, with who did it, when, from where and what changed.