Why Is My Yardi Bank Reconciliation Not Balancing? How to Find the Difference

Last updated July 2026.

A Yardi bank reconciliation will not balance when something sits on one side of the comparison and not the other. The Difference field is the gap between what the general ledger says about that bank code and what the bank statement says, and Yardi blocks posting until it reads zero. In practice the cause is almost always one of four things: a bank fee or interest entry that was never posted, a GL cutoff date pulling the wrong period, a deposit recorded twice or recorded but never banked, or a transposed digit in a keyed amount.

Why won't my Yardi bank reconciliation balance?

Yardi puts a GL column beside a Bank column. The GL side totals the cash accounts tied to the bank code, adjusted for book reconciling items. The Bank side starts from the ending balance you typed off the statement and adjusts for outstanding checks, deposits in transit, and bank reconciling items. When those two columns disagree, the difference is a real transaction that exists in one place and not the other. It is not a rounding quirk and it will not resolve itself.

The reason it feels hard is that one side of the comparison is data you can query and the other side is a PDF you have to read. That asymmetry is what turns a five minute check into an afternoon.

Check the GL cutoff date before anything else

This is the fastest win and the most commonly missed one. If the GL cutoff date does not match the statement end date, Yardi includes transactions from a period the statement does not cover, and every total looks wrong even though every individual entry is correct. Reset the cutoff to the statement closing date, resubmit, and see whether the difference survives. A surprising share of stuck reconciliations end right there.

The related trap is a transaction posted to the wrong accounting period. If someone dated a rent receipt into next month, it will not appear where you expect it, and no amount of clearing items will close the gap.

The differences that explain most stuck Yardi bank recs

Before hunting line by line, look at the shape of the number. The amount itself usually tells you what kind of error you are dealing with.

How to find the difference in minutes instead of hours

The reliable method is to stop reading and start comparing. Get both sides into columns and let a formula do the matching.

1. Get the statement into rows. Export the bank data if your bank publishes a treasury file, or convert the statement PDF to Excel so every deposit, check, and fee becomes a dated row with an amount and a running balance.
2. Export the Yardi side. Pull the transaction list for the same bank code and the same GL cutoff period.
3. Match on amount and date. A lookup formula across the two amount columns flags everything that appears on one side and not the other. Those flagged rows are your entire problem set.
4. Total each side. If the sum of the flagged items equals your difference, you have found all of it. If it does not, you are missing a whole category, usually fees or an uncleared prior period item.
5. Post and clear. Enter the genuine bank items you had not recorded, clear the matched ones, and the Difference field should drop to zero.

The running balance column is the part people skip and then regret. It is what lets you confirm you captured every line on the statement rather than most of them, because the last row has to equal the ending balance you typed into Yardi.

What is the difference between a bank reconciling item and a book reconciling item?

A bank reconciling item is an adjustment to the bank side, used when the statement itself is wrong or incomplete, such as a deposit the bank credited to the wrong account. A book reconciling item is an adjustment to the general ledger side, used when Yardi holds the incorrect figure and needs correcting. Choosing the wrong one moves the difference in the wrong direction, which is why a reconciliation sometimes gets further from zero after an adjustment rather than closer.

Why Automatic Bank Reconciliation still leaves you with a difference

Automatic Bank Reconciliation imports a BAI2 file from the bank and clears the transactions that match the ledger on amount, date, and reference. It is genuinely useful on a high volume operating account. What it does not do is resolve exceptions, and exceptions are the entire reason a reconciliation fails to balance. The items the engine cannot match are precisely the ones with a keying error, a missing posting, or a timing difference.

There is a second limitation worth planning around. Automatic Bank Reconciliation only works where the bank supplies BAI2 on a schedule. Plenty of community banks and credit unions publish nothing but a PDF statement, and some larger banks charge for the SFTP delivery. For those accounts, and for any period before the arrangement started, the PDF is your only source and the comparison is manual either way.

Stale outstanding checks quietly break the next close

Checks that were issued and never presented sit in the outstanding list indefinitely. Individually they are harmless. Collectively they make the outstanding total unreadable, and they hide the one genuine reconciling item you are looking for. Age the list at least quarterly, chase anything past 90 days, and void or escheat under your state's unclaimed property rules rather than letting the list grow. A reconciliation with four outstanding checks is auditable. One with four hundred is not.

Trust accounts raise the bar

Property management runs client money, so the standard is exact, every month, per bank code. Most states require a three way trust account reconciliation so that funds held for owners and tenants reconcile precisely and that no individual property goes negative inside a pooled account. That means each operating, security deposit, escrow, and reserve account reconciles on its own rather than in aggregate, and it means being able to prove the position for a single owner or association on request. Once the statement is a spreadsheet, that proof is a filter rather than an afternoon of paging through PDFs, and the same file feeds the owner statements and the year end schedules. Teams that need the finished ledger presented as board ready reports often push the reconciled data straight into a tool that builds GAAP style financial statements rather than formatting them by hand.

When a previously reconciled month stops balancing

If last month tied out and now it does not, someone edited or deleted a transaction inside a closed period. Do not try to force the current month to absorb it. Go back, re-tie the earlier month, and work forward. Locking closed periods once they are reconciled prevents the problem from recurring, and it is the single control that saves the most time over a year.

The practical takeaway

Most stuck Yardi reconciliations are not complicated, they are just tedious to search. Check the GL cutoff date, read the shape of the difference, then get both sides into columns so a formula does the matching. The accounts that cause the most pain are the ones without a bank file, and those are exactly the ones where converting the statement changes the job from reading to comparing. The same approach works whether you are closing a single association account in Breeze or dozens of bank codes in Voyager.