Wanderwares
ResearchMSP
Run the PM Automation Leak Audit

Property Management Research

Security Deposit Ledger Exceptions Before Move-Out Accounting

The refund calculation happens at move-out, but the difficult work starts earlier: finding and clearing the ledger, evidence, and ownership exceptions that can make an automated disposition wrong.

September 3, 2026·~8 min read·Research note

Methodology and caveat

Methodology

This article combines current regulator guidance from Oregon and California, a New York enforcement example, official Buildium product and training material, and one current public operator discussion about Yardi. The regulator sources show the control and documentation requirements; the vendor sources show real automation progress; the operator discussion is a single experience, not prevalence data. Requirements vary by jurisdiction and portfolio, so the analysis maps workflow risk rather than giving legal or accounting advice.

The work starts before move-out

Security-deposit accounting is often described as a final calculation: subtract permitted charges from the deposit and refund the balance. Operationally, that calculation is only the last step. Before a manager can trust it, the deposit recorded on the tenant ledger must agree with the liability and the cash being held, all relevant charges must be posted to the correct lease, and the file must contain enough evidence to support each deduction.

Oregon's Real Estate Agency makes the control structure explicit. It says security-deposit accounts must be reconciled monthly by comparing the adjusted bank balance, the receipts-and-disbursements record or check register, and the sum of individual security-deposit balances. The property manager or principal broker must review and approve the reconciliation.1 This is one state's rule, not a national standard, but it illustrates why a clean tenant ledger matters before anyone begins a move-out disposition.

Buildium's description of the tenant ledger reaches the same operational endpoint from the software side. The ledger carries charges, payments, adjustments, deposits, and the running balance through the lease. At move-out it should show the original deposit, deductions, explanations, and final refund amount.2 If an earlier receipt was misapplied, a transfer was recorded against the wrong unit, or an adjustment lacks context, the disposition workflow inherits the problem.

The pre-disposition exception queue

The hidden queue appears when the system has a lease and a deposit balance but not yet a complete, defensible instruction for what to do with the money. Different teams often own different inputs: site staff complete the inspection, maintenance gathers estimates or invoices, accounting reviews the ledger, and the resident provides a forwarding address or electronic refund details. The PMS can calculate from posted data; it cannot safely assume that missing data means zero.

Workflow

System handles
Exception
Human required

Confirm deposit ownership and ledger balance

Verify the amount held, account location, lease, unit, and whether the manager or owner holds the funds.

Assemble final charges and evidence

Connect inspection findings, invoices or estimates, photos, unpaid rent, and final utilities to the correct tenant.

Exception review

Deposit balance disagrees across ledger, liability, and bank records

Owner-held funds are not available in the manager's trust account

Inspection charge lacks an invoice, estimate, or supporting detail

Late utility or vendor charge arrives after the draft disposition

Forwarding or refund instructions are missing

Approve disposition and create refund

A human confirms permitted deductions, evidence, timing, and the destination of any remaining balance.

Zero the deposit liability and preserve the audit trail

The automation boundary

A PMS can apply posted charges and create a payable. The unresolved work is deciding whether every required charge and document has arrived, whether the underlying ledger is trustworthy, and whether the proposed disposition is allowed and explainable.

Deadlines turn small gaps into operational risk

Incomplete information becomes more expensive when the refund clock is running. California Courts says a landlord generally has 21 days after move-out to return the deposit or send the remainder with an itemized statement. When deductions exceed $125, invoices or receipts generally must accompany the statement; if repairs are unfinished for a good reason, the landlord may use a good-faith estimate and later send receipts.3 That structure creates a dependency chain between inspection, vendor documentation, accounting, and resident communication.

Illustrative deadline

21 days

California's general post-move-out window for returning the deposit or sending an itemized disposition. Other jurisdictions differ, so automation needs property-specific rules rather than one universal timer.[[3]]

