A Service Charge Budget Is a Promise to Spend Other People's Money in a Particular Way

Managing a jointly owned building is a different business from managing a landlord's portfolio, even though the two are usually done by the same company with the same staff.

A landlord is one person with one interest. A building is hundreds of owners with one shared cost base, an apportionment rule that decides who pays what, an approved budget that sets the ceiling, a collection rate that never reaches a hundred per cent, and a set of contractors whose invoices arrive whether or not the money came in.

The arithmetic is not difficult. What makes it fail is that the five moving parts — budget, apportionment, invoicing, collection and spend — usually live in four places, and the variance between them is computed once, after the year has ended, at which point the only available action is to explain it.

The chain, and the fact that decides everything downstream

A budget is approved for a period, by line: cleaning, security, lifts, insurance, utilities, management, reserve. That total is then divided among units by an entitlement, invoiced, collected, and spent against the same lines it was approved as.

The single fact that decides whether any of this is auditable is where the entitlement lives.

Entitlement — the share of the common cost attaching to each unit — is the multiplier on every owner's invoice for the life of the building. If it sits in a spreadsheet, then every service charge invoice the association has ever issued rests on a file that has been edited by an unknown number of people, has no version history anyone consults, and cannot be reconciled to the registered documents it came from.

An apportionment nobody can audit produces invoices nobody can defend, and the challenge arrives one owner at a time.

That is not a hypothetical failure mode. It is the ordinary state of a large number of buildings, and it is stable for years, because an entitlement error produces a perfectly normal-looking invoice. Nothing is wrong until somebody with an interest recalculates their own share.

The regulator has already specified the shape

In Dubai this is not left to convention. RERA, through Dubai Land Department, operates Mollak, an e-system for jointly owned properties that regulates service charges and monitors their payment, and DLD publishes a service charge index alongside it. Service and utilisation fees for jointly owned property are submitted for approval rather than simply set, and the escrow mechanism for jointly owned property accounts runs through the same system.

The practical consequence for a management company is worth stating plainly, because it is often heard as a compliance burden and is actually a design constraint that helps.

The budget is a document that gets approved externally, so it has a version and a status rather than being a working figure. Collections are visible to somebody other than you. The money sits in an account with a defined purpose. And the reconciliation between what was approved, what was invoiced, what was collected and what was spent is not an internal management report — it is the thing the arrangement exists to produce.

A system that treats the budget as a soft target and the reconciliation as a year-end exercise is not aligned with any of that, and the misalignment surfaces as a scramble.

Where the year actually goes wrong

Five failures, none of which announces itself.

Spend without a budget line. A contractor invoice arrives for something genuinely necessary that was never budgeted. It gets coded to the nearest line. The line overruns, the reason is not recorded, and the variance discussion twelve months later is archaeology.

The collection rate is assumed rather than tracked. The budget was built assuming near-full collection. Actual collection is lower, always, and the contracts were signed for the full amount. The building is now committed to spending money it has not received, and nobody computed the gap until the cash ran short.

The reserve fund is treated as cash. It is in the same account, it is a number in the same ledger, and it is available to whoever needs to pay a bill this week. Reserve funds exist precisely to not be available for that, and a reserve spent on operating costs is a capital problem deferred, silently, into someone else's term of office.

Variance is produced annually. Budget against actual, per line, is only useful while there is time to act. Produced in month thirteen, it is a report about a decision that can no longer be made.

Recoverable and non-recoverable costs are mixed. Some costs belong to the association and some to the developer or the owner directly. Coded together, they are separated later by whoever is asked to separate them, which is a task with no correct answer available.

The trust problem, again, with a committee attached

The money is not the management company's. That is the same fact that governs an individual owner's balance and the payout against it, and the same disciplines follow — spend within authority, reconcile to receipts, keep the balance visible as an obligation rather than as turnover.

Two things change when the owner is a body rather than a person.

The number of people entitled to ask goes from one to hundreds, so a statement that requires assembly by a person is not merely slow, it is unservable. Owners have to be able to see their own position without anybody producing anything.

And the authority is a committee decision with a record, rather than a clause in a contract. That makes the approval itself a record the system has to hold — who approved which budget, when, and what was actually approved — because in a dispute the question is not whether the spend was sensible but whether it was authorised.

Where our own software stops

Worth being direct about, because the alternative is a promise that fails at the worst moment.

Proptec handles the property and facilities side: units, tenancies, work orders and SLA clocks, spend against a mandate, and the accounting underneath. It is deliberately not a Mollak bridge. DLD's service charge platform has a real integration interface gated on an accreditation, and implementing half of that would be a promise the software cannot keep — a partial integration to a regulated system is worse than none, because people rely on it.

That is the same honesty as the rest of the limits on the product page: it does not fetch the rental index, and it does not validate the format of an Ejari number or an Emirates ID check digit, because neither algorithm has been published and a rule inferred from a handful of samples refuses genuine documents with no way to overrule it. What it does check is the thing that is reliably wrong: the same registration number sitting on two tenancies.

What to make a vendor show you

1. Show me the entitlement per unit as a stored, auditable value with a source, not a spreadsheet column.
2. Change one unit's entitlement and show me what it does to every invoice that depends on it.
3. Show me budget, invoiced, collected, spent and remaining for one line, today.
4. Try to code a purchase invoice to a line with no remaining budget. Something should happen.
5. Show me the collection rate per building, and the resulting funding gap against committed contracts.
6. Show me the reserve fund as a separately identified balance rather than a number in the same pool.
7. Give an owner his own position without anybody in your office producing a document.
8. Show me the approval record for the current budget: who, when, what version.
9. Separate recoverable from non-recoverable spend at the point of coding, not at year end.

Item 3 is the whole test. Everything else on the list is a way of making item 3 possible.

Item 4 is the one that reveals the design. There is no single right behaviour — refusing outright is wrong for an emergency lift repair — but something has to happen: a warning, an approval step, a flag on the line. Silence means the budget is decoration.

The short version

A service charge budget is an authority to spend a defined amount of other people's money on defined things. Every failure in this business is the same failure wearing different clothes: one of the five numbers — approved, apportioned, invoiced, collected, spent — was not available at the time somebody needed to make a decision, so the decision was made on the others.

The entitlement is the load-bearing one, because it multiplies into every invoice and cannot be corrected retrospectively without reissuing history. Get it into a system with a source and a version before anything else on the list.

If you manage both jointly owned buildings and a landlord's portfolio — most companies here do — the broader piece is a tenancy is a schedule of things that have not happened yet, and what the leasing side looks like as one system is on the real estate and leasing page.