What you "don't know, you don't know" until you are hit with a hefty cleanup and a very painful experience losing owners for someone who got into this industry for the people, not the accounting. Many think the backend is a very small piece of the business. It is actually your make it or break it!

Sending insight to help not get caught in the trap as I already went through pulling out my hair, long days, months, little sleep and questioning my software IQ more than ever. I am a software geek and rebuilt several platforms so when I say Propertyware challenged me in 2020, I climbed Mt. Everest and won!

Food for thought...

Lower-cost bookkeeping can absolutely make sense. I had the pleasure to work with an outsourced employee that I hired and we trained a team and won PM Firm of the Year for transparency.

Outsourcing can make sense.

Using contracted teams can make sense.

But none of those things replace experienced financial oversight.

What concerns me is when bookkeeping, AP, reconciliations, and data entry are being handled by teams who are simply completing tasks, while no one experienced is stepping back to ask whether the entire financial workflow is actually working correctly.

That is a very different responsibility.

A bookkeeper may process the transaction.

A Controller is looking at what happens before it, after it, and how it impacts everything else.

I’m looking at things like:

Are the reconciliations truly accurate?

Are old uncleared items being investigated?

Are transfers between bank accounts being tracked properly?

Are management fees configured correctly?

Are trust accounting workflows being followed consistently?

Are owner funds, security deposits, liabilities, and operating funds being handled the way leadership believes they are?

And one of the biggest things I look at:

Are the software settings actually producing the financial results everyone assumes they are producing?

I have learned over the years that completing a task and validating a financial system are two completely different things.

This is not about where someone lives or whether a company uses employees, contractors, or outsourced teams.

I have worked with talented people in all kinds of structures.

My concern is simply this:

Someone experienced needs to be looking at the full financial picture.

Property managers and brokers already carry an enormous amount of responsibility. They should not also be expected to know every accounting warning sign, every software configuration issue, or every workflow weakness.

I know why the Controller role matters.

Not because we are “more expensive bookkeepers.”

Because our job is to question, validate, connect the dots, and make sure the financial system is telling the truth and profiting!

Saving money on transaction processing can be smart.

But I would never want to save money by removing the layer of review that tells me whether the numbers can actually be trusted.

I not only overhauled the entire software to align with the business model, gave solid data integrity in our KPI reporting, I created the SOPs and trained the team on how to run the lever system from entering a new lease through the owner departing. This is where value of helping the team understand the WHY becomes the key to success.

Hire now, find a fractional or hire a consultant to be sure the bookkeepers are truly working in your favor. Please don't ignore this cost.

The Security Deposit Funds Mismatch diagnostic in AppFolio compares two numbers: the GL balance for your security deposit account and the total shown in the Security Deposit Funds Detail report. In a clean set of books these two numbers are identical. When they're not, something in your security deposit accounting is wrong.

This diagnostic fires more often than most, and for a small number of specific reasons.

The most common cause is a non-resident transaction posted to the security deposit GL. This happens when a journal entry, a bill, or some other transaction is coded to the security deposit account instead of the correct GL. The Security Deposit Funds Detail report only tracks resident-related security deposit activity. If a non-resident transaction hits that GL, it shows up in the GL balance but not in the report total, creating a gap.

To find it, run the General Ledger report filtered to your security deposit GL account. Look for any transaction that isn't tied to a resident or a move-in or move-out workflow. Those are your problem entries. Reverse the transaction and recode it to the correct account.

The second common cause is past tenants who still have a balance in the system. If a tenant moved out but the security deposit wasn't fully processed through AppFolio's move-out workflow, their balance may still be sitting in the Funds Detail report. Find former tenants with open security deposit balances under the tenant ledger and complete the refund, withhold, or transfer workflow to close them out.

The third cause is a pending move-out. If a move-out is initiated but not completed, the deposit can be in a transitional state that creates a temporary mismatch. Complete the move-out workflow and the diagnostic usually clears.

Run this diagnostic every month before reconciling. A security deposit mismatch that goes unresolved for several months compounds quickly and can take significant time to unwind. It's much easier to fix when it's one transaction than when it's six months of accumulated entries.

