LearnKenya Use CasesAutomating Chama Records: Contributions, Reminders, Reports
Kenya Use Cases

Automating Chama Records: Contributions, Reminders, Reports

Chama groups in Kenya manage real money, often hundreds of thousands of shillings, using WhatsApp messages and handwritten notebooks. Automating your chama records with Google Sheets, scheduled reminders, and simple reports reduces errors, builds trust among members, and takes the awkwardness out of chasing contributions. This guide covers what to automate and what to keep under human control.

Bonaventure Ogeto July 30, 2026 9 min read

Chama groups in Kenya manage real money, often hundreds of thousands of shillings, using WhatsApp messages and handwritten notebooks. Automating your chama records with Google Sheets, scheduled reminders, and simple reports reduces errors, builds trust among members, and takes the awkwardness out of chasing contributions. This guide covers what to automate and what to keep under human control.

Why Chama Record-Keeping Deserves Better Than a Notebook

Kenya has thousands of active chamas (investment groups, merry-go-rounds, savings circles). Most of them share a common problem: the treasurer tracks contributions in a notebook or a personal WhatsApp message thread, and everyone else has to trust that the numbers are right.

This creates real friction. Members wonder if their payment was recorded. The treasurer spends hours reconciling M-Pesa messages against their notes. Monthly meetings turn into accounting arguments instead of investment discussions. When the treasurer changes, the handover is chaotic because the records live in one person's phone or notebook.

The fix is not complicated software. It is a shared, structured spreadsheet that every member can view, combined with automated reminders so the treasurer does not have to personally chase each person.

Important caveat before we go further: chamas handle real money that belongs to real people. We are automating records and reminders only. Decisions about investments, loans, and payouts should always involve the full group. Never automate money movement without explicit group agreement and proper controls.

What to Automate (and What Not To)

Safe to automate:

  • Contribution tracking (who paid, how much, when)
  • Monthly reminders before the contribution deadline
  • Overdue contribution notices
  • Monthly summary reports (total collected, who is up to date, who owes)
  • Meeting minutes distribution

Keep under human control:

  • Actual money movement (M-Pesa transfers, bank transactions)
  • Loan approvals and disbursements
  • Investment decisions
  • Changes to contribution amounts or group rules
  • Adding or removing members

This boundary matters. Automation should make the treasurer's administrative work easier. It should never replace the group's collective decision-making on financial matters.

Step 1: Build the Chama Tracker in Google Sheets

Create a Google Sheet called "Chama Tracker" and share it with all members as "Viewer" (only the treasurer and secretary get "Editor" access). This way everyone can see the records but cannot accidentally change them.

Sheet 1: Member Directory

Member NamePhoneEmailJoined DateStatus
Jane Wanjiku0712 XXX XXXjane@email.com2024-01-15Active
Peter Ochieng0723 XXX XXXpeter@email.com2024-01-15Active

Sheet 2: Monthly Contributions

Create columns for each month. Rows are members.

MemberJan 2026Feb 2026Mar 2026Apr 2026...Total PaidTotal ExpectedBalance
Jane Wanjiku5,0005,0005,000-15,00020,000-5,000
Peter Ochieng5,0005,0005,0005,00020,00020,0000

Use formulas to calculate totals and balances automatically. =SUMIF and =COUNTBLANK formulas are particularly useful here.

Sheet 3: Transaction Log

Every M-Pesa payment gets logged here with the full details.

DateMemberAmount (KES)M-Pesa CodePayment ForRecorded By
2026-07-05Jane Wanjiku5,000RK4XXXXXXXJuly ContributionTreasurer

This is the audit trail. When someone disputes a payment, you check this sheet against their M-Pesa statement. Having the transaction code eliminates arguments.

Sheet 4: Summary Dashboard

