Demand

This page shows one demand: what it bills, what the buyer or member has to pay, what has come in against it and where that money has been placed. It is where you check a draft and issue it, start recording the TDS the buyer deposited, place received money on the charges, and cancel a demand raised by mistake.

Where to find it

• The demand number or the eye icon on the Demands list, on a booking's Demands & money tab, on a member's offer, or in a demand run's list of demands.
• Drafting a demand from a booking or an offer opens its page straight away.
• A demand link on the booking's installments table, on a payment's allocations, or in the booking cancellation wizard.
• 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 demand doesn't exist, the page shows "Not found" and "That item could not be found."

Before you start

To issue a demand, the project's promoter company needs active books with a fiscal year covering the demand date, and every charge being billed (and GST) needs a ledger mapping in those books under Component mappings.

What you see

The header shows the demand number with the status badge and a blue project badge. The line underneath names the buyer or member, the booking ("booking …") or "member offer" with the membership number, the unit, and the amount billed ("… billed"), followed by "… payable in money after … TDS" when TDS applies.

When the demand is cancelled, an alert reads "Cancelled on …. An issued demand is cancelled with a credit note that settles its bill."

Details

Field	What it shows
Demand date	The date of the demand. The sales voucher is dated this day.
Due date	When payment is due.
Buyer / Member	The buyer (on a booking) or the society member (on an offer), with their phone number.
Booking / Offer	The booking number, as a link when you have the View permission on Bookings; or, for a member, "Redevelopment offer on …" with the project and the offer's status.
Issued	When the demand was issued.
Sales voucher	The voucher posted on issue. It is a link when you have the View permission on Vouchers.
Narration	The narration, which also appears on the sales voucher. A cancellation reason is added here.

Amounts

A demand bills the buyer or member the full total. On a booking demand where TDS under section 194-IA applies, the buyer keeps back the TDS and deposits it with the Income Tax department, so the card also shows what they are expected to pay in money and what has been evidenced as a TDS credit:

• Total amount: the value of the charges before GST.
• GST: the GST on those charges.
• Grand total billed: the charges plus GST, which is what the buyer's ledger is debited with.
• Expected TDS with its section and rate (for example "Expected TDS 194-IA @ 1%"), shown as a deduction, only when TDS applies.
• Payable in money: the grand total less the expected TDS, that is what the buyer should transfer.
• Received: money received and cleared against this demand.
• TDS credited: the TDS credits recorded against this demand (shown when TDS applies or a credit exists).
• Outstanding: what is still open on the bill (the grand total less the money received and the TDS credited), in amber while the demand is open.
• Of which TDS credit pending: the part of the outstanding amount that is the TDS the buyer is expected to deduct but has not yet evidenced with a TDS credit (shown while there is any).

When TDS applies, a note explains: "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."

Demands issued before 10 October 2026 booked their TDS on issue and keep that model. Their card reads Total amount, GST, Grand total, TDS with its section and rate ("TDS 194-IA @ 1%") as a deduction, Grand total payable to developer (what the buyer was billed, that is the charges plus GST less the TDS), Received, Outstanding (the payable less the money received) and Form 16B (the certificate number and date, once recorded). The note reads "Issued before 10 October 2026: the TDS was posted to TDS Receivable on issue, so the buyer owes the payable. The buyer deposits the TDS with the Income Tax department and gives a Form 16B, recorded here."

Instalments

"What this demand bills, as the payment plan reads." One row per installment, with #, Particulars (the construction stage, "Due …" with a date, or "At the time of possession"), Amount (excl. GST), GST and Total, and a Total row at the foot.

Appropriation against charges

This card appears once money has been received against the demand (and stays while anything is still placed on the charges, even after a receipt bounced). "The money received against this demand, placed on the charges its instalments cover - by you, in any split; nothing is assumed."

