Society maintenance collection

Aangan: society maintenance that collects itself

A volunteer treasurer should not have to match bank credits to flats by hand every month.

View live productBook a consultation
Aangan committee dashboard showing a two-wing building with each flat coloured paid, due or overdue, a collection ring and a list of decisions waiting for the treasurer
Built for
Housing societies, apartment associations and RWAs
Channels
UPI for payment, WhatsApp for bills and receipts
Published pricing
Free up to 20 flats, then ₹6 per flat a month

The problem in the real world

In most small housing societies the treasurer is a volunteer with a day job. Every month they post in the WhatsApp group, wait, and then read the society's bank statement line by line, trying to work out which credit came from which flat.

UPI makes paying easy and reconciling hard. A credit carries an amount, a payer name and sometimes a note. It rarely carries the flat number. The payer may be a spouse, a tenant or a name abbreviated by the bank.

Then come the arguments. Late fees depend on a bylaw nobody quotes the same way twice, and the receipt book is filled in when someone remembers. The money is there. The record is what breaks.

The hard part

Matching a UPI credit to the right flat

The rule: A payment should land on the flat that owes it, even when the payer never says which flat that is.

Edge cases

  • The credit arrives with no flat mentioned at all.
  • The payer name is shortened (RAHUL D) while the resident on record is longer (Rahul Dsouza).
  • Several flats owe similar amounts in the same cycle, so amount alone proves nothing.

How it is handled

Aangan compares the payer name and the amount against the residents and dues on record, then proposes a flat. In the demo workspace the proposal appears as a decision for the treasurer, with the reason written out ("The amount and name match B-404") and a single Match button. The software narrows the search, and a person confirms the doubtful ones. We have not published matching thresholds because we did not review the matching code for this page.

From bank credit to receipt

  1. A credit lands

    ₹2,900 from RAHUL D. No flat in the note.

  2. Compare the payer name

    Checked against the residents on record.

  3. Compare the amount

    Checked against what each flat owes this cycle.

  4. Name and amount point to one flat

    Aangan proposes B-404 and says why.

  5. Treasurer taps Match

    One decision instead of a statement search.

  6. Receipt goes out on WhatsApp

    The flat turns green on the building view.

Aangan decision queue listing a remind-all action, two unmatched UPI credits each with a suggested flat, and cash held by the guard
From the product's demo workspace. Names and figures are sample data.

Late fees that follow the bylaws and explain themselves

The rule: A late fee is added on the day the society's own rule says, and the resident is told why.

Edge cases

  • Each society writes its own bylaw, so the rule has to be set per society, not hard-coded.
  • A resident who pays before the cut-off must never receive a fee or a firm reminder.
  • Long-pending flats need a human conversation, so they escalate to the committee instead of generating more messages.

How it is handled

The rule is set once by the committee. On the seventh day after the due date the firm-reminder routine adds the fee the bylaws allow and sends a message that states the reason, which removes the awkward call from the committee. At thirty days the routine stops messaging the resident and sends the committee a short list of long-pending flats.

One due, from bill to settlement

  1. Billed

    1st of the month

  2. Nudged

    3 days before due

  3. Due today

    Pay button in the message

  4. Late fee added

    7 days after due, with the reason

  5. With the committee

    30 days after due

  • Exit: PaidAt any point the flat leaves the chain. Reminders skip anyone who already paid.

Billing and reminders without a person pressing send

The rule: Every flat is billed on the 1st and nobody who has already paid is chased.

Edge cases

  • Bills must price each flat from its own area, not a flat rate for the whole building.
  • A receipt must exist the moment money lands, not at month end.
  • Residents who keep paying late should be offered a way to stop it happening again.

How it is handled

Autopilot runs a fixed set of routines on a calendar. Each routine states what it does and when, and can be switched off. The demo shows the last run time for each one. Message volume is a plan limit: the free Starter plan includes 100 WhatsApp messages a month and the Society plan removes that cap.

