Bank reconciliation for property managers breaks when the bank feed pulls some transactions and skips others. Auto matching then fails, and the accountant ends up reviewing every line by hand. URBI approaches reconciliation differently, and the procedure below will close your month on any platform you already use.
Why do bank feeds miss transactions?
Bank feeds miss transactions because they are a copy of the bank's activity, not the bank itself. The feed is a nightly file pulled through an aggregator, and every step between bank and ledger can drop a line. Each failure mode needs a different fix.
- Timing. The feed reports the posted date, your ledger the transaction date. A deposit made Friday posts Monday, so it sits in your books and not on the statement. That is not an error and is never adjusted away.
- Description formats. Matching rules key on memo text. Banks reformat descriptors without warning, and a processor that changes its merchant descriptor silently breaks every rule built on the old one.
- Awkward transaction types. Cleared debits and credits usually arrive. Returned items, chargebacks, reversals, wire fees, and bank adjustments arrive late, arrive as a different type, or never arrive.
- Multiple accounts. Operating, trust rent, deposit, and reserve accounts each need their own connection. When only some are connected, a transfer between two appears once instead of twice.
- Batch deposits. The bank sees one deposit. Your ledger holds twenty resident payments. A matcher seeking one line of that amount finds nothing: the relationship is one to many.
- Outages and expired connections. Feeds break when a bank changes its login flow or asks for a new security code, and stop quietly. Most backfill only a limited window, so a gap caught weeks later may never fill.
What do accountants actually report about this?
Accountants describe the same sequence across platforms: the feed is inconsistent, auto reconciliation cannot match what is not there, and the fallback is manual review. These are individual accounts, not a measure of frequency, and each reviewer also praised the product.
An Accountant and Lease Administrator writing about Buildium on Capterra in May 2026 wrote that the "bank feed, is not consistent, some charges come through and some does not," then described reviewing every transaction manually. The same review called the platform user friendly and praised its reporting and bill payment.
An Accounting Assistant writing about Yardi Breeze on Capterra in March 2026 reported that "Sometimes it gets laggy or slow. Especially during peak seasons, like month ends." The same reviewer praised the simple interface and easily found functions. A small delay per line becomes hours when line counts peak.
An Accounting Manager writing about AppFolio on G2 in April 2026 noted that "integration with other systems like QuickBooks Online is limited," making a redundant accounting workflow harder to build. The same reviewer credited the product with centralizing accounting, reporting, and property management in one place.
None of this tells you the current state of any product. Treat it as a list of things to test on a demo, with your own bank and statement. Reconciliation is a workflow problem, so the procedure below is platform independent.
How do you run a month end bank reconciliation that actually closes?
You run it in a fixed order, and the order is the method. Most reconciliations that take days took days because someone skipped step two, then hunted a variance that was already there. You need a statement, a ledger, and a spreadsheet.
1. Set a cutoff and hold it
Pick the statement end date and stop entering transactions dated on or before it. Anything arriving afterward belongs to next period, however urgent. Download the statement as a PDF for the balances you sign off on, and a CSV for sorting.
2. Prove the opening balance before anything else
Your prior period reconciled ending balance must equal this statement's opening balance. If it does not, stop. Something was posted, edited, or deleted in a period you already closed, and time spent on current month lines before you find it is wasted. This is the most commonly skipped step, and the most expensive to skip.
3. Tick and tie in both directions
Build two lists, not one. List A is every bank line with no matching book entry. List B is every book entry with no matching bank line. Sort both by amount, largest first: large items resolve fastest and often explain smaller ones. What remains is your exception list.
4. Categorize every exception before adjusting anything
Each exception is one of four things, and only two of them get a journal entry:
| Category | What it looks like | What you do |
|---|---|---|
| Timing | Deposit in transit, outstanding check | Nothing. It goes on the reconciling schedule, not into an entry |
| Missing book entry | Bank fee, interest, NSF return, automatic debit | Post it, dated the bank's date |
| Error | Wrong amount, wrong property, transposed digits | Correct it forward as a new entry. Never edit history |
| Unknown | You cannot explain it | Escalate. Do not close around it |
One shortcut earns its place: if your variance divides evenly by nine, you probably transposed two digits.
5. Run the equation
Bank ending balance, plus deposits in transit, minus outstanding checks, plus or minus bank errors, gives the adjusted bank balance. Book balance, plus credits not recorded, minus debits not recorded, gives the adjusted book balance. The two must be equal. If not, the month is not closed.
What are the rules for unmatched deposits and outstanding checks?
These two cause most of the damage, so each gets a rule that never bends.
Never plug a deposit, always trace it. A deposit with no book entry is a batch of resident payments, an owner contribution, an interest credit, a reversal, or income posted to the wrong property. Each has a document behind it, a deposit slip or a settlement report, and you trace it there first. A batch must equal the sum of a nameable set of ledger receipts around that date. Posting it to miscellaneous income instead is how revenue lands on the wrong property's financial statements.
Age outstanding checks, never delete them. A check you wrote that has not cleared is a reconciling item, not a missing transaction, and stays on the list until it clears. Keep a schedule with issue date, check number, payee, and amount, and review by age:
- Under 30 days. Normal. Leave it.
- 30 to 90 days. Contact the payee. A vendor who has not deposited a check usually never received it, and the address on file is often why.
- Beyond 90 days. Escalate to a decision. Many banks will not honor a check months after issue.
Never void an old check by deleting the original entry. If the payee still holds it, you have erased a real obligation while the liability still exists. Reissue with a stop payment instead. Long uncashed items raise unclaimed property questions that vary by state, so confirm treatment with your accountant.
What should you escalate instead of solving?
Escalate anything suggesting a problem larger than the line in front of you:
- A trust or deposit account holding less than the deposits you owe. That is a shortfall, not a reconciling item, and it goes up the same day. Most US jurisdictions treat trust accounting shortfalls as serious.
- Any unexplained variance, however small. It is usually the visible edge of a systematic problem. Rounding does not produce variances in double entry books.
- Any prior period balance that moved. Find out who and how before closing another period on top.
- Any transaction nobody authorized. That is a fraud question, not an accounting one. Notify the bank first.
- Any feed gap older than the backfill window. If the feed will not retrieve it, someone must enter it manually, and that needs assigning.
Never force a balance by plugging the difference to a suspense account, matching unrelated items, or deleting a transaction. All three work once and cost you next month.
What should you ask when you demo any platform?
Ask about mechanics, not features, and bring your own statement:
| Question to ask | Why it matters |
|---|---|
| How far back does the feed backfill after a break? | Whether a missed gap can ever self repair |
| Can one bank deposit match many ledger receipts? | Batch deposits are the most common unmatched item |
| Can I close one bank account without the others? | A blocked trust account should not hold up operating close |
| Who do I reach at close when the feed is down? | Support access is a close blocking dependency |
Where does URBI fit?
URBI Accounting is In Beta, so treat this as what to evaluate rather than a finished claim. It is a full double entry engine, and matching runs in three passes: deterministic rules you define, then algorithmic matching on amount and date, then HERO AI reasoning on what is left. Only your own rules match without a person, and HERO proposes rather than posts.
Two design choices matter here. Close runs per bank account rather than all at once, so one problem account does not block the whole month end close. The QuickBooks Online sync is two way with echo suppression, so nothing books twice. There is more in our pieces on AI bank reconciliation, QuickBooks for condo accounting, and URBI for residential buildings.
Frequently asked questions
Is a deposit in transit the same as a missing transaction?
No, and confusing the two is the most common reconciliation mistake. A deposit in transit is recorded in your books, dated before the cutoff, and has not reached the statement yet. It is a reconciling item needing no journal entry. A missing transaction exists at the bank but never entered your books, and that one does need an entry.
How long should a month end bank reconciliation take?
It depends on your exception count, not your transaction count. A portfolio with clean feeds and a held cutoff reconciles an account in under an hour, because most lines match without review. The same portfolio after a broken feed connection takes days. That is why proving the opening balance first matters.
What if the bank feed misses transactions every month?
Then treat it as a connection problem, not a reconciliation problem. Check whether every account is connected separately, whether the connection needs a fresh login, and whether the missing items share a type such as returns or transfers. A consistent pattern usually points at one fixable cause, worth documenting for a full cycle before you raise it.
Reconciliation is one of the few property accounting tasks where a disciplined manual procedure beats a weak automated one, so it is worth writing down whatever you run it on. To see how URBI handles matching and per account close on your own books, email hello@myurbi.co.
