Every trust accounting guide says the same thing. Never mix client funds with operating funds. Most operators know this, agree with it, and intend to follow it.

Commingling still happens, and rarely because someone decided to do it. It happens because a payment processor settles into one account, because a tenant paid two things in one transaction, or because a refund came back to wherever the original payment left from.

The rule about what may and may not cross between accounts is the easy part. This is about the mechanisms that produce a breach while everyone is following the rule as they understand it.

Why the Accidental Cases Are the Dangerous Ones

Two reasons.

• Intent is often not the test. Regulators generally treat commingling as a matter of where funds were held, not why. A deposit made into the wrong account and corrected the following day may still be a violation in the jurisdiction concerned. The specific position varies by state, which is exactly why the accidental cases are worth understanding rather than relying on good faith.

• They repeat. A deliberate breach is one event. A payment processor routing settlements into the wrong account does it every day until someone notices, and the pattern is what turns a technical issue into a serious finding.

1. Payment Processing Defaults

One modern source of risk is payment processing, particularly when settlement and fee-routing settings are not reviewed closely.

Online rent collection introduces a step that did not exist with cheques. Money goes to a processor, is held briefly, and settles to a bank account on the processor's schedule. Several things can go wrong in that gap.

• Gross settlement. The processor deposits the full amount collected, then debits its fees separately. Where the full amount includes both rent belonging to owners and a fee belonging to you, the deposit is mixed before anyone touches it.

• Single-account configuration. The processor is set up with one destination account. Rent, application fees, late fees and any charge you retain all land in the same place.

• Fee debits from the trust account. Processing fees deducted directly from the account the settlements land in. Where that is the trust account, business expenses are being paid from client funds.

• Chargebacks and reversals. A reversed payment comes back through the same route it went out, which may not be where the corresponding funds now sit.

What to check: which account each payment type settles into, whether settlement is gross or net, and where processing fees are debited from. This is a configuration question rather than an accounting one, and it is usually answerable in an afternoon.

2. Mixed Transactions

A tenant pays one amount covering more than one thing.

First month's rent and a security deposit in a single transfer. Rent plus an application fee. A move-in payment covering rent, deposit and a pet fee. Each of those amounts may belong somewhere different: the deposit in a deposit account, the rent in the trust account for the owner, the application fee possibly to you.

The payment arrives as one number. If the amounts belong in different accounts, the payment has to be allocated and routed correctly rather than treated as a single undifferentiated receipt.

Two ways this goes wrong. The split never happens, because the payment was reconciled as a single line. Or the split happens days later, leaving funds in the wrong account in the interim, which may itself be the issue depending on the jurisdiction.

What to prevent it: collect distinct payment types as distinct transactions wherever the payment method allows it. Where a combined payment is unavoidable, split it on receipt rather than at month end, and document the split. The accounting treatment of deposits has its own requirements that make this more than a tidiness question.

3. Operating Before the Account Exists

A new market, a new entity, or a first management agreement signed before the banking is in place.

Funds arrive. There is nowhere compliant to put them. They go into the operating account with every intention of transferring them once the trust account opens.

In some jurisdictions, depositing client funds into an operating account can constitute commingling from the moment of deposit, even if the funds are transferred later. Some frameworks address this directly by requiring a trust account to be opened within a defined period of receiving trust funds, and several also require the regulator to be notified of the account within a set window after opening.

The related version is a lapse: an account closed during a bank change, or a notification requirement missed when a new account was opened, leaving a period where funds were held in an account that was not properly designated.

What to prevent it: open and notify the account before the first management agreement is signed, not before the first payment arrives. The gap between those two events is where this happens.

4. Reversals and Corrections

Money going backwards is where account discipline usually breaks.

• A returned payment. A tenant's payment bounces after the funds were already disbursed to the owner. The reversal hits the trust account, the owner has the money, and the shortfall has to be covered from somewhere. Covering it from operating funds is well-intentioned and, in many jurisdictions, its own violation.

• A refund of something you retained. An application fee refunded to a declined applicant, or a fee reversed after a dispute. The original receipt may have gone to operating; the refund may leave from trust, or the reverse.

• A duplicate payment. Returned to the payer, and the question is which account it comes back from.

• A correction of an earlier error. Moving funds to fix a misposting. The correction itself is a transfer between accounts and needs the same documentation as any other crossing.

What to prevent it: decide in advance which account absorbs each type of reversal, and document the decision. The instinct under time pressure is to move money from wherever it is available, and that instinct is what creates the problem.

5. The Buffer That Grew

Some jurisdictions permit a limited amount of the firm's own money in a trust account for specific purposes, such as bank service charges. Others restrict or prohibit this practice. The permitted amount and purpose should be confirmed for the applicable jurisdiction.

