NirmaanOne Help
How-toReviewed 2026-09-29

Bill and collect a member's charges

Raise and issue a demand on the charge and tax rows of a society member's redevelopment offer, record the member's receipt against it, and place the money on the charges.

Bill and collect a member's charges

A redevelopment offer can carry charges the member pays the developer (differential area, legal fees, with their GST) alongside the benefits the developer pays the member. The two never net off: charges are billed with a demand on the offer and settled by the member's receipts, while benefits go out through payouts. This guide bills one member's charge rows, records the money and places it on the charges.

Before you start

  • The member's offer is Issued, Accepted or Signed (Issue an offer with its letter) and carries charge lines. The Charges block and the Demands on this offer block are shown only on an offer that already has charge lines; newer offers carry benefits only, and what an allottee pays for extra area goes through their purchase estimate and booking instead (Start allottee purchases).
  • The project promoter's books exist and are active with a fiscal year covering the demand date (Set up the books), and every charge and tax component on the offer is mapped to a ledger in those books (Map a charge component to a ledger).
  • Permissions, as the role editor shows them: the View permission on Termsheets to open the offer; Create and Issue on Demands to bill; Create on Payments to record the receipt and Edit on Payments to clear it; Edit on Demands to appropriate. In the default roles the Administrator, the Finance Lead and the Accountant hold the money permissions; the Rehab Officer can open offers but not bill them.
  • A demand on a member's offer carries no TDS: the member pays the full total. Once a live demand exists, the offer can no longer be reopened or changed ("A demand has been raised on this offer; cancel the demand first").
  • To bill every member's due rows across a project in one go, use a demand run with Subjects set to "Member offers (charges and GST)": Bill a whole project with a demand run.

