Separate a grouped property deposit before it is matched in QuickBooks

A grouped bank deposit is a receipt at the bank, not an explanation of the activity inside it. Before matching it in QuickBooks, build a deposit register that shows the operational report lines, any allowed deductions already shown in the report, and the QuickBooks record the bank receipt is expected to settle.

This is a managed bookkeeping control between property software, QuickBooks and bank activity. It does not promise a software integration, and it does not determine how owner, tenant, tax or trust-related activity should be treated.

Start with the bank receipt, then name its scope

Give the deposit a stable reference. Record the bank account, amount, posting date, bank description, entity, property selection, source-report name, report date range and report-generation time. A label such as “daily deposit” is not enough when one receipt may combine several properties or operational events.

Property-management software can provide its own accounting and reporting views. For example, AppFolio describes accounting reports, financial reporting and export capability.¹ That supports collecting the actual report used for the review; it does not establish that every firm must use QuickBooks or that every export should be posted there.

Use a deposit register with three evidence layers

Keep one row per bank deposit and three attached layers:

Use a clear status: supported and matched, supported but waiting for bank, banked but missing operational detail, or exception. The status tells the next reviewer what is known without forcing a classification decision.

Worked example: one receipt, two properties

Illustrative example. The operating bank shows an $18,460 receipt on October 3. The manager saves a property-software collections report generated that morning. It lists $11,900 connected to Property A and $6,560 connected to Property B, for the same $18,460 total. QuickBooks already contains a $18,460 clearing entry tied to the agreed reporting batch.

The register links all three records under DEP-1003-01. The reviewer confirms the entity, property scope and report cutoff before matching the bank line to the existing QuickBooks entry. The bank receipt is not entered again as unrelated income simply because it arrived through the feed.

If the operational report totals $18,710 instead, leave the $250 difference visible. It may be a timing item, an omitted line, a bank charge, a duplicate record or another explanation. Do not create a balancing entry until the source is identified and the responsible accounting reviewer decides the appropriate treatment.

Test for a duplicate before accepting a match

Ask two questions in sequence:

1. Is the bank receipt represented by an existing QuickBooks record that is supported by the operational batch?
2. Has that operational activity already reached QuickBooks by another route, such as a prior import, journal workflow or manually entered deposit?

Intuit’s current guidance for duplicate bank-feed activity is useful when a downloaded transaction appears more than once.² The specific repair depends on the actual file and workflow, so preserve the report and transaction references before changing anything.

Keep exceptions useful at close

Add the deposit reference, amount, missing evidence and owner to the reconciliation exception log. If a property or entity label is unclear, consult the property-to-QuickBooks mapping register before assigning it. For records entering from an export, the pre-import guide helps the team decide whether a row should be imported, matched, retained as reference or held.

At close, review the register for unsupported bank receipts, supported batches without a bank receipt, and receipts matched more than once. That turns a vague “sync issue” into a small queue of evidence questions that operations and bookkeeping can resolve together.