The consequence is not theoretical. In a 2022 enforcement action, the New York Attorney General said a property company failed to return deposits or provide itemized lists within the state's 14-day window for 129 tenants, resulting in an agreement to return about $296,000, train staff, and pay a penalty.4 The case does not prove how common the problem is. It does show that a missed operational handoff can become a material compliance and customer-trust failure.

  • A missing invoice can block a deduction or force an estimate-and-follow-up workflow.
  • A late final utility charge can reopen a ledger after the draft statement is prepared.
  • An owner-held deposit can make the ledger look complete while the manager still lacks control of the cash.
  • An unposted credit or prior adjustment can change both the refund and the resident's final balance.
  • A missing forwarding address or refund election can delay delivery even after accounting is complete.

Counterevidence: software is doing more

Run the PM Automation Leak Audit

It would be inaccurate to frame this as a missing PMS feature. Buildium offers a dedicated move-in and move-out course covering receipt, withholding, refund, prepaid rent, and deposits held by a rental owner.5 A current Yardi operator discussion likewise describes a distinct Deposit Accounting step that can apply open charges and automatically create a refund payable after move-out; the operator still has to complete the process and issue the payment.6 These are meaningful capabilities, not spreadsheet substitutes in name only.

The nuance is that transaction automation works best once the case is ready. Software can post, calculate, generate a payable, and maintain an audit trail. It does not know by itself whether the inspection is complete, whether a vendor's invoice is still outstanding, whether an owner-held balance is actually recoverable, or whether a manual adjustment represents a valid correction. The operator's job shifts from arithmetic and data entry toward evidence completeness and exception review.

The latest operator question is also useful precisely because it is modest: someone using a mature enterprise system still needed to confirm whether move-out alone created the refund or whether a second accounting function was required.6 That is not evidence that Yardi is deficient. It is evidence that workflow state, permissions, training, and human handoffs remain part of the control surface even when the accounting engine is capable.

A safer automation pattern

The safest automation target is not an autonomous decision to keep or return tenant money. It is a pre-disposition readiness check that continuously asks whether the case contains the inputs a reviewer needs. The system can flag disagreements, request missing artifacts, calculate time remaining under the configured jurisdiction, and prepare a review packet without deciding contested facts.

  • Reconcile deposit held, tenant sub-ledger, liability account, and bank or owner-held status.
  • Confirm that inspection completion, charge coding, and supporting evidence are present.
  • Track vendor estimates that must later be replaced or supplemented by final receipts.
  • Watch moved-out residents with nonzero deposit balances or refund payables that have not been issued.
  • Escalate cases by configured deadline and amount while preserving human approval for deductions and adjustments.

Design principle

Automate evidence gathering, reconciliation checks, timers, and follow-up. Keep judgment over disputed damage, allowable deductions, and trust-fund corrections with an authorized reviewer.

What this means for Wanderwares

For Wanderwares, the practical opportunity sits one layer above the PMS ledger. A useful automation should detect which upcoming move-outs are not disposition-ready, explain why, assign the missing input to the correct person, and keep the case moving until an authorized reviewer can approve it. The PMS remains the financial system of record; the automation becomes the exception coordinator.

A pilot should measure readiness lead time, exception age, number of manual touches, cases completed before the configured deadline, and the share of draft dispositions reopened because new evidence arrived. Those measures reveal whether automation is reducing avoidable coordination without pretending that every deduction can be decided by a rule.

Run the PM Automation Leak Audit

Sources

  1. [1]Maintain Clients' Trust Accounts - Oregon Real Estate Agency
  2. [2]Tenant Ledger - Buildium
  3. [3]Guide to security deposits in California - California Courts
  4. [4]Attorney General James Recovers Nearly $300,000 of Illegally Withheld Security Deposits for Brooklyn Tenants - Office of the New York Attorney General
  5. [5]Move-ins and Move-outs for Rentals - Buildium
  6. [6]Move out - Reddit r/yardi

Based on publicly available regulator guidance, enforcement material, vendor documentation, and one operator discussion. Requirements vary by jurisdiction and portfolio. This article is operational research, not legal, accounting, or compliance advice.

← See all research
Wanderwares

Find the manual work your business software leaves behind.

Product

PM Automation Audit

Company

ResearchMSP Automation

Contact

luigi@trywanderwares.com
2026 Wanderwares. All rights reserved.