Financial Management for Churches in Kenya: Offerings, Funds & Trust (2026)
A church runs on the trust of the people who give to it — and trust, in money matters, is built by controls, not intentions. Here is how well-run Kenyan churches handle offerings, project funds, buying, and assets so that the giving is protected and the accounting is beyond doubt.
A church is a financial institution that rarely thinks of itself as one. Money arrives — offerings, tithes, pledges, project gifts — often in cash, handled by volunteers, counted after a service, and banked by whoever is trusted. Nobody in the room intends anything but good stewardship. And yet the absence of controls is precisely how good churches end up with painful disputes, unexplained gaps, and, worst of all, faithful members quietly wondering where their giving went. The purpose of financial discipline in a church is not suspicion; it is the opposite. It protects the money, protects the people who handle it, and protects the trust that giving depends on.
1. Offerings: the money that arrives as cash and trust
The offering is the hardest money to control precisely because it arrives as cash, in the emotional context of worship, handled by volunteers who would be offended by the suggestion of oversight. But cash counted by one person and banked by the same person is a risk to everyone — most of all to that honest person, who has no record to clear them if a figure is ever questioned. The discipline that works is dual control: collections recorded by service, counted by at least two people together, and reconciled against what was actually banked. Proper offering reconciliation is not a lack of faith in the counters; it is the thing that lets the congregation have complete faith in them.
2. Project & building funds: giving with a purpose
When members give toward a building, a bus, or a mission, that money carries a promise — it will be used for that purpose and nothing else. Honoring the promise requires tracking those funds separately from general offerings, recording pledges against actual receipts, and being able to show, at any moment, how much was given, how much spent, and what remains. This is fund accounting, structurally identical to how an NGO tracks restricted donor funds — and church building funds fail the same way NGO grants do when the money is pooled into one account and the separate promise is lost. A building fund nobody can account for does not just risk money; it kills the giving.
3. Procurement: spending the congregation's money
Churches buy constantly — construction materials, sound equipment, event supplies, vehicle repairs — and in many the buying is entirely informal: a leader authorizes a purchase verbally, someone pays, a receipt appears later, and the only record of price and approval is memory. That is exactly the environment where costs drift and, occasionally, worse. A simple requisition-and-approval discipline — spending above a threshold approved before it is committed, with quotes on record for larger items — lets the church spend deliberately and answer the members' entirely fair question: who approved this, and was it a good price?
4. Assets: what the church owns in trust
Over years, a congregation accumulates real assets — instruments, sound and media equipment, chairs, vehicles, land, and buildings, much of it bought with sacrificial giving. Without a register, these are bought again when they cannot be found, lost when custodians move on, and impossible to account for to the board. An asset register with named custodians and periodic verification is modest work that honors the giving those assets represent, and it is exactly the kind of record a diligent board and any external examiner will expect.
| Area | The risk without control | The discipline |
|---|---|---|
| Offerings | Cash exposed; counters unprotected | Dual-control counting, reconciled to banking |
| Project funds | Purpose lost, giving collapses | Restricted-fund tracking, pledges vs receipts |
| Procurement | Costs drift, no approval on record | Requisition and approval by threshold |
| Assets | Rebought, lost, unaccountable | Register with custodians and verification |
Transparency is a form of ministry
The end product of all these disciplines is a set of figures the leadership and members can actually trust — income, fund positions, and spending presented clearly rather than from a spreadsheet only the treasurer understands. In a church, that transparency is not mere administration; it is faithfulness to the people whose giving makes the work possible, and it is very often what unlocks the next season of generosity.
None of this requires a large finance office or complex software — it requires an operational backbone that records giving under control, keeps restricted funds separate, governs buying, and tracks assets, all on one trustworthy record. For a church, that backbone is not bureaucracy imposed on ministry; it is the stewardship that makes the ministry credible.
What AWRA OpsHub does today
- Expenses coded to a category and a project, with a full audit trail. Not to a department — which matters, because a department is exactly what a ministry budget is set on.
- Budgets per department and category over a period, which is how a ministry or committee budget is modelled. Read the caveat below on what its actual spend can and cannot see.
- Procurement with permission-gated approval, and a purchase order that can only be raised from an approved quotation.
- An asset register with named custodians and movement history.
- Payroll for church staff, including Kenyan PAYE, NSSF, SHIF and housing levy on date-effective rules.
- A consolidated payments register and reporting with export.
What it does not do
- No offering, tithe, donation or contribution record. There is no giving entity of any kind, so collections are not something the system captures.
- No member or giving records, and therefore no contribution statements.
- No pledge tracking and no pledge-versus-receipt comparison.
- No fund accounting. There is no restricted/unrestricted fund type and nothing prevents spending a designated fund on something else.
- No dual-control counting workflow for cash collections.
- No bank reconciliation — no statement import and no matching.
- A ministry budget only half-sees its own spend. The budget is set on a department; a purchase order carries one, so procurement spend against it is properly scoped, but a standalone expense does not — so that half of the comparison is category-wide across the whole church. The Budget vs Actual report shows the two channels in separate, labelled columns rather than adding them into one figure that would look scoped and not be. If you want a ministry's whole spend in one number, run it as a project instead: a project is the one dimension carried by expenses, purchase orders, stock issues and invoices alike.
Be clear about the shape of the fit before you evaluate us. The money going out — buying, budgets, assets, staff costs — is genuinely well covered and is where most governance failures actually happen. The money coming in is not covered at all: offerings, pledges and member giving live in whatever you use today. Churches that want one system for both should look at dedicated church management software; churches that already have giving handled and are struggling with procurement and assets are the fit here.
What is not built today can still be built for you
Anything described above as not built is a statement about what ships in the standard product today — not a limit on what AWRA OpsHub can do for your organisation. Kenya's eTIMS integration and its maintained payroll engine are both in the product because clients needed them and commissioned them; neither appeared by itself, and the same door is open for the gap you just read about. Two honest qualifications so this is worth what it claims: a handful of gaps on this blog are deliberate refusals rather than missing work — a statutory ledger we will not sign our name to, a rule that would decide a tax question for you, a clinical or member-funds record that belongs in a regulated system — and where that is true the post says so in those words rather than calling it a gap. Everything else is a scope, a timeline and a price.
The operational work, which is what most commissions actually are
An extra approval stage in a chain that does not match the standard one, a custom field set on employees or assets that only your sector needs, an expiry that has to block an order rather than send an email, a report your board asks for in a shape nothing produces, or a scanner or weighbridge feeding the goods-in door. These are the commissions we are asked for most often and the smallest ones we quote — and unlike a revenue-authority pipeline, none of them waits on a regulator.
The module-shaped gaps, which are the ones this blog admits most often
A price list with real discount authority, a customer-facing quotation that expires, a bill of materials or recipe costing, a staff advance that is issued, acquitted and chased, a member or unit ledger, a matching rule that holds a payment. Each of these is a build rather than a setting, and each has been quoted before — a bigger piece of work than a custom field, with a written spec and a date instead of a roadmap slide.
The report, document or pack nothing currently produces
The board pack in the shape your board actually asks for, a donor or funder layout, an invoice or receipt template carrying what your regulator or your customer expects, a dataset the report builder cannot reach yet. Usually the fastest thing on this list to deliver, because the data is already in the system.
Systems, rails and hardware you already run
The accounting package, CRM, online store, core banking or custom database you intend to keep — connected through our API so a fact is entered once and appears everywhere it is needed. Plus the physical edge: a scanner, a scale, a weighbridge or a till peripheral feeding the door it belongs to.
How it works: you describe the requirement, we return a written scope, timeline and cost, and once agreed it is built into your environment and maintained as part of the product. Nothing here waits on a regulator or a published specification, which is why operational builds are the ones we quote fastest. Tell us the requirement that would otherwise rule us out — that is a better first conversation than a demo.
Tell us what your operation needsSteward the giving with the transparency it deserves
Procurement whose chain actually refuses, department budgets, an asset register with custodians and staff payroll — the money-going-out side of church governance.
Explore church finance & operationsFrequently asked questions
Is financial control in a church a sign of distrust toward volunteers?
No — it is the opposite. Controls like dual-control counting protect honest volunteers as much as the money, because they create a record that clears the counters if a figure is ever questioned. Cash handled by one person with no record leaves that person exposed to suspicion they cannot disprove. Good controls are an act of care toward the people who serve.
What does a church need beyond a simple cashbook?
A cashbook records that money moved; it cannot enforce dual-control counting, keep restricted project funds separate from general offerings, govern who approved a purchase, or track assets. Those are the disciplines that protect giving and sustain trust — an operational backbone the cashbook was never designed to provide.
How should building and project funds be handled?
As restricted funds tracked separately from general offerings, with pledges recorded against actual receipts and every disbursement attributed, so you can show at any meeting how much was pledged, received, spent, and remaining. Pooling project money into one general account is how the purpose gets lost and the giving toward it collapses.
Is this practical for a small congregation without a finance office?
Yes — small churches benefit most, because they depend on volunteers whom good controls protect. The right approach is to start with offering recording and reconciliation, which delivers protection and trust immediately, then add project-fund tracking, procurement, and asset registers as capacity grows.
