Branches & Satellites: Running Several Congregations as One Church
A church that plants a second congregation has created an accounting problem before it has created a ministry one. What each site keeps, what rolls up, who approves what — and the remittance arrangement that quietly determines whether branches trust the centre.
Growth in a church usually arrives as a second site rather than a bigger building, and the financial arrangements are typically improvised in the first year and never revisited. The branch collects, keeps some, sends some, and the centre finds out what happened when a summary arrives — assembled differently each month by a volunteer treasurer doing their best.
By the third or fourth site this is no longer sustainable, and by then the habits are established. Deciding the structure early — even a simple one — is considerably easier than correcting it once four congregations each have their own approach.
Three models, chosen deliberately
There are essentially three ways to run multi-site church finances, and the trouble comes from operating one while describing another.
If sites are small and newly planted
Centralised
All banking, payments and records run through the centre. Branches hold no funds. Simple, safe, and slow — a branch waiting three weeks for a repair approval will eventually stop asking and start paying cash from the offering.
If sites are established with their own leadership
Delegated within limits
Branches operate within a threshold and a budget, remit the balance, and the centre approves anything larger. This is where most growing churches land and it works — provided the thresholds are real and the reporting is consistent.
If sites are effectively separate congregations
Autonomous with consolidation
Each site runs its own finances and contributes to the centre on an agreed basis. The centre consolidates for reporting and governance rather than controlling day to day. Requires the strongest reporting discipline of the three.
The failure mode is a church that describes itself as centralised while branches in practice hold cash and pay for things — which means there are unrecorded transactions in a structure that assumes there are none.
The dangerous arrangement is not any of the three models. It is describing yourself as centralised while branches quietly pay for things out of the offering, because that structure assumes transactions that nobody is recording.
What every model needs regardless
| Requirement | Why it holds in all three models |
|---|---|
| Income recorded at the site where it was received | Otherwise a remittance is the only record and the gross figure is lost |
| A consistent category list across sites | Consolidation is impossible if each site names things differently |
| One approval threshold policy, applied everywhere | Different thresholds per site is how the weakest site becomes the route for everything |
| A fixed reporting date each month | Late reporting from one site delays the whole picture and becomes normal |
| Assets recorded against the site holding them | Equipment moves between sites constantly and is then owned by nobody |
The first row is the one most often broken. A branch that banks its offering and remits a net figure has destroyed the gross income record — the centre can see what arrived, not what was given, and the difference is whatever the branch spent locally. That is not dishonesty; it is a reporting structure that makes local spending invisible by design.
The remittance arrangement is a relationship
Whatever the formula — a percentage of income, a fixed monthly contribution, everything above a local allowance — the arrangement should be written down and stable. Churches that renegotiate remittance informally, or vary it by circumstance, generate a specific and corrosive suspicion: branches begin to believe they are subsidising a centre whose spending they cannot see.
The remedy is symmetry. If branches report their income and expenditure to the centre, the centre should report what it does with the remittances back to the branches. A one-page annual statement showing what central funds went on — shared staff, denominational obligations, support for newer plants — prevents more conflict than any policy document. Branches are almost always content to contribute; they resent contributing to something opaque.
What a site-level picture makes visible
Illustrative, in KES. Whether to allocate central costs to sites at all is a governance choice — many churches deliberately do not. But a church that cannot produce this view is unable to answer the question when a branch eventually asks it, and the question always gets asked eventually.
Equipment moves and nobody owns it
Multi-site churches share equipment constantly — the PA system that goes to the new plant for a season, the instruments borrowed for a conference, the chairs that went to the branch and stayed. Within two years nobody can say what each site holds, and the annual accounts carry a fixed asset figure that no longer corresponds to anything physical.
Recording assets against a site, with movements between sites as recorded transfers, keeps this honest for the cost of a few seconds per move. It matters more than it sounds during a leadership change: an incoming site leader inheriting an accurate list of what they hold starts from a position of clarity, and one inheriting nothing starts by quietly writing off whatever cannot be found. The wider discipline is in church asset registers and procurement governance.
What we do and do not do
What AWRA OpsHub does today
- Locations, departments and projects — with one asymmetry to design around. Assets, purchase orders and employees all carry a department, so a site reports properly on those. A standalone expense does not, so per-site expenditure only reports if you run a standing project per site. Do that from the start; it is far harder to backfill.
- A shared category and fund structure, applied consistently across every site.
- Approval thresholds enforced by permission rather than by policy statement.
- Assets recorded against a site with transfers between sites as recorded movements.
- Reporting by site and consolidated, schedulable to site leaders and the centre.
- An audit trail and document storage with access logging across all of it.
More we can add to your workspace
- Separate legal entities with intercompany accounting. Sites are locations within one organization, not independent entities with eliminations between them.
- A remittance calculation. Whatever your formula is, the transfer is recorded rather than computed.
- A church management system. Membership, attendance, small groups and pastoral records are elsewhere.
- Per-site data isolation. Site leaders see what their permissions allow, and permissions are by module rather than by location — a site treasurer with expenditure access can see other sites' expenditure.
That last line is the one to test against your governance before rollout. If site-level data separation is a firm requirement rather than a preference, raise it early — it is a visibility model question, not a setting.
Anything above that you need, we can build for you
Everything listed above as something we can add describes what ships in the standard product today — it is a starting point, 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 whatever you just read about. One qualification so this is worth what it claims: a small number of things on this blog we deliberately leave to a specialist rather than build — 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. 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 additions, which are the ones readers ask for 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 needsOur take
Pick one of the three models and describe yourself accurately. Record income where it is received rather than netting it into a remittance, use one category list and one threshold policy everywhere, and report centrally-held funds back to the branches once a year. That last habit costs an afternoon and prevents the resentment that quietly ends multi-site arrangements.
See multi-location operations
Income, expenditure and assets recorded by site, one shared category structure, enforced approval thresholds and consolidated reporting.
Explore financial governanceFrequently asked questions
Should branches have their own bank accounts?
It depends on which of the three models you have genuinely chosen. Centralised means no, and then branches must be able to get things paid for quickly enough that they do not start using cash from the offering. Delegated within limits usually means yes, with a threshold and a budget. The failure is having branch accounts while describing the church as centralised — that arrangement produces transactions the structure assumes do not exist.
How should income be recorded at a branch?
At the branch, gross, before any local spending or remittance. A branch that banks its offering and remits a net figure has destroyed the record of what was actually given — the centre sees what arrived, not what came in, and the difference is invisible local expenditure. Recording gross costs nothing and is the foundation of every other report you will want.
Can each site see only its own figures?
Not reliably — permissions are by module rather than by location, so a site treasurer with expenditure access can see expenditure across sites. In practice many churches accept this, since branch leaders seeing each other's figures is often positively healthy. If genuine per-site isolation is a governance requirement, raise it early in evaluation rather than assuming it is configurable.
What remittance formula works best?
Whichever one is written down and stays stable. A percentage of income, a fixed monthly contribution, or everything above a local allowance all work; renegotiating informally or varying it case by case does not, because it generates the belief that branches are subsidising a centre whose spending they cannot see. Pair whatever you choose with a one-page annual statement of what central funds went on.
How do we keep track of equipment that moves between sites?
Record each asset against the site holding it and each move as a transfer, which takes seconds and keeps the register honest. Multi-site churches share equipment constantly and within two years nobody can say what each site holds. It matters most at a leadership change: an incoming site leader who inherits an accurate list starts from clarity, while one who inherits nothing starts by writing off whatever cannot be found.
