AppFolio Cleanup After a Messy Go-Live: How Opening Balance Errors Wreck Your Reconciliation

Most AppFolio reconciliation problems do not start with this month's transactions.

They usually start at go-live.

We see it all the time: a property manager moves into AppFolio, the opening balances get rushed, old bank activity gets imported inconsistently, and a few "temporary" journal entries are used to force things into place. The system goes live, everyone moves on, and then the real pain starts later.

Now the bank reconciliation keeps breaking. Adjusted cash does not make sense. Old uncleared items never go away. Security deposit balances feel off. Every month becomes a new version of the same cleanup.

If that sounds familiar, there is a good chance the real issue is not your current bookkeeping. It is the foundation you started from.

What a Messy AppFolio Go-Live Usually Looks Like

A messy go-live is not always obvious on day one. In fact, it often looks "good enough" at first.

The books may appear close. The balances may seem reasonable at a high level. Reports may even tie out well enough to keep moving.

But under the surface, we usually find one or more of these problems:

• Opening bank balances entered incorrectly
• Stale uncleared transactions brought over without context
• Duplicate transactions from imports or manual entry
• Security deposit liabilities loaded inconsistently
• Owner balances or prepaid rent entered to the wrong accounts
• Journal entries used to force reports to match instead of fixing the source issue
• Prior-period cleanup pushed into the current month without a clear audit trail

That is when reconciliation stops being a monthly process and starts becoming a monthly mystery.

How Opening Balance Errors Show Up Later

Opening balance issues rarely stay isolated.

Once the wrong numbers are in AppFolio, every month after that gets harder to trust.

Here is how it usually shows up:

The Reconciliation Technically Closes, but Something Still Feels Off

This is one of the biggest red flags.

Someone gets the bank rec to finish, but the process only works because they are adjusting around old issues. The reconciliation may be marked complete, but the underlying books are still wrong.

Old Uncleared Items Never Go Away

If transactions were loaded incorrectly during go-live, they can sit on the reconciliation for months. People start ignoring them because "they've always been there," which usually means the real issue never got resolved.

Journal Entries Start Piling Up

When the starting point is wrong, teams often patch the symptoms instead of fixing the source. A few cleanup entries turn into a recurring habit. Before long, the general ledger is doing too much heavy lifting for a bank rec problem.

Trust and Operating Cash Stop Making Intuitive Sense

You should be able to explain why cash is what it is. When opening balances are wrong, even experienced operators lose confidence in what they are looking at. That is especially dangerous in trust accounting.

Why Quick Fixes Usually Make It Worse

This is the trap.

When reconciliations are under pressure, the temptation is to make the report work right now and ask questions later. That usually means:

• Adding a journal entry to offset a difference
• Clearing an item without proving what it is
• Reclassing activity into a different account to make the rec move
• Carrying unexplained differences forward

The problem is that these fixes do not remove the original error. They bury it.

Then next month's reconciliation inherits both the original problem and the workaround.

That is how a go-live issue turns into a long-term reporting issue.

What to Check First

If you suspect the problem started during implementation, start here:

Compare the opening bank balance to the real bank balance. Go back to the go-live date and verify what the actual cleared balance should have been. Do not assume the imported number was right.

Review uncleared transactions from the first reconciliation period. Look for items that should never have been carried in as open, duplicates that got entered twice, or transactions posted with the wrong date.

Inspect early cleanup journal entries. If the first few months contain unusual journal entries, especially ones hitting cash or reconciliation-related accounts, that is worth slowing down and understanding.

Review related balances, not just the bank rec. If security deposits, prepaid rent, owner funds, or intercompany balances were loaded incorrectly, the bank rec may just be where the pain shows up first.

How to Clean It Up the Right Way

In most cases, the right fix is not "do another reconciliation."

It is:

1. 1Identify the true starting error
2. 2Separate opening balance issues from current-period activity
3. 3Remove duplicate or unsupported entries
4. 4Correct the ledger with a clean, documented approach
5. 5Rebuild trust in the reconciliation from a known-good point

Sometimes that means going back further than anyone wants to. But if the base is wrong, moving faster just spreads the problem around.

When It Is Time for a Real Reset

If your team is saying things like:

• "It has been off since conversion"
• "We just book an adjustment every month"
• "No one really knows what this old item is"
• "The rec closes, but the reports still do not feel right"

Then it is probably time to stop patching and do a proper cleanup.

That does not always mean starting over completely. But it does mean treating the issue like a structural problem, not a monthly one.

A clean AppFolio reconciliation depends on clean setup. If go-live was rushed or messy, the fix is usually not more force. It is better diagnosis.

---

If your AppFolio reconciliation has felt off since go-live, we can help clean up the foundation. PM Bookkeeper works inside AppFolio to untangle opening balance issues, fix broken reconciliations, and get your books back to a place you can trust. Get a quote and let's take a look.