Case study · Property OS
Property OS: from a paper register to bills on WhatsApp
Billing and collections for residential societies and townships, with one live register for every house and a clear trail for every correction.
The problem
The register lives in a notebook
A residential society runs on money that comes in from many households, month after month. In most places that still means a paper register, a calculator and a lot of memory. It works until it does not, and it fails in four familiar ways.
- The register is on paperAmounts live in a notebook and on a calculator.
- Arrears are guessworkWho owes what, and since when, nobody can say quickly.
- Corrections overwrite historyA wrong bill gets scratched out, and the trail is lost.
- Bills are typed one by oneEvery bill is typed and sent by hand, one house at a time.
How it works
Four steps, from register to certificate
Watch one township go through a billing cycle. Pick a step to jump to it.
Property OS
Mistakes fixed by credit note, with a full audit trail
A wrong bill is never edited. A credit note is stacked on it, then the statement and no-dues certificate follow.
- Every house, one register. The committee decides each amount, so it is entered, not guessed by the system.
- Bills numbered without gaps, sent where residents already are. A draft becomes a bill run. Exceptions are flagged before anything goes out.
- Receipts and arrears per house, always current. Payments come back, receipts are stamped, and the houses still owing are queued.
- Mistakes fixed by credit note, with a full audit trail. A wrong bill is never edited. A credit note is stacked on it, then the statement and no-dues certificate follow.
Set up
Every house, one registerThe committee decides each amount, so it is entered, not guessed by the system.Bill
Bills numbered without gaps, sent where residents already areA draft becomes a bill run. Exceptions are flagged before anything goes out.Collect
Receipts and arrears per house, always currentPayments come back, receipts are stamped, and the houses still owing are queued.Correct
Mistakes fixed by credit note, with a full audit trailA wrong bill is never edited. A credit note is stacked on it, then the statement and no-dues certificate follow.
What a person still decides
The committee decides. The office records.
Property OS never invents an amount. The committee sets every amount and approves each bill run before a single bill goes out.
Exceptions are shown first, so the committee sees the odd ones before they are sent.
The office records payments as they arrive, and the receipt and the arrears update at once.
A mistake is never erased. It is corrected by a credit note, so the full history stays readable.
Where it is used
Places that collect from many households
- Residential societiesMonthly maintenance, one clear register, and receipts that go out the same day.
- Apartment associationsShared costs split fairly, with arrears visible per flat.
- TownshipsMany lanes and many houses, billed in one run and followed up from one queue.
Next
Bring your register and see a bill run
A short call is enough to see whether Property OS fits how your society collects.
More case studies