Forecast parent and sub-customer invoices from the invoice rows first, then roll them up for management. Do not add a parent subtotal to the underlying sub-customer invoices; that would double count the same receivables.

Know what the hierarchy changes

QuickBooks can group customers under a parent and can bill a parent for sub-customer charges. It can also subtotal open receivables by a parent grouping. Those features change how invoices are organized and presented. They do not create an additional receivable above the individual open invoice rows.

Build two linked views:

  • **Invoice view:** one row per invoice ID, with billed customer, parent customer when present, open balance, due date, and evidence.
  • **Management view:** subtotals by legal payer, operating location, project, or internal account owner, using the invoice rows as the only amount source.

The invoice view protects arithmetic. The management view supports concentration and ownership decisions. The QuickBooks customer-statement comparison explains why a communication document and an invoice-level aging view may have different scopes.

Define the payer and operator separately

A sub-customer may represent a site, project, department, or operating unit while the parent receives the invoice. Capture both identities when the source supports them:

| Field | Purpose | | --- | --- | | Invoice customer | Preserves the source transaction identity. | | Parent customer | Supports grouping and concentration analysis. | | Bill-parent flag | Identifies the intended billing presentation. | | Payer evidence | Records which entity is expected to process payment. | | Internal owner | Assigns the next action without changing the payer. |

Do not assume every sub-customer shares one payment process. Use the recorded billing setup and actual invoice evidence. If the hierarchy changed after the forecast export, record that as a source change rather than rewriting the old snapshot.

Prevent concentration errors

Customer concentration should reflect the management decision. A finance owner might need both parent-level exposure and sub-customer operating detail. Sum each invoice once, then calculate parent share from that same base. The customer-concentration guide provides a way to connect grouped exposure to forecast risk without losing invoice traceability.

Before publishing a forecast, reconcile:

  1. Invoice-row open balances to the dated AR export.
  2. Sub-customer rows to the parent mapping used for management.
  3. Parent subtotals back to the exact included invoice IDs.
  4. Any customer statement to the same date and scope.
  5. Owners and expected collection dates to payer-specific evidence.

Decision rule

Use the customer hierarchy as a classification layer, never as a second amount layer. Preserve each invoice row, roll it up once, and state whether the expected payer is the parent or sub-customer. The AR Pulse example shows the invoice-level traceability expected before a grouped action list or four-week range is trusted.