Custom Housing Society Management Software

Description

Solution Housing society management software

WavX builds housing society software for RWAs, builders and facility-management companies: maintenance billing and collection, receipts and defaulter tracking, a gate and visitor log, complaints, notices and amenity booking. A billing-office system for one society plans at about ₹3 to ₹4.4 lakh on the WavX estimator. Most single societies are better served by a ready-made society app; custom pays off for builders and managers running many.

Tell us what you need built Last updated 2 October 2026

What WavX builds

WavX builds society management software as a custom web application for the managing committee or the facility office, with a resident app and a guard app where they are needed. It is one of the custom software and business systems WavX offers, and it sits alongside the real estate work.

Three kinds of buyer usually ask for it, and they need quite different things:

A single RWA or co-operative housing society. The pain is collecting maintenance, chasing defaulters and keeping the accounts clean at committee handover.

A builder who hands over several projects and wants residents on one branded platform from possession day, with snag lists and handover records before the RWA takes charge.

A facility-management company running housekeeping, security and maintenance across many societies, which needs one back office, per-society books and per-society staff.

The first is usually better served by a ready-made app. The second and third are where custom software earns its cost.

The modules

Module

What it does

First release?

Flats, owners and tenants

Unit register, owner and tenant records, parking slots, move-in and move-out

Yes

Maintenance billing

Per-flat charges by area or flat type, sinking and repair funds, water and power-backup charges, late fees

Collection and receipts

UPI, card and net-banking payment, automatic receipts, cheque and cash entry by the office

Defaulters and reminders

Outstanding by flat, reminders on WhatsApp or SMS, notice letters

Accounts and reports

Collection register, fund balances, expense entry, export for the auditor or Tally

Complaints and helpdesk

Plumbing, electrical and common-area tickets, assigned to staff, with status for the resident

Usually

Notices and polls

Circulars, AGM notices, simple polls with one vote per flat

Gate and visitor log

Guest pre-approval, delivery and cab entries, domestic staff attendance, vehicle log

Gated societies

Amenity booking

Clubhouse, hall and court slots, deposits and cancellation rules

If amenities are charged

Resident app

Bills, payment, complaints, visitor approvals and notices on the phone

Second release, often

Multi-society back office

One login across societies, per-society books, staff and vendor management

Builders and facility managers

Amenity booking is the same slot-and-deposit problem covered on the booking platform development page.

Billing: where society software succeeds or fails

Maintenance billing looks simple and is not. The rules differ from society to society and change by AGM resolution. The software has to handle, at least:

Charge basis. Per square foot, per flat type, or a flat amount, often with different rates for owners and tenants, or for occupied and vacant flats.

Funds. Sinking fund, repair fund and other heads that must be shown separately in the accounts.

Pass-through charges. Water, power backup and common electricity split by meter or by share.

Interest and late fees as the bye-laws set them, with the committee able to waive a charge with a recorded reason.

Part payments and advances , allocated against the oldest dues first unless the committee decides otherwise.

GST, where it applies. The government's February 2018 release says GST is payable where a member's monthly contribution exceeds ₹7,500 and the RWA's annual turnover is ₹20 lakh or more. A large township can cross both lines; most small societies do not. The software should let your CA set this rather than hard-coding it.

If a ready-made app cannot express your society's rules without a spreadsheet beside it, that is a sign it is the wrong product, not a reason to keep the spreadsheet.

What builders and facility managers need on top

A platform that serves many societies is a different product from one society's app, and the difference is mostly in the back office.

Need

Single society

Builder or facility manager

Accounts

One set of books

Separate books per society, consolidated reports for the company

Staff

A few guards and a manager

Staff rostered across sites, attendance per site, vendor contracts

Handover

Not applicable

Snag lists per flat, possession records, and a clean transfer of the society's data to the elected RWA

Branding

The society's name

The builder's or manager's brand across every site

Access

Committee and residents

Company admins, site managers, committees and residents, each seeing only their part

The handover row is the one most often missed. When the RWA takes charge it should receive its own data, in a form it can use, without depending on the builder's account.

Collections and reminders

Online collection runs through a payment gateway, with each payment matched to the flat and the bill automatically. For residents who want to pay without thinking about it, a recurring UPI Autopay mandate debits them each cycle within RBI's limits and notice rules. Reminders go out on the WhatsApp Business API from the society's own number, not from the treasurer's phone.

Visitor data is personal data

A gate log holds names, phone numbers, vehicle numbers and often photos of every visitor and domestic worker. Under the Digital Personal Data Protection Act and the Rules notified on 14 November 2025, the society or its manager is responsible for that data. The government's release on the Rules describes clear consent notices, security safeguards and prompt notice to people affected by a breach. In practice:

