Under Budget and In Trouble: Service Charge Reconciliation
A service charge is a budget residents pre-fund and an account you have to reconcile back to them at year end. Most Kenyan schemes collect diligently, spend reasonably, and never close the loop — which is why the AGM is an argument.
Service charge is the only money in property management that residents pay before it is spent, on the strength of a forecast, with a legal expectation of being told afterwards what actually happened. That makes it structurally different from rent. Rent is a price. Service charge is a budget with a reconciliation obligation attached — and a scheme that treats it as a monthly fee to be banked and drawn against will eventually face a room full of owners asking a question it cannot answer.
The budget is a promise about a specific list
A service charge budget that says "KES 9.6m for the year" is not a budget; it is a number. A budget is the list underneath it — security, cleaning, water, electricity for common areas, lift maintenance, generator fuel and servicing, garbage collection, insurance, borehole, landscaping, management fee, and a contribution to reserves — each with an amount and a basis. The list is what makes overspending visible in March rather than discoverable in December, and it is what makes the AGM a review rather than a confrontation.
It matters because the failure mode of an aggregate budget is specific and predictable. Total spend comes in close to total budget, everybody relaxes, and inside that total the security bill has quietly grown 30% while the reserve contribution was never funded at all. Two errors that cancel in the total, and only one of them is survivable.
A 48-unit scheme, one year, closed properly
This scheme came in under budget and is in trouble. It funded its operating shortfall out of the reserve line, which is the single most common failure in Kenyan schemes and the one that produces a KES 4m special levy when the lift finally fails. The total looks fine. The composition is the diagnosis, and only a line-level budget shows it.
Arrears are a budgeting problem, not just a collections problem
A scheme budgeting KES 9.6m and collecting 92% has not budgeted KES 9.6m — it has budgeted KES 8.9m and hoped. Either build the expected shortfall into the charge, so the paying majority covers it explicitly and knows they are doing so, or fund the gap from reserves as a disclosed decision. What must not happen is the shortfall silently absorbing the reserve contribution, because that converts a collections problem into a capital problem several years later, when it is far more expensive and nobody remembers the cause.
Reserves are the line everybody raids
Lifts, generators, boreholes, roofs, water tanks and repainting are certainties with long intervals. A scheme that does not fund them monthly is not cheaper — it is deferring, at a worse price, to be paid by whoever owns the unit when the bill lands. That is a wealth transfer between owners, which is exactly why the Sectional Properties Act framework contemplates reserves and why a corporation that skips them is storing up both a financial and a governance problem.
The practical control is a separate account, not a separate line. A reserve contribution that sits in the same bank account as the operating float will be spent on operations, because money in one account is fungible no matter how the spreadsheet labels it. Two accounts, one transfer per month, and a rule that transfers out of reserves need a committee resolution — that is the entire mechanism, and it survives changes of management agent in a way a budget note does not.
-
Build the budget as a list, with a basis per line
Every line gets an amount and a reason for that amount — last year plus inflation, a signed contract, a metered rate, a quoted figure. Lines whose basis is "same as last year" are the ones that drift, and naming the basis is what surfaces them.
-
Set the charge on collectable income, not budgeted expenditure
Divide by your realistic collection rate, or fund the gap from reserves as a disclosed decision. Pretending 100% collection is what makes the shortfall invisible and the reserve raid inevitable.
-
Bill it as an invoice per unit, per period
Not a note in a WhatsApp group. A numbered invoice with a due date creates an arrears position you can age, chase and prove — and it is the document a defaulter's lawyer will ask to see.
-
Code every cost to the budget line it belongs to
This is the step that gets skipped and the one everything else depends on. A cost coded to "repairs" when the budget line is "lift maintenance" makes variance analysis impossible, and no amount of year-end effort recovers it.
-
Review variance quarterly, not annually
Three months in, a line running 30% hot is a conversation. Twelve months in, it is a special levy. The quarterly review is where a budget stops being a document and becomes a control.
-
Close the year with a dated reconciliation, and circulate it
Budgeted against actual per line, collections against billings, opening and closing reserves, and the arrears position by unit. Circulate it before the AGM, not at it — owners who read it in advance ask better questions and fewer of them.
| Can you produce it? | Aggregate budget only | Line budget, costs uncoded | Line budget, costs coded |
|---|---|---|---|
| Total budget versus total spend | Yes | Yes | Yes |
| Variance per line | No | No | Yes |
| Whether reserves were actually funded | No | Partly — configurable by you | Yes |
| A defensible AGM pack | No | No | Yes |
| Next year's budget from evidence | No | No | Yes |
| Arrears aged per unit | Partly — configurable by you | Partly — configurable by you | Yes |
Built and maintained Configurable by you, not maintained by us Not built
The third row is the one nobody thinks to test and the one most likely to embarrass you. If a system matches actual spend to a budget on category alone, two budgets sharing a category are both shown the same money — and a total that adds them together counts the same expenses twice.
Can a budget be held per line with its own period?
Make them prove it: Create two budget lines in the same period and check they report separately.
Does actual spend match to the budget line?
Make them prove it: Post one expense and check which budget line moves.
Can two budgets share a category safely?
Make them prove it: Create two budgets with the same category and period, then read both actuals.
Is service charge billed as an invoice per unit?
Make them prove it: Look for a numbered document with a due date and an ageing position.
Can reserves be tracked separately from operating funds?
Make them prove it: Ask where a reserve balance lives.
Can you export the year in one action?
Make them prove it: Ask for last year's budget, actuals and variance as a file.
What AWRA OpsHub does today
- Budgets as records with an amount, a category, a period and start and end dates, so a service charge budget can genuinely be held as a list of lines rather than a single figure.
- A budget-versus-actual report with variance and percentage used per line, over a selected window, exportable to CSV and PDF, with over-budget lines flagged.
- A department on a budget, so lines can be grouped by the team or function that owns them.
- Service charge billed as a customer invoice — numbered, dated, with a due date, partial payments, a balance, and an ageing position per payer. Arrears become a provable receivable rather than a grievance.
- A statement of account per unit-holder, emailable as a PDF over any date range, which is the document to send a resident disputing their arrears.
- Approval thresholds on spend, so a requisition above a configured amount must be approved before a purchase order exists — the control that stops a committee discovering a KES 400,000 commitment after the fact.
- A full chart of accounts including a reserve-style equity account, so an operating fund and a reserve fund can be held as distinct accounts in the ledger.
- Recurring tasks that genuinely spawn occurrences, so the quarterly variance review and the annual reconciliation can be scheduled rather than remembered.
What it does not do
- Actual spend matches a budget on category and period only. This is the caveat worth reading twice. Expenses carry no department, so a budget scoped to a department is compared against that category across the entire organisation — the department on the budget names the line and contributes nothing to the arithmetic. Two schemes, or two buildings, each holding a "Security" budget will both be shown the combined security spend. The report now labels the column as covering all departments and counts each category once in its totals, but the per-line figure genuinely is organisation-wide and cannot be narrowed until expenses carry a department.
- No unit or apportionment logic. Nothing divides a budget by units, applies a unit factor, or produces a per-unit charge. That arithmetic is yours, and so is keeping it consistent when a unit is subdivided.
- No recurring invoice generation, so the monthly or quarterly service charge invoice is raised by hand for every unit, every period. At 48 units this is the dominant administrative task of running the scheme.
- No sinking or reserve fund mechanics. You can hold a reserve account and post to it, but nothing enforces the monthly transfer, nothing blocks a withdrawal without a resolution, and there is no reserve adequacy calculation against a replacement schedule.
- No arrears escalation ladder. Ageing exists; a reminder-then-notice-then-legal sequence with dates and evidence does not.
- No year-end reconciliation pack. Budget-versus-actual, collections-versus-billings, reserve movement and arrears by unit exist as separate reports and are assembled into a document by a person.
- No unit-factor or mixed-use apportionment, so a scheme where a ground-floor shop pays a different multiple than a studio maintains that multiple outside the system entirely.
The budgeting frame is real — budget lines with periods, a variance report with over-budget flags, service charge as a proper ageing invoice, approval thresholds on spend, and a ledger that can hold a reserve fund separately. Two things need naming plainly. Actual spend is matched on category, so scope your categories tightly and uniquely if you run more than one scheme, because a shared category name will merge their spend. And every service charge invoice is typed each period. Price that second one in hours at your unit count before you commit; it is the honest cost of this approach and it does not reduce with practice.
The short version
Budget as a list, set the charge on collectable income rather than budgeted spend, and put reserves in a second bank account. The scheme in the worked example came in under budget and is heading for a special levy — a total will never tell you that.
Collections against these invoices are covered in rent and service charge collection, the metered lines in the budget are dealt with in utilities and recharges, and the reserve-funded items are the plant sitting on your asset register. How to structure buildings and units in the first place is set out in modelling buildings and units.
Close the year with a document, not an argument
Budget lines with periods and variance, an exportable budget-versus-actual report, service charge as an ageing [invoice](/glossary/invoice) per unit, statements per resident, and approval thresholds on spend. Per-unit apportionment, recurring invoices and reserve-fund mechanics are not built — the note above is specific about each.
See property finance in AWRAFrequently asked questions
What should a service charge budget contain?
A line per cost with an amount and a stated basis — security, cleaning, common-area water and power, lift maintenance, generator fuel and servicing, garbage, insurance, borehole, landscaping, management fee and a reserve contribution. The basis matters as much as the amount: lines justified as "same as last year" are the ones that drift, and naming the basis is what exposes them.
How should the monthly charge per unit be calculated?
Divide budgeted expenditure by your realistic collection rate, not by 100%. A scheme budgeting KES 9.6m that collects 92% has really budgeted KES 8.9m and hoped for the rest. Either build the shortfall into the charge so the paying majority knows it is covering defaulters, or fund it from reserves as a disclosed decision — but never let it silently absorb the reserve contribution.
Why is a reserve fund so often unfunded?
Because it is the only line with no immediate consequence. Skipping security means no guard tonight; skipping the reserve contribution means nothing at all until the lift fails. Keep reserves in a separate bank account with transfers out requiring a committee resolution — money in one account gets spent on operations no matter how the spreadsheet labels it.
Can a scheme come in under budget and still be in trouble?
Routinely, and it is the failure this post exists to name. Total spend lands near total budget while inside it security has grown 30% and the reserve contribution was never made. Two errors that cancel on the total, one of which produces a special levy years later. Only line-level variance shows it, which is why the quarterly review matters more than the annual one.
Should service charge be invoiced or just requested?
Invoiced — numbered, dated, with a due date. It creates an ageing receivable you can chase and prove, and it is the document a defaulter's advocate will ask for. A WhatsApp reminder is not evidence of a demand, and schemes that pursue arrears without invoices generally discover this at the least convenient moment.
What is the trap when running two schemes in one system?
Shared category names. If actual spend is matched to a budget on category, then two schemes each with a "Security" budget are both shown the combined security spend of both — and any total that adds the lines together counts the same expenses twice. Prefix categories per scheme, or accept that every variance figure is organisation-wide.
What belongs in the year-end pack?
Budget against actual per line, collections against billings, opening and closing reserve balances with every movement, and arrears aged by unit. Circulate it before the AGM rather than handing it out at one — owners who have read it ask sharper and far fewer questions, and the meeting becomes a review instead of a cross-examination.
