Collecting dues by bank transfer and QRIS without chasing everyone

Most Indonesian membership organisations collect dues the same way: a bank account number in the group chat, and a hope that people transfer. It is cheap, everybody knows how to do it, and there are no gateway fees eating a percentage of a small fee. It is also completely silent - your bank tells you money arrived, and almost nothing about who sent it or what it was for.

That silence is where the treasurer's evenings go. This piece is about keeping the convenience of transfer while getting rid of the detective work.

Why a transfer is hard to attribute

The problem is structural rather than anyone's fault. A transfer arrives with an amount, a timestamp, and a sender name that may be a nickname, a spouse's account, a parent's account, or an abbreviation the bank truncated. Members frequently pay a slightly different amount because they rounded, or they paid for a friend as well, or they included an event fee in the same transfer without mentioning it.

So the treasurer is left holding a bank statement with forty lines and a member list with a hundred and twenty names, trying to make the two meet. Do this every month and it is not a small job, and it is the single most common reason a volunteer treasurer resigns.

The unique amount trick

The most effective fix costs nothing and needs no software. Give each member a unique payable amount by adding their member number to the fee: member 41 pays Rp 250.041, member 117 pays Rp 250.117. Now the amount itself identifies the payer, and reconciliation goes from detective work to matching numbers.

It works because the extra rupiah are trivially small, so nobody minds, and because it survives all the real-world messiness - it does not matter whose account the money came from, or that they forgot the reference, because the amount carries the identity.

Two cautions. Tell members plainly why the amount is odd, or a helpful person will round it to 250.000 to be tidy. And keep the suffix short enough that the total still reads as the price; if your fee is Rp 50.000 and the suffix is 117, the number starts looking strange.

References, and why they only half work

The obvious alternative is asking members to put their name or member number in the transfer description. It helps, and you should ask for it, but do not build your process on it. Some banking apps hide the field, some members skip it, some type something meaningful only to them, and the field is sometimes truncated by the time it reaches your statement.

Treat the reference as a useful bonus and the amount as the reliable identifier. If you get both, reconciliation is trivial. If you get only the reference, you will still be chasing a handful of payments every cycle.

Where QRIS fits

QRIS solves a different problem: it removes the typing. A member scans, the amount is already filled in, and there is no chance of a mistyped account number or a wrong figure. For payments taken at an event - a ticket, a subscription paid at the door, a donation - it is much better than reading out an account number to a room.

What QRIS does not automatically solve is attribution. A static QRIS code is exactly as anonymous as a bank transfer: you know money arrived, not who sent it. Dynamic QRIS, generated per payment through a payment provider, does carry the reference through and can tell your system which member paid - which is the version worth having if you are collecting from more than a handful of people, and it is what a membership system connects to.

The tradeoff is fees. A percentage of a Rp 250.000 annual fee is real money for a small organisation, and for a club of eighty members it may simply not be worth it. A reasonable middle path many organisations land on: transfer with unique amounts as the default for annual dues, QRIS for anything paid on the spot.

Make paying easy at the moment of intent

Whatever method you use, the most common reason a member has not paid is not reluctance. It is that they read the reminder while doing something else, meant to pay later, and forgot. Every extra step between deciding to pay and having paid loses some of them.

So put the account number in the message itself rather than telling people to check the pinned post. Put the exact amount, including their unique suffix, in the message addressed to them. If you use QRIS, attach the code rather than describing where to find it. This sounds trivial and it moves the numbers noticeably. Our guide on renewal reminder timing covers when to send those messages.

Confirm every payment, promptly

The most under-rated habit in dues collection is confirming receipt. A member who transfers into silence does not know whether it arrived, whether they used the right account, or whether they are now a member in good standing. Some of them will chase you, which costs you more time than the confirmation would have. Most will not, and will simply feel slightly uneasy about the whole thing.

A short message the same day - "received, thank you, you are paid up to March 2027" - closes the loop, prevents duplicate payments, and does more for the felt professionalism of a small organisation than almost anything else you can do for free. If you are collecting through a system, this is automatic; if you are collecting by hand, it is worth making it a rule.

When to stop doing this by hand

Unique amounts and prompt confirmations will carry a small organisation a long way, and there is no shame in staying there. The signals that you have outgrown it are specific: reconciliation is taking more than an hour a month, more than one person needs to see who has paid, you are chasing renewals individually because you cannot tell who owes you, or the treasurer has started talking about stepping down. Our guide to matching transfers to members goes deeper into the reconciliation problem itself, including what to do with the payments that stay a mystery.