Check a property-software export before it reaches QuickBooks

Before moving property-software activity into QuickBooks, define exactly what the export contains and whether those events already appear in the books. A file that uploads successfully can still duplicate revenue, bills or cash activity when the same events arrived through another workflow.

The safest preflight does not begin with the Import button. It begins with a controlled batch, a record map and a decision for each type of activity: import, match, reference only or hold for review.

Give the export a batch identity

Save an unchanged copy of the source export. Record the software, report or export name, business entity, property selection, period, accounting basis, generation time, row count and control totals. Give the file a batch ID such as PM-2026-08-A.

AppFolio describes customizable financial reports and secure export functionality. Those capabilities support access to property data; they do not determine what a separate QuickBooks file should contain. Confirm the actual enabled features, permissions and reporting scope for the firm.

The control sheet should answer:

• Which legal entity and bank accounts does the export cover?
• Is each row detail, a summary, a receivable, a payable, a settlement or another record type?
• Which property and owner references are present?
• Has this period or batch been transferred before?
• What record, if any, already represents the event in QuickBooks?
• Who approves mappings and unresolved exceptions?

Do not combine exports from different cutoffs or accounting bases into one unexplained batch.

Route each record type before moving data

Use four actions:

1. Import candidate: the agreed QuickBooks scope needs the record and no existing representation was found.
2. Match or link: an existing QuickBooks record or bank transaction represents the event and should be connected under the approved workflow.
3. Reference only: the property-software detail supports a report or reconciliation but does not belong as a second transaction in this QuickBooks entity.
4. Hold: the entity, mapping, amount or prior-transfer status is unresolved.

The action is a control decision, not a universal accounting rule. The responsible accountant and the firm’s system design establish which records belong in each set of books.

Worked example: three rows, three different actions

Illustrative example. Batch PM-2026-08-A includes these record groups for Property P-17:

The table does not prescribe entries or determine who legally owes an amount. It shows why “exported” is not the same as “ready to import.” The $1,860 repair bill remains visible rather than being copied into the wrong entity simply because QuickBooks has a vendor with the same name.

Check for existing representations

Intuit identifies overlapping imports, bank feeds and app records as common causes of duplicate QuickBooks transactions. It advises checking the underlying statement and matching an existing record where appropriate instead of adding another copy.

For each import candidate, search the agreed date range and compare amount, reference, payee, account and attachment. A similar amount is a clue, not proof. Grouped deposits, fees and timing differences may prevent an automatic match.

Also check the batch history. A renamed export file can still contain rows transferred in an earlier run. Use stable source IDs or a documented composite key rather than the filename alone.

Verify the batch after processing

Preserve the pre-import file and record what the process actually accepted, rejected or changed. Then compare:

• Source rows to processed rows by action.
• Source control totals to the amounts intentionally represented in QuickBooks.
• Imported references to the property and entity map.
• Bank-feed items to existing records so cash is not added as new activity twice.
• Held exceptions to a named owner and next review date.

Save the QuickBooks report or transaction list used for verification with its settings and generation time. If the result is wrong, use the software’s supported correction process and the retained batch evidence; do not upload a revised file blindly.

Start with the system-role matrix to decide what belongs in each system. Then use the reconciliation exception log for held items. DaxSync provides a managed accounting handoff and reconciliation process; it does not claim a native, automatic or real-time connection between platforms.