When receivables are separated across QuickBooks accounts, parent customers, or locations, build the forecast only after proving that every intended open-invoice population is present exactly once. Do not forecast from the first aging report that looks complete. Preserve each report's scope, combine the source rows, remove only verified duplicates, and reconcile the result to the supported control total.
Intuit's guidance on grouping receivables recommends one A/R account in the usual setup, while explaining parent-and-subcustomer and location approaches for grouping open receivables. It also notes that location reporting can require separate reports whose totals must be combined. That makes report scope a first-class forecast control.
Start with a scope register
Create one row for every source report before importing invoice detail:
| Scope field | What to preserve | Why it matters | | --- | --- | --- | | Report name and date | Exact report and as-of date | Prevents mixing snapshots | | A/R account or grouping | Account, parent, or location filter | Exposes omitted populations | | Currency and entity | Source settings used | Prevents incompatible totals | | Row count and open total | Observed report controls | Supports tie-out after merging | | Export file reference | Authorized source file | Keeps every finding traceable |
If a report is filtered by location, confirm that transactions without a location are not silently excluded. If a parent-customer view is used, preserve the underlying invoice and subcustomer identity rather than forecasting only from the parent subtotal.
Merge rows without netting away identity
Use a stable invoice key built from supported source fields such as customer, invoice number, transaction date, and open amount. Flag repeated keys for review; do not delete a row merely because two descriptions look similar. A single invoice can appear in more than one reporting view when the views overlap.
After merging, classify every row as included once, duplicate under review, excluded by documented scope, or unresolved. The included rows should tie back to the sum of the source scopes after verified overlap is removed.
The filtered aging report checklist provides a related control for report filters. The A/R aging versus balance-sheet reconciliation explains why a difference needs diagnosis before forecasting.
Forecast only after the population ties out
Once the combined invoice population is controlled, add the decision fields: evidence status, blocker, expected week, confidence label, owner, next action, and review date. Keep the source account or location on every row so forecast totals can be traced back to their origin.
Do not treat a location, parent customer, or A/R account as a collection assumption. Those fields explain organization and scope. The expected week still needs current invoice-level evidence.
A practical completeness test
Before releasing the four-week view, answer four questions:
- Which reports and filters define the population?
- Do their observed totals reconcile after documented overlap?
- Can every forecast row trace to one source invoice?
- Are any unassigned or duplicate rows visible rather than silently removed?
Intuit's A/R reconciliation guidance lists report settings and transaction issues that can cause A/R differences. Resolve or label those differences before using the result as a cash decision layer.
AR Pulse analyzes an authorized customer-provided QuickBooks receivables export. It does not change accounts, merge customers, or alter reporting settings. View the one-page example to see how source rows, exceptions, and collection assumptions remain linked.