Where a buffer is permitted, it is usually a specific amount for a specific purpose. What happens over time is that nobody tracks it. A rounding difference stays in. An unclaimed balance is left rather than escheated. An earned fee is not transferred and quietly becomes part of the cushion.

Five years later, the account holds several thousand dollars of firm money that nobody can account for. It is not identifiable as a permitted buffer, it is not attributable to any client, and it shows up on a reconciliation as an unexplained excess.

What to prevent it: know the permitted amount for your jurisdiction, record the buffer as a separate identified item, and check it as part of each reconciliation rather than treating it as background.

The Sixth One

Not on the list because it is not quite accidental, but it belongs here: managing a property you own alongside properties you manage for others.

Rent on your own property is your money. Rent on a client's property is not. When both flow through the same processes, the same staff and the same accounts, the separation depends entirely on coding discipline. Some jurisdictions address licensee-owned property directly, including how deposits on those properties must be handled.

Where this exists in an operation, it is worth treating as a structural question rather than a coding one.

What Catches Them

Most of these are invisible in ordinary bookkeeping. The bank balance looks fine. The general ledger balances. The error is in which account funds sat in, not in whether the arithmetic works.

Two things surface them.

• The three-way reconciliation. Some commingling issues may not be obvious from a bank-to-ledger comparison alone, because the overall totals can still appear to tie. Comparing the trust ledger with the individual owner and tenant balances provides another level of accountability. The step-by-step mechanics cover how the comparison works.

• Reviewing the account configuration, not just the transactions. Processor settings, fee debit destinations, refund routing. These produce recurring errors that transaction-level review keeps correcting without ever fixing.

Both belong in the month-end process rather than in an annual review, because a configuration error caught in month one is a correction and the same error caught in month eleven is a pattern.

If You Find One

Three things, in order.

• Stop the mechanism. If a processor is settling into the wrong account, fix the configuration before anything else. Correcting the transactions while the cause continues means doing it again next month.

• Establish the extent. How long, how many transactions, how much. A single misrouted payment and eight months of misrouted settlements are different situations and are treated differently.

• Take advice on the correction. How a commingling error should be corrected, whether it needs to be disclosed, and what the correction itself may require depends on the jurisdiction and the circumstances. Moving funds to fix it can create its own issue, particularly where the correction involves putting firm money into a client account.

That last point is the one worth being careful about. The obvious remedy is not always the permitted one, and this is a question for an attorney or compliance adviser rather than a judgement made in the moment.

Frequently Asked Questions

1. What is commingling in property management?
Holding funds belonging to clients, meaning owners and tenants, together with the management company's own operating or personal funds. It is prohibited in some form across jurisdictions, and regulators generally treat it as a matter of where funds were held rather than whether anyone intended a breach.

2. Can commingling happen by accident?
Yes, and it commonly does. Payment processors settling mixed amounts into a single account, combined tenant payments covering rent and deposits, operating before a trust account is open, reversals returning to the wrong account, and permitted buffers growing untracked all produce commingling without anyone deciding to mix funds.

3. Is it still commingling if funds are transferred out the same day?
That depends on the jurisdiction. Some frameworks address where funds were deposited rather than how long they remained there, so a same-day correction may not resolve the underlying issue. The applicable rule should be confirmed for the relevant state.

4. Can I put my own money into the trust account to cover a shortfall?
In many jurisdictions this is itself a form of commingling, because the account is intended to hold only client funds. Some states permit a limited amount for specific purposes such as bank service charges. Where a shortfall exists, the appropriate correction depends on the jurisdiction and is worth taking advice on rather than assuming.

5. How do you detect commingling in the accounts?
Comparing the trust ledger against the sum of individual owner and tenant balances is the main control, because it can expose funds that are present but not attributable, or attributable but not present. Reviewing payment processor and bank configuration is the other, because configuration errors produce recurring problems that transaction review keeps correcting without fixing.

6. What should you do if you discover accidental commingling?
Stop the mechanism producing it, establish how long it has been happening and how much is involved, and take advice before making the correction. How a commingling error should be corrected and whether it must be disclosed depends on the jurisdiction and the circumstances.

The Rule Is Not the Hard Part

Nobody needs to be told not to mix client money with business money. The operators who breach the rule are almost never the ones who did not know it.

What produces these breaches is the gap between a policy and the places money actually moves through: a processor's default settings, a tenant paying two things at once, a reversal landing wherever the original payment came from. Those are configuration and process questions, and they are answerable.

RIOO is a property management platform built on NetSuite, with leasing and property accounting in the same underlying system.

Note: Guidance in this article is general and does not constitute legal advice. Rules on commingling, permitted firm funds in a trust account, deposit timing, correction of errors and disclosure obligations are set by individual states and vary by jurisdiction and licence type. Where a commingling issue is identified, take advice from an attorney or compliance adviser familiar with the relevant state's requirements.