Offering & Tithe Reconciliation: Counting, Controls & Trust
The offering is the hardest money any organization handles: cash, collected in an atmosphere of trust, counted by volunteers. Getting it right is not about suspicion — it is about protecting the money, the counters, and the confidence of everyone who gives.
Almost every control problem in a church converges on one moment: the offering has been collected, and now it must be counted, recorded, and banked. It is cash, so it is anonymous. It arrives in a spiritual context where talk of controls feels out of place. And it is handled by volunteers whose integrity nobody doubts. Every one of those facts, which makes oversight feel unnecessary, is exactly what makes it necessary — because cash with no record protects no one, least of all the honest people handling it. Reconciling offerings properly is the single most important financial discipline a church can adopt, and it is simpler than most fear.
The principle: never one person, never one step
The foundation of offering control is dual control — no single person alone with the cash at any stage where a figure could change. Two or more people count together. The count is recorded and signed by both. The banking is done by someone able to confirm it matches the counted figure. This is not because any one person is suspected; it is because a figure agreed and signed by two people, then reconciled to the bank, is a figure nobody can later question. Dual control is the mechanism that converts "we trust the counters" into "we can demonstrate the counters were right" — and those are very different kinds of safety.
The chain that has to reconcile
A sound offering process is a chain of figures that must agree end to end: what was counted, what was recorded, and what was banked. Break the chain — count without recording, bank without reconciling — and a gap can open with no way to explain it. Keep the chain intact and every shilling has a path from the plate to the bank statement.
The offering chain, step by step
- Collections separated by service and, where relevant, by type (tithe, general, project) before counting.
- Counted by two or more people together, never one person alone.
- The counted total recorded and signed by the counters at the point of counting.
- Cash banked intact, and the bank deposit reconciled against the signed count.
- Any variance between counted and banked investigated and recorded — not absorbed.
Designating giving correctly
Not all giving is general. A member may give a tithe, drop something in a general offering, and add a gift toward the building fund — three different purposes in one envelope. If everything is counted as one lump, the restricted project giving loses its designation the moment it hits the plate. Good practice separates giving by type at the point of counting, so tithes, general offerings, and project gifts each land in the right fund and the promise attached to designated giving is honored from the very first step.
Digital giving does not remove the need to reconcile
M-Pesa and bank transfers are increasingly a large share of church giving, and they feel automatically safe because there is no cash to count. But they still need reconciling — mobile-money and bank receipts matched against recorded giving and designated to the right fund, exactly as cash is. The channel changed; the discipline of making the records agree did not.
Offering reconciliation is the first and most important pillar of church financial management, and it is where trust is either built or quietly eroded. A congregation that knows its giving is counted under proper controls, recorded honestly, and accounted for transparently gives more freely — and the volunteers who serve at the counting table are protected rather than exposed. That double protection, of the money and the people, is the whole point.
What AWRA OpsHub does today
- Expense and payment records with categories, projects and an audit trail, for what the collection is later spent on. Not departments — an expense carries no department, so a project is the code that actually reports.
- Budgets per department and period to hold a designated purpose as a spending limit — a soft one. The budget check warns; it does not block, and it passes silently when no budget matches the category.
- Named users on every action with full audit logging, so post-banking movements are attributable.
What it does not do
- No collection or offering record. Nothing captures a service collection, a counter, a count sheet or a banking slip.
- No dual-control workflow. The two-counter discipline this article describes cannot be enforced by the system — it is a manual control.
- No fund designation. There is no fund entity, so a collection cannot be tagged to a building fund or a mission fund at the point of counting.
- No bank reconciliation. No statement import and no matching, so the collection-to-banking tie-out is manual.
This article describes a control design worth running on paper. Almost none of it is enforced by us, and we would rather say so than let you assume the count sheet lives here. Where we help is afterwards: once the money is banked, budgets, coded expenses and governed procurement make the spending side verifiable.
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 needsReconcile every offering under proper control
Budgets that hold a designated purpose, coded expenses and governed buying — so what happens to the collection after banking is verifiable.
Explore church finance & operationsFrequently asked questions
Why do churches need dual control for counting offerings?
Because cash counted and banked by one person leaves both the money and that person unprotected — there is no record to clear an honest counter if a figure is ever questioned. Two or more people counting together, recording and signing the total, and reconciling it to the bank converts personal trust into a demonstrable record, which protects everyone involved.
What are the steps in reconciling an offering?
Separate collections by service and giving type, count with two or more people together, record and sign the counted total, bank the cash intact, and reconcile the deposit against the signed count — investigating and recording any variance rather than absorbing it. The counted, recorded, and banked figures must agree end to end.
How should different types of giving be handled?
Separate them at the point of counting — tithes, general offerings, and designated project gifts each go to the right fund. If everything is counted as one lump, restricted giving loses its designation immediately, breaking the promise that a building or mission gift will be used for its stated purpose.
Does M-Pesa and bank giving still need reconciliation?
Yes. Digital giving feels automatically safe because there is no cash, but mobile-money and bank receipts still need to be matched against recorded giving and designated to the correct fund. The channel removes the counting, not the discipline of making the records agree.
