Import a Bank Statement Into Buildium (CSV/OFX)

Why Buildium won't import your PDF

Buildium reconciles property bank accounts from structured transaction files, CSV and OFX, but it cannot read a PDF statement. A PDF is a printed page, not a table of dated transactions, so there is no column of amounts for Buildium to import and match. When your bank only supplies a PDF, or you are working an account the automated feed never touched, the activity is stuck in a document Buildium has no way to open. Converting the statement to a CSV or OFX turns it into transactions Buildium can upload and reconcile, so a month of rent deposits and owner disbursements comes in as data rather than hand-keyed lines.

Bank feeds vs a manual CSV/OFX import

Buildium's bank feed connects a supported account and pulls transactions automatically, which covers the ongoing case well. The manual import exists for everything the feed does not: a bank that is not supported, an account you have not connected, or history from before the feed was set up. In those situations you download a CSV or OFX from the bank, or convert a PDF statement into one, and upload it under the bank account in Buildium. The system then matches the imported transactions against entries already in Buildium, which is the same reconciliation flow the feed uses, just fed by a file you provide.

Importing statements older than the feed window

A new bank feed connection typically brings in only about the last 90 days, and that limit trips up property managers who need to reconcile earlier periods. The workaround is to temporarily disconnect the bank feed, import the older statements for the periods you need, then reconnect the feed for ongoing activity. Converting those back-period PDFs to CSV or OFX is what makes the manual import possible, since the bank often will not re-issue a machine-readable file for a statement that old. This is the practical way to close a gap between when an account opened and when the feed started.

Matching and clean reconciliation

Reconciliation in Buildium comes down to matching imported transactions to what is already recorded, and the usual snags are missing transactions from timing delays, duplicates where the same entry lands twice, and balance differences from outstanding checks or deposits. A clean converted file reduces two of those directly: consistent dates and amounts help Buildium match rather than flag, and reviewing every transaction in the converter before export keeps duplicates and misreads out of the upload. That leaves you with genuine timing items to clear rather than data-entry noise to untangle.

Trust accounting and privacy

Property management often runs through trust accounts holding tenant and owner funds, so the records you import are sensitive and the reconciliation carries compliance weight. Statements are processed to build the CSV or OFX and then deleted automatically, with nothing retained on a server afterward, which keeps client trust data out of a third-party tool. For a manager running several properties or entities in Buildium, bulk conversion turns a folder of statements across accounts into import-ready files in one pass, so bringing historical or unsupported-bank activity into Buildium stays both fast and defensible.

Frequently Asked Questions