Start with files
Use supported GL Detail and Transaction Register exports. For bank-to-book review, add a bank activity file for the same account and period.
Synthetic proof pack
See the complete export → review → download path.
This public sample uses synthetic property, owner, ledger, and bank data. It shows what UnitClose prepares, what remains visible for human review, and what the product does not decide.
The run
One bounded workflow, with the review points left visible.
Assign properties
Map property codes to the external owner who should receive the statement. Unassigned codes stop for review.
Inspect warnings
Confirm headers, opening balances, proposed matches, unmatched rows, exception categories, and the final calculation.
Take the artifacts
Download a branded owner statement or a bank-to-book worksheet plus an exceptions file. UnitClose does not send it for you.
Trace one number
$7,950 of OAK-101 income remains inspectable.
The synthetic source contains $7,800 of rent income and $150 of late fees for OAK-101. The statement preserves those account lines and totals them to $7,950 for the period.
Source rows$7,800 + $150
Statement sectionTotal Income $7,950
Download the synthetic source CSV · Download the owner/property map
Show the unresolved work
Unmatched rows are surfaced, not hidden.
The sample includes two outstanding checks and one deposit in transit. They remain in the worksheet and exceptions CSV with the next review action.
Scope boundary: this is a bank-to-book comparison for professional review. It is not an audit, compliance determination, or replacement for jurisdiction-specific three-way trust reconciliation.
Continue
Check whether your files fit before choosing a plan.
The public proof pack demonstrates output format and review boundaries. Actual compatibility still depends on edition, headers, file types, mappings, and the workflow you are trying to complete.