Column	What it shows
Charge	The charge, with its GST rate.
Instalment	The installment it belongs to: its number and stage or date.
Billed	What this demand bills for that charge, GST included.
Appropriated	How much of the money received you have placed on it.

The foot shows the totals and "Received against this demand · not yet appropriated": the money received and how much of it is still not placed on any charge (in amber).

If a receipt bounced or was cancelled after you placed it, a red alert reads "… is placed on the lines but only … has been received (a receipt bounced or was cancelled). Reduce the appropriation."

TDS credits against this demand

This card appears on a demand that bills the full total once a TDS credit exists or TDS is still expected. It lists the credits with Credit (the number, which opens the TDS credit), Date, Form 16B / 26QB (the certificate number and the challan number, or "—"), Status (Recorded in green, Cancelled in red with the amount struck through) and Amount. The link All TDS credits (the View permission on Payments) opens TDS credits filtered to this demand. With none recorded it reads "None yet. When the buyer hands over the Form 16B (or the 26QB challan), click Record TDS credit on the Amounts card."

Receipts against this demand

The receipts allocated to this demand: Receipt (the number, which opens the payment, or "Pending"), Date, Status (Pending, Cleared, Bounced or Cancelled) and Allocated. With none it reads "Nothing received yet."

Documents

The Documents card lists the documents generated for this demand, such as a demand letter. It shows when you have the View permission on Generated Documents. When there are none it reads "No documents generated for this record yet".

Tasks

The Tasks card lists the tasks linked to this demand, for example the call-the-buyer tasks created when a demand is overdue. It shows when you have the View permission on Tasks.

What you can do

The header buttons show only when the demand's status allows them and you hold the permission; they are hidden, not greyed out, otherwise. Appropriate and Save appropriation are the exception: they stay on screen and are greyed out with a reason.

History

History in the header (hover "Who changed this record, what and when") opens the panel History · <demand number>: who changed the demand, what they changed and when, newest first. See History panel.

• Who: anyone who can open this page. Open in the audit log at the foot of the panel needs the View permission on Audit Trail.

Workflows

Runs one of your organization's manual workflow rules on this demand. The system rule Send payment reminder emails the "Payment reminder" message to the buyer, with an optional "Note to the buyer (optional)". It applies to Issued and Partially Paid demands; on other demands it stays in the menu and, when you pick it, a small dialog explains "This workflow cannot run right now: the record does not meet its conditions."

• Who: anyone with the View permission on Workflow Runs. The menu shows only when at least one manual rule exists for demands.

Booking

Opens the booking's Demands & money tab. It shows on demands raised on a booking.

• Who: anyone with the View permission on Bookings.

Offer

Opens the project's Society & Tenants tab, where the member's offer lives. It shows on demands raised on a member's offer.

• Who: anyone with the View permission on Projects.

Record receipt

Opens Record receipt with the booking or member filled in and Amount received set to what this demand still takes in money; the receipt settles the payer's open demands by itself, oldest due first, so this demand is listed under What this receipt settles with its share.

• Who: anyone with the Create permission on Payments. In the default roles that is the Administrator, Finance Lead and Accountant.
• When: while the demand is Issued or Partially Paid, and on a Paid demand that still shows an Outstanding amount (the buyer paid the money due but deducted no TDS, so the TDS part is still open and may arrive as money).
• What happens next: the receipt is recorded as Pending. When it is marked cleared on the payment's page, it appears under Received and the demand turns Partially Paid or Paid (Paid once the money received reaches Payable in money, even while the TDS credit is still pending). A receipt can also be recorded from Record receipt against a Paid demand that still has an amount Outstanding, for a buyer who did not deduct TDS after all; this page's button is not shown then.

Edit

Opens the slide-over Edit draft demand, where you change:

