Document a property-software transaction missing from QuickBooks

When a transaction appears in property software but not in QuickBooks, do not start by recreating it. First prepare a missing-record packet that identifies the operational event, the expected QuickBooks representation, the bank evidence if relevant, and every alternate route by which it might already have reached the books.

Make the packet

Include the operational report name, generated time, entity, property or listing ID, source transaction ID, amount, date, report basis, expected QuickBooks account or workflow, and reviewer. Attach the bank reference only when the event should have a bank leg in the defined scope.

AppFolio describes accounting reports and export capability for property-management teams.¹ The actual reports, permissions and setup vary. The packet records the report that was actually used; it does not promise a DaxSync integration.

Use four dispositions

Illustrative example. An operational report shows a $2,860 maintenance charge for Property 18. A QuickBooks search finds no vendor bill, but the bank feed shows a $2,860 debit that has not been reviewed. The packet links the source transaction, property ID and bank line. The correct next step may be an approved match or posting workflow after the reviewer confirms the documents; it is not to add a second $2,860 expense.

Check alternate routes before posting

Search by amount, vendor, date range, property ID and batch reference. Look for a prior export, manual entry, clearing record, bank-feed item or journal process. Intuit provides current guidance for duplicate bank-feed transactions; preserve the references before changing anything.²

Keep the packet with the mapping register and add unresolved cases to the reconciliation exception log. This is a managed reconciliation control. It does not make decisions about tax treatment, trust-account requirements, or what an owner should be charged.