How Does Society Maintenance Software Match UPI Payments?

Society maintenance software matches a UPI payment to a flat by comparing the payer's name and the amount against your residents and this month's open dues, then proposing the most likely flat for the treasurer to confirm. Done well, the treasurer stops reading bank statements line by line and only decides the doubtful cases.

This post walks through that logic using Aangan, the society maintenance product Taheri Developers built, because matching is an engineering problem before it is an accounting one. The product is summarised in the Aangan case study; here we go further into the reasoning, compare the options a committee really has, and say plainly where each one fits. One caveat up front: the case study publishes no customer numbers or testimonials, and neither does this post. Everything below describes what the product is designed to do.

Why a UPI payment is hard to match to a flat

A bank statement tells you who paid, how much and when. It does not tell you which flat the money is for. UPI credits often arrive with no flat number in the note, the person paying may be a spouse or a tenant rather than the registered owner, and some banks shorten the payer's name. Multiply that by a few hundred flats paying in the same week and the treasurer ends up reading the statement line by line against a WhatsApp group thread.

Committees try to fix this at the source by asking residents to write the flat number and bill month in the payment remark. A Housing Society Times article on UPI for maintenance bills recommends exactly that, and it helps. But it depends on every resident remembering every month, so unlabelled credits keep arriving.

Three situations cause most of the manual work:

• A credit with no flat reference. The only clues are the payer's name and the amount.
• A short or unfamiliar name. The bank shows an abbreviation of the resident's name, or a family member's name instead of the owner's.
• Several flats owing the same amount. When maintenance is charged by flat area, many flats can owe an identical figure, so the amount alone cannot decide.

NoBrokerHood's guide to auto reconciliation describes the same pattern: repetitive matching across many flats leads to late receipts, ledgers that drift away from the bank balance, and disputes that surface only when a resident complains. It treats these as a result of manual volume rather than carelessness, and we agree.

How society maintenance software matches a UPI payment to a flat

The approach in Aangan, as described on its case study page, is that the software narrows the search and a person settles the doubt. It works in four steps:

1. Read the credit. The software takes the payer's name and the amount from the bank credit.
2. Compare it with what is owed. It checks both against resident records and the dues of the current cycle.
3. Propose a flat and explain why. The suggestion carries its reasoning, for example that the amount and the name both fit one particular flat.
4. Let the treasurer confirm. One Match button settles it. If the evidence is thin, the treasurer decides.

The case study gives a worked example. A ₹2,900 credit arrives from "RAHUL D" with no flat in the note. Aangan checks it against residents and the cycle's dues and proposes B-404. The treasurer confirms, a receipt goes out on WhatsApp, and the flat turns green on the building view. The names and flat in that example are sample data, not a real society.

Two design choices make this workable. Payments go straight to the society's own bank account, so the money is already where the committee expects it. And the matching narrows the field instead of deciding, which is why the case study leaves doubtful cases to a person.

What happens after the match: late fees, receipts and the ledger

Late fees that follow your bye-laws

Late fees cause more arguments than almost anything else in a society, because the rule differs from one society to the next and gets quoted from memory. In Aangan the committee sets the late-fee rule once for the society. Residents who pay before the cut-off never see a fee or a firm reminder, and a payment at any point removes the flat from the reminder chain.

The timeline on the case study page is short. A gentle reminder goes three days before the due date and a nudge on the due day, both skipping anyone who has paid. Seven days after the due date a firm reminder adds the fee the bye-laws allow and explains the reason in the message. At day 30, messages to the resident stop and the committee receives a short list of long-pending flats for a human conversation.

Whatever tool you use, the rule itself has to be legitimate first. A MyGate guide to late payment penalty rules says penalties are shaped by the society's bye-laws and the law it is registered under, and generally need a general body resolution rather than a committee announcement. Check your registered bye-laws and your state's act before configuring any rate, and treat figures quoted on blogs as examples, not limits. This is general information, not legal advice.

Receipts and the ledger

