Month-end for donation income: a reconciliation routine your treasurer can actually keep

Why "just do it at year-end" doesn't work

The pain is familiar: it's the 3rd of the month, the treasurer has a bank statement, a CHIP settlement report, a stack of bank-in slips and a spreadsheet of cash counted by whoever was on duty that Sunday — and none of the totals agree. Left until the annual audit, this becomes weeks of archaeology instead of a monthly hour.

Neither Act names "monthly close," but both point the same way. A society's annual return to the Registrar of Societies must include "the accounts of the last financial year of the society, together with a balance sheet showing the financial position at the close of the last financial year" ^[1]. A company limited by guarantee (CLBG) has a sharper version: under section 245 of the Companies Act 2016, a company and its directors must keep accounting records that "sufficiently explain the transactions and financial position of the company," enter transactions within sixty days, and retain the records for seven years ^[2] — contravention carries a fine of up to RM500,000, up to three years' imprisonment, or both ^{[2, s245(9)]}.

A CLBG that only "explains" January's transactions in November has arguably already missed that 60-day window. And no treasurer wants to discover in March that eleven months of cash and bank-ins were never matched to anything. Monthly reconciliation is how you keep either duty true all year, instead of reconstructing it once.

Practical tips

• Put reconciliation and month-end close on the calendar as a fixed date each month, not "whenever someone has time."
• Treat the annual return and the audit as the output of twelve tidy months, not a separate project.

Gateway settlements: one lump sum, days later, minus fees

The pain: a donor gives RM100 on your website on the 28th. The money that actually lands in your bank account on the 3rd of next month is part of a lump sum — say RM4,238.50 — covering several days of donations, net of the gateway's processing fees. Nothing on the bank statement says "RM100 from that donor."

There's no statutory rule on gross-versus-net recording for a gateway specifically. If your organisation is a CLBG, the same section 245 test applies directly: a bank line showing one net, fee-deducted lump sum doesn't "sufficiently explain" the individual gifts that produced it ^[2]. A society isn't bound by section 245 at all — but the same logic still holds as plain good practice, and it's what your own accounts need to hold up at your annual general meeting.

Practical tips

• Record each donation at its gross amount, and book the gateway's fee as a separate expense line — never net the fee off the donation, or your donation report understates what donors gave.
• Reconcile against the gateway's own settlement report, not the bank line alone — it shows which transactions make up the payout, where the bank statement shows only the total.
• Expect a gateway donation to sit unmatched until a settlement report covering its date exists; pull settlement data directly where your tools support it, rather than re-typing a PDF by hand.

Bank-ins and DuitNow transfers with no name attached

The pain: RM500 arrives by DuitNow or interbank GIRO with a reference like "IBG TRF 88213" and nothing else. Was it a donor's pledge instalment, a bank-in for last week's offering, or something unrelated to donations entirely?

Neither Act specifies how to identify an anonymous transfer — this is operational hygiene, not a filing requirement.

Practical tips

• Ask donors who bank in directly to put their name or a reference in the transfer description, and publicise that ask on your donation page.
• When a transfer can't be matched with confidence — the amount could belong to more than one donation, or there's no reference at all — don't guess. A wrong match creates a wrong receipt, which is worse than a slow one.
• Chase the reference with your bank before asking your donor base at large. Keep a written policy for a deposit still unidentified after 30 days — who chases it, and when it goes to the committee rather than staying with the treasurer alone.

Duplicate entries: the online gift that gets recorded twice

The pain: a donor gives online, then also transfers separately by mistake, or a volunteer records a bank-in without checking whether the online system already caught the same gift. The same RM200 counts twice — and if nobody catches it before the annual return, your accounts overstate income for the year.

This is exactly why reconciliation happens before new manual entries go into the ledger, not after: matching a bank line to a donation you already hold is what surfaces "this is already here" before it becomes a duplicate. A duplicate already recorded and marked complete is corrected by a void with a stated reason, never a silent deletion — deleting the trace makes it impossible for an auditor to see that a correction happened at all.

Practical tip: before recording any manual bank-in or cash gift, search your existing records by donor and amount for that date — a five-second check that catches most duplicates before they exist.

The donation box: two counters, late banking, one ledger entry

The pain: a temple's or clan association's donation box is opened, counted by whoever's available, and banked whenever someone next visits the bank — sometimes weeks later. Nobody but the counter can say the total is right.

