Online maintenance payment and autopay
Residents pay from the bill itself, autopay handles the ones who would rather not think about it monthly, and every payment reconciles to the invoice and the ledger without a treasurer matching anything by hand.
Online maintenance payment lets residents pay by UPI, card or netbanking directly from the invoice, with autopay e-mandates for recurring dues. Receipts issue instantly, payments reconcile to the invoice and the ledger automatically, and failed or duplicate payments are handled without manual intervention.
Make paying easier than delaying
Most maintenance arrears are not refusal. They are friction. A member who has to remember the amount, open a banking app, type an account number and an IFSC, add a reference nobody will read, and then send a screenshot to a WhatsApp group, will do it — but not on the due date, and not every month.
Every step in that sequence is a place to stop. The screenshot step is the worst of the lot, because it converts a payment into a task for the treasurer: open the image, read the amount, find the flat, mark it paid in the sheet. Five hundred flats produce five hundred of those, and the reconciliation lag becomes the arrears figure.
A payment link on the bill removes the whole sequence. Societies that make this change usually see the collection curve shift within two cycles — not because anyone was persuaded, but because the reason for delay was procedural.
What happens when a resident taps pay
The treasurer’s involvement in a successful payment is zero, which is the whole objective.
Autopay with e-mandates for fixed monthly dues
A resident can authorise a recurring mandate once, after which each month’s bill is collected on the due date without any action. For the substantial fraction of members whose maintenance is a fixed amount they have no intention of disputing, this removes the transaction entirely.
Mandates carry a cap the resident sets, and a bill exceeding it is presented for approval rather than collected silently. A member is notified before each collection, so autopay never becomes a surprise debit — which is the failure that gets mandates cancelled en masse.
Partial and advance payments, and how they are allocated
Members can pay part of a bill or several months ahead. A partial payment is allocated and the balance stays outstanding with the reminder schedule intact; an advance is held and drawn down against future bills rather than sitting as an unexplained credit.
Partial payments allocate against the oldest outstanding invoice by default, following the allocation rule the committee sets. Getting this rule explicit matters: it decides whether a part payment reduces the principal or the accrued late fee first, which residents notice.
Both cases are where spreadsheet billing usually breaks down, and both are common — the member clearing arrears in instalments and the member who pays a year ahead before travelling are the two most frequent non-standard cases in any society.
Multiple gateway options, and who pays the charges
The society chooses its gateway rather than being locked to ours, which matters because gateway pricing is negotiable at volume and settlement timelines differ. Switching gateway does not mean switching platform. Paid amenity bookings and deposits use the same gateway and the same receipt series.
Charges are shown transparently and can be borne by the society or passed to the payer, according to what the general body has resolved. That decision has a real annual cost at scale and belongs to the members, so the software makes it a setting rather than a default.
Dues never affect gate access or amenity entry unless the general body has explicitly resolved it, so collection is never enforced at the barrier.