Collect only what the guard needs to let someone in.

Decide how long visitor entries and photos are kept, and delete them after that.

Give guards a login each, so the log shows who approved an entry.

Keep the data in an account the society controls.

The Rules have an 18-month phased timeline; check the current position with your adviser.

What it costs to plan for

Planning ranges from the WavX software cost estimator , with standard design selected. A range is the subtotal minus 15% to plus 25%. They are not quotes.

Configuration

Estimator settings

Subtotal

Planning range

Estimator timeline

Billing office for one society: billing, online collection, receipts, defaulters

Internal tool ₹2,00,000 + auth and roles + payments; small scale

₹3,50,000

₹2,97,500 to ₹4,37,500

4–8 weeks

Society platform with resident app and gate approvals

Custom web application ₹4,50,000 + auth and roles + payments + real-time + companion mobile app + reporting; small scale

₹9,20,000

₹7,82,000 to ₹11,50,000

14–22 weeks

Multi-society platform for a builder or facility manager

SaaS product ₹7,00,000 + auth, payments, real-time, mobile app, admin panel, analytics dashboard, reporting; growing scale (×1.3)

₹18,72,000

₹15,91,200 to ₹23,40,000

22+ weeks

Running costs are separate: hosting, WhatsApp and SMS charges, payment gateway fees, and maintenance, which WavX plans at 15–25% of build cost per year . The society software cost guide discusses per-flat subscriptions against custom builds in more detail.

How the build runs

Rules first. Collect the bye-laws, the last AGM resolutions on charges, a year of bills and the auditor's last report. Billing is designed from these.

Opening balances. Every flat's outstanding and advance, agreed with the treasurer before go-live. Most disputes after launch come from this step being rushed.

First release. Billing, collection, receipts and defaulters, run for one full billing cycle alongside the old method.

Second release. Complaints, notices, amenity booking, then the gate and resident apps.

Handover. Admin training for the committee and office, and written instructions that survive the next committee election.

When a ready-made society app is the better buy

Do not commission a custom build if:

You are one society with standard billing. A ready-made app is cheaper, starts at once, and its vendor handles updates.

Nobody will own the system after the current committee. Custom software needs a named owner. Committees change; a vendor's product does not depend on who was elected.

The real problem is defaulters who will not pay. Software makes the dues visible and the reminders automatic. It does not settle disputes.

Custom software is the stronger choice for a builder or facility manager running many societies, for a township whose billing the products cannot express, or for anyone who wants the platform and the resident relationship to be their own.

What to have ready before asking for a quote

Number of societies, towers and flats, and whether tenants are billed separately.

The bye-laws or resolutions that set charges, funds and late fees.

Two or three recent bills and the collection register.

How visitors and staff are logged at the gate today.

Which systems it must talk to: a payment gateway, Tally or the auditor's format, WhatsApp.

Frequently asked questions

How much does custom society management software cost?

On the WavX software cost estimator, a billing-office system for one society plans at roughly ₹2,97,500 to ₹4,37,500, and a resident app with gate approvals at ₹7,82,000 to ₹11,50,000. A multi-society platform for a builder or facility manager plans far higher. These are planning ranges, not quotes.

Is it worth an RWA building its own app?

For a single society, usually not. Ready-made society apps cover billing, visitors and complaints for a per-flat fee and are maintained by their vendor. Custom software makes sense for builders, facility-management companies and large townships that want one platform across many societies, their own brand, or billing rules the products cannot handle.

Does maintenance billing need GST?

It depends on the amount per member and the RWA's turnover. The government's February 2018 release says GST applies where the contribution exceeds ₹7,500 per month per member and the RWA's annual turnover is ₹20 lakh or more. The software should handle both cases; your CA decides which applies.

Can residents pay maintenance automatically every month?

Yes. A recurring UPI mandate through a payment gateway lets a resident approve once and be debited each cycle, within the limits and notice rules RBI sets. We cover how that works on our UPI Autopay page.

Who owns the residents' data?

The society or the company running it, not WavX. The database sits in a cloud account in your name and your company owns 100% of the code we ship. Visitor photos and phone numbers are personal data, so retention rules should be set before launch.

Sources

PIB: GST Council recommends granting relief from GST on services provided by RWAs to their members (7 February 2018) · read 2 October 2026

PIB: Government notifies DPDP Rules to empower citizens and protect privacy (14 November 2025) · read 2 October 2026

Related

Solutions by business type

Razorpay integration

Build or buy calculator

Mobile app development

Build your own software — your way, your pricing.

WavX Solutions is here to create your own software in a fully custom way, built exactly how you work — with a pricing model that fits your business. Connect now and let's build it.

Contact Now helpwavx@gmail.com