Voyager, Breeze and the existing setup
Confirm the product and reports before defining the handoff
Voyager and Breeze are distinct Yardi products, so a service scope should not assume identical report names, permissions, modules or accounting depth. Start by confirming which product is used, which reports are available, how property and company records are separated, and whether a separate general ledger also needs to be reconciled.
Where property-management reports and general-ledger records are held in different places, the agreed workflow can compare totals and supporting detail, trace differences and retain an exception log. The method depends on the records and mappings available; no generic checklist can replace confirmation of the client’s actual configuration.
If the portfolio is using Yardi today but month-end still depends on manual exports, spreadsheets or repeated re-checking, the first step is to map where each balance originates and which person reviews it. Accounstone can then discuss a defined preparation scope without proposing an unrequested software migration or configuration project.