Map duplicate customer profiles before forecasting, but do not alter the dated export just to make the analysis look cleaner. Group supported duplicates for concentration and ownership, preserve every invoice row, and leave any permanent QuickBooks merge to an authorized bookkeeping decision.

Diagnose identity before changing records

Two similar customer names are not automatically the same payer. Compare source fields such as display name, company name, billing address, email domain, parent relationship, tax identifier when appropriately available, and invoice history. Record why two profiles are considered the same business or why they must remain separate.

Use a review table:

| Export customer | Proposed normalized customer | Evidence | Decision | Reviewer | | --- | --- | --- | --- | --- | | Source value | Management grouping only | Matching fields and contradictions | Match, separate, or unresolved | Named finance owner |

Unresolved records should remain separate in invoice arithmetic and receive a review flag. This avoids collapsing two customers based only on a similar name.

Preserve invoice-level amounts

Customer normalization changes grouping, not the source balance. Keep invoice ID, source customer ID, source customer name, open balance, due date, and export timestamp. Add a normalized management ID in a separate field. Then calculate customer concentration from the normalized view while reconciling totals to the unchanged source rows.

The duplicate-invoice screening guide addresses repeated transactions. Duplicate customer profiles are a different problem: valid invoices can be split across more than one customer identity.

Treat a QuickBooks merge as a separate control

Intuit documents that merging customer profiles moves the duplicate profile's data into the profile kept, makes the duplicate inactive, and is permanent. It also identifies prerequisites involving sub-customers. That is a bookkeeping change with consequences beyond a forecast cleanup.

Before any merge, an authorized owner should confirm the profiles, sub-customer and project relationships, retained name, access and reporting consequences, and rollback limitations. AR Pulse does not change books. During analysis, a reversible mapping table is enough to create a management rollup.

If source records change after the export, preserve the old snapshot and document the bridge. The edited-invoice workflow illustrates the same version-control principle for transaction changes.

Check the forecast effects

Duplicate profiles can distort more than the customer subtotal. Review:

  • parent-level concentration;
  • the number of invoices assigned to one owner;
  • payment-history context;
  • follow-up notes and commitments stored under different profiles; and
  • whether a single payer appears to have competing expected collection dates.

Do not combine payment evidence unless the identity match is supported. A shared domain or similar display name alone is not enough.

Decision rule

Normalize reversibly for analysis, reconcile to the original invoice rows, and escalate permanent source-system changes to the authorized bookkeeping owner. Finance teams can use the AR Pulse example report as a model for source-row traceability without granting access to the accounting system.