Collecting varisankhya: a working system for subscriptions and arrears

Varisankhya, the monthly family subscription, is the steadiest money a mahallu has. It is also where most committee frustration lives: arrears that nobody can state precisely, families who insist they paid, collectors who each hold part of the picture in a pocket notebook. Almost none of that is a payment problem. It is a record problem, and record problems have fixes.

This is the system that works, whether the register is a book or software. None of it needs a larger committee. Most of it is deciding things once instead of renegotiating them monthly.

Fix each family's amount once, in writing

Every recurring argument about varisankhya traces back to an amount that was agreed verbally, years ago, by people no longer on the committee. Fix it: the register holds every house, and against every house the monthly amount that family agreed to pay. Families differ, and the register should say so plainly rather than pretend one rate fits everyone.

Do this and the outstanding figure becomes arithmetic. Months elapsed, times the agreed amount, minus what was received. Nobody's memory is involved, which means nobody's memory can be disputed. If the register itself does not exist yet, start with building a mahallu register before anything else.

Let people pay any way, but land it in one register

Some families pay the collector at the door, some walk to the masjid counter, some send a bank transfer from another city or another country. Accept all of it. The one rule that keeps the books whole is that every channel ends in the same register, with the same details: date, amount, family, which months it covers, how it was paid and who received it.

The failure mode is a bank transfer that lives only in a passbook, or a door collection that lives only in a pocket notebook, waiting to be copied in later. Later is where figures die. Whatever was collected today is entered today, and each entry carries the name of the person who took the money, which protects the collector more than anyone else.

Give a receipt for every payment, every time

A receipt is the family's copy of your record, and it is what settles the "we already paid" conversation two years from now, in your favour or theirs, but settled either way. Serial number, amount, the months covered, the receiver's name. If receipts come from a system, a way for the family to check their own payment history removes the most common phone call a treasurer takes.

Produce the arrears list monthly, from the register

Once amounts are fixed and payments are entered promptly, the arrears list is a report, not a project. Run it on a fixed date each month: every family, agreed amount, months outstanding, amount outstanding. The committee sees the whole picture in one page, and the follow-up work can be divided sensibly instead of falling on whoever remembers.

Follow up early, and follow up quietly

A reminder in the first or second week of a missed month is a courtesy, and it is received as one. The same message after eleven months is a demand, and it arrives on top of an amount that has grown embarrassing to pay at once. Early follow-up is not strictness. It is what keeps the relationship easy and the amounts small.

• First missed month: a short message to the family, sent by a person, not read out anywhere. Committee-triggered WhatsApp works well for this; see follow-ups for how to run it from the arrears list itself.
• A few months in: a visit rather than a message, ideally by someone the family knows. Most long arrears are not refusals. They are a changed circumstance nobody told the committee about.
• Long-standing arrears: agree a plan, in writing, in the register: instalments alongside the current month, or a committee-approved waiver of part or all of it. An arrear that will never realistically be paid should be formally settled, not carried forever as a number that shames both sides.

And one rule above all of it: arrears are never announced. No list on a noticeboard, no names in a general body meeting. The moment arrears become public, families stop coming to the committee with their difficulties, and collections get worse, not better.

Handle advances and part-payments without fudging

A family paying six months ahead of Ramadan travel, or paying half a month now and half later, is normal life. The register has to represent both honestly: an advance is credited to the specific future months it covers, and a part-payment leaves the balance of that month visibly due. Rounding these into lump sums is how a register drifts from reality one small kindness at a time.

When the collector changes

Collection routes change hands more often than committees do. The handover is the same principle as the treasurer's: the incoming collector gets the register position for their houses, the outstanding per family, and any agreed plans, in writing. What must not transfer is a pocket notebook that only its author can read. The broader handover discipline is covered in keeping mahallu and masjid accounts.

Where software earns its place

Everything above can be done on paper, and a small mahallu with one collector can genuinely run it that way. The paper version strains when several people collect at once, when families pay through several channels, or when the arrears list takes an evening to compute instead of a click. InflowBooks, which we make, holds the register of houses and agreed subscriptions, records collections against the months they cover with the collector's name frozen on each entry, produces the outstanding list on demand, and runs committee-triggered WhatsApp follow-ups from that list. The documentation shows all of it before you commit to anything.

Common questions