Collect
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.
07. Collect
Collection turns the payment schedule into money in the bank: a demand bills one or more installments (or a member's offer charges), the receipt is recorded and cleared, and the money is placed across the demand's charge lines by hand. Demand runs bill a whole project at once. The accounts team does this chapter, with the collections executive chasing what is overdue and the finance head watching the RERA accounts: every receipt enters the project's collection account, and the bank's daily sweep to the RERA separate and operative accounts is mirrored in the books by a system rule.
Before you start
06. Sell for bookings with a finalized payment plan, or 05. Tenant offers and allotments for member charges. Every charge component must be mapped to a ledger in the promoter's books before a demand can issue, which is the first article below. The organization's TDS and escrow share rules come from 01. Set up the organization.
In this chapter
- Map a charge component to a ledger: Tell the books which ledger each charge posts to; demands cannot issue without it.
- Raise and issue a demand on a booking: Bill one or more installments of a booking and issue the demand.
- Bill and collect a member's charges: Raise the demand on a society member's offer charges and take their receipt.
- Bill a whole project with a demand run: Bill everything due on a project in one batch.
- Cancel or correct a demand: Fix a draft, or cancel an issued demand with a credit note.
- Record and clear a buyer's receipt: Record the buyer's money, clear it to post the receipt voucher, and record Form 16B for the TDS.
- Appropriate a receipt across a demand's charge lines: Place the money across the demand's charge lines in the split you decide.
- Bounce a returned payment or correct a pending one: Mark a returned cheque as bounced, or fix a receipt that has not cleared.
- Chase overdue demands: Find what is overdue, send reminders and read the ageing.
- Check the RERA accounts and the sweep share: Read the project's RERA accounts card and the statement, and set the escrow share the sweeps follow.
- Sweep the collection account by hand: Post the day's sweep yourself when the daily rule is off or a day failed to post.
- Component mappings: Which ledger each charge component posts to in the chosen books.
- Demands & money: The booking's demands, receipts, payouts and commission in one place.
- Demands: Every demand in the chosen books.
- Demand: One demand: installments, GST and TDS, receipts and appropriation.
- Demand runs: Every demand run and the dialog that drafts one.
- Demand run: One run: what it drafted, skipped and failed to issue.
- Payments: Every receipt and payout, and the buttons to record one.
- Record receipt / Record payout: The form for a receipt or a payout: who, how, how much, against what.
- Payment: One payment and its actions: clear, bounce, cancel, edit.
- Edit payment: Change a payment that has not cleared yet.
- RERA accounts: The RERA accounts statement for one set of books or one project: receipts into the collection account, sweeps, withdrawals and balances.
- RERA sweeps: Every mirrored bank sweep, and Sweep now.
- RERA sweep: One day's sweep: its receipts, split and voucher; post, edit, cancel or reverse it.
- Component mappings: which ledgers a charge posts to: Main ledger, tax ledger, cost centre and the deferred-revenue ledger a mapping names.
- Demands, demand runs and the GST split: What a demand is, how it is numbered and how GST is split.
- TDS under section 194-IA: The 1% the buyer withholds, the threshold, and how the demand shows it.
- Receipts and payouts: allocation, clearing and the UTR: Pending, cleared, bounced: when a receipt actually posts.
- Manual appropriation of receipts: Why a receipt settles the demand as a whole and you decide the split by hand.
- Party ledgers, bill-wise tracking and ageing: The bill-wise ledger every buyer and member gets, and the ageing built on it.
- Numbers and series: documents, bookings, demands, payments and vouchers: How demands, demand runs and payments are numbered by financial year.
- RERA accounts and the daily sweep: The three accounts, the daily sweep NirmaanOne mirrors, and the certified withdrawals.
What comes next
Money going the other way is 08. Pay out. What the postings do to the ledger, the month-end review and revenue recognition are in 10. Accounting, reports and revenue recognition. Reminders and demand letters can be automated in 11. Automate.
Related
- 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.
- 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.
- Bill and collect a member's chargesHow-to
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 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.
- 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.
- 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.
- Bounce a returned payment or correct a pending oneHow-to
Mark a cheque or transfer the bank returned as bounced so its voucher is reversed and the demand reopens, and fix, cancel or delete a payment that is still pending.
- 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.
- Check the RERA accounts and the sweep shareHow-to
Set the organization's escrow share rule (or a project's own share), make sure every receipt enters the project's collection account, and read the RERA accounts card and statement to see that the daily sweeps to the RERA separate account meet the share.
- 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.
- 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.
- 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.
- 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.
- 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.
- Demand runScreen
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.
- PaymentsScreen
Every receipt and payout of the chosen books, with filters and search, and the buttons to record a receipt, record a payout or open the payout runs, the RERA sweeps, the TDS credits and the escrow withdrawals.
- 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.
- Edit paymentScreen
Change the date, mode, amount, bank details and, on a payout, the allocations of a payment that hasn't cleared yet, and optionally clear it in the same step; a receipt settles the open demands again by itself when saved.
- RERA accountsScreen
The RERA accounts statement for one set of books, or one project: what reached the collection account, what was swept to the separate and operative accounts and at what share, what was withdrawn from the separate account, and the movement on the four accounts' ledgers.
- RERA sweepsScreen
Every RERA sweep of the organization, one per receipt the moment it clears into a project's collection account (mirroring the bank's sweep of that account into the RERA separate and operative accounts) or one per clearing date from the Sweep now dialog that previews and posts sweeps by hand.
- Component mappings: which ledgers a charge posts toConcept
A component mapping tells one set of books where a charge component posts: a main ledger, an optional second tax ledger, an optional cost centre and, for sale and tenant charges, the revenue treatment; demands, commissions, benefit accruals, payouts and cancellations all read it, and an unmapped component stops the posting.
- 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.
- 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.
- 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.
- Party ledgers, bill-wise tracking and ageingConcept
A party ledger is the bill-wise ledger a set of books keeps for one buyer, society member, channel partner or vendor, created on first use with a generated code; every posting on it is allocated as New Ref (opens a bill), Against Ref (settles one), Advance or On Account, so the books know what each bill still owes and how overdue it is.
- Numbers and series: documents, bookings, demands, payments and vouchersConcept
How NirmaanOne numbers what it creates: generated documents, bookings, demands, demand runs, payments, payout runs and revenue runs take a prefix, the Indian financial year and a five-digit serial (BK-2026-27-00007), while vouchers are numbered on posting from their voucher type's prefix, padded counter and suffix.
- RERA accounts and the daily sweepConcept
Every buyer payment enters the project's collection account; the bank sweeps it daily, the escrow share (70% under RERA 2016, or the project's own share) to the RERA separate account and the rest to the operative account. NirmaanOne mirrors the sweep as a Contra voucher per receipt the moment it clears, records certified withdrawals from the separate account, warns on receipts banked elsewhere and reports where the money stands; it never moves the money itself.