NirmaanOne Help
How-toReviewed 2026-09-29

Raise and issue a demand on a booking

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.

Raise and issue a demand on a booking

A demand is the bill for one or more installments of the buyer's payment schedule. You draft it from the booking by picking the installments, check the GST and the TDS the buyer will deduct, and issue it: issuing posts the sales voucher (the buyer's ledger debited with a bill, revenue and GST credited) and from then on receipts settle it. Use a demand run instead to bill every buyer of a project at once.

Before you start

  • The booking is Active and its termsheet exists, so the schedule has installments: Issue, accept and sign the buyer's termsheet. Only Pending or Partially Paid installments with an amount, and not already on a live demand, can be billed. A construction-linked installment gets its due date when the stage is achieved.
  • 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 on the installments (and the GST component) is mapped to a ledger in those books (Map a charge component to a ledger). Without a mapping the draft is fine but the issue is refused.
  • You need the Create permission on Demands to draft and the Issue permission on Demands to issue: in the default roles the Administrator, the Finance Lead and the Accountant. Edit on Demands lets you change a draft. Without a permission the button isn't shown.
  • TDS under section 194-IA is computed by the organization's rule in force on the demand date (1% from ₹50,00,000 of consideration as seeded; see Organization). The demand still bills the full total; the TDS reduces what the buyer pays you in money, and the buyer deposits it with the Income Tax department and hands over Form 16B, which you record as a TDS credit (TDS under section 194-IA).

Steps

  1. Open the booking and choose the Demands & money tab (Demands & money). On the Demands card ("Bills raised on the payment schedule; issuing posts the sales voucher.") click Raise demand. The slide-over "Raise demand on <booking no>" opens with Demand date (today), Due date and Narration (placeholder "Shown on the demand and the sales voucher"), and the table Installments to bill: one row per open installment with #, Due (the date, "On <stage>" or "At possession", plus its status badge), Total amount, GST, TDS and Payable. A partly paid installment is marked "Partly paid"; one whose charges are partly on another demand reads "<n> of its charges already billed".
  2. Tick the installments to bill, or click Select all open installments (Clear all unticks them). Picking an installment bills every open charge row in it. The footer row reads "Demand for <n> installment(s)" with the summed amount, GST, TDS and payable, and the note under the table reminds you that "The figures follow the schedule as at each due date; the demand recomputes TDS by the rule in force on the demand date." Set the Due date (the hint reads "Defaults to the latest picked due date (<date>)." once rows are picked) and, if you want, type a Narration.
  3. Click Draft demand · <payable> payable (greyed out until an installment is ticked; amounts in this dialog have no ₹ sign, as in "5,25,000.00"). You see "Demand drafted for <total>." and the demand page opens (Demand) with a Draft badge. The draft already carries its DM- number. The header reads "<buyer> · booking <no> · unit <no> · <total> billed · <payable> payable in money after <TDS> TDS". The Details card shows the dates, Buyer, Booking and Narration; the Amounts card shows Total amount (the amount before GST), GST, Grand total billed, "Expected TDS 194-IA @ 1%" as a deduction, Payable in money, Received, TDS credited and Outstanding, with the note "The buyer is billed the full total and pays it in money less the TDS they deduct (194-IA). The TDS reaches the books when their deposit (Form 16B / 26QB) is recorded as a TDS credit; the demand reads Paid once the money received reaches the payable, with the TDS credit shown as pending until then." The Instalments card lists what is billed "as the payment plan reads" with Amount (excl. GST), GST and Total per instalment.
  4. Check the figures. If something is off, click Edit: the slide-over "Edit draft demand" lets you change Demand date, Due date and Narration and tick or untick the rows; click Save changes. You see "Demand updated." Changing the demand date recomputes the TDS by the rule in force on the new date.
  5. Click Issue. The dialog "Issue this demand?" reads "The demand gets its number and the sales voucher is posted: the buyer's ledger is debited with a new bill, revenue and GST are credited per component. Lines can no longer change." Click Issue. You see "Demand <no> issued; voucher <no> posted." The badge reads Issued, Issued and Sales voucher (a link to the voucher) fill on the Details card, Edit, Issue and Delete disappear from the header, and Record receipt appears next to Cancel demand.
  6. To send the demand letter, click Generate document on the Documents card, choose "Demand letter (standard)" under Template and click Generate. You see "<number> generated." (a DL- number). On the row, click Email, type the buyer's address under To and click Send ("Sent to <addresses>."), or Download PDF. The template ships as a Draft; an administrator publishes it once under Document templates. To email the letter on every issue automatically, switch on "Demand issued: email the demand letter (system)" under Rules; it ships off.

