Property management accounting: charge codes to GL

Search for accounting software and you will find a hundred products built around one assumption: a business is a single company with a single set of books. Property management breaks that assumption in the first week. A manager running twelve buildings for eight owners is not keeping one set of books — they are keeping many small ones, each of which must stand on its own when the owner, the accountant, or a regulator asks.

This post walks through the accounting architecture property management actually needs — charge codes, general ledger mapping, per-entity books, and the trial balance that proves them. It is written for Canadian property managers who have outgrown the spreadsheet and want to know what "real" accounting software should be doing underneath. Your accountant governs the treatment; this is the operational map.

Why property accounting breaks generic tools

Three structural facts separate property management from ordinary small-business accounting. First, the reporting unit is the property or the ownership entity, not the management company — every owner expects statements for their asset, and mixing two owners’ numbers in one ledger is not a formatting problem, it is an accounting failure. Second, much of the money that moves through a manager’s hands is not the manager’s money. Where you manage for third-party owners, provincial rules generally apply — in BC, rental property management is a licensed activity under the Real Estate Services Act, with trust account requirements administered by BCFSA. Your obligations depend on your licence and your province; your managing broker and your accountant are the authorities. Third, the volume profile is unusual: hundreds of small, recurring, predictable transactions a month, which is exactly the shape of work that should be systematized and exactly the shape that drowns a spreadsheet.

Generic accounting tools can be bent around the first fact with classes and tags, and around the third with discipline. The second fact — money held for others, with separation and evidence requirements — is the one that deserves real structure from day one.

Charge codes: the revenue taxonomy

A charge code is the answer to a simple question asked hundreds of times a month: what is this tenant being billed for? Base rent, parking, storage, utilities recovery, common area maintenance, late fees, NSF charges — each is a charge code, and the code carries the accounting decision with it: which revenue account it posts to, whether tax applies, and how it appears on the tenant’s ledger and the owner’s statement.

The discipline sounds trivial and is not. When the charge taxonomy lives in column headers and staff memory, every new hire invents categories, every building bills slightly differently, and year-end becomes a reclassification project. When it lives as a managed list — one taxonomy, owned by whoever owns the books, mapped once to the general ledger — every lease charge created anywhere in the portfolio lands in the right account automatically. The taxonomy is small: most portfolios need a few dozen codes, not hundreds. What matters is that it is singular, and that adding a code is a decision rather than a keystroke.

From charge to ledger: the posting path

Follow one month of one lease through the system. The lease carries its recurring charges — say base rent and parking, each on a charge code. On the first of the month, those charges become receivables on the tenant’s ledger: the tenant owes, and revenue is recognized against the accounts the codes map to. When the payment arrives, cash increases and the receivable clears. Every step is a balanced pair — debits equal credits — which is the property a general ledger enforces and a spreadsheet merely hopes for.

Whether you recognize revenue when charged or when collected — accrual versus cash — is a question for your accountant, and the answer may differ by entity. What the software must guarantee either way is that the path from lease to charge to receivable to receipt is one connected chain, so "what does unit 204 owe and why?" is a lookup, not a reconstruction.

The trial balance is the proof

A trial balance is the least glamorous report in accounting and the most honest: every account in the ledger with its debit or credit balance, and a total that must agree with itself. For property managers it matters twice over. Per entity, it is the proof that the owner’s books stand on their own — assets, liabilities, income, and expenses for that ownership structure, balanced. Across the portfolio, it is the month-end discipline: the rent roll, the receivables ledger, and the general ledger describing the same buildings must tell the same story, and the trial balance is where disagreement surfaces.

A useful habit for any manager evaluating their current setup: ask for last month’s trial balance for one owner entity. If producing it takes more than a few minutes — or if the answer involves the phrase "we’d have to pull that together" — the books are being assembled on demand rather than kept.

What to look for in software — the Canadian checklist

When property managers in Canada evaluate accounting-capable software, the questions that separate real structure from marketing are specific:

• Per-entity books: can each ownership entity produce its own trial balance, or are owners simulated with tags on one company file?
• A managed charge-code taxonomy that maps to the chart of accounts — one list, one owner, applied everywhere.
• Support for the separation your licence requires: owner funds distinguishable from operating funds, with records that show it.
• Sales tax handling appropriate to your situation — GST treatment on fees and recoveries varies, and your accountant should approve the configuration.
• An audit trail: who created, changed, or reversed any entry, with corrections as new attributable events rather than silent edits.

This is the architecture PropertyOps-Zaavi is built on. The module is in early access: properties, units, residents, leases, and lease charges on a managed charge-code taxonomy are live today, with rent-roll visibility across the portfolio — and the OpSphere platform’s accounting core, a double-entry general ledger with a chart of accounts, controlled periods, and trial balance reporting, is the foundation those records are designed to post into. If the money workflows you need are further along than early access supports, an established property accounting suite is the honest recommendation — but if fragmentation across owners, buildings, and spreadsheets is the cost you feel, the record foundation is the place to start.