Commingling is a lawsuit on layaway
By Loay Kadmany · July 19, 2026
Rent from forty doors, repair float, reserve money, and your own fee income, all sitting in one operating account. Every manager who runs a main account knows the quiet arithmetic of remembering whose money is whose.
Somewhere in your books right now, one property is probably floating another. Not because anyone decided to lend money between owners, but because the industry default is a single operating account that holds every owner’s rent, every building’s repair float, and the manager’s own fees in one undifferentiated balance. So here is the claim, stated plainly: commingling is a lawsuit on layaway, and the industry has misdiagnosed it. It gets treated as a character problem, something dishonest managers do. Most commingling is not fraud. It is the default output of software that handed the manager one bucket and called it accounting.
One account, everyone’s money
Walk through what that account actually holds on the 5th of any month. Rent collected for dozens of owners who have not been paid yet. Money set aside, in theory, for one building’s furnace. Your management fees, earned but not yet swept. Maybe a security deposit or two, if your state has not already forced those elsewhere. The software tracks properties, but the bank sees one number. The books can say a specific property carries a specific balance; the account cannot. Whose dollars are whose is a story the ledger tells about a pile the bank keeps as one lump.
Then the furnace at one property dies the week before its rent arrives. The invoice gets paid from the main account, which means it gets paid, mathematically, with rent collected for other owners. Nobody calls it borrowing. It will be made whole when the late rent lands, and it usually is. But for that week, one owner’s money covered another owner’s repair without either of them knowing, and the only record of the loan is a bookkeeper’s intention to true it up. That is commingling funds in property management as it actually happens. Not a scheme. A Tuesday.
Most commingling isn’t fraud. It’s software that handed the manager one bucket and called it accounting.
How a borrow becomes a finding
This matters because property management is one of the few businesses whose bank handling gets examined by a licensing body. State real estate commissions audit how managers hold and move client funds, and in many states, rent you collect for an owner is trust money from the moment it arrives, with rules about where it may sit and what it may touch. See trust account for the concept. The examination does not begin by questioning your honesty. It begins by asking for records. And the findings that end up threatening a license tend to have started exactly like the furnace week: a temporary borrow between properties, a shortfall quietly covered by the pile, a fee swept a little early. Words like commingling and conversion appear in findings written about managers who never intended either.
The trap is that one bucket makes the innocent version and the fraudulent version look identical from the outside. Both show client money covering something that was not that client’s. Intent lives in the bookkeeper’s head. The account has no way to testify on your behalf.
Why policy fails inside one bucket
Every manager who has thought about this has a policy. A procedures manual that says never pay one property’s bill with another property’s rent. A spreadsheet with a tab per owner. A rule that fees only sweep on the 15th. A monthly three-way reconciliation tying the bank to the books to the owner ledgers. These are real controls, and diligent operators run them for years. But notice what every one of them has in common: the bank account is not a party to any of it. The balance is shared. The separation exists in documents about the account, never in the account. Every safeguard is a memory, and memories have sick days, staff turnover, and Decembers.
You can’t policy your way out of a shared bank account. Separation has to be structural.
Separation that is structural
This is the problem AXYS was built around, and the answer is architectural rather than procedural: stop asking one account to hold everyone’s money, and stop asking policy to do a structure’s job. AXYS is property management software with built-in banking, which means the accounts and the ledger live in one system, and that system can enforce separations a procedures manual can only describe.
- Per-company accounts. Each management company operates its own accounts inside the platform. Your money is not a row in a shared pool, and the banking surface shows balances the ledger stands behind.
- Wallet roles. Operating cash and reserve cash are different roles in the system, not different columns in a spreadsheet. Funds held under the reserves role are structurally distinct from operating float, the same way an operating account and a reserve account are distinct, because that is what they are.
- Per-property reserve sub-ledgers. Each property’s reserves are their own sub-ledger. One building’s vacancy cushion and another building’s roof fund are separate records with separate balances, so a per-property balance is a fact the system holds, not a figure someone derives.
- Numbered movements. Every reserve movement is a double-entry event with its own sequential identifier, a source, and a destination. Money can move between properties, but only as an explicit recorded movement that lands in both sub-ledgers with a number on it. The silent borrow does not exist, because there is no way to move money silently.
Look at what that last mechanism does to the furnace week. The need has not changed: a repair is due before the rent that funds it. What changed is the shape of the act. Covering it from another property’s balance is no longer an unrecorded intention. It is a numbered movement, visible in the sub-ledgers of both properties, checked by reconciliation against the actual balance, with a paired movement when it gets repaid. The structure does not make the decision for you. It makes the decision a record.
An audit never asks whether you meant well. It asks for one property’s balance on one date, and the account either knows or it doesn’t.
The question an audit actually asks
Strip away the procedure and every trust accounting examination in property management reduces to one question, asked many times: whose money is this, and where was it on this date. A one-bucket operation answers by reconstruction. Export the bank activity, rebuild the allocations, and hope the spreadsheet version of events survives contact with the examiner’s sample. A structurally separated operation answers by reading: here is the property, here is its sub-ledger, here is every numbered movement in and out, and here is the balance on the date you asked about. Same question. Entirely different afternoons.
The steelman: one account with careful books has worked for years
The strongest objection deserves stating at full strength. Plenty of managers have run a single account with meticulous books for decades: reconciled monthly, tied out to the penny, never a finding, never an owner shorted. The one-bucket model plus discipline is not a fantasy. It is how most of this industry has always operated, and for many operators it has genuinely worked.
All of that is true, and none of it is the point. The one-account model does not fail on an average day. It fails on the day someone else picks: the audit letter, the owner dispute, the partnership dissolution, the month the bookkeeper leaves. It works until an auditor asks for a per-property balance on a specific date and will not take a derived answer about an account that physically held everyone’s dollars together. What you produce that day is a reconstruction of where the money was, built by the same organization whose handling is being examined. It may be perfect. It is still testimony, not evidence. Careful bookkeeping is a person. Structure is a property of the system, and it does not take Decembers off.
A note on compliance: trust accounting requirements for property managers vary by state, and some states prescribe exactly how client funds must be held, where, and under whose name. AXYS provides a structure that is friendly to trust accounting discipline: separated accounts, role-scoped funds, per-property sub-ledgers, and numbered movements. That is a statement about architecture, not a claim of compliance with any state’s statute. Confirm your state’s requirements with your real estate commission and your attorney.
Picture the letter arriving, because it arrives on a schedule you do not control. In one version of that week, you are exporting a year of bank activity and rebuilding allocations at night, hoping the story balances. In the other, the answer to every per-property question is a record you open and read. Same portfolio. Same repairs, same late rent, same furnace. The only difference is whether the separation between your owners’ money existed in your procedures or in the accounts themselves.
What is commingling in property management?
Commingling is holding funds that belong to different parties in one undifferentiated account: rent collected for different owners, reserve money, security deposits, and the manager’s own fee income mixed in a single balance. Many states restrict or prohibit it for client funds, and it is one of the most common findings in trust account examinations.
Is a reserve the same as a trust account?
No. A reserve is money set aside for a property’s future expenses, while a trust account is a legal arrangement for holding client funds, defined by state law. Whether reserve funds must be held as trust funds depends on your state. The discipline of keeping them separate and traceable per property is valuable either way.
Does AXYS make me compliant with my state’s trust accounting rules?
No software can claim that on its own, and AXYS does not. AXYS provides structural separation: per-company accounts, role-scoped funds, per-property reserve sub-ledgers, and numbered movements, which support trust accounting discipline. Confirm the specific requirements with your state real estate commission and your attorney.
How does AXYS keep one property’s money from covering another’s?
Each property’s reserves live in their own sub-ledger, and money moves between properties only through explicit, numbered, double-entry movements with a recorded source and destination. There is no way to move funds silently, so a cross-property transfer is always a visible record rather than a bookkeeper’s intention.
See how reserves and separation work
Book a 30-minute walkthrough and watch per-property reserves, wallet roles, and numbered movements keep every dollar attributable.
