The building accounting year: from budget to year-end statement

Every spring, managers of owners’ communities disappear into the same project: reconstructing a year of building finances well enough to produce the annual statement. Bank statements get re-downloaded, shoeboxes of invoices get sorted, and a document the owners will scrutinize line by line gets assembled from memory and archaeology. It routinely costs weeks per building.

Here is the reframe that dissolves the project: the annual statement is not a task that happens in spring. It is the output of a loop that runs all year. The names differ by country, and some statutes are stricter than others, but the loop itself is universal. Every owners’ community, whatever the local law calls its parts, runs the same five steps: a budget, monthly advances against it, month-by-month bookkeeping, a year-end statement, and settlement. Run them as a rhythm and year-end is arithmetic. Skip them and year-end is archaeology.

Step 1: The budget, decided once, resolved formally

The year starts with a plan: expected costs per category (cleaning, elevator, insurance, utilities, maintenance), plus a contribution to the reserve as its own line, never mixed into running costs. From the total, each owner’s share follows from the building’s cost-splitting rule, whether that is equally per unit, by ownership share, or by a weighted key the community has agreed for specific costs.

Divided by twelve, those shares are the monthly advances each owner will pay all year. Two details decide whether the rest of the year runs smoothly:

• The split must be exact. Per-owner amounts have to re-sum to the planned total to the cent, with rounding assigned deliberately. A plan that is 40 cents short becomes a statement that cannot balance in December.
• The budget is a resolution. The assembly approves it, and that approval belongs in the building’s decision record with the vote behind it, because every advance you collect for the next twelve months rests on it. That record-keeping discipline is its own topic: why assembly minutes shouldn’t live in email.

Step 2: Advances that collect themselves

Twelve months of collecting the same amounts from the same people is the most automatable work in the whole profession, and the least automated in practice.

The critical property is that the monthly round should create itself from the approved budget. Each month’s collection goes out with a unique payment reference per owner, so incoming money matches back to the person who sent it, and a scannable payment code turns “pay your share” into a two-second phone action instead of a form to fill in. Where the local banking system supports pull-based collection, the whole round becomes one file uploaded to the bank portal. Whatever the channel, the rule is the same: if producing March’s collection requires you to remember March, one distracted month quietly breaks the year.

Step 3: Bookkeeping as a ten-minute monthly habit

Between the advances coming in and the invoices going out, the building account accumulates the raw material of the annual statement: transactions. The habit that keeps the loop alive is small. Import each bank statement when it arrives, let incoming rows match to owners by reference, and assign each outgoing row to its cost category while you still remember what it was. Ten minutes a month, as described in running building finances without a spreadsheet.

This is the step that replaces the spring archaeology. A statement assembled in December from categorized transactions is a report. The same statement assembled in March from uncategorized paper is a reconstruction, and reconstructions are where errors and owner distrust are born.

Supplier invoices, meanwhile, are increasingly arriving as structured data rather than paper: a parsed invoice can become a categorized draft cost in one confirmation, with the original filed against its retention duty, which runs the better part of a decade in most countries. One less shoebox.

Step 4: The statement, computed, not composed

If steps 1 to 3 ran all year, the annual statement is a derivation: total costs per category against the budget, each owner’s share by the same split rules, each owner’s actual payments from the matched transactions, and the difference per owner. Alongside it, the community’s asset position: account balances, the reserve, receivables.

Two things legitimately block the computation, and good tooling names them instead of producing a silently wrong document. A coverage gap, meaning a period with no imported statement, so money moved that the record cannot see. Or uncategorized rows, transactions no one assigned. Both are findable in minutes in December. Both are landmines in March.

Step 5: Settlement, and the lock

The assembly reviews the statement and approves it; that approval is itself a resolution for the register. Then the differences settle: owners who underpaid against their actual share owe the balance, owners who overpaid carry a credit. Billing these individually, by hand, per owner, is the last stronghold of year-end drudgery, and there is no reason for it. The per-owner results are already computed; turning them into settlement charges and credits should be one action, not an afternoon of arithmetic and copy-paste.

And once approved, the period locks. No edits to a closed year, ever; corrections happen as documented entries in the new period. Immutability of accounting records is a near-universal accounting principle, but the deeper reason is the same as with the resolution register: a record that provably cannot be quietly rewritten is a record nobody has to take on faith.

Two side streams deserve their own visibility year-round rather than a year-end surprise. The reserve is the owners’ long-term money and should be trackable as its own balance, ideally on its own account, with contributions visible against the plan. And the accountant handoff should be an export, not a retyping: standard booking export formats exist precisely so your records flow into an accountant’s software instead of being read out over the phone.

The dividend: owners who can see for themselves

Run the loop and something changes beyond your own workload. Every owner has, at any moment, a current answer to the questions that otherwise fill the assembly’s first hour: what have I paid, what do I owe, how large is the reserve, what did the community spend on. When the running ledger is visible all year, the annual meeting stops being an audit of the manager and returns to being a decision-making body.

That is the real case for the loop. The weeks saved every spring are the obvious return. The compounding one is trust: a community that can verify its manager’s numbers at will is a community that renews the contract without a fight.