Trust accounting sounds like an accountant problem right up until it becomes your problem.
Then it's the 1st, four spreadsheets are open, the bank balance doesn't match the ledger, an owner is asking where their money is, and somebody is trying to remember whether that security deposit was ever refunded.
None of that is a math problem. It's a bookkeeping-structure problem, and structure is learnable. Here's the version without the jargon.
Not legal or accounting advice. Rules vary by state and country, so confirm the specifics with your accountant or attorney.
The one idea underneath all of it
Money you hold for someone else is not your money, even while it's in your account.
Guest payments, owner funds, and security deposits pass through your hands on the way to somebody else. Your management fee is yours. Everything else is held in trust, and the whole discipline exists to keep those two categories from touching.
Most jurisdictions with a licensing regime say some version of the same thing: hold client funds in a designated account, don't commingle them with operating funds, keep records that let anyone reconstruct whose money is whose at any moment, and be able to prove it on demand.
Everything below is just how you keep that promise without losing your mind.
The four things that have to stay separate
Operating money. Your fees, your payroll, your software, your rent. This is the account you run your business from.
Client or trust funds. Guest payments before they're disbursed, owner funds awaiting payout, and money collected for owner expenses. It sits in a designated account and it is never used to cover your own costs, even temporarily, even with a plan to put it back.
Security deposits. Often a separate bucket with its own rules about interest and timing. Treat them as untouchable until the stay is closed and the claim window has passed.
Taxes collected. Lodging and occupancy taxes are somebody else's money too. Collected, held, remitted. Not revenue, not float.
The classic mistake isn't fraud. It's a manager covering a vendor invoice out of the trust account on a Friday because payroll cleared and the operating balance is thin. Even paid back on Monday, that's commingling, and it's the finding that turns a routine audit into a bad month.
The paper trail auditors ask for
If someone shows up asking questions, they want to see the same handful of things.
A three-way reconciliation. Bank balance, ledger balance, and the sum of every owner's individual balance all agree. If your system can't produce the third number instantly, month-end will always be manual.
A ledger per owner and per property. Not one big account with a memo field. Individual balances that roll up.
Source documents. Invoices, receipts, contracts, signed agreements, refund records. Attached to the transaction, not in a folder somebody has to go find.
A clean audit history. Who changed what, when. Deleted transactions are a red flag; voided ones with a reason are normal.
Disbursement records. What went out, to whom, when, and what it was for.
Notice that every one of those is a byproduct of good structure, not a report you build. If you are building them, you are doing bookkeeping twice.
Why the 1st feels like a deposition
The panic almost always comes from the same root cause: the money moved in one system and got recorded in another.
Payments happen in a processor. Reservations live in the PMS. Expenses live in a spreadsheet, or in QuickBooks, entered by hand later. Payouts get built in a fourth place. Nothing is wrong on purpose, but nothing agrees automatically either, so every close is a reconciliation project that starts from scratch.
A short list of the usual culprits:
- Refunds and partial refunds recorded on the payment side but never against the owner's ledger.
- Chargebacks that arrive weeks later, after the payout already went out.
- Adjustments made to a reservation total without a matching ledger entry.
- Owner expenses paid from operating and reimbursed inconsistently.
- Deposits released early because the stay "looked fine."
Each one is small. Together they're the reason nobody trusts the number until it's been checked twice.
What good looks like
You don't need a bigger spreadsheet. You need fewer places for the same dollar to exist.
When payments, ledgers, and payouts share one system of record, a few things become true at once. Every charge, refund, and fee posts to the right ledger the moment it happens. Owner balances are live, not assembled. Reconciliation is a check, not a build. Chargebacks land with the documentation already attached, because IDs, e-signatures, and IP records were captured at booking instead of hunted for later.
Then month-end becomes a review instead of an investigation. You look at the reconciliation, you confirm it ties, you disburse, and you go home.
A month-end sequence that works
Same order, every period. Boring is the goal.
- Post everything. All charges, refunds, fees, and expenses through the last day.
- Clear the exceptions. Failed payments, open disputes, unapplied credits, pending deposits.
- Run the three-way reconciliation. Bank, ledger, and the sum of owner balances agree, or you stop and find the difference now instead of after payout.
- Review owner statements. Net first, plain line-item names, comparison to last period.
- Disburse, and record it. Same day each period so owners can plan.
- Remit taxes on their own schedule, from the taxes-collected bucket.
- Close the period so nobody edits history quietly.
Do that seven-step loop the same way every month and the 1st stops being an event. It's a Tuesday.
The real payoff
Clean trust accounting isn't about surviving an audit, though it does that.
It's that you can answer any money question in under a minute. Owners get paid on a date they can predict. Nobody on your team is afraid of the ledger. And when you buy a portfolio or open a market, the books don't become the bottleneck.
Chargebacks, meet paper trail.
Want month-end to be a review instead of a rescue?
See how Direct handles payments, ledgers, and payouts in one system of record.
