RT/RW Treasurer Problems When Collecting Dues

Few people become an RT/RW treasurer by choice. RT/RW are the neighborhood units of Indonesian residential areas, and their treasurer is usually appointed at a meeting for being careful, or because nobody else volunteered, and suddenly holds the neighbors' money. The work is unpaid, fitted around a day job, and watched by people they see every day.

This article covers the human side of the role, from billing neighbors to handover, with a practical fix for each. For tools built for this role, see RT/RW treasurer software.

Summary

A treasurer's heaviest burden is often not the math but the position: billing people they know, in spare time, while accounting for every rupiah. Three habits help:

• Collect in the name of the rules. The amount, due date, and payment method are agreed at a residents' meeting, so the treasurer carries out a shared decision.
• Separate community funds from personal money. Dues go into a dedicated community account, and every payment is recorded with its proof.
• Work on a fixed schedule. Recording, reminders, and reports happen on the same dates every month.

Common Challenges

Seven problems RT/RW treasurers often face, each with a fix:

1. Billing your own neighbors feels awkward. Billing someone you greet every morning is not like billing a customer, so many treasurers put it off. The fix: send the bill as a routine announcement, identical for every household, and cite the meeting decision when explaining the amount.
2. Volunteers with day jobs. Treasurers are usually unpaid, and payment messages at any hour make the job feel endless. The fix: set two or three recording times a month and name a fellow committee member as backup.
3. Scattered transfer receipts. Receipts arrive via private chats, the residents' group, or a word in passing, and some are missed until a resident feels billed twice. The fix: agree on one channel for proof and record every payment with it.
4. "Have I paid?" over and over. Every question means opening the records again. The fix: give residents a way to check their own status, such as a per-household summary shared per community policy.
5. Community and personal money mixed together. When dues land in the treasurer's personal account, the community balance blurs into salary and daily spending, inviting misunderstanding even when the treasurer is honest. The fix: use a dedicated community account only for community matters, and agree at a meeting on who else knows about it.
6. Accountability at residents' meetings. The summary is often prepared the night before, and detailed questions get answered without proof. The fix: use the same report format every period and prepare proof in advance.
7. Handing over to the next treasurer. Records often live on the outgoing treasurer's phone, so the successor starts from scratch and residents question the balance. The fix: prepare a handover package of resident data, payment status per period, the account balance, and the proof archive, then hand it over with the RT or RW head as witness.

Practical Checklist

Check whether the treasurer's work is in order:

• The amount, due date, and payment method are in the meeting minutes.
• Dues go into a dedicated community account, not a personal one.
• There is one official channel for submitting payment proof.
• A fellow committee member can stand in for the treasurer.
• Residents can check their payment status without asking directly.
• The meeting report format stays the same each period.
• The proof archive is accessible to administrators, not just kept on a personal device.

If many are unchecked, start with the dedicated account and the proof channel.

Recommended Workflow

One treasurer work cycle, from the start of a term to handover:

1. Agree on rules, roles, and the account. At a residents' meeting, set the amount, due date, payment method, who supports the treasurer, and one dedicated community account for dues.
2. Issue bills together. The same format and date for every household makes a bill feel like an announcement, not a personal reprimand.
3. Record at fixed times. Outside the announced dates, the treasurer need not answer every payment message right away.
4. Let the schedule do the reminding. Reminders go out on fixed dates, and lingering arrears are handled in stages following how to reduce housing dues arrears, not the treasurer's courage.
5. Report in a fixed format. Before the meeting, prepare a collection summary, status per community policy, and supporting proof.
6. Tidy the archive at the end of each period. Handover then means summarizing, not rebuilding.

Illustrative example: an RT with 60 households sets dues at Rp50,000 per month, with a target of Rp3,000,000. The treasurer records payments on the 5th and 20th. At the end of March, 52 households have paid (Rp2,600,000) and 8 have not (Rp400,000). With dues in the dedicated account, that income needs no separating from personal transactions. At the meeting, the treasurer presents those three numbers and shows proof when asked.

Workflow Comparison

The biggest difference is the treasurer's position: in the first approach, they field every question and draw suspicion when numbers do not match; in the second, well-kept records answer most questions. To weigh whether a spreadsheet is still enough, read OmahKu vs Excel for treasurers.

How OmahKu Billing Helps

OmahKu Billing helps move routine treasurer work from private chats to centralized records:

• Recurring bills per period set by administrators, with amounts adjustable per resident or unit, and notifications through channels the administrators configure.
• Automatic payment reminders before and after the due date for residents who have not paid, so the treasurer need not remind neighbors one by one.
• Payment status (paid, unpaid, arrears) per resident or unit on the administrator dashboard, updated after a transaction is recorded.
• Digital payment proof per transaction, accessible to administrators and residents, so "have I paid?" is answered by the records.
• Exportable reports per period on payment status, arrears, period summaries, and payment proof, for meetings and handover.
• Report visibility set by administrators per community policy, and access limited by administrator role.
• Digital payment methods depending on account configuration and payment provider, with fund flow, settlement time, and fees following the provider's terms.

OmahKu is not a bank. It records and reports transactions but does not replace the administrators' bank account. Keeping dues in a dedicated community account is still good practice. See also OmahKu for treasurers.

Getting Started

1. List every channel residents now use to pay and send proof.
2. Propose a dedicated community account and one proof channel at the next meeting.
3. Set and announce regular recording times.
4. Appoint a fellow committee member as backup treasurer.
5. Start the handover package early in your term.

The OmahKu team helps with onboarding according to community size. To discuss your neighborhood's needs, reach us through the contact page.