5 ways to reduce service charge arrears without conflict

A treasurer in Masaki sends a WhatsApp message. It is the seventh of the month. The message says, in a single text, “Service charge was due last week. Please pay. Also, the lift making noise again? Anyone know when the plumber is coming for 4B? We need to discuss the generator fuel contract.”

By the time the thread has forty replies, nobody has paid. Two owners are arguing about the generator contract. A third has posted a photo of a leaking pipe from 2022. The service charge reminder has become invisible, buried under the noise.

Arrears management works best when it is systematic, not reactive. The difference between a building that collects 95% of its service charges and one that scrapes 60% is rarely the financial capacity of the owners. It is the design of the collection workflow. Remove friction, separate payment from discussion, apply a consistent reminder cadence, and the default rate drops — without a single hostile confrontation.

Here are the five patterns that make this possible. Each has the same starting point: your building’s service charge collection is not a negotiation. It is a system. And systems perform better than people at this job.

---

1. A single visible channel — not five WhatsApp groups

The most common arrears driver in Tanzanian buildings is not refusal to pay. It is confusion about what is owed, when it is due, and where to pay it.

What happens in most buildings:

• The treasurer posts the service charge amount in WhatsApp Group #1.
• The due date is mentioned verbally at a committee meeting that nobody attended.
• Someone asks how to pay and gets a different answer depending on which committee member replies first.
• A new owner who bought in December does not know the payment schedule and nobody told her.
• The treasurer’s M-Pesa number changed in March and half the owners missed the update.

What a single visible channel looks like:

One place — a portal, a monthly email, a notice board — where every owner can see, at any time:

• The current service charge amount.
• The due date.
• The payment methods (TIPS merchant account, M-Pesa business number, bank transfer — all routing to the body corporate’s official account).
• Their own balance — paid, outstanding, or in credit.

This week’s action: For every owner in your building, can they answer these three questions in thirty seconds without asking anyone? (1) How much do I owe this month? (2) When is it due? (3) Where do I pay it? If the answer to any of these is “I’ll ask the treasurer,” you have a visibility problem, not a payment problem.

The single-channel rule extends to the technology stack. When your building is on TIPS, every owner can pay from any mobile wallet — M-Pesa, Tigo Pesa, Airtel Money — through one merchant account. No confusion about which number to use. Read more about how TIPS transformed service charge collection.

---

2. A consistent reminder cadence — before and after

Most committees send one reminder, on the due date, and then go silent for 60 days. By the time the second reminder arrives, the owner has forgotten the first one, the arrears have compounded, and the conversation starts from a place of tension.

What a structured reminder cadence looks like:

Timing	Message	Tone
T-7 days	”Service charge of TZS 150,000 is due on the 1st. Current balance: TZS 0. Pay via…”	Informational
Due date (T=0)	“Payment is due today. Thank you to the 23 owners who have already paid.”	Positive social proof
T+7 days	”Your service charge is now one week overdue. Please settle at your earliest convenience.”	Gentle prompt
T+14 days	”Arrears of TZS 150,000 now stand at 14 days. Interest accrues at the prevailing rate per s.62 of the Act.”	Factual, statutory
T+30 days	”One month overdue. Please contact the treasurer to discuss if you are facing difficulty.”	Open door, not threat

Each message is separate, automated, and delivered through the single visible channel. The owner knows what is coming and when. There is no surprise — and no confrontation.

Swahili template (T+7 days):

“Habari. Tunakukumbusha kuwa ada yako ya huduma ya TZS 150,000 ilipaswa kulipwa tarehe 1. Tafadhali lipa kupitia namba yetu rasmi ya malipo. Kama tayari umelipa, asante — tafadhali puuza ujumbe huu.”

Committee mistake: Combining the reminder with grievances. The T+7 message should not include “Also, your parking space…” or “The committee has decided…” The reminder is a transaction. Keep it clean.

---

3. Separate payment from discussion — the single-thread rule

The most damaging operational pattern in a Tanzanian building is mixing payment reminders with building-wide discussions in a single WhatsApp group. The payment message goes out. Someone replies with a grievance about the lift. Someone else replies to that with a comment about the guard. Twenty messages later, twelve owners have muted the group, the original payment message is scrolled off-screen, and nobody paid.

Committee mistake: Using the same WhatsApp group for service charge reminders and building-wide discussion. This single pattern is responsible for more missed payments than any other operational failure.

The fix:

• One thread for payment status. Only the treasurer posts. Only “paid” or “I have a question” replies are relevant.
• A separate thread for building operations — lift, security, water, waste.
• A separate thread for governance — AGM, by-laws, committee decisions.
• A separate thread for noise, parking, and social disputes.

When an owner brings a lift complaint into the payment thread, the treasurer moves it: “Please post lift issues in the Operations thread. Thank you.” The boundary is enforced consistently. Within two months, the norm is set.

For the broader argument on why mixing channels destroys trust and enables the free-rider dynamic, see the free-rider problem and the four modules that fix it.

---

4. Exception tracking — formal, not verbal