A month on autopilot

  1. 1st, 9:00 am

    Bills raised

    Each flat priced by area, with a pay link.

  2. 5th, 7:00 pm

    Transparency report

    Money in, money out and the balance, to every flat.

  3. Due minus 3

    Gentle reminder

    Skips anyone who already paid.

  4. Due day

    Due-day nudge

    Exact amount and a pay button.

  5. Due plus 7

    Firm reminder and fee

    Fee added, reason stated.

  6. Every payment

    Signed receipt

    PDF receipt on WhatsApp as money lands.

Aangan autopilot screen with a five-step line from bill raised to committee escalation and a list of scheduled routines with their last run times
From the product's demo workspace. Names and figures are sample data.

A ledger the committee and the auditor can trust

The rule: Every rupee in or out is written down once, with a receipt number, and can be found again.

Edge cases

  • Payments arrive by UPI, card and cash, and cash sits with a person until it reaches the bank.
  • Owners and tenants are different people for one flat, and the tenant may be the one paying.
  • An auditor will ask for the whole ledger, not a screenshot of it.

How it is handled

Each entry carries a receipt number, the flat, the payment mode and the time. Receipt numbers in the demo follow a society, financial year and running-number pattern. The ledger is searchable by flat, vendor or UTR and exports for the auditor. Cash collected by staff stays a visible item on the dashboard ("with the guard") until someone marks it deposited. The Federation plan adds Tally export and GST invoices.

What one ledger entry carries

  • Receipt number

    Example from the demo
    GR/26-27/0170
    Why it matters
    Society, financial year and a running count

  • Flat and payer

    Example from the demo
    A-302, Sandeep Chauhan
    Why it matters
    Ties the money to a home and a person

  • Mode and time

    Example from the demo
    UPI, 9:01 pm
    Why it matters
    UPI, card and cash are told apart

  • Split

    Example from the demo
    Maintenance and a festival charge
    Why it matters
    One payment can settle two dues

  • Delivery

    Example from the demo
    WhatsApp, read
    Why it matters
    Shows the resident actually got the receipt

Names and numbers are sample data from the demo workspace.

Aangan ledger with a closing balance, money in and out for the month, an export for the auditor button and a day of receipts with their numbers
From the product's demo workspace. Names and figures are sample data.

How it fits together

  • UPI payments

    Straight to the society's own account

  • Society rules

    Flat areas, charges, bylaw late fees

  • Staff entries

    Cash collected, expense bills by photo

Aangan

  • Payment matching
  • Dues and late fees
  • Autopilot scheduler
  • Ledger

  • WhatsApp

    Bills, reminders, receipts, monthly report

  • Signed PDF receipts

    One per payment

  • Auditor export

    Tally export and GST invoices on Federation

What this means for your business

  • Matching bank credits to invoices

    Name-and-amount matching with a person confirming the doubtful cases is the same approach as reconciling bank receipts against open invoices in a custom ERP, for Indian businesses and for UAE businesses reconciling bank transfers.

  • Rule-driven fees and penalties

    A late fee that is configured per society is the same problem as per-customer credit terms, penalties and early-payment discounts in billing software. The rule is data the business owns, not code only we can change.

  • Automation that knows when to stop

    Reminders that skip anyone who already paid, and routines that hand over to a human at a set point, are what make automated invoicing and collections safe enough to leave running.

Tech notes
  • Observed from the running product: a Next.js application on Vercel, with a light and dark theme and a Ctrl+K command search for flats and actions.
  • WhatsApp is the delivery channel for bills, reminders, receipts and the monthly report. Payment is UPI directly to the society's account, with no convenience fee on UPI.
  • Not reviewed: matching thresholds, late-fee rule types, job scheduling and duplicate-send protection. We have left those out rather than guess.
  • Screens are from the product's demo workspace (Gulmohar Residency). All names, flats and amounts are sample data.

Have logic this messy in your operations? Let's talk.

Book a consultationContact us