File compatibility
Know what UnitClose can process before you upload.
UnitClose is a file-based companion for supported Yardi Breeze® and Breeze® Premier exports. It does not connect to Yardi or your bank, and it stops uncertain files for review instead of silently guessing.
Owner-statement runs
| Intended Yardi exports | GL Detail and Transaction Register |
|---|---|
| Accepted file types | .csv, .xls, and .xlsx |
| Files per run | Up to five files |
| Owner/property setup | Import property codes from a rent roll or GL Detail export, then assign each code to the correct external owner. |
| Before subscription | A built-in synthetic sample portfolio is available so the workflow can be inspected before a paid run. |
What stops a statement run for review
- Required columns are missing or the header layout is not recognized.
- A property code has not been assigned to an owner.
- An opening balance is required but has not been provided.
- The uploaded files do not represent the supported statement workflow.
UnitClose shows the warning and keeps the run editable. It does not invent a header mapping, owner assignment, or opening balance.
Bank-to-book reconciliation runs
| Required files | Exactly two: a Transaction Register export and bank activity for the same account and review period. |
|---|---|
| Accepted file types | .csv, .xls, .xlsx, .ofx, .qfx, and .qbo |
| Named bank layouts | Chase, Bank of America, Wells Fargo, Citi, and U.S. Bank |
| Other tabular exports | Choose the generic option and review the date, description, and amount columns before processing. |
| Required confirmation | Account label, bank-statement ending balance, and book ending balance |
| Subscription | An active UnitClose subscription is required for a bank-rec run. |
What the bank-rec output establishes
UnitClose prepares a bank-to-book worksheet and exceptions file with proposed matches and visible unmatched items. A qualified person must review the source files, mappings, exceptions, balances, and final package.
Not currently supported
- Yardi Voyager or enterprise migration work
- Direct Yardi API integration, scraping, synchronization, or write-back
- Automatic bank connections or transaction feeds
- HOA or association accounting
- Regulated affordable-housing reporting
- Complex commercial CAM accounting
- A promise that every custom export layout will work without review
Data-handling boundary
Uploaded financial files and processing intermediates are temporary work material. They are designed to be deleted after processing, with a 24-hour object-storage lifecycle backstop. Financial ledger rows do not go into Postgres. Read the complete data-handling model.
Before choosing a plan
- Confirm that your workflow uses the intended exports and file types above.
- Confirm that a qualified person can review mappings and exceptions.
- Use the built-in synthetic statement sample to inspect the workflow.
- Choose a plan only when the supported file-based boundary fits how your team closes the month.