Skip to the upload
Read-only · Berean never writes back · Nothing you upload is stored
BEREAN
← Back to the free audit

Free instant audit

Upload both exports.

One general ledger from your property software, one from your accounting system, both holding the same books. Berean checks each file against its own arithmetic before it compares anything, compares only the dates both files cover, and tells you what it left out. It never writes back to either system, and it does not keep your files. Use the same company or owner, property/activity coverage, currency and accounting basis. Do not pair property or trust books with corporate books, owner summaries or net remittances.

1 · Choose both exports

Berean works out which system each file came from by reading it, so these two slots are only here to stop the same file being uploaded twice. Up to 3 MB for the two together, and 25,000 rows per file.

Your property software export

The general ledger from Buildium or AppFolio.

Your books export

The general ledger from QuickBooks Online.

How to get your export

Buildium

Reports → General ledger → Export to CSV

AppFolio

General Ledger → Actions → Export as CSV; include all accounts and the same dates as QuickBooks

QuickBooks Online

Reports → General Ledger → Export as CSV

Export the report unedited. Berean re-checks each file against its own arithmetic, and an edited export usually fails that check.

2 · Confirm and run

The comparison runs in memory. Nothing about either file is written to a database, and nothing is written back to your property software or your accounting system.

Are these records meant to agree?

Do not compare a property's or trust account's books with the management company's own books. A monthly summary or a deposit after fees is not equivalent transaction detail. Matching records show only agreement between exports; both can contain the same wrong entry.

Berean needs both sides before it can compare anything.

Quick guide: from two exports to a reviewed finding
  1. Choose records that should agree. Use the same company or owner, property/activity scope and reporting dates. This comparison supports US dollars (USD) only, including files with no currency label. Use the same accounting basis too. Do not pair a property’s trust books with the management company’s corporate books.
  2. Export both general ledgers. Use an unedited Buildium or AppFolio CSV and a QuickBooks Online CSV. Keep the report’s basis label. For AppFolio, confirm the basis in the upload settings. If you have a monthly summary or a deposit after fees instead of comparable transaction detail, stop and review that relationship separately.
  3. Check the files before running. Confirm their scope. In your workspace, check the file names, dates and totals on the control sheet. Replacing a file requires a new confirmation.
  4. Read the coverage first. Check the dates compared, excluded activity and limitations. No finding is not the same as every transaction being checked. Matching exports can share the same wrong entry.
  5. Review each finding. In the paid workspace, open its source rows. Decide whether the difference is expected or needs a correction, and save your reason. A difference is not automatically an error or missing money.
  6. Correct, then check again. Make any accounting change in the source system, export fresh files, and rerun Berean. The guided correction workflow supports its stated cases; saving a review or a draft does not change QuickBooks, Buildium or AppFolio.

Agreement checks compare supplied evidence with the terms entered by the reviewer. They answer a different question from whether two exports agree. This comparison is not a bank or trust reconciliation.

Walk me through preparing my files (opens in a new tab)