Some owners genuinely cannot pay on time. A tenant stopped paying rent. A business delayed a contract payment. A medical emergency consumed the month’s cash flow. When the committee has no formal exception-tracking process, these legitimate cases get lumped with wilful defaulters, and the resulting blanket enforcement alienates people who would otherwise pay voluntarily.

What exception tracking looks like:

Every exception is a record — not a verbal understanding between two people at the gate:

Field	Example
Unit	B-12
Owner	Juma Hassan
Amount in arrears	TZS 450,000 (3 months)
Reason	Tenant vacated; new tenant pays from 1 June
Agreed plan	Pay TZS 150,000 per month starting 15 June; arrears cleared by 15 September
Committee owner	Treasurer — Amina Mwakyoma
Status	Active — first payment received 15 June

The owner gets a written copy of the agreement. The committee reviews the exception log monthly. If an owner breaches the plan — no payment by the agreed date — the exception converts to a formal enforcement action, with a clear audit trail showing that the committee gave them every opportunity.

Ina maana gani? Mkataba wa malipo — a payment agreement — is more powerful than a demand letter because it demonstrates good faith on the committee’s side. If the matter ever reaches a dispute resolution forum, the record of accommodation makes the committee’s position unassailable.

---

5. Monthly trend review — a 15-minute committee ritual

Most committees discover an arrears crisis when it is already a crisis. The treasurer finally does the maths and realises that 40% of the building is behind, the sinking fund is depleted, and the lift contractor is threatening to stop work.

What monthly trend review looks like:

Once a month, in the committee meeting, spend exactly 15 minutes on this agenda:

1. Ageing snapshot: How many units in each bucket — 0–30 days, 31–60, 61–90, 90+?
2. Trend line: Is the total arrears position going up, down, or flat compared to last month?
3. New entries in the 61+ bucket: Which owners crossed the two-month threshold this month? What action is being taken?
4. Exception plan compliance: Which owners on payment plans missed an instalment? What is the follow-up?
5. One decision: Do we need to adjust anything — reminder frequency, payment channels, exception terms — based on this month’s data?

That is it. Fifteen minutes. The committee does not debate individual cases. The committee reads the dashboard, spots the trend, and makes one operational decision.

The average Dar es Salaam body corporate does none of this. The average Dar es Salaam body corporate only discovers its arrears problem when the lift breaks and there is no money to fix it. By then, the problem is not just financial — it is social. Owners who have been paying are furious that their money has been subsidising defaulters. The building’s social contract is broken. And the committee — volunteers who never signed up to be debt collectors — resigns.

---

The legal escalation ladder — when systematic collection is not enough

For the 5–10% of owners who will not pay regardless of how clean your collection workflow is, the Act provides a legal escalation ladder:

Step	Action	Legal basis
1	Written reminder (T+14 days)	Committee discretion
2	Formal demand notice	s.62 — interest accrues
3	Offer payment plan with deadline	Committee discretion — good faith documented
4	Notice of intention to register a charge on the unit title	s.62 — arrears as debt
5	Issue clearance certificate reflecting arrears — blocks unit sale or refinance	s.30 — purchaser protection
6	Legal action — court application for recovery	s.63

Every step is documented. Every document is filed. By the time legal action is contemplated, the audit trail is complete, and the committee’s position is legally unassailable.

Important: The Act does not give the committee the power to disconnect water, electricity, or lift access for arrears unless the by-laws specifically authorise it — and those by-laws must be properly ratified at an AGM and filed with the Land Registry. Arbitrary disconnection without proper by-law authority exposes the committee to legal liability.

---

The tone guide — firm without being hostile

Tanzanian condominium culture places a high premium on heshima — mutual respect — and social harmony. A collection workflow that feels like harassment will fail because owners will withdraw from engagement entirely. The tone of every communication matters.

What works:

• Neutral, procedural language. “Your account shows an outstanding balance of…” not “You still haven’t paid…”
• Social proof on the positive side. “85% of owners have already paid this month.” This signals that paying is normal.
• The exit door. Every reminder includes “If you have already paid, please disregard this message.” This respects the owner who paid late and prevents defensive replies.
• Swahili that is respectful, not confrontational. “Tafadhali wasiliana nami” (Please contact me) rather than “Lipa mara moja” (Pay immediately).

What fails:

• Public shaming in WhatsApp groups. It generates a week of drama, the target owner leaves the group, and three other owners mute it permanently.
• Threats the committee cannot enforce. “We will cut your water” — unless your by-laws explicitly authorise it, you will not, and the owner knows this.
• Emotional appeals. “We are all struggling” is true but irrelevant to an owner who has already decided not to pay. Stick to the facts.

---

This week action

Open whatever you use to track service charge payments — a notebook, a spreadsheet, a WhatsApp chat — and produce two numbers: how many units are current, and how many are more than 30 days behind. If you cannot produce those numbers in under five minutes, your collection system has already failed. The building does not have an arrears problem. It has a visibility problem — and visibility is the cheapest problem to fix.

For how the right payment infrastructure eliminates collection friction, see TIPS and service charge payments. For the financial controls that protect what is collected, consult the case for dual-signatory payments. And for the broader compliance framework, see the RERA-readiness checklist.

Updated June 2026 for RERA draft status.