Real Estate

Society Management ERP — 450-Unit Gated Community, Bangalore

WALKTHROUGH · HYPOTHETICAL

12 STAFF USERS

RESIDENTIAL GATED COMMUNITY · 450 UNITS, 3 TOWERS · BANGALORE

14 WEEKS BUILD TIME

KEY OUTCOME

Monthly maintenance collection rate: 65% → 94% within 3 months. AGM accounts preparation: 3 weeks → 1 day. 100% of complaints formally tracked with SLA for the first time.

THE PROBLEM

What was happening before

Prestige Greenfields — the name is fictitious, the situation is not — is a 450-unit gated community in Whitefield, Bangalore, spread across three towers: A, B, and C wing. The residents welfare association is governed by a seven-member elected committee: Chairperson, Secretary, Treasurer, and four ordinary members. The community has 450 families, a clubhouse, a gym, a party hall, three sports courts, and a 24-hour security team of eight guards. Monthly maintenance collections, when everybody paid, amounted to ₹27 lakh. Everybody did not pay.

The billing process was a WhatsApp message. On the first of every month, the Secretary typed a message — 'Dear Resident, your maintenance for [Month] is ₹4,500. Please transfer to society account [account number] and share screenshot in this group.' The message went out to a 450-member WhatsApp group. Residents who paid screenshot their UPI transaction. The Treasurer manually updated an Excel sheet for each payment received. Residents who did not pay received no further automated communication — whether they received a follow-up depended entirely on whether the Secretary personally sent them a message, which he did for the most persistent defaulters but could not sustain for 158 non-paying units every month.

The society had a Tally account maintained by the Treasurer — a retired accounts professional who had been on the committee for six years. She was the only person who could log into it. She was the only person who understood the chart of accounts she had configured. Every month she spent three days preparing a one-page summary of income and expenditure that she presented at the committee meeting. The committee reviewed the summary. They asked questions. She answered them. Nobody else could independently verify the numbers by opening the books, because nobody else had access or could interpret them if they did. The Chairperson described this as a single point of failure sitting on ₹82 lakhs of society funds — the combined balance of the maintenance fund, sinking fund, and corpus fund.

The visitor management system was a paper register in a wooden stand at the main gate. Guards wrote down the visitor's name, the resident's flat number, the visitor's vehicle number, and the entry time. Exit time was recorded when the visitor left. The register was never cross-referenced against the resident's permission. A guard who had been at the society for six months knew which faces to let in. A new guard, or a guard at night, let in anyone who stated a flat number with sufficient confidence. Three months of registers occupied a shelf in the security cabin. If the committee wanted to know whether a particular visitor had entered on a particular date, someone had to physically search through paper.

Resident complaints came into a WhatsApp group called 'Society Issues — Greenfields'. The Secretary monitored it. When a complaint appeared — 'Lift in B wing not working since yesterday' or 'Water leakage in corridor near B-404' — the Secretary forwarded it to a second WhatsApp group containing the maintenance vendors. The plumber acknowledged with a thumbs-up. Whether the plumber actually came and fixed the issue was unknown to the Secretary until the resident posted again — either 'Thanks, it's fixed' or 'Still not resolved, it's been 4 days.' There was no formal assignment, no deadline, no escalation, and no proof of resolution. The committee had no idea how many complaints were open at any given moment or how long they typically took to close.

Amenity bookings — specifically the party hall and the clubhouse function room — were managed on a WhatsApp group called 'Amenity Booking Requests'. A resident posted: 'Booking party hall for 15th November, evening 6–10 pm.' The Secretary replied 'Confirmed' in the chat. Another resident, scrolling the group two days later, missed the first message and posted: 'Booking party hall 15th November 6–10 pm for my son's birthday.' The Secretary confirmed again, having forgotten the earlier booking. On the 15th November, two families arrived at the party hall at 6 p.m. with decorators and catering. The Secretary spent the evening on the phone mediating. This happened three to four times a month across the clubhouse and the party hall.

The Annual General Meeting preparation was the event the Treasurer dreaded most. The AGM required a full-year income-expenditure statement, a balance sheet, a receipts-and-payments account, and a statement of funds. Preparing these from the Tally instance took three weeks. She would spend evenings and weekends for most of January compiling the December year-end accounts while also managing January's billing. By the time the AGM was held in late January, the accounts she presented were accurate — but the preparation had consumed her almost entirely. The committee had discussed whether they should hire a professional accountant to take over, but could not agree on how to give a stranger access to the society's financial records when the records were on the Treasurer's personal Tally instance.

