Society Maintenance Online Payment: UPI, Receipts and Reconciliation

Collecting society maintenance online

The treasurer's real job in most societies is not accounting. It is matching a bank statement full of UPI credits labelled UPI/4471829/PAYMENT against a list of 180 flats, every month, by hand.

Online collection is worth doing for exactly one reason: it can eliminate that matching step. If a payment arrives already attached to a bill, a flat and a period, the reconciliation is done at the moment of payment rather than reconstructed a fortnight later. Everything else — convenience for residents, fewer cash handling risks, faster collection — is real but secondary.

This page covers the payment methods worth offering, what a compliant receipt has to contain, and the failure cases that decide whether the system saves the treasurer time or costs them more.

The methods, and what each actually costs

For Indian housing societies UPI is the default answer. Merchant discount rate on UPI for most society-sized collections is effectively nil, and resident adoption is near universal.

The one to think carefully about is credit card. A 2% fee on a ₹6,000 monthly bill across 180 flats is over ₹2.5 lakh a year. Either exclude it, or pass the charge to the payer explicitly — and if you pass it on, show it as a separate line before payment, not as a surprise.

Reconciliation is the feature

A payment page that dumps money into the society account without tagging it has solved nothing.

What you want is a payment that carries the bill identity end to end: resident opens their bill, pays from it, and the credit lands already associated with that flat, that bill and that period. The ledger updates without a human deciding what the payment was for.

Three cases break this, and you should ask any vendor how they handle each:

• Part payments. A resident owes ₹6,000 and pays ₹4,000. Does it apply to the oldest outstanding bill, the current one, or sit unallocated? Your bye-laws or a general body resolution should set the rule — oldest-first is the usual and the most defensible.
• Overpayment and advances. Residents routinely pay a round figure. That surplus must land in a visible advance balance and auto-apply next cycle, not vanish into "miscellaneous receipts".
• Direct bank transfers. Someone will always NEFT the society account directly. There must be a way to record that payment against a bill manually, or your ledger drifts from your bank.

Receipts: what has to be on them

Every payment needs a receipt issued automatically, not on request. At minimum:

• Society name, registration number and address
• Receipt number from an unbroken sequence
• Date of receipt and date of payment
• Flat number and the member's name
• Period the payment covers
• Amount, broken into heads — maintenance, sinking fund, water, arrears, interest
• Payment method and reference number
• GST details only if the society is actually registered and liable

That last point catches people out. Societies whose aggregate turnover crosses the registration threshold, and which charge above the per-member exemption, may be liable for GST on maintenance. Both the threshold and the exemption limit have changed over the years and the treatment has been litigated, so confirm your society's position with its auditor rather than assuming — and do not print a GSTIN on a receipt if the society does not have one.

Receipts should be immutable once issued. If a receipt needs correcting, issue a documented reversal; never silently edit a receipt that a member is already holding.

Handling failed and pending payments

This is the part that generates angry calls, and it is worth designing for.

A UPI payment can be debited from the resident and still fail to confirm to the society, usually because the callback was lost. The resident sees money gone and a bill still marked unpaid. If your process is "wait and see," you have a furious member.

• Reconcile against the gateway, not just the callback. A scheduled check that pulls settled transactions catches every lost callback.
• Show a clear pending state. "Payment received, confirming with bank" is very different from "unpaid", and prevents a duplicate payment.
• Give the resident their reference number immediately, so they can raise it with their bank.
• Never auto-charge a late fee on a payment made before the due date but confirmed after it. Judge lateness by payment time, not settlement time.
• Have a documented refund path for genuine duplicates, with committee sign-off, and account for refunds properly.

Getting residents to switch

Announcing a payment link does not move the needle. What works:

• Send the bill and the payment path in the same message. Reduce it to one tap.
• Keep offering cheque and cash for one or two cycles, then narrow it — publish the date in advance.
• Fix the receipt experience first. Residents who receive an instant receipt trust the channel; those who have to ask do not.
• Target the treasurer's pain, not the resident's: even 70% online collection removes most of the monthly matching work.

How this works on Plinth

Residents pay directly from the bill they are looking at, so the payment is tied to the flat, the bill and the period from the outset. The receipt is generated automatically on confirmation.

Payment status is explicit rather than binary — a payment awaiting bank confirmation is visibly pending, not silently unpaid — so residents do not pay twice while a callback is in flight. Payments recorded outside the app, such as a direct bank transfer or a cheque, can be entered against the bill so the society ledger and the bank statement stay in agreement.

Every posting is written to the append-only audit log, so a receipt cannot be quietly altered after a member has been given it.

Frequently asked questions

Is there a charge for residents to pay by UPI? For normal person-to-merchant UPI collection there is no MDR, so societies typically absorb nothing and charge nothing. Card payments are different — decide and disclose your policy before enabling them.

Can we insist all residents pay online? Practically you can make it strongly default, but a blanket refusal to accept any other tender is hard to defend and unnecessary. Narrow the alternatives gradually instead.

How do we handle a resident who pays the exact bill but not the arrears? Apply payments oldest-first by policy, and make that policy a written general body resolution. Then the allocation is a rule, not a monthly argument.

Does online payment mean the society needs a payment gateway account? Yes — collections settle into the society's own bank account through a gateway or aggregator. The account must be in the society's name; never route society collections through an office-bearer's personal account or UPI ID.

What about GST on maintenance? It depends on the society's turnover and per-member charge, and the rules have shifted. Ask your auditor for a written position rather than copying another society.

Step-by-step guides

• Resident: Use Online Payments

Related: UPI Autopay mandates for societies · maintenance dues reminders and escalation · society financial statements