monthly cash reconciliation time for average accounting teams
47%
of real estate investment firms hold 200+ bank accounts
56%
of finance teams still reconcile bank accounts manually
6.4 days
median month-end close across all industries
Bank reconciliation in Yardi Voyager should take hours, not days. But for most property management teams, it's still the single biggest bottleneck in the month-end close. The culprits are almost always the same: bank accounts that weren't set up correctly, transactions that never made it to the general ledger, timing mismatches between GL cutoff dates and bank statement dates, and stale uncleared items that nobody investigates.
This guide walks through the most common Yardi bank reconciliation failures we see across multifamily, commercial, and mixed portfolios, explains what causes each one, and provides specific steps to fix them inside Voyager. We also cover Yardi's built-in Automatic Bank Reconciliation (ABR) module, which most Voyager clients already have access to but aren't using, and how to configure it to auto-clear 60–80% of your transactions every month.
Chapter 1
Why Bank Rec Is the Bottleneck Nobody Talks About
Bank reconciliation is the unglamorous foundation of property management accounting. Nobody gets excited about it. Nobody puts it in a conference keynote. But when it breaks, everything downstream breaks with it: financial reporting is delayed, owner distributions are held, debt covenant calculations are unreliable, and audit preparation becomes a scramble.
The numbers tell the story. Research from Numeric finds that cash reconciliation is cited as the most time-consuming component of the month-end close, consuming between 20 and 50 hours of the average accounting team's time each month. A survey by REdirect Consulting found that 47% of real estate investment firms hold more than 200 bank accounts each. At 30 minutes per account in a best-case scenario, that's 100 hours or more of manual reconciliation work every month. The same survey revealed that 64% of property management firms don't have a treasury management system in place to handle cash position reporting and reconciliation efficiently.
Meanwhile, a 2024 Airbase survey found that 56% of finance teams still reconcile manually. And according to APQC's benchmarking research, the median month-end close still takes 6.4 calendar days across all industries. For property management firms juggling dozens or hundreds of bank accounts across multiple entities, that number is often worse.
The gap between where most teams are and where they could be is enormous. For property management companies running Yardi Voyager, many of the tools to close that gap are already included in their license. They just aren't being used.
Chapter 2
How Bank Reconciliation Works in Yardi Voyager
Yardi bank reconciliation is a three-column matching process. Understanding this architecture is essential to troubleshooting, because most reconciliation failures trace back to a misunderstanding of how these three columns interact.
Column 1: GL Information. This displays the total of all cash accounts linked to a given bank code across every property associated with that bank. It also shows any uncleared Book Reconciling Items (adjustments where the GL is incorrect and needs correction). The Reconciled GL Balance is the GL Balance adjusted by any Book Reconciling Items.
Column 2: Bank Information. This starts with the ending balance you enter from your bank statement. It adjusts for uncleared checks (Outstanding Items), deposits in transit, and any Bank Reconciling Items (adjustments where the bank statement is incorrect). The result is the Reconciled Statement Balance.
Column 3: The Difference. This is the gap between the Reconciled GL Balance and the Reconciled Statement Balance. The reconciliation cannot be posted until this difference equals zero.
Within the reconciliation screen, you work through item types sequentially: Deposits, Checks, Other Items, Bank Reconciling Items, and Book Reconciling Items. Each transaction from the bank statement must be matched and cleared. Any transaction that appears in Voyager but not on the bank statement remains outstanding. Any transaction on the bank statement that doesn't appear in Voyager needs to be recorded before the reconciliation can close.
This is where things go wrong.
PRO TIP: Use the "Print" button mid-reconciliation to generate a PDF of outstanding items. It's often easier to work from a hard copy or second screen than toggling within the Voyager interface. This also creates a snapshot you can reference if you need to back out and start over.
Chapter 3
The 8 Most Common Yardi Bank Rec Failures
1
Missing Bank Account Setup for New Properties
This is the most dangerous bank rec failure because Yardi won't tell you it's happening. When a new property is acquired and the bank account isn't immediately set up in Voyager with the correct property and GL account associations, transactions get processed through the wrong cash account or don't appear in the bank reconciliation screen at all.
What happens: Expenses are paid from the wrong cash account. Deposits aren't captured in the GL. When you finally run the bank rec, the numbers are off by an amount that's nearly impossible to trace without going transaction by transaction.
How to fix it: Before making any deposits or withdrawals for a new property, the bank account must be created in Voyager with the correct property association, GL cash account linkage, and bank code. This is a day-one task during property onboarding, not something that can wait until month-end.
Prevention: Build bank account setup into your property acquisition checklist. Verify that every new property has its bank accounts configured and linked before the first transaction is posted.
2
Transactions on the Bank Statement Not Recorded in the GL
Bank fees, interest income, wire transfers, mortgage payments with variable interest, and direct tenant deposits regularly appear on bank statements without corresponding GL entries. Someone needs to review the bank statement and record these transactions before reconciliation can begin. As REdirect Consulting notes, it's common practice to have someone review bank statements daily and record these transactions, but that's often not a realistic expectation for understaffed accounting teams.
What happens: The bank statement shows transactions that have no match in Voyager. The difference column won't reach zero until every transaction is accounted for.
How to fix it: Record missing transactions via journal entries or through the appropriate Voyager module (AP for vendor payments, AR for tenant payments). Post them to the correct period before attempting to clear items on the reconciliation screen.
Prevention: Implement a process for reviewing bank statements weekly, not monthly. Even a quick scan for unexpected debits or credits prevents the month-end pileup.
3
GL Cutoff Date Mismatches
Yardi's bank reconciliation uses a GL Cutoff Date to determine which transactions appear on the reconciliation screen. If transactions are posted to the GL in a period that falls after your cutoff date, they won't show up in the reconciliation even though they may appear on the bank statement.
What happens: You see a transaction on the bank statement and can't find it in the reconciliation screen. It exists in Voyager, but it was posted to a future period or a period after your selected cutoff.
How to fix it: Verify the GL Cutoff Date matches the last day of your reconciliation period (typically the last day of the month). Check whether any transactions were inadvertently posted to the following month. If necessary, redate the transactions or adjust your cutoff.
Prevention: Standardize your GL cutoff dates across all properties. Ensure that AP and AR teams understand which period transactions should post to before month-end close begins.
PRO TIP: Before opening the reconciliation screen, run a quick GL Detail report filtered by bank account and date range. If the transaction count doesn't match what you expect, you'll catch posting period issues before you're halfway through clearing items.
4
Stale Uncleared Checks and Deposits
Over time, uncleared items accumulate on the bank reconciliation screen. Checks that were issued months ago but never cashed, deposits that were recorded in Voyager but never appeared on the bank statement, and old adjustments that nobody investigated. These stale items make every subsequent reconciliation harder and introduce risk.
What happens: The outstanding items list grows longer every month. Accountants scroll past old items without investigating them. Some of those items represent real problems: lost checks, duplicate payments, or recording errors.
How to fix it: Review all uncleared checks older than 90 days and all uncleared deposits older than 15 days. For checks, determine whether they need to be voided and reissued. For deposits, confirm whether the funds were actually received by the bank. Clear resolved items and investigate anything unexplained.
Prevention: Set a monthly review cadence for uncleared items. Industry best practice is to void checks outstanding for more than 180 days (check your state's unclaimed property laws for specific requirements) and to investigate any uncleared deposits older than two weeks.
PRO TIP: Create a saved report in Voyager that filters uncleared checks older than 90 days and uncleared deposits older than 15 days. Run it on the first business day of every month. If the list isn't getting shorter, your process has a gap.
5
EFT and ACH Transaction Errors
Electronic fund transfers add complexity because they involve timing gaps, partial payments, bank processing delays, and occasional errors. An ACH payment sent from Voyager may not clear the bank for several business days. If an incorrect amount is sent or a payment goes to the wrong recipient, it can take up to 10 business days to correct, according to Lynx Systems.
What happens: EFTs appear in the GL immediately when posted but don't clear the bank for days. If the amounts don't match (due to bank fees or partial returns), the reconciliation flags them as unmatched.
How to fix it: Match EFT transactions by reference number, not just amount. Account for any bank processing fees that reduce the net amount received. Record returns or reversals as separate transactions.
Prevention: Ensure EFT documentation is complete before processing. Verify bank account numbers and routing numbers during vendor and tenant setup. Use Yardi's payment processing features to generate an audit trail that links GL entries to bank transactions.
6
Intercompany and Pooled Account Complexity
Many property management firms use pooled bank accounts where multiple properties share a single bank account, or intercompany accounts where funds move between entities. These structures make reconciliation significantly more complex because the bank sees one account while Voyager tracks multiple property-level cash accounts.
What happens: The total across all property cash accounts linked to a bank code doesn't match the bank statement because intercompany transfers, management fee allocations, or pooled disbursements create internal transactions that have no corresponding bank movement.
How to fix it: Reconcile intercompany transfers before running bank reconciliations. Verify that offsetting entries exist for every internal transfer. For pooled accounts, ensure that the sum of all property-level cash accounts equals the bank balance before reconciliation begins.
Prevention: Document your intercompany transfer process and ensure both sides of every transfer are posted in the same period. Run a pre-reconciliation check that compares total Voyager cash for each bank code against the bank statement balance.
7
Duplicate Transactions
Duplicate payments and duplicate deposits are more common than most teams realize, especially in organizations where multiple people have posting access. A vendor payment processed through AP and also recorded as a manual check creates a double debit. A tenant payment entered through the resident portal and also manually posted creates a double credit.
What happens: The GL balance is overstated or understated by the amount of the duplicate. The reconciliation may still balance if both duplicates cleared the bank, but the financial statements are wrong. If only one instance cleared, the reconciliation won't balance and the duplicate shows as an outstanding item.
How to fix it: Run a duplicate transaction report before reconciliation. In Voyager, compare AP check registers and AR receipt registers for matching amounts, dates, and payees. Void the duplicate and post a correcting entry.
Prevention: Implement segregation of duties so that the person who enters transactions is not the same person who posts them. Use Voyager's workflow approval features to add a review step before payments are processed. Restrict manual check entry permissions.
8
Reconciling Items That Never Get Resolved
Yardi provides both Bank Reconciling Items and Book Reconciling Items as tools to temporarily account for discrepancies. Bank Reconciling Items are used when the bank statement is incorrect (the bank made an error). Book Reconciling Items are used when the GL is incorrect (your team made an error). These are meant to be temporary. In practice, many teams create reconciling items and never resolve them.
What happens: Reconciling items accumulate over months or years. Each one represents either a bank error that was never disputed or a GL error that was never corrected. The reconciliation technically balances, but the underlying data is wrong.
How to fix it: Review every open reconciling item. For Bank Reconciling Items, contact the bank to dispute or confirm the transaction. For Book Reconciling Items, post the correcting journal entry. Clear the reconciling item once the underlying issue is resolved.
Prevention: Treat reconciling items as exceptions that require investigation, not as a permanent parking lot for problems. Set a policy that no reconciling item should remain open for more than one reconciliation cycle without documented justification.
PRO TIP: Reconciling items are the "junk drawer" of accounting. If an item has been sitting there for 60 days, it isn't a reconciling item — it's an uncorrected error. Treat any reconciling item older than one cycle as an open investigation, not a placeholder.
Chapter 4
Diagnosing a Bank Rec That Won't Balance
When the difference column isn't zero and you can't figure out why, work through this systematic diagnostic:
Verify the bank statement ending balance. This sounds obvious, but data entry errors on the opening screen are surprisingly common. Confirm that the balance you entered matches the bank statement exactly, including cents.
Check the GL cutoff date. Make sure you're looking at the right period. Transactions posted after your cutoff won't appear.
Look for transactions on the bank statement that aren't in Voyager. Bank fees, interest, wire transfers, and ACH debits are the usual suspects. Record them before proceeding.
Check for transactions in Voyager that shouldn't be there. Voided checks that were already cashed, reversed transactions that the bank already processed, or transactions posted to the wrong bank code.
Run the Bank Reconciliation report mid-process. Click Print at any point during reconciliation to see the current state. Compare the report's outstanding items list against your bank statement line by line.
Check for rounding differences. Especially with international transactions or currency conversions, small rounding differences can prevent the reconciliation from posting. Use Book Reconciling Items for legitimate rounding adjustments, but document them.
Verify bank code assignments. If a property was recently added or a bank account was recently changed, confirm that the bank code in Voyager matches the actual bank account on the statement.
If none of these steps resolve the difference, the issue is likely in a prior period. Run the previous month's reconciliation report and verify that the opening balance matches what was posted.
Chapter 5
Yardi's Automatic Bank Reconciliation (ABR) Module
Most Voyager clients don't realize that automatic bank reconciliation is included in their existing license. The ABR module uses BAI2 files, a standard banking format, to automatically match and clear transactions on the bank reconciliation screen. It's one of the highest-impact, lowest-cost improvements available to any Yardi client, and most teams aren't using it.
How ABR Works
Your bank generates a BAI2 file containing all transactions for a given period. Most banks provide this at no charge, either through their online portal or via automated SFTP delivery.
The BAI2 file is uploaded into Yardi Voyager.
Voyager's ABR engine reads the file, matches transactions against the GL by amount, date, and reference number, and marks matching items as cleared on the bank reconciliation screen.
What to Expect
With default configuration, ABR typically auto-clears 50–85% of transactions according to industry benchmarks. At BC Solutions, our clients using ABR consistently see 60–80% of transactions auto-clear each month. With optimization of matching rules and transaction naming conventions, some accounts reach full automated reconciliation.
Manual reconciliation vs. ABR with optimized processes:
Metric
Manual Reconciliation
Optimized (ABR + Process)
Time per Account
2–4 hours
15–30 minutes
Auto-Clear Rate
0%
60–80%
Data Integrity
High risk of manual entry error
System-verified audit trail
Month-End Close Impact
Bank rec is the bottleneck
Reconciliation done by day 3
Scalability
Each new account = more hours
Each new account = minutes
Audit Readiness
Scramble to reconstruct
Clean trail, always current
For a portfolio with 50 bank accounts, the difference between these two approaches is roughly 100–175 hours per month — the equivalent of a full-time accounting position dedicated entirely to clearing transactions that a machine could handle.
Setting It Up
ABR requires the GL Posting Utilities Plug-In 7.2 or above. The setup process involves:
Contacting your bank to request BAI2 file delivery (ask about SFTP options for automation).
Configuring the BAI2 import settings in Voyager to map your bank's transaction codes to Yardi transaction types.
Running the import and reviewing the results. Unmatched items appear in the reconciliation screen for manual review.
Refining matching rules based on the types of transactions that aren't auto-clearing.
The BAI2 file can be run for all bank accounts simultaneously. Yardi separates the accounts automatically when processing the file, so you don't need to run individual imports for each account.
What to Ask Your Bank Before Setting Up ABR
Use this checklist when contacting your bank to request BAI2 file delivery. Getting clear answers upfront prevents weeks of back-and-forth during ABR implementation.
File Format & Availability
Do you support the BAI2 (Bank Administration Institute) file format for transaction reporting?
Is BAI2 reporting included in our current account package, or is there an additional fee?
Can BAI2 files be generated for all of our accounts in a single consolidated file?
What transaction types are included in the BAI2 file? (Confirm: deposits, withdrawals, fees, wire transfers, ACH, returned items)
Delivery Method
Can you deliver BAI2 files via automated SFTP? If so, what are the setup requirements?
If SFTP isn't available, can we download BAI2 files from your online banking portal?
What time are daily BAI2 files available? (For same-day vs. next-day processing)
Can we receive files on a daily AND monthly cadence, or do we need to choose one?
File Configuration
What is your default BAI2 transaction code mapping? (Request their code reference document)
Do your BAI2 files include check numbers and reference numbers in the detail records?
How are ACH transactions identified in the file? (Batch vs. individual detail)
Are wire transfers broken out separately, or combined with other electronic transactions?
Technical Details for Yardi Setup
What is the routing number and account identifier format used in the BAI2 header records?
Are there any special characters or encoding issues we should be aware of?
Who is our technical contact for troubleshooting file delivery issues?
Is there a test/sandbox environment where we can validate the file format before going live?
Timeline & Next Steps
How long does it take to activate BAI2 reporting from the date of request?
What paperwork or authorization is needed to enable BAI2 access?
Can we receive a sample BAI2 file to validate against our Yardi configuration before full activation?
Implementation Note: Most banks can activate BAI2 reporting within 5–10 business days. If your bank doesn't support BAI2, ask about OFX or CSV alternatives — Yardi can work with these formats through additional configuration, though BAI2 remains the most reliable option for automated matching.
PRO TIP: When you first run ABR, don't panic if the auto-clear rate is low. The default matching rules are conservative. After the first month, review what didn't match and why. Most of the time it's naming inconsistencies between your bank's transaction descriptions and Voyager's payee names. Fix those, and your auto-clear rate jumps significantly in month two.
Beyond ABR: Bank Book and RPA
For firms managing very large portfolios, Yardi Voyager Bank Book provides an additional layer of automation with direct bank feeds, intelligent transaction categorization, and multi-currency support. For organizations that need even more automation, robotic process automation (RPA) bots can be configured to download bank files, upload them to Yardi, process the ABR, and generate exception reports, all without human intervention.
Chapter 6
Building a Bank Rec Process That Scales
The difference between teams that close in 5 days and teams that close in 15 isn't talent or staffing. It's process. Here's the framework that works for our clients managing portfolios of 50 to 500+ properties.
Daily: Record Cash Transactions
Don't wait for the bank statement. Review online banking daily (or set up automated BAI2 feeds) and record new transactions as they appear: wire transfers, ACH debits, bank fees, and direct deposits. When the bank statement arrives, there should be no surprises.
Weekly: Review Uncleared Items
Every Friday, review the outstanding items list for each bank. Investigate anything older than 30 days. Escalate anything older than 90 days. This prevents the month-end scramble of sorting through dozens of stale transactions.
Monthly: Reconcile Within 5 Business Days
With daily recording and weekly reviews, month-end reconciliation becomes a verification exercise rather than a detective project. Set a hard deadline of the 5th business day after month-end for all bank reconciliations to be completed and posted.
Quarterly: Audit Your Process
Review reconciliation turnaround times across all properties. Identify accounts that consistently take longer. Investigate recurring unmatched transaction types. Refine ABR matching rules based on the patterns you see.
Property Onboarding: Get It Right Day One
Every new property should have bank accounts configured in Voyager before the first transaction posts. This includes operating accounts, security deposit accounts, reserve accounts, and any escrow accounts. Document the bank code, GL account mapping, and BAI2 configuration for each account.
Chapter 7
Common Mistakes That Make Everything Harder
Reconciling outside of Yardi
Some teams export data to Excel and reconcile there. This creates a parallel process that doesn't update Voyager's reconciliation status, doesn't catch internal control issues, and doubles the work. Always reconcile inside Voyager.
Ignoring the three-way reconciliation
For trust accounts and security deposit accounts, bank reconciliation is only step one. Step two is reconciling the bank balance to the property trial balance (tenant and owner ledgers). Skipping this step means you've confirmed the bank matches the GL but haven't confirmed that the GL matches your obligations.
PRO TIP: For trust accounts, bank reconciliation is only the first leg. The three-way reconciliation matches the bank to the GL to the tenant/owner ledgers. If those three don't agree, you have a fiduciary problem, not just an accounting one. Run all three checks before signing off on any trust account.
Using reconciling items as a permanent fix
Book and Bank Reconciling Items are temporary tools for identified discrepancies. They are not a substitute for correcting the underlying error. Every reconciling item should have a resolution date and an owner.
Falling behind
Bank rec compounds. If you skip January, February becomes exponentially harder because you're now investigating two months of transactions with fading memory of what happened. Monthly reconciliation is non-negotiable. Some firms with high transaction volumes benefit from weekly or even daily partial reconciliation.
Not leveraging ABR
The Automatic Bank Reconciliation module is included with Voyager. Every hour spent manually clearing transactions that ABR could handle automatically is an hour that could be spent on exception investigation, financial analysis, or owner reporting.
Chapter 8
Frequently Asked Questions
How long should bank reconciliation take in Yardi?
With proper setup, daily cash recording, and ABR enabled, a single bank account should take 15–30 minutes to reconcile. Without these practices, the same account can take 2–4 hours. For portfolios with hundreds of accounts, the difference between these approaches is measured in full-time employees.
What is a BAI2 file?
BAI2 (Bank Administration Institute format 2) is a standardized electronic file format that banks use to deliver transaction data. It contains structured records of deposits, withdrawals, fees, and other transactions that Yardi can read and match against the GL automatically. Most banks provide BAI2 files at no charge.
Is Yardi's Automatic Bank Reconciliation included in my license?
Yes. Both BAI2 imports and the ABR function are included in the core Yardi Voyager license for clients running GL Posting Utilities Plug-In 7.2 or above. While some banks may charge for automated BAI2 delivery via SFTP, the file can typically be downloaded manually from the banking portal at no additional cost.
What percentage of transactions does ABR auto-clear?
With default configuration, ABR typically auto-clears 50–85% of transactions. With optimization of matching rules and consistent transaction naming conventions, some accounts achieve near-complete automated reconciliation. The remaining items require manual review, which is where most of the value-add investigation happens.
What's the difference between Bank Reconciling Items and Book Reconciling Items?
Bank Reconciling Items adjust for errors on the bank's side (the bank statement is wrong). Book Reconciling Items adjust for errors on your side (the GL is wrong). Both are temporary and should be resolved within one reconciliation cycle.
How often should bank reconciliations be performed?
Monthly at minimum. Compliance requirements in most states mandate monthly reconciliation for trust accounts. For operating accounts with high transaction volumes, weekly or even daily partial reconciliation using ABR can significantly reduce month-end close time.
What should I do with checks outstanding for more than 6 months?
Review your state's unclaimed property (escheatment) laws. In most states, checks outstanding for 1–3 years must be reported and remitted to the state. As a practical matter, checks outstanding more than 180 days should be investigated. If the payee cannot be located, void the check in Voyager and follow your state's unclaimed property procedures.
Can I reconcile multiple bank accounts simultaneously?
When using ABR with BAI2 files, yes. The BAI2 file can contain data for all bank accounts. Yardi separates and processes each account individually. Manual reconciliation, however, should be done one account at a time to maintain accuracy.
What causes the "Difference" field to show a non-zero amount?
The Difference equals the Reconciled Statement Balance minus the Reconciled GL Balance. Non-zero differences are caused by uncleared items on either side: transactions in the GL that haven't been matched to the bank statement, transactions on the bank statement that haven't been recorded in the GL, or reconciling items that haven't been resolved.
Should I reconcile in Yardi or in Excel?
Always in Yardi. Reconciling outside of Voyager means you lose the audit trail, don't update Voyager's reconciliation status flags, can't leverage ABR, and miss internal control issues that only surface within the system. Excel reconciliation also creates a parallel set of records that can diverge from the system of record.
Chapter 9
When to Call for Help
Some bank reconciliation issues resolve with process discipline and better use of Voyager's built-in tools. Others require expert intervention:
You're more than 3 months behind on reconciliations.
Catching up involves unraveling months of transactions, which requires someone who can work systematically through the backlog without introducing new errors.
Your reconciling items have been open for multiple periods.
Long-standing reconciling items often mask deeper chart of accounts issues, misposted transactions, or bank account configuration problems that need to be traced to their source.
You've recently acquired properties or changed bank accounts.
Migration-related bank rec issues are among the most complex to resolve because they involve matching transactions across systems, validating opening balances, and ensuring that nothing was lost in the transition.
You're not using ABR and want to implement it.
While the technical setup isn't complicated, optimizing the matching rules for your specific banking relationships and transaction patterns requires experience across many Yardi environments.
Your month-end close consistently takes more than 7 business days.
Bank rec shouldn't be the bottleneck. If it is, there's usually a combination of process, configuration, and staffing issues that a fresh set of expert eyes can diagnose faster than internal trial and error.
BC Solutions provides bank reconciliation support as part of our Yardi Help Desk service. Whether you need help catching up on a backlog, implementing ABR, or building a month-end close process that actually works, our team has deep experience across multifamily, commercial, and mixed portfolios.
Our team specializes in Yardi Voyager bank reconciliation, ABR implementation, and month-end close optimization across multifamily, commercial, and mixed portfolios.