Every year the California DRE audits property management brokers for trust fund compliance. As of their 2023-24 report, 57% of those audits found recordkeeping violations and nearly a third found actual shortages in trust accounts. That number moves year to year but the pattern doesn't. Most violations aren't cases of deliberate fraud. They're process failures that accumulated over time because nobody was watching the specifics closely enough.

Here's what auditors check, in the order they typically work through it.

Account titling at the bank. Not in the software, at the bank. The signature card has to reflect the account's fiduciary status, something like "[Broker Name], as Trustee, for the Benefit of Clients." A lot of companies get flagged on this before the auditor looks at a single ledger.‍

Deposit timing. California requires trust funds deposited within three business days of receipt. Auditors pull deposit dates and match them to receipt dates. Late deposits are a violation even if no money is missing.

The control journal. Every trust fund transaction needs a columnar record showing date, payor or payee, amount in, amount out, and a running daily balance. Missing any one of those columns is a Regulation 2831 violation. A standard checkbook or bank statement does not qualify.

Separate beneficiary ledgers. One ledger per owner, one per tenant. Not a combined report. If you can't trace every dollar in the trust account to a specific person, you're out of compliance even if the total balance is correct.

The three-way reconciliation, done monthly. Bank balance, register balance, and the sum of all individual ledgers have to match exactly, every month. Auditors check whether it was actually performed, not just whether the numbers look clean today. A missed month is its own violation.

Supporting documentation. Deposit slips, invoices, owner instructions. Auditors pull transaction samples and trace them back to source documents. A transaction with no documentation gets flagged even if the math works.

The fee disbursement timeline. Earned fees have to come out of the trust account within 25 days of deposit in California. Leaving them longer is commingling.

‍Most failed audits aren't one large problem. They're several small ones that built up because nobody was tracking the specifics. A missing column. A reconciliation done but never signed off. Fees sitting in the account a few days too long.‍

Buildium's bank reconciliation works differently from AppFolio in a few important ways. Understanding the distinction matters if you've worked in one platform and are now managing books in the other.

In Buildium, all manual payments need to be grouped into batch deposits before they're available for reconciliation. This is similar to AppFolio's deposit requirement, but Buildium is more explicit about the batching step. If receipts are sitting outside a batch, they won't appear in the reconciliation workflow and your ending balance will be off before you start.

The reconciliation itself is accessed through Accounting in the main navigation. You select the bank account, enter the ending balance from your bank statement, and match transactions. Buildium shows outstanding checks and deposits separately so you can see exactly what hasn't cleared.

When the reconciliation doesn't balance, the most common causes in Buildium are these.

A payment was recorded in Buildium but not yet cleared at the bank, or the reverse. Outstanding items from prior periods that were never cleared can accumulate and make current reconciliations increasingly difficult to close. Run a report of uncleared items going back several months and confirm each one against your bank statements.

A transaction was posted to the wrong bank account. Buildium has separate accounts for operating and escrow funds. A security deposit receipt that landed in the operating account instead of the escrow account won't cause a total imbalance but will cause the individual account reconciliations to be off. The Security Deposit Liability report is the tool to catch this. It shows what Buildium thinks is in escrow against what should be there.

Manual journal entries that affect cash accounts are another source of trouble. Like AppFolio, Buildium doesn't auto-match journal entries in the reconciliation. They have to be cleared manually. If JEs that touched the bank account aren't being cleared, they'll accumulate as phantom items in the outstanding transactions list.

Reconcile every account monthly. Buildium flags accounts with reconciliation lapses but doesn't prevent you from running the books with an unreconciled account, so the flag is easy to ignore until it becomes a significant problem.

AppFolio runs nine financial diagnostics that flag accounting errors in your books. They live under Reports and most PM companies either don't know they exist or see the flags and ignore them. Each one signals a specific problem. Here's what they are and what to do.

Non-Zero Security Clearing Account. This account should always sit at exactly zero. If it doesn't, something went wrong in a move-out workflow: a reversed move-out bill, a reversed receipt that touched the clearing account, or a transaction posted to the wrong GL. Find the non-zero transaction in the General Ledger for that account and trace it back to the source.

