The Money in Your Account Is Not Your Money

A managing agent's bank account fills up with rent. Very little of it is his.

What is his is a management fee, usually a percentage, usually of something the contract defines loosely enough to argue about later. The rest belongs to owners — one balance per owner, sometimes one per building, reduced by whatever was spent on their behalf with their authority, payable when it has actually cleared.

That is four numbers: collected, fee, spend, payable. In most property operations at least two of them are produced monthly by a person with a spreadsheet, which means they exist once a month, cannot be produced in between, and are defensible only to the extent that the person is available to defend them.

Every serious dispute a managing agent has with an owner is one of those four numbers.

An owner balance is a liability, not a performance figure

Start with the accounting, because getting it wrong here makes everything downstream unfixable.

Rent collected on a managed unit is not revenue. Your revenue is the management fee. The rest is money held for somebody else, and on a properly built balance sheet it sits as a liability — an amount owed to owners — that goes up when receipts clear and down when payouts are made.

Booked the other way, as revenue with the payout as a cost, three things break at once. The profit and loss becomes meaningless, because turnover is now the rent roll of buildings you do not own. The balance sheet stops showing what you owe, so nobody can see the obligation. And the payout decision loses its anchor: if the owner balance is not a liability with a real number on it, the question "can we pay him this week" has no arithmetic answer and becomes a judgement about how much is in the bank.

If the amount you owe owners is not a line on your balance sheet, then nobody in the business knows what it is, including you.

Deposits compound this. A security deposit is neither revenue nor an owner balance — it is money held against a condition that has not been inspected yet, refundable to a third party. Mixed into the general pool, it is spent without anyone deciding to spend it, and the shortfall surfaces at a move-out, which is the worst possible moment to discover it.

The four rules that prevent the arguments

None of these is a policy. Each is a state transition a system either enforces or leaves to a person.

Pay only from receipts that have cleared. An owner paid from a cheque that later bounces has been paid with your money, and getting it back is a negotiation with your own customer. This is the direct downstream consequence of treating a post-dated cheque as cash on receipt — the error starts in the instrument register and arrives here as a payment you cannot reverse.

Spend only within the mandate. The owner signs an authority with a threshold on it: repairs up to a stated figure without asking, above it with approval. Spending above that threshold is spending somebody else's money uninvited, and the fact that the repair was necessary is not a defence anybody accepts after the fact.

Never let a unit with no live mandate. An expired management agreement does not expire quietly — it expires and the unit keeps being let, invoiced and maintained by an agent with no current written authority. Letting property you have no authority to let is the shortest route to a claim, and the trigger is a date passing, which is exactly the kind of event a system notices and a person does not.

Compute the fee on collection, not on billing. A fee taken on invoiced rent is a fee taken on money that has not arrived. When a tenant defaults, the agent has been paid and the owner has not, and the conversation that follows is not recoverable by explaining the accounting policy.

What a defensible statement actually contains

An owner statement exists to end an argument before it starts. That means it has to be reconstructable by the person receiving it, which is a higher standard than being correct.

Cut by unit, because a portfolio is let one unit at a time and an owner thinks about it one unit at a time. Then, per unit: what was invoiced and for which period; what was received, with the date it cleared rather than the date it was handed over; what is outstanding, aged from when the instalment fell due; what was spent, each line tied to a work order and a supplier invoice he can open; the fee, with the base it was calculated on printed next to it; and the resulting balance, with the movement since last time.

Two details do most of the work. Printing the fee's base rather than just the fee removes the most common source of dispute in one stroke. And distinguishing cleared from received tells an owner why his balance is lower than the rent roll suggests, which is otherwise the question he asks every month.

A statement that cannot be reconstructed by the person receiving it is not a statement. It is an assertion with a total on it.

Why this is a systems problem rather than a bookkeeping one

The obvious objection is that a competent accountant can produce all of this in a spreadsheet, and that is true. The reason it fails anyway has nothing to do with competence.

The inputs arrive from four different places. Receipts come from the instrument register as cheques clear. Spend comes from work orders and vendor bills raised by an operations team. The fee comes from a contract term. Arrears come from an invoicing schedule. A spreadsheet is a snapshot of those four at the moment somebody assembled it, and it starts drifting immediately — which is why it can only be produced monthly, and why the mid-month question has no answer.

There is a second-order effect that matters more. Because the statement is expensive to produce, it is produced rarely, and because it is produced rarely, nobody looks at an owner's position between statements. Vacancy, arrears and unapproved spend all accumulate in that window. The reporting cadence quietly sets the management cadence, which is the same pathology as a dashboard that is technically correct and still misleading — the number is real, it is just not available at the speed decisions are made.

The same problem with a committee attached

Where the money belongs to one owner, the discipline above is between two parties and a contract. Where it belongs to a body of owners — a jointly owned building, a service charge budget, a reserve fund — it is the same trust arithmetic with more people entitled to ask about it and a regulator interested in the answer.

The mechanics diverge enough to be worth their own treatment: a service charge budget is a promise to spend other people's money in a particular way.

What to make a vendor show you

1. Show me one owner's balance mid-month, live, without anyone opening a spreadsheet.
2. Show me that balance as a liability on the balance sheet, not as revenue.
3. Receive a cheque, and show me the balance not move. Clear it, and show me it move.
4. Attempt a payout larger than the cleared balance. It should be refused.
5. Raise a repair above the mandate threshold without approval. It should be refused.
6. Expire the mandate and try to let the unit. It should be refused.
7. Show me the fee with its calculation base printed beside it on the statement.
8. Take a deposit and show me it is not in the owner's balance and not in yours.
9. Give me a statement where every spend line opens the work order and the supplier invoice behind it.

Item 3 is the one that separates a property system from an accounting system with property fields. Item 4 is the one that separates a product from a demo: refusing a payout is a gate, and gates are difficult to build and impossible to add afterwards.

The short version

You are holding cash that belongs to somebody else, spending some of it on his instructions, and keeping a defined share. That is a trust relationship, and trust relationships are audited by the person on the other side of them, usually at the worst moment.

Four rules make the arithmetic hold: pay from cleared funds only, spend inside the mandate, never let without a live one, and take the fee on collection. All four are refusals rather than reminders, and a refusal is the only version of a rule that survives a busy month.

Proptec enforces those four as gates, keeps the owner balance as a real liability, and cuts every figure by unit because that is how a portfolio is let and how an owner is paid. Trans Emirates run a portfolio of over five thousand units on it; the other companies live on it are in the case studies.

If you are earlier in the question, the broader piece is a tenancy is a schedule of things that have not happened yet, and what this looks like built as one system is on the real estate and leasing page.