Steps

  1. Open the project and choose the Society & Tenants tab (Society & Tenants). On the Offers (term sheets) card, open the member's offer (the row's open icon, or the member's Offer badge on the members card). The drawer "Offer · <member>" opens with the status badge. Below the Charges block (badge "The member pays us") you see Demands on this offer: "Bills for the charge and tax rows. Issuing posts the sales voucher on the member's ledger; receipts settle it bill by bill." with the demands already raised and a Raise demand button.
  2. Click Raise demand. The slide-over "Raise demand on the offer to <member>" opens with the note "Only charges and tax the member pays can be demanded. Benefits the developer pays are settled by payouts and are not listed here." Under Schedule rows to bill, each open row shows the Charge (tax rows carry a badge "Tax <rate>% on <charge>"), the Row number, Due and the Open amount; a partly paid row is marked "Partly paid".
  3. Set Demand date (today by default) and Due date (the hint reads "Defaults to the latest picked due date (<date>)." once rows are ticked), optionally type a Narration ("Shown on the demand and the sales voucher"), and tick the rows to bill, or click Select all open rows. The footer button reads Draft demand for <open total> (amounts in this dialog have no ₹ sign, as in "1,18,000.00") and stays greyed out until at least one row is ticked.
  4. Click Draft demand for …. You see "Demand drafted for <total>." and the demand page opens (Demand) with a Draft badge and its DM- number. The header reads "<member> · member offer (<membership no>) · <payable> payable"; the Details card shows Member and Offer ("Redevelopment offer on <project> · <status>"); the Amounts card shows Total amount, GST and Grand total payable to developer with no TDS line; the Instalments card lists what is billed. Use Edit to change the dates, narration or rows while it is a draft.
  5. Click Issue. The dialog "Issue this demand?" explains that the sales voucher is posted and the lines can no longer change; click Issue. You see "Demand <no> issued; voucher <no> posted." The badge reads Issued, Issued and Sales voucher fill on the Details card, Edit, Issue and Delete disappear, and Record receipt appears next to Cancel demand. The Offer button in the header brings you back to the Society & Tenants tab.
  6. When the member pays, click Record receipt on the demand. The Record receipt page opens with the badge "Money in": Party reads "Society member" with the Society and Member filled, Project is set, and Amount received holds the demand's open amount. The card What this receipt settles reads "The amount settles the member's open demands by itself, oldest due first, then their undemanded charge rows; anything left stays on account on the payer's ledger." and lists the member's open demands with the share each gets; nothing is picked by hand. Books starts with the books chosen in the accounting header; if it is blank, pick the project promoter's books, or saving stops with "Choose the books (or a booking the books follow from)".
  7. Fill Received on (today by default), Mode (NEFT by default), the instrument details (UTR / reference for NEFT, RTGS, IMPS, UPI or Card; Cheque number, Cheque date and Drawn on for a cheque or demand draft) and Into our account (the promoter's bank accounts, shown as "<bank> ····<last 4> · <purpose>"; the hint reads "The books need a bank ledger for this account."). Check the line under What this receipt settles: "<amount> settles the above" when the whole amount lands on the member's demands, or "<settled> settles the above · <rest> on account" when part stays on the member's ledger. Then click Save and clear. You see "<receipt no> cleared; voucher <no> posted." and the payment page opens with a Cleared badge and the voucher link. If the money is not yet in the bank, click Save as pending instead ("Payment recorded as pending.") and use Mark cleared on the payment page once it is: Record and clear a buyer's receipt, step 5.
  8. Back on the demand, the status reads Paid (or Partially Paid) and the card Appropriation against charges has appeared. Click Appropriate, type the amount to place on each charge row and click Save appropriation. You see "<appropriated> of <received> received is now placed on the lines." and the offer's charge rows read Paid or Partially Paid. Details in Appropriate a receipt across a demand's charge lines.

What happens next

  • Issuing posts a Sales voucher dated the demand date: the member's ledger is debited with a bill numbered as the demand, and each charge is credited to its mapped ledger with its GST legs (CGST + SGST when the member's state is the project's state or blank, IGST otherwise). Clearing the receipt posts a Receipt voucher that settles the bill.

  • The demand appears under Demands in the sidebar with a purple Member offer badge, and the receipt under Payments with the party shown as "<name> (member <no>)".

  • A member's charges can also be collected without a demand: on Record receipt pick Party "Society member", the Society and the Member, and the card What this receipt settles lists the member's open demands first, then their undemanded charge rows ("<charge> #<n>", "Undemanded charge row, due <date>"), oldest due first; the amount settles them in that order by itself. A row that is on a live demand is settled through that demand, not on its own. The empty card reads "No open demands or charge rows on this member's offers." or, before a member is picked, "Pick the member to see their open demands."; with nothing open the line reads "Nothing open to settle: the whole <amount> stays on account."

  • Benefit rows the developer pays the member are never offered against a receipt; they are paid through a Member Benefits payout run (Payout runs).

  • To cancel or correct the demand: Cancel or correct a demand.

If something goes wrong

  • "No open charge rows: every charge is paid, cancelled or already on a live demand." in the raise dialog: nothing is left to bill. (An offer with no charge lines shows no Demands on this offer block at all.) See Nothing to demand (trouble.collections.nothing-to-demand).
  • "A <status> offer cannot be billed; issue it first": the offer is still Draft or was cancelled. Issue it first (Issue an offer with its letter).
  • "Charge component <code> has no ledger mapping in books <name>" when issuing: map the component under Chart of Accounts > Component mappings. See Component not mapped (trouble.accounting.component-not-mapped).
  • "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." when raising, issuing or clearing. See No books yet (trouble.accounting.no-books-yet) and Books inactive (trouble.accounting.books-inactive).
  • "No fiscal year covers that date. Open the next fiscal year under Books first." See Fiscal year missing (trouble.accounting.fiscal-year-missing).
  • "Saved as pending, but clearing failed: These books have no ledger for that bank account. Add a bank ledger under Chart of accounts first.": the receipt is saved as Pending; add the bank ledger (or Sync bank ledgers on the project overview) and use Mark cleared. See Clearing failed (trouble.accounting.clearing-failed).
  • A button is missing (Raise demand, Issue, Record receipt, Save and clear): your role lacks the permission named in the front matter. See No permission (trouble.common.no-permission).

Related

  • Society & TenantsScreen

    On a redevelopment project, link the society being redeveloped, keep its members and the project's landowners and PAP tenants, and give each of them an offer that allots new units and sets the benefits the developer pays.

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

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

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

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

  • AllotteeScreen

    One society member, landowner or PAP tenant on a page: who they are, what they hold today, their co-owners, their offers on each project, the letters and files filed for them, their bank accounts and parking.

  • Raise and issue a demand on a bookingHow-to

    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.

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

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

  • Issue an offer with its letterHow-to

    Publish the offer letter template once, then issue a draft offer so the letter is generated and filed with it and the offer moves to Issued.

  • Split the entitlement and start the allottee's purchasesHow-to

    Decide how the entitled area falls on each allotted unit and how much of the extra area the allottee pays for, then open a purchase per unit and price it through the usual estimate, approval and booking.

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

  • Member offer (term sheet): benefits and charges, never nettedConcept

    The one live offer an allottee has on a project: the area they hold and are entitled to, the new units allotted, and the money on both sides, benefits the developer pays and charges the member pays, each with its own schedule and never set off against the other.

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

  • Manual appropriation of receiptsConcept

    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.

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

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

  • Record payment refuses to save: the party, books, direction or allocations do not fitTroubleshooting

    A receipt or payout needs exactly one party (or a booking that gives the buyer) and a set of books; a payout also needs TDS no larger than the amount and allocations that name one open target each, add up to no more than the amount, match the direction and belong to the payee. A receipt settles the payer's open demands by itself, so its allocation messages reach the form only when a demand closed between the preview and the save. A receipt refused over the buyer's TDS or over GST has its own article.

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

  • Payment saved but clearing failed, or payouts in a run could not be clearedTroubleshooting

    The payment was recorded as Pending but its voucher could not be posted, most often because the books have no bank ledger for the account the money went through; fix the cause and clear it again.

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