Convert a Bank Statement to Reconcile in Yardi Voyager

Yardi's Automatic Bank Reconciliation

Yardi Voyager runs property accounting at scale, and its Automatic Bank Reconciliation, or ABR, is built to make monthly reconciliations fast. You import a bank file and Yardi auto-clears the transactions that match what is already posted, typically 60 to 80 percent of them, dropping a per-account reconciliation from hours to well under an hour. ABR comes with the core Voyager license through the GL Posting Utilities plug-in at no extra fee. The catch is the file it wants, which is not a PDF statement.

BAI2 first, OFX or CSV as alternatives

Yardi's ABR is built around BAI2, a bank-native file format that carries transaction codes Yardi maps to its own transaction types, and it is the most reliable input for automatic matching. Most banks can deliver BAI2, often by nightly SFTP or a manual portal download. When a bank cannot, Yardi can be configured to accept an OFX or CSV file instead. That alternative path is what a converted statement targets, since a converter produces OFX or CSV, not the bank-issued BAI2 feed itself.

When you only have a PDF statement

Plenty of situations leave you without a BAI2 file: an older period from before the feed was set up, an account the feed does not cover, or a bank that hands you nothing but a PDF. In those cases you fall back to the OFX or CSV path Yardi supports, and converting the PDF statement is what produces that file. It pulls each transaction into a clean, dated row so the alternative import has structured data to match against, rather than leaving you to key a month of activity into Voyager by hand.

Transaction codes and the exceptions

Whatever file you feed it, Yardi's import is configured to map the bank's transaction codes to Yardi transaction types, which is what lets ABR clear matches automatically and leave only exceptions for review. A clean converted file keeps that mapping honest: accurate dates, amounts, and descriptions mean fewer mismatches and a shorter exception list. You still review what did not clear, but you start from good data instead of chasing errors introduced by manual entry.

Accuracy and privacy

Because property accounting has to tie out to the bank across many accounts, every transaction is reviewable in the converter before export so a misread figure does not enter the reconciliation. The output arrives as a clean OFX or CSV for Yardi's alternative import path. Since a statement holds real account activity, the file is processed to build it and then deleted automatically, with nothing kept on a server afterward.

Frequently Asked Questions