Skip to content
Cheqify.app — Cheque Printing Software
Back to Blog

Cheque handling for housing societies and RWAs — the treasurer's guide (2026)

October 12, 2026Cheqify Team9 min read
Cheque handling for housing societies and RWAs — the treasurer's guide (2026)

Somewhere in your city tonight, a volunteer treasurer is sitting at a dining table with a rubber-banded stack of cheques, an open register, and a cup of tea going cold. Two hundred and fourteen flats. Maintenance billed quarterly at ₹4,800. A hundred and sixty cheques in hand, forty of them post-dated, three from members who have bounced before — and an audit at the end of the year where every rupee will need a paper trail.

Nobody trained this person. The treasurer of a housing society or RWA is an unpaid volunteer with a day job, elected at an AGM, handed a cheque book and a half-filled register by someone already halfway out the door. The bank, meanwhile, treats the society like any other account holder. Full formality. Zero allowances.

This is the manual nobody hands over. One caution before anything else: cooperative housing societies are governed by state legislation, and the detail — bye-laws, recovery procedures, audit requirements — varies from state to state. RWAs are often registered under different laws again. Everything below is operational practice that holds everywhere; for anything statutory, your society's registered bye-laws and your state's Act are the authority, not a blog post.

Two flows, one tired volunteer

Every society's cheque work splits into two streams that behave nothing alike. Incoming: maintenance cheques from members — high volume, small amounts, arriving in bursts around billing dates, some post-dated, a few destined to bounce. Outgoing: the society's own payments — security agency, housekeeping, lift AMC, common-area electricity, the auditor's fee. Lower volume, larger amounts, and every single one needs two signatures and a reason on record.

Treat them as one pile and you'll drown by the second quarter. Treat them as two systems — a collection register for what comes in, an issue register for what goes out — and the whole year runs on rails. That's the entire architecture. Everything below is detail.

Incoming: the maintenance cheque flow

A maintenance cheque is easy to receive and remarkably easy to lose track of. So the rule is: three things happen before that cheque leaves your hands. Every time. No exceptions.

One — record it. Flat number, member name, cheque number, bank, date, amount: one line in the collection register. The flat number is the key field; six months from now, nobody remembers which Mr. Shah gave which HDFC cheque. Two — issue a stamped receipt with the cheque number written on it. That receipt is the member's proof and your future peace treaty (more on that later). Three — into the deposit batch. Not into a drawer.

Then deposit on a fixed rhythm — say every Tuesday and Friday — the whole batch in one deposit run with a listed slip, so the register, the slip, and the bank statement can be matched line by line. Cheques left lying around go stale: a leaf is valid for only three months from its date, and a society that deposits "whenever someone is free" will eventually find dead paper in the drawer. Annoying? Yes. Also completely avoidable with two calendar entries.

The PDC pile

Many societies collect the year in advance: four post-dated cheques from each flat, one per quarter. On a 200-flat society, that's a cupboard holding 600-odd post-dated cheques — real money in paper form, and it deserves better than a shoebox.

Keep PDCs in a dated folder, sorted by presentation month, with a schedule sheet on top: flat, cheque number, date, amount. At the start of each month, pull that month's cheques, run them through the same record–receipt–deposit flow, and tick the schedule. Present on or after the written date, never before — a PDC presented early simply comes back. And when a member asks you to hold a cheque past its date ("salary issue this month, please deposit after the 15th"), write it on the schedule and get the request in writing, even as a WhatsApp message. Memory is not a system.

When a maintenance cheque bounces

It will happen. Across 200 flats, a few returns a year is normal arithmetic, not a scandal.

The sequence: the bank returns the cheque with a memo naming the reason — funds insufficient, signature mismatch, a closed or frozen account — and debits the society a return charge. The first move is administrative, not legal. Inform the member, pass the bank's charge on to them as your bye-laws allow, and re-present the cheque if the reason was funds and the member asks for it. Most cases end right there, with mild embarrassment and a replacement cheque.

For repeat offenders, societies have escalation routes: late-payment interest as the bye-laws provide, dues shown against the flat in the AGM accounts, and formal recovery mechanisms under the state cooperative framework — the exact procedure differs by state, which is precisely where your Act and your local housing federation come in. Section 138 of the NI Act — criminal prosecution for a bounced cheque — exists as the outer weapon, but for a neighbour who missed one quarter, it's rarely the first tool anyone reaches for. This is general information, not legal advice; for actual recovery action, sit with the society's lawyer or the federation first.

Outgoing: the society's own cheques

Now the other direction. A mid-sized society writes 15–30 cheques a month: the security agency, the housekeeping contractor, the lift AMC, common-area electricity, water tankers in a bad summer, property tax, insurance, the plumber who fixed the terrace leak, the auditor.