• Demand date (required; "Enter a date" when it's empty);
• Due date (optional; "Enter a valid date" when it isn't a date);
• Narration (up to 2,000 characters);
• the schedule rows it bills: a table of Charge, Row (number and stage), Due and Open, with a tick box per row. It lists the rows already on this draft and every other open row not yet on a demand.

Save changes (with the open total in brackets when rows are ticked) is greyed out until you change something; Cancel closes the panel without saving. The message "Demand updated." confirms the save.

• Who: anyone with the Edit permission on Demands. In the default roles that is the Administrator, Finance Lead and Accountant.
• When: only while the demand is Draft. An issued demand can't be edited: "Only a Draft demand can be edited; cancel it and raise a new one."
• What happens next: the demand's lines are rebuilt from the rows you picked. Changing the demand date also re-reads the TDS rule in force on the new date.
• If it's refused, for example "Schedule row … of … is already on a demand", the reason shows at the top of the panel.

Issue

Sends the demand to the accounts. The confirmation "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.

• Who: anyone with the Issue permission on Demands. In the default roles that is the Administrator, Finance Lead and Accountant.

• When: only while the demand is Draft.

• What happens next: "Demand … issued; voucher … posted." The demand turns Issued and a Sales voucher, dated the demand date, is posted in the books of the project's promoter company:

  • the buyer's ledger (or the member's ledger, created the first time it's needed) is debited with the Grand total billed as a new bill, numbered as the demand and due on the due date. Nothing is posted for the TDS at issue: it reaches the books when the buyer's deposit is recorded as a TDS credit (see TDS under section 194-IA);
  • each charge is credited to the ledger mapped for it, and GST is credited as CGST and SGST halves, or as IGST when the buyer's or member's state differs from the project's site state;
  • a charge whose revenue treatment is With the unit (the unit's price: base price, floor rise, PLC, parking, club, legal and the like) is credited to its contract liability ledger instead of revenue: 2100 Contract Liability - Sale of Units, or 2110 Contract Liability - Differential Area for a member's differential area, or whatever ledger the mapping names. It stays there until a revenue run recognises it. This doesn't happen when the books' revenue policy in force on the demand date is Revenue on billing; then every charge is credited to its mapped ledger straight away.

  Issuing also sets off any workflow rules your organization runs when a demand is issued, such as emailing the demand letter.

• If it's refused, the reason shows in the dialog, for example "Charge component … has no ledger mapping in books …", "These books are inactive. Reactivate them under Books to post entries.", "The project's promoter company has no books yet. Set them up under Books first.", "No fiscal year covers that date. Open the next fiscal year under Books first.", "That fiscal year is closed.", "This booking is cancelled and can no longer be changed." or "A … offer cannot be billed; issue it first".

Cancel demand

Opens "Cancel this demand?" with a Cancellation date (today by default) and an optional Reason (up to 255 characters). The dialog explains:

• for a draft: "The draft is marked cancelled and its rows are freed.";
• for an issued demand: "A credit note reverses the sales voucher and settles the bill. A demand with receipts against it cannot be cancelled; bounce or reallocate those first."

Click Cancel it, or Keep it to back out.

• Who: anyone with the Edit permission on Demands.
• When: while the demand is Draft, Issued or Partially Paid. The app refuses once money has been received: "Money has been received against this demand; bounce or reallocate those payments first", while a TDS credit is recorded against it: "A TDS credit is recorded against demand <no>; cancel it under Payments > TDS credits first", or while a pending receipt is allocated to it: "A pending payment is allocated to this demand; cancel or reallocate it first". In practice a Partially Paid demand can only be cancelled through the booking's Cancel booking wizard. See Demand cannot be cancelled.
• What happens next: "Demand cancelled." The demand turns Cancelled and the reason is added to the narration. For an issued demand, a Credit Note dated the cancellation date reverses the sales voucher. The schedule rows it billed are free to go on a new demand. A cancellation date before the demand date is refused: "The reversal date cannot be before the original voucher date."

Delete

Removes a draft for good. The confirmation reads "Delete this draft?" and "The draft is removed and its schedule rows become available again." Click Delete.

• Who: anyone with the Delete permission on Demands. In the default roles that is the Administrator and the Finance Lead.
• When: only while the demand is Draft.
• What happens next: "Draft demand deleted." You go back to the booking's Demands & money tab, the project's Society & Tenants tab, or the Demands list.

Record TDS credit

On the Amounts card. Opens Record TDS credit with this demand already chosen, where you enter the TDS the buyer deducted and deposited, with the Form 16B and the 26QB challan, and click Record and post. The credit posts a Journal voucher that debits TDS Receivable and credits the buyer against this demand's bill, so TDS credited rises and Outstanding falls. See Record a TDS credit.

• Who: anyone with the Create permission on Payments. In the default roles that is the Administrator, Finance Lead and Accountant.
• When: only on a demand that bills the full total (issued on or after 10 October 2026), while it is not Draft or Cancelled and something is Outstanding.
• If it's refused, the reason shows on that page, for example "Demand <no> has <open> open; a TDS credit of <amount> is more than that" or "The TDS credit cannot be dated before the demand (<date>)". See TDS credit refused.

Record Form 16B

On the Amounts card of a demand issued before 10 October 2026. It reads Form 16B once a certificate is recorded. Opens "TDS certificate (Form 16B)": "The buyer deducted … (…) on demand … and deposits it with the Income Tax department. Record the certificate they hand over." Fill in Certificate number (placeholder "Form 16B / challan reference", up to 50 characters) and Certificate date, and click Save. The message "Form 16B recorded." confirms it.

• Who: anyone with the Edit permission on Demands.
• When: only when the demand carries TDS, booked it on issue (before 10 October 2026) and is not Draft or Cancelled. This is the only change an issued demand accepts. On a demand that bills the full total the button is not shown, and a certificate sent to it is refused: "Demand <no> bills the full total; record the TDS the buyer deposited as a TDS credit (Payments > TDS credits), which carries the Form 16B and the 26QB challan". Nor does such an older demand take a TDS credit: "Demand <no> booked its TDS when it was issued; record the buyer's Form 16B on the demand itself (Record Form 16B on its Amounts card)".

Appropriate

On the Appropriation against charges card. It turns the Appropriated column into amount boxes so you can place the money received on the charges, in any split. Each box takes at most the charge's billed amount. Click Save appropriation to keep the split, or Cancel to leave it as it was.

• Who: anyone with the Edit permission on Demands.
• Greyed out with one of these reasons on hover:
  • "Appropriating needs permission to update demands" when you don't have the permission;
  • "A … demand takes no appropriation" when the demand is Draft or Cancelled;
  • "Nothing has been received against this demand yet".
• Save appropriation is greyed out with "A charge takes at most what this demand bills for it (…)" when a charge gets more than it bills, or "… placed but only … received" when the split adds up to more than was received.
• What happens next: "… of … received is now placed on the lines." The split replaces the previous one. Each schedule row billed by the demand is marked Paid, Partially Paid or Pending according to what is placed on it (plus anything a receipt put on that row directly). Nothing is posted to the accounts: the receipt already did that.

Generate document

On the Documents card. Generates a document for this demand from one of your published templates, such as a demand letter. The documents themselves are listed under Generated documents.

• Who: anyone with the Create permission on Generated Documents.

The card also has Preview (anyone who can see documents): pick a template and see on screen what Generate would produce for this record, without numbering or keeping anything. Each generated row has a Regenerate icon (the Create permission on Generated Documents) that makes a fresh document from the same template with today's data; the old one stays until you delete or void it. See Generated documents.

Add task

On the Tasks card. Adds a task linked to this demand. See Tasks.

• Who: anyone with the Create permission on Tasks.

Statuses

• Draft: created from a booking, an offer or a demand run. Issue moves it to Issued; Cancel demand to Cancelled; Delete removes it.
• Issued: the sales voucher is posted. A cleared receipt or a TDS credit moves it to Partially Paid or Paid; Cancel demand (with nothing received or credited) moves it to Cancelled with a credit note.
• Partially Paid: something has come in, money or a TDS credit, but less than the demand settles on.
• Paid: the money received has reached Payable in money (the TDS credit may still be pending), or nothing is Outstanding. On a demand issued before 10 October 2026: the money received covers the Grand total payable to developer.
• Cancelled: final.

A bounced receipt or a cancelled TDS credit moves a Paid or Partially Paid demand back to Partially Paid or Issued. Cancelling a booking in the Cancel booking wizard also deals with its demands: drafts are deleted, unpaid ones reversed, and paid ones settled with a credit note.

Things to know

• Only issuing touches the accounts. A draft posts nothing, so you can check the figures, change the rows or delete it without leaving a trace in the books.
• Billing isn't revenue until the run says so. Under Ind AS 115 or AS (Guidance Note 2012) the unit-price charges of a demand sit in the contract liability, and the page shows nothing different: the same Sales voucher link, the same amounts. Which ledger each charge went to is on the voucher, and the Contract balances report shows what is billed ahead of revenue. Charges treated as On billing or Pass-through on Component mappings are unaffected.
• A demand is numbered when it's drafted, not when it's issued (numbers look like DM-, the financial year and a running number, across the organization). Deleting a draft can leave a gap in the series, and the financial year in the number is the one of the first demand date, even if you later change the date.
• TDS under section 194-IA is worked out from the organization's TDS rule in force on the demand date, on booking demands only, once the deal's consideration reaches the rule's threshold. Your organization starts with a rule of 1% from ₹50,00,000. It is applied to the value before GST: on ₹18,00,000 of installments with ₹90,000 GST, the demand bills ₹18,90,000, the expected TDS is ₹18,000 and the buyer pays ₹18,72,000 in money; the ₹18,000 is settled by a TDS credit when the buyer's Form 16B or 26QB challan is recorded. The rules are kept under Organization settings, in "TDS on sales (section 194-IA)". Issued demands keep their figures when a rule changes. See TDS under section 194-IA.
• A TDS credit is its own record, kept under Payments > TDS credits with its own number and voucher. It can be cancelled there (the demand's bill opens again by that amount), and a demand with a credit against it cannot be cancelled until the credit is.
• Member-offer demands bill only what the member pays: their charges and GST under the offer. Benefits you pay the member are settled by payouts, never by demands.
• Receipts settle the demand, not its charges. A cleared receipt makes the demand Partially Paid or Paid, but the schedule rows are marked paid only when someone places the money on them with Appropriate. Nothing is split automatically. The most you can place is the money received; a TDS credit settles the bill but is never placed on the charges, so on a demand with TDS the TDS share of a line stays unplaced.
• A cancelled demand frees its rows. Once cancelled, its schedule rows can be billed again on a new demand.
• While a demand is live on a member's offer, the offer can't be reopened or cancelled: "A demand has been raised on this offer; cancel the demand first".
• Overdue follow-up is automatic. System workflow rules act on booking demands that are past due: at 7 days the Accountants are notified and a Sales Executive gets a task to call the buyer; at 30 days the Finance Leads and Sales Managers are notified and a Finance Lead gets a high-priority task. Emailing the demand letter on issue and emailing overdue reminders ship switched off.
• A demand drafted by a demand run looks like any other; its page doesn't show the run it came from.
• The cancelled alert mentions a credit note even for a cancelled draft, which never had one.

Related

• Demands
• Demand run
• Record receipt
• Payment
• TDS credits
• Record TDS credit
• TDS credit
• Record a TDS credit
• Voucher
• Component mappings
• Revenue policy
• Revenue run
• Contract balances
• Demands & money (booking)
• Cancel booking
• Society & Tenants
• Organization settings
• History panel
• Generated documents
• Tasks