Use simple formulas to create an overview.

  • Total members: =COUNTA(MemberDirectory!A2:A)
  • Total collected this month: =SUM(Contributions!B2:B)
  • Members who have paid: =COUNTA(Contributions!B2:B)-COUNTBLANK(Contributions!B2:B)
  • Members who owe: =COUNTBLANK(Contributions!B2:B)
  • Total chama balance: running sum of all contributions minus all payouts

Step 2: Automate Contribution Reminders

This is where you save the treasurer from the uncomfortable job of personally messaging each member who has not paid.

Using Google Apps Script for email reminders:

Open the Chama Tracker, go to Extensions, then Apps Script. Create a script that runs on the 1st of each month (or three days before your contribution deadline) and sends a reminder to every member.

The reminder email should include: the contribution amount, the deadline, payment details (M-Pesa Till/Paybill or the treasurer's M-Pesa number), and a reminder to share the M-Pesa confirmation code.

Set the script to run automatically using a monthly trigger. The treasurer does not have to do anything; the system handles it.

For a second reminder (overdue): Create another trigger that runs three days after the deadline. This script checks the Contributions sheet, finds members whose cell for the current month is still empty, and sends only to them.

The overdue message should be firm but respectful: "Hi [name], our records show that your [month] contribution of KES [amount] has not been received yet. The deadline was [date]. Please send your contribution to [payment details] and share the M-Pesa confirmation code with the treasurer."

This is important: the message comes from the system, not from the treasurer personally. This removes the social awkwardness of one friend chasing another for money. The treasurer can honestly say "the system sends those reminders automatically."

Step 3: WhatsApp Reminders (The Practical Approach)

Most chamas communicate on WhatsApp, not email. Since you cannot fully automate WhatsApp messages without the API, here is what works.

Create a standard message template. Save it in the treasurer's WhatsApp Business quick replies or in a Google Doc.

Monthly reminder template: "Hello Chama Family! Reminder: [month] contributions of KES [amount] are due by [date]. Send to M-Pesa [number], name: [registered name]. Please share the transaction code here or with the treasurer. Thank you!"

Overdue template: "Hi everyone, quick update: [number] members still have outstanding [month] contributions. If you have already paid, please send your M-Pesa confirmation code to the treasurer. If not, please send by [new deadline]. Asante!"

Use Google Calendar to trigger the reminder. Set recurring calendar events for the 1st and 5th of each month. When the notification pops up, the treasurer copies the template, fills in the details, and posts to the chama WhatsApp group. This takes one minute.

The personal element actually helps here. A WhatsApp message in the group is visible to everyone, which creates gentle social accountability.

Step 4: Generate Monthly Reports Automatically

At each monthly meeting, the treasurer presents a summary. Instead of manually compiling this, set up formulas in the Summary Dashboard sheet to generate it automatically.

Monthly report template (copy from the dashboard):

  • Contributions received this month: KES [total]
  • Members paid in full: [number] of [total members]
  • Outstanding contributions: KES [total owed]
  • Running chama balance: KES [total]
  • Members with overdue balances: [list names and amounts]

If you want to go further, use Google Apps Script to compile this report and email it to all members automatically on the day before the monthly meeting. Members arrive informed, the meeting focuses on decisions instead of accounting, and the treasurer's workload drops significantly.

Handling the Sensitive Parts

Chama money automation requires extra care because trust is involved.

Transparency is protection. The biggest advantage of a shared Google Sheet is that every member can see the records at any time. This protects the treasurer from accusations and gives members confidence. Never keep financial records in a tool that only one person can access.

Two-person verification. For recording payments, consider having both the treasurer and the secretary verify each entry. The treasurer logs the payment; the secretary confirms it against the M-Pesa transaction code. This takes extra effort but prevents errors and suspicion.

Regular backups. Google Sheets saves automatically, but download a copy (Excel format) at the end of each month and store it in the chama's shared Google Drive folder. If anything happens to the sheet, you have historical records.

Access control. Only the treasurer and secretary should have edit access. All other members get view access. If the treasurer changes, transfer edit access to the new person and revoke it from the outgoing one. Do this in the same meeting where the handover happens.

No automating actual payments. We said this earlier, but it bears repeating. Automation should never move money. It tracks, reminds, and reports. The actual transfer of funds (M-Pesa to the chama's account, payouts to members, investment transfers) must always be initiated by authorized people following the group's agreed process.

Tools Beyond Google Sheets

If your chama outgrows a spreadsheet, these tools are designed for group financial management.

M-Changa. A Kenyan platform designed for group fundraising and contributions. It handles collection and provides a dashboard, though it is more focused on fundraisers than ongoing chamas.

ChamaSoft. Built specifically for Kenyan chamas. Handles contributions, loans, dividends, and reports. Has a free tier for small groups.

Eazzy Chama by Equity Bank. A banking-integrated solution for chamas that bank with Equity. Offers contribution tracking, loan management, and investment features.

For most chamas with fewer than 30 members and straightforward monthly contributions, Google Sheets with automated reminders is sufficient. Move to a dedicated platform when your chama starts issuing loans, making investments, or growing beyond what a spreadsheet can handle comfortably.

FAQ

Should we automate reminders for individual members or just post in the WhatsApp group?

Both work, and you can use both. Group reminders create social accountability (everyone sees who has and has not paid). Individual reminders are more discreet and less embarrassing for members who are having a tough month. A good approach: send the general reminder to the group, then send individual follow-ups privately only to members who are overdue after the deadline.

How do we handle members who consistently pay late?

This is a group governance issue, not an automation issue. Your chama constitution should specify penalties for late payment (a small fine is common) and what happens after repeated late payments. Automation can flag the pattern (the spreadsheet clearly shows who pays late every month), but the group decides how to respond.

What if a member says they paid but it is not in the records?

Ask for the M-Pesa transaction code. Check it against the treasurer's M-Pesa statement. If the payment exists but was not recorded, update the sheet and note the error. If the code does not match, the member needs to follow up with Safaricom. This is exactly why recording M-Pesa transaction codes matters: it turns a "he said, she said" situation into a verifiable fact.

Is it safe to put chama financial records on Google Sheets?

Google Sheets is encrypted and requires login to access. It is significantly more secure than a physical notebook (which can be lost, damaged, or altered) or a WhatsApp message thread (which disappears if someone clears their chat). Set strong passwords on Google accounts, use viewer-only access for most members, and enable two-factor authentication for the accounts that have edit access.

Frequently Asked Questions

### Should we automate reminders for individual members or just post in the WhatsApp group?

Both work, and you can use both. Group reminders create social accountability (everyone sees who has and has not paid). Individual reminders are more discreet and less embarrassing for members who are having a tough month. A good approach: send the general reminder to the group, then send individual follow-ups privately only to members who are overdue after the deadline.

How do we handle members who consistently pay late?

This is a group governance issue, not an automation issue. Your chama constitution should specify penalties for late payment (a small fine is common) and what happens after repeated late payments. Automation can flag the pattern (the spreadsheet clearly shows who pays late every month), but the group decides how to respond.

What if a member says they paid but it is not in the records?

Ask for the M-Pesa transaction code. Check it against the treasurer's M-Pesa statement. If the payment exists but was not recorded, update the sheet and note the error. If the code does not match, the member needs to follow up with Safaricom. This is exactly why recording M-Pesa transaction codes matters: it turns a "he said, she said" situation into a verifiable fact.

Is it safe to put chama financial records on Google Sheets?

Google Sheets is encrypted and requires login to access. It is significantly more secure than a physical notebook (which can be lost, damaged, or altered) or a WhatsApp message thread (which disappears if someone clears their chat). Set strong passwords on Google accounts, use viewer-only access for most members, and enable two-factor authentication for the accounts that have edit access.

Start the Free Preview

7-minute Welcome lesson, no purchase required

B

Bonaventure Ogeto

Founder, Mctaba Labs

Software engineer building products for the African market. Teaching 10,000+ students across multiple platforms. BSc Mathematics & Computer Science from JKUAT.