Every outgoing cheque gets a line in the issue register before it is signed: cheque number, date, payee, amount, purpose, and the bill or committee-resolution reference that authorises it. A signed cheque with no register line — that's how audit queries are born. And because most of these payments repeat monthly to the same payees, they make a natural batch job: prepare the month's cheques in one sitting, sign in one sitting, record in one sitting. One evening a month instead of a running trickle.

Who signs — the mandate is the whole game

A society's account is operated jointly — typically any two among chairman, secretary and treasurer, exactly as named in a managing committee resolution the bank holds on file, with specimen signatures. No volunteer signs alone. And the bank matches signatures against its file, not against who currently holds the post.

Read that last sentence again, because it is the number-one operational failure at every handover: the bank does not know your AGM happened. Until the new committee's resolution and specimen signatures reach the branch, the old mandate stands — and a cheque signed by the shiny new treasurer is, to the bank, signed by a stranger.

SituationWho signsWhat the bank needs on file
Routine vendor paymentAny two authorised signatories (commonly secretary + treasurer)Current committee resolution + specimen signatures
Large or unusual paymentThe same two signatures, backed by a specific committee resolutionThe standing mandate; the resolution lives in your minute book
New committee elected at the AGMOld signatories, until the mandate is updatedFresh resolution naming new signatories + specimens + KYC
A signatory resigns mid-termRemaining/replacement signatories per the updated mandateResolution recording the change + the replacement's specimen signature
Fixed deposits, account changesUsually all named signatoriesA transaction-specific resolution

Formats vary by bank; a few requirements vary by state. The principle doesn't: update the mandate before the next cheque, not after the first return.

The audit file — what the auditor will actually ask for

Societies are audited every year (a statutory requirement under cooperative law in most states — your state's Act sets the detail). The auditor's cheque-related list is predictable, which means you can build it all year instead of reconstructing it in a March panic:

  • The collection register, matched to the receipt books — every maintenance cheque tied to a flat and a receipt number.
  • The issue register — every outgoing cheque tied to a purpose and an authorisation.
  • Monthly bank reconciliation — register versus statement, with every difference explained.
  • Unpresented cheques at year end — issued but not yet cleared; the classic reconciliation item.
  • The PDC schedule — cheques in hand are neither income received nor money in the bank, and the auditor will want the list.
  • Cancelled leaves — kept and defaced, never torn out and thrown away, so the cheque-number sequence has no unexplained holes.

Do the reconciliation monthly and audit season becomes an afternoon. Skip it until year end and it becomes the reason treasurers refuse a second term.

The disputes a good record ends

"I gave my cheque in March." Receipt number 4127, register line 214, deposited on the 9th — argument over in one minute. "The society never paid the lift company." Issue register: cheque 001482, cleared on the 21st. A society runs on neighbourly trust, and nothing preserves neighbourly trust like a record that makes arguments unnecessary.

A society's cheque book outlives every committee that signs it. Members move, signatories change, arguments fade — the register is the only witness that stays, and it is the one thing the auditor, the bank and the annoyed neighbour all agree to trust.

Handover — the checklist for the next committee

When the committee changes, these move — physically and formally, against a signed handover note:

  1. Unused cheque books, with leaf counts written down and verified.
  2. Both registers, receipt books (used and blank), and the cancelled-leaf file.
  3. The PDC folder, with its schedule current.
  4. The list of unpresented cheques and any pending bounce cases, each with its status.
  5. The bank mandate update — new resolution, specimen signatures, KYC — submitted before the new committee signs anything. Plus the branch contact who actually processes it.

Half an hour of ceremony that saves the next volunteer six months of archaeology.

Stop hand-writing them

Here's the quiet upgrade almost no society has made. A committee writing 25 cheques a month hand-writes 300 a year — payee, date, figures, amount in words, twice — and then copies each one into the register by hand again. Two chances to make an error per cheque, and the record is a second job.

Printing the society's cheques on the bank's own leaves collapses the two jobs into one. Cheqify prints on 300+ Indian bank layouts, writes the amount in words automatically so words and figures can never disagree, and — the part built for treasurers — creates the record as a side effect: every cheque logged at issue and tracked to clearance, which is the issue register the auditor asks for. The joint signatures still go on by hand, as they should. Everything else stops depending on a volunteer's evening.

The society still runs on trust. The paperwork just stops running on memory.

Society cheques, printed and tracked. Print the society's cheques through Cheqify on 300+ Indian bank layouts — amount in words automatic, two-signatory discipline intact, and an issue-to-clearance record built as you go. 100% free, which suits a society's budget exactly. Start at app.cheqify.app.

Frequently Asked Questions

Explore More from Cheqify

Related Posts