Segregation of duties is standard financial-control practice, not a Societies Act or Companies Act clause — but it is exactly what makes an accounting record capable of being "conveniently and properly audited," the second limb of the Companies Act's own test ^{[2, s245(1)(b)]}. A single person's count, banked whenever convenient, produces a total nobody else can verify against anything.

Practical tips

• Two people count every donation box together and sign the count sheet together; neither is the person who later reconciles or approves the entry.
• Bank the cash as soon as practical after counting, and record the count date and the bank date separately — if they're more than a few days apart, note why so it doesn't look unexplained later.

Refunds, reversals, and the void that corrects your books (not the bank)

The pain: a card payment is reversed by the gateway days after the receipt already went out, or a completed donation turns out to be against the wrong campaign. Either way, the month's totals need correcting — and correcting them casually is how a small mistake becomes a bigger one.

Voiding a donation corrects your own record; it never moves money, because sending money back happens at the bank or the gateway, not inside your books. A gateway reversal that happens after a receipt has gone out is a different animal from a data-entry mistake, and the two shouldn't be handled the same way without someone actually checking the money is genuinely gone.

Practical tips

• Require a written reason for every void — "why" is what lets someone else understand the correction six months later.
• Keep the person who requests a void separate from the person who approves it, especially for anything touching a donor's receipt, and don't treat every reversed or unsettled gateway payment as a void by default — confirm against your own bank or gateway record first.

Unidentified receipts: suspense is a queue, not a drawer

The pain: money that clearly came in but nobody can yet tie to a donor or campaign. Parked in "suspense," it's easy to forget until an auditor asks what it is and finds it's eight months old.

Nothing in either Act names a "suspense account" or sets a deadline for clearing one. A society's annual return must still include accounts and a balance sheet for the year ^[1], and a CLBG's accounting records must "sufficiently explain" every transaction ^[2] — an unexplained line sitting in suspense for months is precisely what neither lets you present as a finished account.

Practical tip: review every unresolved suspense item as part of the same routine as reconciliation, not a separate, forgotten list — and set an internal target (30 days is common) after which an unresolved item goes to the committee for a decision rather than staying in limbo.

Signing a month off — and what happens when someone edits it later

The pain: the treasurer reconciles, signs off, reports to the committee — and three weeks later notices a backdated donation quietly changed last month's total.

"Closing the books" sounds more final than it usually is. Signing off a month is a record that you reviewed it and it reconciled — a checkpoint, not a vault. A later entry dated into that month is normal (catching up a backlog happens everywhere), and the honest answer to "can anything still change a closed month?" is yes. What matters is whether the change is visible: every write to a signed-off month should leave a trace naming who made it and when — "closed" means reviewed and traceable, not frozen.

Practical tip: when you report a closed month to the committee, note that it was reconciled on a given date, and check the following month for any adjustment that landed inside it. Revisiting a signed-off month should be a deliberate, visible decision — not a quiet backdated edit nobody else sees.

Why a clean month matters beyond your own books

A month that reconciles cleanly is also what a downstream process depends on. If your organisation issues e-Invoices, LHDN's monthly consolidated filing bundles every donation without a named buyer's tax number into one submission early each month (see Do we need an e-Invoice for a donation?). A donation still unmatched, undated or duplicated when that submission runs either files wrong or gets stranded outside the window — and untangling a filed e-Invoice is far more work than untangling a reconciliation line.

What this means for your organisation

1. Fix a monthly close date and treat it as non-negotiable, not "when there's time."
2. Pull both your bank statement and your gateway's settlement report before you start matching.
3. Record gateway donations gross, with fees booked as a separate expense line.
4. Search before you record any manual bank-in or cash entry, to catch a duplicate before it exists.
5. Count every donation box with two people, and keep the counter, recorder and approver separate wherever your team size allows.
6. Investigate every unmatched or unidentified line before the month closes, not after.
7. Void, don't delete — a written reason and a second person's sign-off, for anything touching a receipt or donor record.
8. Sign the month off with a note, and check the following month for any adjustment landed inside a period you already reported.
9. Keep records long enough — a CLBG's are a statutory seven years under the Companies Act ^{[2, s245(3)]}; see How long to keep donation records for the fuller picture.