Manual appropriation of receipts
A receipt settles a demand as a whole; which charges the money was for is decided by you, on the demand, in any split up to each line's billed amount and up to what was received, and that split is what marks the payment schedule's rows paid.
Manual appropriation of receipts
Appropriation is your decision about which charges the money received against a demand was for. A receipt settles the demand as one bill; NirmaanOne never guesses how that money spreads over the Unit Price, the Floor Rise, the GST and the rest. On the demand you place the received amount on its lines by hand, in any split, and that split is what marks the corresponding rows of the buyer's payment schedule as paid. It matters because the charges carry different GST rates, land in different ledgers on the demand, and are reported on separately (for example on the cost sheet and the RERA accounts statement), so the office, not a rule, should say what a part payment covered.
How it works in NirmaanOne
Received and appropriated are two different figures
- Received is the sum of cleared receipts allocated to the demand. It moves the demand from Issued to Partially Paid and to Paid (when received reaches the payable amount, which is the total less the TDS the buyer deducts). This happens when the receipt is cleared.
- Appropriated is what you have placed on the demand's lines. Nothing is placed until you do it. The demand shows both, and "Received against this demand · not yet appropriated" for the gap.
Where you do it
On Demand, the card Appropriation against charges appears once anything has been received. It lists one row per demand line: the Charge (with its GST rate for a GST line), the Instalment it belongs to ("#<n> · <stage or date>"), Billed and Appropriated. Press Appropriate (the Edit permission on Demands), type an amount against each line, and Save appropriation. The save replaces the whole split: a line left blank or at 0 carries nothing.
The buttons are greyed out with the reason on hover when they cannot be used:
- "Appropriating needs permission to update demands";
- "A <status> demand takes no appropriation" (only Issued, Partially Paid and Paid demands take one);
- "Nothing has been received against this demand yet";
- "A charge takes at most what this demand bills for it (<charges>)" and "<placed> placed but only <received> received" on Save appropriation.
The two limits are the whole rule: a line takes at most its billed value (its amount, or its GST for a GST line), and all lines together take at most what was received. On success the toast reads "<appropriated> of <received> received is now placed on the lines."
What it changes
- Each payment-schedule row the demand bills is paid by exactly what is appropriated to its line. The row's Paid figure and status follow: Paid when the appropriated amount reaches the row's amount, Partially Paid when something is placed, Pending when nothing is. The installments table on the booking's Termsheet & schedule tab and its Paid total show this.
- No accounting entry is made. The receipt already posted bank against the buyer's ledger when it was cleared; an appropriation only records which charge the money was for.
- A cancelled demand's lines carry nothing, and its rows become free again.
Because of this, a booking shows two different "paid" figures on purpose: the Money card on the booking overview and the Received (cleared) figure on Demands & money count money received against demands, while the termsheet tab's Paid counts what has been appropriated to rows.
When a receipt bounces
Bouncing or cancelling a receipt lowers the received amount but leaves your split standing. The demand then shows a red alert, "<appropriated> is placed on the lines but only <received> has been received (a receipt bounced or was cancelled). Reduce the appropriation.", until you appropriate again with lower figures.
The TDS share
The buyer pays the developer the total less TDS and deposits the TDS with the Income Tax department, so "received" never includes that part. Appropriation is capped at what was received, which means the lines of a demand with TDS can never be placed in full, and one of its schedule rows stays Partially Paid by the TDS amount even when the demand itself is Paid.
Example
Demand DM-2026-27-00012 on booking BK-2026-27-00007 bills the plinth installment of unit A-1203. Its lines and their billed values:
| Line | Billed |
|---|---|
| Unit Price | ₹23,86,500.00 |
| Floor Rise | ₹35,000.00 |
| PLC (Preferred Location Charge) | ₹40,000.00 |
| Parking | ₹1,00,000.00 |
| GST 5% | ₹1,28,075.00 |
| Total | ₹26,89,575.00 |
TDS at 1% on the ₹25,61,500.00 ex-GST amount is ₹25,615.00, so the buyer owes ₹26,63,960.00.
- Rakesh Shah pays ₹20,00,000.00 by NEFT. When the receipt is cleared the demand becomes Partially Paid with Received ₹20,00,000.00 and nothing appropriated yet; every schedule row of the installment is still Pending.
- The accountant presses Appropriate and places the whole ₹20,00,000.00 on Unit Price (allowed: it is below the line's ₹23,86,500.00 and equal to what was received). The Unit Price row of the plinth installment becomes Partially Paid, the others stay Pending. Typing ₹24,00,000.00 against Unit Price instead would grey out Save appropriation with "A charge takes at most what this demand bills for it (Unit Price)".
- A second receipt of ₹6,63,960.00 clears. Received is now ₹26,63,960.00, equal to the payable, so the demand is Paid. The accountant appropriates again: Unit Price ₹23,86,500.00, Floor Rise ₹35,000.00, PLC ₹40,000.00, Parking ₹1,00,000.00 and GST ₹1,02,460.00, which is everything received (₹26,63,960.00). The four charge rows are Paid; the GST row stays Partially Paid, ₹25,615.00 short, because that part was deposited as TDS and never received.
Had the first receipt bounced after step 2, the card would have shown "20,00,000.00 is placed on the lines but only 0.00 has been received (a receipt bounced or was cancelled). Reduce the appropriation." until the split was cleared.
Where you see it
- Demand: the Appropriation against charges card, Appropriate and Save appropriation.
- Termsheet and schedule: the installments' Status and Paid columns, which follow the appropriation.
- Booking overview and Demands and money: the received figures that do not.
- Payment: clearing and bouncing the receipts that set the received amount.
Related
Related
- 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.
- PaymentScreen
One receipt or payout: its details, amounts and allocations, and the actions to clear it, bounce it, cancel it, edit it or delete it.
- Record receipt / Record payoutScreen
Record money received from a buyer or society member, or paid to a channel partner or society member: who, how and how much. A receipt settles the payer's open demands by itself, oldest due first; a payout is allocated to commissions or benefit rows by hand. A buyer's consideration and GST are two separate receipts; the TDS they deducted is a TDS credit.
- 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.
- 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.
- Booking overviewScreen
A booking's home page: the applicant and unit, parking, dates, money summary, termsheet status and possession, with the buttons to edit the booking, see its history, jump to the opportunity or cancel it.
- 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.
- Receipts and payouts: allocation, clearing and the UTRConcept
A receipt is recorded as Pending and settles the payer's open demands by itself, oldest due first; a payout is allocated to commissions or member rows by hand. Both post their voucher only when cleared and can be bounced afterwards; the UTR is the bank's transfer reference, typed on NEFT-style payments and per payout when a payout run is cleared.
- 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.
- Charge groups and per-line GSTConcept
A charge group is a section of the cost sheet with a default GST rate; every charge line carries its own GST, worked out from the estimate override, the plan line, the component or the group, in that order.