Society maintenance billing software
Set the billing structure once and the monthly run stops being a day of work. Invoices generate, deliver themselves, apply late fees uniformly, and chase the rest on WhatsApp, SMS and email.
Society maintenance billing software generates invoices automatically from your billing rule — per square foot, per flat or a hybrid — applies late fees and interest uniformly, delivers bills on WhatsApp, SMS and email, and tracks dues with ageing and defaulter reports.
Manual billing is why collections slip
In most societies the monthly bill run is one person and a spreadsheet, usually over a weekend. Carpet areas are multiplied by a rate, a handful of flats get adjustments somebody remembers, last month’s arrears are carried forward by hand, and five hundred PDFs are generated and emailed. It works, until the person doing it travels, resigns, or makes a copy-paste error in row 214.
The errors are not the main cost. The main cost is that a manual run makes everything downstream approximate. Late fees are applied to the flats somebody noticed rather than to every flat that qualified. Arrears ageing is a snapshot taken whenever the sheet was last opened. Nobody can answer what is outstanding today without rebuilding the sheet.
That approximation is what collection rates respond to. A member who receives a bill on the first, a reminder on the tenth, and a late fee on the sixteenth — every month, the same way, as does everyone else — pays differently from one who receives a bill whenever it is ready and a reminder when somebody is annoyed.
- Manual runs are bus-factor one. The whole billing cycle usually lives in one volunteer’s spreadsheet and their head.
- Selective enforcement invites challenge. A late fee applied to some defaulters and not others is the one a member successfully contests.
- Ageing is unknown between runs. Without live arrears, a committee cannot see a collection problem until the quarter is over.
Key capabilities
The first three decide whether the bill is right. The last three decide whether it gets paid.
Automatic invoices — per sq ft, per flat or custom
The billing rule is stated once and applied every cycle. Per square foot on carpet or built-up area, a flat rate per unit, or a hybrid where some heads are area-based and others are equal per flat — which is what most societies actually run, since a lift charge is arguably per flat while a common-area maintenance charge is arguably per area.
Per-head rules can differ. Sinking fund as a percentage of maintenance, water on consumption, a fixed parking charge per allotted slot, non-occupancy charges only for tenanted flats. Different wings, unit types and towers can carry different rates where the general body has resolved them.
Late fee and interest applied automatically
Your bye-law rule is configured — flat fee, percentage, or simple interest per annum — with the grace period and the due date. It then applies to every qualifying flat on the same day, without anyone deciding who to charge.
Uniformity is the legal point as much as the operational one. A late fee applied inconsistently is the one that gets waived under challenge, and a committee that has waived one has effectively waived them all. Automation removes the discretion that creates the exposure.
GST-compliant invoice formats
For societies registered under GST, invoices carry the fields a tax invoice requires — GSTIN, HSN or SAC, taxable value, rate and amount per head, and the society’s registered particulars. Exempt and taxable heads sit on the same bill with the split shown explicitly rather than blended into one figure.
Whether a society must register, and whether a particular member’s contribution is exempt, depends on turnover and on the per-member monthly threshold, and the position has moved more than once. We configure to your accountant’s determination rather than asserting a rule; what the software guarantees is that the resulting bill is internally consistent and reproducible.
Reminders on WhatsApp, SMS and email
Reminders run on a schedule the committee sets — say, three days before due, on the due date, and then at seven-day intervals — and stop automatically when the bill is paid. Nobody sends them and nobody has to remember to stop.
WhatsApp matters disproportionately in Indian societies because it is the channel people actually read. A reminder carrying the amount, the due date and a payment link converts far better than an email attachment, and the difference shows up in the collection curve within two cycles.
Ad-hoc, advance and one-time charges
Not everything is monthly. Move-in charges, event and clubhouse fees, a one-time repair levy approved by the general body, a penalty for a bye-law breach — each can be raised against a flat and appears on the next bill rather than being collected informally and recorded in a notebook.
Advances are handled properly rather than as a negative balance. A member who pays six months ahead has that held as an advance and drawn down each cycle, which is what keeps both the ledger and the member’s statement honest.
Defaulter lists and ageing reports
Ageing is live: what is outstanding, by flat, bucketed by how long it has been outstanding. That is the report that tells a committee whether it has a collection problem or a small number of long-standing cases, which are different problems with different remedies.
The defaulter list is generated from the same data the member sees on their own statement, which removes the argument about whether the number is right and moves the conversation to payment. Where recovery escalates, the statement of account is the document that supports it.
How it works
The whole cycle runs without a person in it, which is what makes it consistent enough to be defensible.
Who it helps
Billing is the module that most often justifies the platform on its own, because the time it removes is concentrated in one volunteer.
How societies actually structure a bill
Very few societies bill purely on one basis. The configuration that matters is the mix, and the resolution that authorised it.
| Billing basis | Typical heads | Suits |
|---|---|---|
| Per square foot | Common area maintenance, sinking fund, repair fund | Properties with widely varying flat sizes |
| Equal per flat | Lift, security, housekeeping, cable | Societies where usage does not scale with area |
| Hybrid | Area-based CAM plus per-flat services | Most societies, in practice |
| Consumption | Water, gas, electricity on sub-meters | Properties with metering in place |
| Per instance | Parking slot, move-in charge, clubhouse booking | Charges tied to a specific entitlement or event |
Works with the rest of KeyMatrix
A bill is not a document; it is a ledger entry with a delivery mechanism. Every invoice raised posts to the accounting ledger as it is created, and every receipt posts against it, which is why there is no reconciliation between billing and books — they are the same records viewed two ways.
The unit record is what makes the bill correct. Whether a flat is owner-occupied or tenanted decides non-occupancy charges; the allotted parking slots decide the parking head; the carpet area on the unit decides the area-based heads. When a flat changes hands, billing follows the handover rather than needing to be told.
Consumption heads come from the meters directly where smart metering is deployed, so a water charge is a reading rather than an estimate that gets argued about at the AGM.
- Accounting. Invoices and receipts post to the double-entry ledger as they happen.
- Online payments. Paid bills reconcile themselves; reminders stop on payment.
- Unit management. Area, occupancy and parking entitlements drive what each flat is billed.
- Smart metering. Utility heads bill from actual readings instead of estimates.