Property management guide

Prepare a property-bookkeeping report map for your CPA

Show which reports come from property software, which come from QuickBooks and how unresolved differences reach the CPA without duplicate activity.

When property software and QuickBooks both contain financial information, a folder full of exports does not tell the CPA which report answers which question. It can also hide duplicated activity, inconsistent cutoffs and unresolved differences.

Create a report map before the handoff. For every file, identify its source system, accounting scope, cutoff, basis, purpose and relationship to the other reports. The map should make it possible to trace a reported total without assuming the two systems carry identical detail.

Ask the CPA what the package must support

Start with the requested review outputs rather than exporting every available report. Confirm:

  • Legal entity or entities in scope.
  • Reporting period and cutoff.
  • Cash or accrual basis used for each report.
  • Financial statements and supporting schedules requested.
  • Property-level detail that must remain available.
  • Open questions that should be shown rather than resolved by assumption.

The CPA decides the required reporting and accounting treatment. The property manager and bookkeeper prepare a consistent record package and identify where a decision is still needed.

Give every report six fields

Use one line in the map for each report:

  1. Report ID and exact name.
  2. Source system and export time.
  3. Entity, property and account filters.
  4. Period and accounting basis.
  5. Purpose in the package.
  6. Tie-out or exception relationship.

AppFolio describes owner statements, income statements, balance sheets, bank-account activity and export functionality. Actual availability depends on the software, subscription, permissions and setup. Record the report that was truly generated rather than a generic label such as “AppFolio financials.”

QuickBooks reports can be run with selected periods and shared or exported. The map should retain those selected settings because a report title alone does not reveal its population.

Use an authority ladder

The two systems may serve different purposes. Define the agreed authority for each type of fact:

  • Property and owner activity: operational platform, QuickBooks or a defined comparison.
  • Management-company operating activity: the agreed company accounting file.
  • Bank activity: named bank statement and account.
  • Property identifiers: the approved property-to-QuickBooks mapping.
  • Accounting decisions: the responsible accountant or CPA.

This ladder does not require two full ledgers. A property platform may already be the accounting system for property books, while QuickBooks holds management-company or agreed summary activity. DaxSync confirms the actual design during scoping.

Worked example: one apartment portfolio

Illustrative example. Elm Residential Management prepares a June package for Elm 8 Holdings LLC:

ID Source Report and scope Purpose Relationship
PF-01 Property software Owner statement; Elm 8; June accrual Property activity detail Supports property-level revenue and expense questions
PF-02 Property software Bank-account activity; Operating 4412; through June 30 Operational cash population Compared with bank statement and agreed QuickBooks account
QB-01 QuickBooks Balance Sheet; Elm 8 Holdings LLC; June 30 accrual Entity financial position Open differences listed in EX-01
QB-02 QuickBooks Profit and Loss; Elm 8 Holdings LLC; June accrual Entity operating result Property detail referenced to PF-01 where applicable
BK-01 Bank Operating 4412 statement; June 30 External cash evidence Compared with PF-02 and QuickBooks
EX-01 Workpaper Reconciliation exception log Unresolved differences Owner, amount, next action and due date

The package does not say PF-01 must equal QB-02 line for line. It states why each exists and records the defined comparison. If QuickBooks receives only approved summaries, the property-software detail remains support rather than a second set of imported transactions.

Keep unresolved differences in the package

Do not “clean” the handoff by removing an unexplained difference. Add an exception line with:

  • Affected report IDs.
  • Amount and date range.
  • What has already been checked.
  • Missing source or decision.
  • Responsible person and next review date.
  • Whether the difference affects the current financial statements.

The reconciliation exception log provides a repeatable structure. A documented open item is more useful to a CPA than an unexplained plug or a silently changed export.

Freeze the package at handoff

Use a clear file name and preserve the generated time, filters and format. Intuit documents exporting reports and lists from QuickBooks Online. Keep the exported file that was actually reviewed, even if the live software changes later.

If the team regenerates a report after a correction, keep a version note: prior file, replacement file, reason, preparer and time. Update the map and exception log together. Do not overwrite the original without a trace.

Run a five-minute handoff check

Before delivery, verify:

  1. Every requested output appears once.
  2. Entity, property, account, period and basis are visible.
  3. Report relationships are stated.
  4. Bank evidence matches the named account and cutoff.
  5. Unresolved differences are explicit.
  6. No file claims CPA review or approval before it happens.

The system-role guide explains what each platform is intended to hold. The same-cutoff packet guide helps align report dates.

DaxSync provides managed bookkeeping and reconciliation across operational records, QuickBooks and bank activity. It does not promise a native or real-time integration, and a prepared report package does not imply CPA approval.

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.

Keep the systems. Connect the books.

Let’s talk about your property software, QuickBooks and the financial reports your business needs.

Book a call
DaxSync

Discovery call

Let’s connect your software and books.

Choose a time to discuss your operational software, QuickBooks and the reports your team needs.

45 minutes · Video call

  • Your software and current accounting handoff
  • The records, differences and reports involved
  • The scope and next steps

No documents needed to get started.

Appointments use our shared Daxable calendar. Your inquiry is for DaxSync.

Loading available times…

Having trouble? Open the calendar in a new tab ↗