Schedules generated from the booking
Pick a plan and the full sequence is written: booking money, down payment, monthly or quarterly kisti, milestone-linked payments and the handover balance. Change the plan and the remaining lines rebuild.
Collections
Installment collection software built for how Bangladeshi developers actually get paid: a kisti schedule generated at booking, a due list that is correct every morning, follow-up that escalates on its own, and a buyer ledger that finance and sales read the same way. Collections stop depending on one person's memory.

A developer's cash position is not decided by how many units were sold. It is decided by how much of the agreed schedule actually arrived this month. On a 36-month kisti plan, a five per cent slippage in collection across 200 buyers is a working-capital problem that shows up two quarters later as a construction delay.
The usual setup makes slippage invisible. The schedule lives in one sheet, receipts in a book, bank statements in a folder, and the follow-up in someone's head. Nobody can answer "who is overdue right now, by how much, and when were they last contacted" without a day of work — so the question stops being asked.
PropERP makes that one screen. Every buyer's schedule is generated from their booking, every receipt posts to the ledger on issue, and the overdue list rebuilds itself overnight. Follow-up is a queue with owners and dates, not a habit.
Booking money, down payment, thirty-six monthly kisti and the handover balance — each line with a due date, a status, a payment channel and a receipt number.
Collections / Payment schedule — A-4A · Rezaul Karim
Unit price
৳ 1.33 Cr
Collected
৳ 34.6 L
8 of 38 lines
Due this month
৳ 2.96 L
Overdue
৳ 2.96 L
1 kisti · 14 days
| # | Milestone | Due | Amount | Status | Receipt |
|---|---|---|---|---|---|
| 00 | Booking money | 29 Jun 2026 | ৳ 5,00,000 | Paid · bKash | MR-00418 |
| 01 | Down payment | 15 Jul 2026 | ৳ 21,68,000 | Paid · Bank | MR-00463 |
| 02 | Kisti 1 of 36 | 05 Aug 2026 | ৳ 2,96,111 | Paid · Nagad | MR-00519 |
| 03 | Kisti 2 of 36 | 05 Sep 2026 | ৳ 2,96,111 | Overdue 14d | — |
| 04 | Kisti 3 of 36 | 05 Oct 2026 | ৳ 2,96,111 | Upcoming | — |
| 38 | Handover balance | 20 Dec 2029 | ৳ 13,34,000 | Scheduled | — |
26% of contract value collected
26%Every receipt posts to accounts on issue — the sales ledger and the finance ledger cannot drift apart.
Pick a plan and the full sequence is written: booking money, down payment, monthly or quarterly kisti, milestone-linked payments and the handover balance. Change the plan and the remaining lines rebuild.
Due today, due this week, overdue by ageing bucket — per project, per buyer, per collector. It is a working list, not a report someone compiles.
SMS at day one, WhatsApp at day seven, a call task at day fourteen, a demand letter at day thirty. The sequence runs automatically and every touch is logged on the buyer.
Partial payments, advance payments, cheque bounce reversal, late fees and waivers are all first-class entries — not manual notes that break the total.
bKash, Nagad, bank transfer, pay order, cheque and cash are separate channels, so matching a bank statement against receipts is a comparison rather than an investigation.
Sales sees what the buyer owes; finance sees the same numbers posted to accounts. There is no monthly exercise to make the two agree because they were never separate.
A 1,450 sft unit at ৳ 9,200 per square foot, on the plan most Dhaka developers offer.
| Component | Basis | Amount | Timing |
|---|---|---|---|
| Booking money | Fixed | ৳ 5,00,000 | On booking |
| Down payment | 20% of unit price | ৳ 21,68,000 | Within 30 days |
| Monthly kisti | 36 equal lines | ৳ 2,96,111 | 5th of each month |
| Utility & extras | At handover | ৳ 4,50,000 | Before possession |
| Handover balance | 10% retained | ৳ 13,34,000 | On completion certificate |
Illustrative figures on a ৳ 1.33 crore unit. The point is the structure: five different payment behaviours on one contract, which is exactly why a single spreadsheet column called "paid" stops being usable.
The line ages past its due date overnight and enters the overdue bucket with an amount and a day count.
SMS and a WhatsApp template go out on your schedule, in Bangla, with the unit and amount merged in.
A call task lands with the assigned collector; the outcome is recorded against the buyer, not in a notebook.
A demand letter is generated with the contract clause, the outstanding amount and the late fee, ready to print or email.
Yes. Plans are defined per project and per unit type — different down payment percentages, different kisti counts, milestone-linked payments for construction-linked plans, and a separate handover component. A buyer can also be put on a bespoke schedule with an approval trail.
The part payment is receipted against the line, the balance remains due with its original date, and the ageing continues on the unpaid remainder. The ledger never shows a line as paid when it is not.
Yes. SMS and Meta-approved WhatsApp templates are sent on a schedule you define, with the buyer name, unit and amount merged in. Every send, delivery and reply is logged on the buyer record.
Yes — generated from the outstanding position with the contract clause, amount, late fee and due date, on your letterhead, in Bangla or English, ready to print or email in a batch.
Each channel is recorded distinctly on the receipt, so a statement from a mobile financial services provider is matched against receipts of that channel only. Mismatches surface as a short exception list instead of a full re-check.
Yes. A receipt posts to the accounts ledger when it is issued. Finance works from the same figures sales sees, which removes the monthly reconciliation meeting rather than shortening it.
Next step
Send us a real payment plan and a week of collections. On the call we will show the same buyers as a due list, an ageing bucket and a follow-up queue, and you can judge whether it beats what you run today.
40 minutes · walked through on your project structure · no card required