What happens next

  • Issuing posts a Sales voucher dated the demand date: the buyer's ledger is debited with the full total as a bill numbered as the demand and due on the due date, and each charge is credited to its mapped ledger with its GST legs (CGST + SGST when the buyer's state is the project's state or blank, IGST otherwise). Nothing is posted for the TDS yet.
  • The demand now shows on the booking's Demands & money tab and under Demands in the sidebar (Demands) as Issued; once its due date passes with money outstanding, the list flags it "Overdue" and the seeded rules escalate at 7 and 30 days: Chase overdue demands.
  • When the buyer pays: Record and clear a buyer's receipt, then place the money on the charges with Appropriate a receipt across a demand's charge lines. When they hand over the Form 16B or the 26QB challan, record the TDS they deducted with Record TDS credit on the demand: Record a TDS credit. The demand reads Paid once the money received reaches Payable in money; the TDS shows as "Of which TDS credit pending" until the credit is recorded.
  • A wrong demand is cancelled with a credit note and raised again: Cancel or correct a demand.
  • To bill every buyer of a project in one action, use a demand run: Bill a whole project with a demand run.

If something goes wrong

  • "No open installments: every one is paid, cancelled or already on a live demand." in the raise dialog: nothing is left to bill on this booking, or the due installments are already on a draft or issued demand. See Nothing to demand (trouble.collections.nothing-to-demand).
  • "Schedule row <n> of <component> is already on a demand" when drafting: someone raised a demand on it meanwhile. Refresh and pick again. Same article (trouble.collections.nothing-to-demand).
  • Raise demand is missing and the tab warns "The booking is cancelled; no new demands, receipts or commissions can be raised on it.", or "This booking is cancelled and can no longer be changed." on issue. See Booking is cancelled or its schedule rows are no longer Pending (trouble.bookings.booking-locked).
  • "Charge component <code> has no ledger mapping in books <name>" on Issue: map the component, then issue again. See Component not mapped (trouble.accounting.component-not-mapped).
  • "The project's promoter company has no books yet. Set them up under Books first." See No books yet (trouble.accounting.no-books-yet).
  • "These books are inactive. Reactivate them under Books to post entries." See Books inactive (trouble.accounting.books-inactive).
  • "No fiscal year covers that date. Open the next fiscal year under Books first.", "That fiscal year is closed." or "Period <n> of <year> is locked": open the period or change the Demand date. See Fiscal year missing (trouble.accounting.fiscal-year-missing).
  • "Only a Draft demand can be issued (this one is <status>)": it was already issued or cancelled elsewhere; refresh the page.
  • "No published template for this record type" in the generate dialog: publish "Demand letter (standard)" first. See No published template (trouble.documents.no-published-template).
  • Raise demand or Issue is missing on an Active booking: your role lacks the Create or Issue permission on Demands. See No permission (trouble.common.no-permission).

Related

  • Demands & moneyScreen

    The booking's demands, receipts and payouts, and channel-partner commission in one place, with shortcuts to raise a demand, record a receipt and accrue commission.

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

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

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

  • Document templatesScreen

    The list of your organization's document templates (demand letters, offer letters, termsheets, agreements, allotment letters, receipts, cost sheets), with filters and the actions to create, duplicate, open or delete one.

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

  • OrganizationScreen

    Your organization's profile and policies: name and invitation expiry, the two-factor requirement, the AI connectors switch, the help-assistant recording switch, the project defaults every project inherits (RERA gate, estimate validity, the two chargeable areas, carpet area offered, revenue method and trigger) and the effective-dated rules: the RERA escrow share that splits every sweep of a project's collection account, TDS on sales and booking cancellation.

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

  • Issue, accept and sign the buyer's termsheetHow-to

    Take the booking's termsheet from Draft to Issued, Accepted and Signed on the Termsheet & schedule tab, optionally emailing the term sheet document through the seeded workflow rule.

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

  • Appropriate a receipt across a demand's charge linesHow-to

    Place the money received against a demand on the charges its instalments cover, in the split you decide, so the booking's schedule rows show what is paid.

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

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

  • Chase overdue demandsHow-to

    Find the demands past their due date, send the buyer a payment reminder from the demand, read the ageing and outstanding bills, and rely on the seeded escalation rules.

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

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

  • Payment plans: lumpsum, cadence, custom and construction-linkedConcept

    A payment plan says how the buyer's total is collected: all at once, in equal installments on a cadence, on agreed dates, or as construction stages are achieved; it lives on the estimate as numbered versions, is finalized with the price for approval, and becomes the booking's schedule.

  • Raise demand finds nothing to bill, or refuses the rows pickedTroubleshooting

    A demand bills open schedule rows: a row that is paid, cancelled, waived, empty or already on a live demand cannot be billed again, a booking needs its termsheet, a member offer must be issued before it is billed, and a demand without TDS has no Form 16B to record.

  • Booking is cancelled or its schedule rows are no longer Pending: the change is refusedTroubleshooting

    A cancelled booking accepts no edits, demands, receipts, commissions or reschedules, and on a live booking only Pending schedule rows can be re-dated; paid, partly paid, waived and cancelled rows stay as they are, and the payment plan of a booked estimate is changed by regenerating the termsheet, never by cancelling the plan.

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

  • Generate document has nothing to offer: no published template for this record typeTroubleshooting

    Documents are generated only from published document templates of the record's type; the starter templates (cost sheet, allotment letter, offer letter and others) ship as drafts, so until someone publishes one, Generate document has nothing to pick, offers issue without a letter and workflow rules that generate the template fail.

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