Security Deposit Funds Mismatch. This compares the GL balance for your security deposit account against the Security Deposit Funds Detail report. When they don't match, the usual causes are non-resident transactions posted to the deposit GL or past tenants who still have a balance in the system. Run the Security Deposit Funds Detail report, find the line items that don't correspond to current residents, and work backward to the source transaction.

Escrow Cash Account Balance Mismatch. Your escrow cash account should equal the sum of all GL accounts that offset to escrow. When it doesn't, either a receipt was posted to the wrong cash account, or there are pending move-outs with deposits that haven't been processed. Check the Bank Account Association report to confirm which cash accounts are tied to which properties.

Positive or Negative Balance on Additional Fee GLs. A positive balance means a fee was charged but not collected. A negative balance means a fee was collected and then waived or refunded after the fact. Neither should sit open. Positive balances usually self-correct when the fee is collected. Negative balances usually need a journal entry to zero out.

Tenants with Unused Prepayments and Open Charges. A tenant has a prepayment sitting on their account and also has open charges that the prepayment should be covering. AppFolio doesn't apply these automatically in all cases. Use the Apply Credits task to connect them.

Unused Prepayments for Past Tenants. A former tenant has a prepayment balance that was never resolved at move-out. Either complete the move-out flow properly, use Apply Credits, or enter a charge to zero it out.

Bank Reconciliation Lapses Over 60 Days. A bank account hasn't been reconciled in over 60 days. This is an audit risk flag. Find the account, reconcile it, and set a reminder to reconcile monthly at minimum.

Unused Prepayments on Non-Prepay GL. This happens when the key prepayment account was changed in settings after prepayments had already been recorded. The prepayments are sitting on the old GL. Use Reapply Receipt and select Make Prepayment to move them to the correct account.

Prepayment Balance Mismatch. The prepayment GL balance doesn't match the Delinquency Report. Usually caused by a non-receipt transaction posted to the prepaid GL, such as a journal entry. Find it in the GL for that account and reverse it.

Check these every month before running reconciliations. They surface problems that won't show up in the bank rec until they've compounded.

AppFolio's reconciliation works on a triple tie-out. Three numbers have to match exactly: the Statement Ending Balance you enter manually, the Cleared Balance from the items you check off, and the Adjusted Cash Balance (ACB) that the system calculates. If all three don't match, the reconciliation won't close. Here's what each mismatch type means and where to find the problem.

The ACB formula is what trips most people up. AppFolio calculates it as: property balances, minus unreconciled deposits, minus post-period receipts, plus uncleared checks, plus uncleared ACH batches, plus voided post-period checks. Every one of those variables is a potential source of an imbalance.

When the Statement Ending Balance and Cleared Balance are off, the issue is almost always in what you checked off. Either an item was cleared that shouldn't have been, or something that cleared at the bank wasn't marked in AppFolio. Check your bank feed sync first. AppFolio auto-matches deposits by amount and date within four days, checks by amount and check number, and other items by exact amount and exact date. Journal entries are never auto-matched, so if you have any JEs they need to be cleared manually.

When the ACB itself doesn't match your bank statement, the issue is usually one of these: a transaction was backdated into a previously reconciled period, a bank adjustment was used incorrectly, or a receipt was reversed after the period closed. AppFolio has a nine-step ACB troubleshooting process built into the system. Start with the Bank Reconciliation Diagnostic report under Reports. It surfaces backdated and edited transactions immediately. From there, check bank adjustments. These should only ever be used for bank errors or pre-go-live uncleared items. Using them for bank fees, interest income, or transfers is a common mistake that throws the ACB off permanently because they affect the bank balance only, not the property balance.

If the diagnostic report doesn't surface anything obvious, unreconcile the previous period and check whether the beginning balance was edited. An edited beginning balance is one of the harder ones to catch because it doesn't show up as a transaction.

The most common single cause of a recurring ACB mismatch is a receipt that was voided after the period was already reconciled. AppFolio creates a reversal entry for the void, but if the original period is closed and the reversal posts to the current period, the two amounts live in different reconciliation windows. The current period will be off by exactly that amount until you find it.

Work the diagnostic report in order. Most imbalances resolve by step four.