“Our treasurer is a wonderful person and she works very hard. But she is the only person in the committee who can read the society's books. If she is unavailable, we genuinely do not know how much money the society has. That is not governance — that is a single point of failure sitting on ₹82 lakhs of society funds.”
— Chairperson · residents welfare association, Bangalore

BEFORE

65%

Monthly maintenance collection rate — 158 units paid nothing each month, and the secretary followed up on each one individually by WhatsApp or phone call

3 days

Every month the treasurer spent preparing the accounts summary for the committee — the only person who could access or interpret the Tally instance she managed personally

Of resident complaints formally tracked — all complaints came into a WhatsApp group, were forwarded to a vendor on another WhatsApp group, and had no resolution confirmation

Paper

Visitor register at the gate — entries by hand, no resident pre-approval, no vehicle tracking, and three months of registers stored in a security cabin with no searchable record

PLATFORM WORKFLOW

How the platform works

Click any module to explore what was built

MODULE 01 OF 06

Resident Registry

Every unit in all three towers has a structured record — owner details, tenancy status, occupant names, vehicle registrations, parking slot, and family member count. This registry is the source of truth for billing, gate approvals, complaint attribution, and NOC checks. When a resident moves out, the record is updated and all history is preserved under the unit, not the person.

Unit-level records with owner name, contact, and ownership documents — tenant details stored separately when the unit is rented out
Vehicle registration and parking slot allocation per unit — guard app references this for vehicle entry without asking the resident each time
Family member and domestic staff registry per unit — forms the basis for gate pass management and daily staff entry logs
Occupancy status tracking: owner-occupied, tenant-occupied, vacant — billing and gate behaviour adjusts per status
Move-in and move-out workflow: incoming resident details entered, outgoing dues checked, NOC issued if clear — all from one unit record

Progress

1 / 6

THE SYSTEM

What I built

I built a full Society Management ERP covering every operational domain the committee had identified as broken: billing, collections, visitor management, complaints, amenity booking, accounts, and committee reporting. The system replaced the 450-member WhatsApp billing group, the paper gate register, the complaints WhatsApp chain, the verbal amenity booking confirmations, and the Treasurer's personal Tally instance — with a structured platform that every committee member, resident, guard, and vendor interacts with through role-appropriate interfaces.

**Resident and unit registry:** The foundation of every other module is a unit-level resident registry. Each of the 450 units has a record with: owner name, owner contact, whether the unit is owner-occupied or tenant-occupied, tenant name and contact if applicable, number of family members, vehicle registrations and parking slot allocation, and occupancy status. This registry is the single source of truth — billing, visitor pre-approvals, complaint submissions, and amenity bookings all reference it. When a resident moves out, their record is updated and the incoming resident's details are entered; all history for the unit is preserved under the unit record, not the person.

**Maintenance billing engine:** On the 1st of every month, the system generates one bill per unit automatically. Bills are configurable by wing and flat type — A-wing 3BHK residents pay a different maintenance amount than B-wing 2BHK residents. Each bill has separate line items for maintenance charge, sinking fund contribution, parking fee if applicable, and utility charge. Penalties from the previous month — calculated at 12% per annum on the overdue amount, prorated daily — are automatically added to the current bill. The bill is sent to each resident by WhatsApp with an embedded payment link. No message is typed manually. No WhatsApp group broadcast. Every resident receives their own bill addressed to their unit.

**Payment collection and auto-reconciliation:** The payment link on each bill connects to the society's payment gateway. When a resident pays — UPI, net banking, or debit card — the payment is captured, a receipt is generated immediately and sent to the resident on WhatsApp, and the bill is marked paid in the system. The Treasurer no longer enters payments manually. UPI transfers to the society bank account are reconciled daily by the system against the bank statement imported or synced via the bank API. Cash payments, made at the society office, are entered manually with a receipt issued. The collection dashboard shows — in real time — how many units have paid, how much has been collected, how much is outstanding, and which units are overdue by how many months.

**Guard app with QR-code pre-approval:** Each guard carries a mobile with the guard app. Residents pre-approve expected visitors from the resident app by entering the visitor's name, phone, expected date, and time window — the visitor receives a WhatsApp with a QR code. At the gate, the guard opens the guard app, scans the QR, and sees the resident's name, flat number, and the approval details. Gate opens. The entry is logged automatically. For unexpected visitors, the guard enters the visitor's name and reason, and a WhatsApp notification goes to the resident: 'Visitor [Name] at the gate requesting entry. Approve or Deny?' The resident taps a button; the guard sees the response on the app. Domestic staff are managed via daily passes or monthly registered passes with photo. Delivery personnel have a separate category with package description. Every entry and exit is timestamped and searchable.

