Website preview · Online inquiries and booking are being connected.

DAXSYNC / PRACTICAL GUIDE

Choose one cut-off date for your reconciliation packet

Avoid comparing different periods or report populations when assembling a property-management reconciliation packet.

Use one cut-off date for the bank comparison, trust-book report, and relevant beneficiary detail. Record when each report was generated. A date printed on the workpaper is not enough if one export includes later transactions or excludes part of the ledger population.

Distinguish three different dates

The transaction date, statement date, and report-generation time describe different things. A transaction posted later may affect a report rerun for an earlier period. The bank statement itself may be unchanged while the system export now contains additional entries.

For that reason, save the report used in the comparison. A link to a live report that changes every time it opens is not a complete record of what was reviewed.

Build a packet cover sheet

Include the account identifier, cut-off date, report names, date filters, included properties or beneficiaries, export time, preparer, and version. List any known differences in scope before trying to reconcile amounts.

For example, an illustrative June 30 packet might contain a June bank statement, a trust-book export through June 30, and beneficiary detail through June 30 that includes both active and relevant closed records. If the beneficiary report is filtered to July activity, stop and correct the report boundary first.

Check the filters that are easy to miss

  • Is the report account-specific, or does it include several accounts?
  • Does it exclude inactive properties, tenants, or owner records?
  • Is the balance as of a date, or activity during a date range?
  • Has a later posting changed a previously exported balance?
  • Do all reports use the same entity and ledger population?

The exact report names vary by property-management software. Document the selected filters rather than assuming another person will recognize the saved view.

Handle a rerun deliberately

If a source report changes, preserve the previous export and create a new packet version. Note what changed, why the report was rerun, and whether the comparison was rechecked. Do not attach the new report to an old signed-off workpaper without explaining the change.

Know when to stop comparing

When report populations cannot be aligned, mark the comparison as incomplete and identify the missing report or access. Repeated arithmetic on incompatible reports will not resolve the problem.

This is operational record preparation, not state regulatory guidance. The three-balance worksheet keeps the cut-off and source references beside the totals they support.

Sources and further reading

Source links provide background. The workflow and illustrative examples above are original educational material.

Our resource guides are prepared with AI assistance. Worked examples are illustrative unless explicitly identified otherwise. This guide does not interpret tax law, payroll law, or state trust-account requirements. Read our editorial standards.

A matching total is the start. An explainable total is the goal.

Discuss your reconciliation