Each payment gets a signed PDF receipt sent on WhatsApp as the money arrives. Receipt numbers follow a pattern of society, financial year and running count; the demo example on the case study is GR/26-27/0170. Every ledger entry records the flat, payer, payment mode, time, split and delivery status, so one payment can settle two dues, such as maintenance and a festival charge.

Cash is covered as well. Cash collected by staff shows on the dashboard as "with the guard" until someone marks it deposited, so the committee can see money that has been collected but is not yet in the bank. The ledger can be searched by flat, vendor or UTR and exported for auditors. According to the case study, the Federation plan adds a Tally export and GST invoices.

A fixed monthly routine ties it together. Bills go out on the 1st with a pay link, a transparency report on money in, money out and balance reaches every flat on the 5th, and each routine can be switched off and shows when it last ran.

Society maintenance software compared: spreadsheet, gateway reconciliation and confirm-to-match

Most committees choose between a few approaches. The list below shows how they differ on the points that usually decide the choice. It is not a scorecard of every product on the market, which would need each vendor's current plan; it covers only the options whose pages we read.

• Spreadsheet plus bank statement. Matching is by hand, often with a match key built from flat number and amount. Best for small societies; NoBrokerHood's guide says Excel suits societies under about a hundred flats. The catch is inconsistent flat numbering and formulas nobody remembers to update.
• Payment-gateway reconciliation. Online payments made through the platform's gateway are matched to the bank settlement automatically. Best where most residents pay inside the app. The catch: ADDA's description of its feature says cheque, NEFT and cash are still reconciled manually.
• Confirm-to-match on direct UPI (Aangan's approach). The software suggests a flat from the payer's name and amount, with reasoning, and the treasurer confirms. Best where residents pay the society's own UPI ID or QR code and the note is often blank. The catch: a person still decides the doubtful credits, and there are no published outcome figures yet.
• Full society platform. MyGate's accounting page lists billing, payment tracking, ledgers, vendor management and reports inside a wider community platform that also covers visitors and communication. Best if you want one app for security, communication and accounts. The catch: you adopt the whole platform.

When Aangan is not the right choice

If your society has fewer than a hundred flats, one treasurer who likes spreadsheets and a modest number of UPI payments, a well-built Excel sheet is probably enough, and NoBrokerHood's guide says as much. If your residents already pay through a gateway built into a platform you use for gate security, adding a second product splits your data across two places. And if you need full double-entry accounting or vendor GST and TDS handling today, confirm exactly what any product covers, ours included, before you commit.

Aangan's published pricing, as stated on the case study page, is free up to 20 flats and then ₹6 per flat per month. The free Starter plan includes 100 WhatsApp messages a month, Society removes the cap, and Federation adds Tally export and GST invoices. Check the live page for current plans before you decide.

What to ask before you choose society maintenance software

Whichever product you shortlist, ask the vendor to show the answer to each of these on a screen, not in a brochure:

• What happens to a UPI credit with no flat number? The answer should describe how a match is proposed, what evidence is shown, and who confirms it.
• Can the committee set the late-fee rule from the bye-laws? Look for a rule you set once, with the reason written into every message.
• Does it handle cash, cheque and card as well as UPI? Mixed collection is normal, and a tool that covers one mode leaves the treasurer reconciling the rest by hand.
• Where does the money go? Payments should land in the society's own bank account.
• Can an auditor get a clean export? Look for search by flat or UTR and an export your auditor or Tally can read.
• What are the message limits? Bills and receipts go over WhatsApp, so check whether your plan caps messages.

Where a custom build comes in

Some societies, federations and builders need more than a ready product: their own charge structures, several buildings under one body, or links to an existing ERP or Tally set-up. The case study notes that matching bank credits to invoices and applying rule-based fees are the same problems found in custom ERP and billing work. That is why Taheri Developers builds custom software and also offers ready products such as Aangan. If that describes you, the useful question is which of your rules are unusual enough that a ready product cannot hold them.

Next step

If your treasurer still reads bank statements line by line, start by counting how many UPI credits arrive each month without a flat number. That count tells you whether a spreadsheet is enough or matching software is worth adopting. If it is the second, try Aangan's free plan through the case study page, or tell us what your society or federation needs and we will say honestly whether a ready product or a custom build fits.