**Complaint helpdesk with vendor assignment and SLA:** Residents submit complaints from the resident app by selecting a category — electrical, plumbing, lift, common area, security, housekeeping — and writing a description with an optional photo. The complaint creates a ticket with a ticket number and a timestamp. The society manager or Secretary assigns the ticket to a vendor or in-house technician with a resolution deadline — 4 hours for critical issues, 24 hours for standard. The vendor receives a WhatsApp with the ticket details. When the work is done, the vendor submits a photo of the resolved issue from their phone. The ticket moves to Resolved. The resident receives a WhatsApp notification: 'Complaint #1043 (Lift B-wing) has been resolved. Please confirm or re-open.' If the resident confirms, the ticket closes. If they re-open it, the ticket escalates to the Secretary automatically. The committee dashboard shows open tickets by category, average resolution time, and overdue tickets — without the Secretary asking any vendor for an update.

**Amenity booking with real-time availability:** The amenity booking module shows a live availability calendar for the party hall, clubhouse function room, gym, and sports courts. A resident selects a date, time slot, and amenity, pays the booking fee online if applicable, and receives a confirmation. The system enforces per-unit booking limits — one party hall booking per unit per month. Double bookings are structurally impossible. The Secretary sees all upcoming bookings on the calendar. Cancellations are processed with a refund if within the cancellation window, configured per amenity. The WhatsApp group for booking requests is retired; the committee stops refereeing conflicts.

**Double-entry society accounts with committee visibility:** Every financial transaction in the system — maintenance receipt, late fee collection, booking fee, bank interest, vendor payment, staff salary, utility bill — is recorded as a double-entry journal entry in the society's ledger. The chart of accounts is structured with four fund buckets: maintenance fund, sinking fund, corpus fund, and general reserve. Every committee member can open the live dashboard and see: total income this month, total expenses, fund-wise balances, pending dues, and a month-wise comparison for the current financial year. Nobody needs to ask the Treasurer what the balance is. The Treasurer's role shifts from sole data custodian to finance reviewer — she still reviews and approves entries, but she no longer has to prepare reports because the reports generate themselves.

**NOC management:** When a resident wants to sell or rent their unit, they submit a NOC request through the resident app. The system checks: whether the unit has any outstanding maintenance dues, whether any complaints are open against the unit, whether the unit has pending penalty balances. If all checks pass, the NOC is generated as a PDF signed digitally by the Secretary. If dues are outstanding, the NOC is held until they are cleared — the system shows the resident exactly what amount is blocking the NOC. This replaced a manual process where the Secretary checked Excel, asked the Treasurer for dues confirmation, and prepared the NOC letter in Word over two to three days.

**Committee dashboard and AGM reports:** The committee dashboard shows the society's operational health in real time: collection rate by wing, overdue units by aging, complaint resolution rate and average closure time, amenity utilisation, and fund balances. The AGM accounts package — balance sheet, income-expenditure statement, and receipts-and-payments account for the full financial year — is generated as a formatted PDF in one click. The Treasurer reviews it for accuracy, the committee approves it, and it goes to the printer. The three-week January ordeal is replaced by a review meeting.

Auto-billing engine with penalty calculation and online payment

Maintenance bills are generated automatically on the 1st of every month — one bill per unit, configurable by wing and flat type, with separate charge heads for maintenance, sinking fund, parking, and utility. Each bill carries a payment link. Payments via UPI or bank transfer are auto-reconciled against the bill. Penalties for late payment accrue automatically after the due date and appear on the next bill without the treasurer calculating them manually.

Guard app with resident pre-approval and QR-code entry

Residents pre-approve expected visitors from their phone — the visitor receives a QR code valid for the approved date and time. The guard scans the code at the gate; the entry is logged automatically with the resident's unit, visitor name, and timestamp. Unexpected visitors are entered manually by the guard and a WhatsApp notification goes to the resident for approval before the gate opens. Deliveries and domestic staff have their own category with daily and monthly pass options.

Double-entry society accounts visible to every committee member

All society income — maintenance receipts, interest income, hall booking fees, penalty collections — and all expenses are entered in a double-entry ledger with fund segregation: maintenance fund, sinking fund, corpus fund. Every committee member can open the live income-expense statement, balance sheet, and fund balances from their phone at any time — not at the treasurer's convenience. The AGM-ready accounts package — balance sheet, income-expense statement, receipts-and-payments account — is generated in one click as a PDF.

THE OUTCOME

What changed

The collection rate change was the most visible outcome and the one the committee had most specifically wanted. In the first month after the auto-billing engine went live, 312 of 450 units paid within the first ten days — compared to the previous pattern where barely 280 units paid across the entire month. By month three, 423 units had paid by the due date. The remaining 27 units had the penalty automatically added to their next bill. The Secretary received twelve follow-up calls in month one — from residents asking how to pay online, not asking whether they owed money. He stopped making outbound collection calls. His estimate of time recovered: eight hours per month.

The treasurer's monopoly on the accounts was broken without drama. In the second week after go-live, the Chairperson opened the accounts dashboard on her phone while sitting in a committee meeting. She asked about the sinking fund balance. Instead of waiting for the Treasurer to look it up in Tally, she read the number off her screen. The Treasurer was initially apprehensive about the visibility — she had been the de facto custodian of the society's financial integrity and was concerned that wider access would lead to uninformed interference. In practice, the opposite happened: the committee asked fewer questions at monthly meetings because they had already reviewed the numbers themselves, and the quality of questions improved because they were comparing this month to last month rather than asking what the numbers were.

The complaint resolution transformation was the one residents noticed most. In the first month, 64 complaints were submitted through the app. Of those, 61 were closed within SLA. Three were escalated to the Secretary because the vendor did not submit a resolution photo within the deadline — in the previous system, all 64 would have been untracked. By month two, residents had started commenting in the society general WhatsApp group — which still existed for announcements — that 'at least the complaint system works.' A resident who had submitted the same lift complaint through the WhatsApp group seven times over three months submitted it once through the app and it was closed with a photo in four hours.

The gate management change had a secondary effect nobody had anticipated. Three weeks after the guard app went live, the security team identified that a domestic worker who had been coming daily as an 'expected visitor' pre-approved by a resident had been using a different name each week. The paper register would not have caught this because nobody cross-referenced names across days. The guard app's searchable entry log — queried by the security supervisor looking for a pattern — surfaced the discrepancy. The committee addressed it with the resident involved. The security supervisor, who had been sceptical of the app at first, became its most vocal internal advocate.

The amenity booking conflicts stopped immediately. On the first weekend after the booking module went live, three party hall bookings were made — on different dates, confirmed instantly, no mediation required. The WhatsApp booking group was archived by the Secretary after two weeks when it became clear nobody was posting to it anymore. The gym and sports court bookings, which had previously been informal first-come-first-serve, now had a 2-hour slot structure with digital confirmation. Two residents who had regularly argued over the cricket practice net — a seasonal fixture in the committee's conflict log — now booked their slots on the app and co-existed without incident.

The AGM in January was the committee's cleanest in six years. The Treasurer spent three hours reviewing the system-generated accounts package — checking entries, verifying fund balances against bank statements, and approving the final numbers. The PDF was sent to the printer on January 18th. The AGM was held on January 25th. Residents received the accounts package at the meeting. Three residents asked detailed questions about specific expense line items — questions they could ask because the accounts were line-item-detailed rather than summarised. The Treasurer answered them comfortably. The accounts were approved in 20 minutes. In the previous year, the approval had taken 45 minutes because residents were questioning summary figures without context. The Chairperson noted at the end of the meeting that this was the first AGM in her six years on the committee where the accounts felt like something the committee owned, rather than something the Treasurer had prepared for them.

BEFORE65% — 158 units defaulting each month

AFTER94% within 3 months — auto-billing with payment link and penalty accrual changed the default behaviour

Monthly maintenance collection rate

BEFORE3 days — treasurer manually compiling from Tally for the committee summary

AFTERReal-time — every committee member sees live income, expenses, and fund balances at any moment

Monthly accounts preparation time

BEFORE0% — all complaints on WhatsApp with no formal tracking or SLA

AFTER100% ticketed — every complaint has an assigned vendor, a deadline, and photo evidence required before closure

Complaint resolution tracking

BEFOREPaper register — no pre-approval, no resident notification, no searchable record

AFTERQR-code pre-approval for expected visitors; unexpected visitors require resident WhatsApp approval before gate opens

Gate visitor verification

BEFORE3–4 double-bookings per month resolved by committee intervention

AFTER0 — real-time availability calendar with per-unit booking limits and instant confirmation

Amenity booking conflicts (party hall, clubhouse)

BEFORE3 weeks — treasurer compiling balance sheet and I&E statement from 12 months of Tally entries

AFTER1 day — committee reviewed and approved the PDF export; printer received it same afternoon

AGM accounts package preparation

Want a system like this for your real-estate organisation?

Get a quote for Society Management ERP