Systems and records
Sales account hierarchy dataset: which account owns a subsidiary's deal?
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Attribute a subsidiary's purchase to the legal entity that signed the order on that date, then roll it up through the parent chain that was true on the close date. Keep the contracting entity, the paying entity, the CRM owning account and the roll-up account as separate fields, and check the CRM's parent field against signed documents and an external entity reference before using it as a label.
License terms
Sales account hierarchy
Key takeaways
- One subsidiary purchase has four account answers: contracting, paying, CRM owning and roll-up.
- The signed order's party clause controls the contracting entity, not the CRM opportunity account.
- CRM parent fields carry no effective date, so rebuild each deal's parent chain as of its close date.
- Acquisitions and divestitures change the roll-up for later deals only, never for deals already closed.
- Anchor entities with dated external references such as LEI relationships, and record their gaps.
- Score the benchmark as of each close date so today's hierarchy cannot leak into historical answers.
How should revenue data identify the account responsible for a subsidiary's purchase?
Attribute the purchase to the legal entity that signed the order on the date it signed, then roll it up through the parent chain that was true on that date. Keep the contracting entity, the paying entity and the CRM account that owns the opportunity as separate fields, because they often differ, and treat the CRM's parent field as a claim to check against signed documents and an external entity identifier.
A sales account hierarchy dataset built this way lets a model answer questions that a flat opportunity export gets wrong: whether revenue from a subsidiary counts toward a parent's enterprise agreement, which account a renewal belongs to after an acquisition, and why the CRM and the contract disagree. Without dates and evidence, the hierarchy in the file is simply today's guess applied to every past deal.
Attribution for sales compensation or territory credit is a separate policy decision layered on top. The dataset should record the facts that policy uses, not bake one company's crediting rules into the label. A team that later changes its crediting policy can then recompute credit from the same evidence instead of relabeling every case by hand.
Four different answers to which account bought it
A single subsidiary purchase can produce four defensible answers, and the benchmark needs all four as separate fields. Collapsing them is how a revenue dataset ends up with labels that contradict its own documents.
| Role | What it means | Where the evidence sits | Typical mistake |
|---|---|---|---|
| Contracting entity | The legal entity that is party to the order or contract | Signature block and party clause of the signed order, amendment or MSA | Assuming the parent signed because the parent has the enterprise agreement |
| Paying entity | The entity invoiced and the entity whose payment cleared | Billing account, invoices and remittance records | Treating a shared-services payer as the buyer |
| CRM owning account | The account the opportunity sits on for pipeline and reporting | Opportunity account lookup and its field history | Reading the current account instead of the account at close |
| Roll-up account | The top of the hierarchy the deal reports into on the deal date | Dated parent chain from the CRM and an external entity reference | Applying today's parent to a deal closed before an acquisition or sale |
What CRM hierarchy fields record, and what they leave out
Most CRMs store one parent pointer per account and little else. That is enough to draw a tree, but not enough to say when the tree was true or which legal entity each node represents.
Salesforce builds parent and child relationships through the Parent Account field on account records. HubSpot uses parent company and child company association labels, where a parent can have many child companies but a child has only one parent. Microsoft Dataverse has a ParentAccountId lookup, described as showing parent and child businesses in reporting and analytics, alongside MasterId and Merged fields that record when an account was merged into another.
None of these fields says whether a node is a legal entity, a division, a site or a sales territory, and none carries an effective date unless field history is switched on and retained. Merges are a particular trap: if related records were moved to the surviving account during a merge, an export can show a deal on an account record that was not the one used when the deal closed. Capture merge fields and field history alongside the tree.
A practical rule for the benchmark is to store each account's parent chain as it was at the opportunity close date, rebuilt from field history where it exists, and to flag cases where history is missing rather than filling them from the current tree.
External references that anchor a legal entity and its parents
An outside reference turns an account name into a legal entity with known parents. None is complete, so record which one was used and its as-of date.
| Reference | What it establishes | Limit to record | Use in the benchmark |
|---|---|---|---|
| GLEIF Level 2 relationship data | Direct and ultimate accounting consolidating parents for entities with an LEI | Parents may be reported as exceptions, for example when the parent has no LEI or the entity opts out | Primary anchor where both entities hold LEIs; store relationship dates |
| D&B D-U-N-S family tree | Global ultimate, domestic ultimate, headquarters, branch and parent roles | Commercially licensed data; check terms before redistributing any field | Matching aid inside the company; exclude licensed fields from a shared dataset unless cleared |
| SEC Exhibit 21 subsidiary lists | A U.S. registrant's subsidiaries and their jurisdictions as of a filing | Smaller subsidiaries can be omitted under the rule's instructions; public registrants only | Dated evidence that an entity belonged to a group at a filing date |
| Signed contract party clause | The exact legal name and often the registration jurisdiction of each party | Only as current as the document; names change | Controls the contracting entity field |
The account hierarchy and evidence matching benchmark
Each benchmark case is one closed or renewed opportunity where the buyer belongs to a corporate group. The case packet below is the template a revenue operations team can fill as is; values shown are illustrative.
At a glance
The account hierarchy and evidence matching benchmark
- Exact entity match: the CRM account, the signed order and the external reference all name the same legal entity.
- Parent-level match: the CRM account is the parent while the order names a subsidiary; correct for roll-up, wrong for the contracting entity.
- Sibling mismatch: the CRM account is a different subsidiary of the same group, often after a rep logs a deal on the account they already own.
- Stale hierarchy: the entity is right but its recorded parent changed after the close date.
- No match: the order names an entity with no CRM account and no external reference, which is a case for abstention.
| Field | Illustrative value | Source record | Rule |
|---|---|---|---|
| case_id and opportunity_ref | AH-0203 / opportunity 7741 | CRM | One case per opportunity version (new, amendment, renewal) |
| close_date | Day 0 of the illustrative timeline | Opportunity history | All other as-of fields are evaluated on this date |
| contracting_entity | Subsidiary S, registered in country B | Signed order form party clause | Exact legal name plus an identifier where one exists |
| governing_agreement | Parent MSA with an affiliate ordering clause | Contract repository | Link the master agreement the order was placed under |
| paying_entity | Parent shared services center | Invoice and remittance | May differ from the contracting entity; never overwrite it |
| crm_account_at_close | Account record for S, later merged | Field history and merge records | Not the account shown today |
| parent_chain_at_close | S, then P (ultimate) | CRM history checked against an external reference | Each link carries its source and as-of date |
| authority_evidence | Signer title and entity on the order | Signature block and approval log | Records who bound which entity |
| conflict_flags | CRM parent differs from external parent | Comparison | List every disagreement; do not resolve silently |
| labels | Owning entity S; roll-up P at close | Reviewer decision | Each label cites at least one signed or dated record |
Contract terms and later events that overrule the CRM's parent account
Signed documents outrank CRM fields, and later events can change the roll-up without changing who signed. These are the patterns that most often make the CRM's answer wrong.
- Affiliate ordering clause: the parent signs a master agreement that lets affiliates place orders. The order form names the subsidiary, so the subsidiary is the contracting entity even though the CRM opportunity sits on the parent.
- Parent signing on behalf of affiliates: the reverse case, where the parent signs the order and the subsidiary only uses the product. The contracting entity is the parent.
- Assignment or novation: an amendment moves the contract to another group entity. The original deal keeps its contracting entity; the renewal follows the new one.
- Acquisition or divestiture after close: the roll-up for deals closed before the event stays with the old parent, and only later deals move. A CRM that re-parents the account rewrites history for every old opportunity.
- Shared-services payment: invoices paid by a group finance entity do not make that entity the buyer.
- Approval contradictions: a discount or credit approval recorded against one account while the signed order names another is a data quality flag worth keeping as its own case.
Worked example (illustrative): an affiliate order under a parent agreement, then a divestiture
This example is invented for teaching and describes no real companies; dates are given as day counts. Parent company P signs a master agreement with an affiliate ordering clause. On day 0, its subsidiary S in another country signs an order form under that agreement. The sales representative who owns P's account logs the opportunity on P's CRM account, and invoices go to S.
Decision for the original deal: the contracting entity is S, because the signed order names S. The CRM owning account is P, a recording choice rather than a fact about the buyer. The roll-up account at close is P, confirmed by the parent chain in the CRM and by an external reference showing S consolidated into P on that date.
On day 240, P sells S to an unrelated group Q, but nobody updates the CRM. On day 365, S renews, and the opportunity is again logged on P's account. Decision for the renewal: the contracting entity is still S; the roll-up account is now Q, and the case carries a conflict flag because the CRM parent field still points to P. The outcome check is the renewal invoice, addressed to S, and the external reference's relationship end date.
The exception to include beside it is the reverse pattern: P signs an order on behalf of its affiliates and pays centrally, and S only uses the service. That case is labeled with P as the contracting entity, so the benchmark tests whether a model reads the signature block rather than the user list.
Scoring the benchmark without leaking today's hierarchy into old deals
Publish the limits next to the scores. The benchmark tests whether a model can reconstruct entity facts from evidence; it does not test whether a company's crediting policy is fair, and external references cover only part of the corporate world. Report the share of cases anchored by an external reference, the share rebuilt from CRM field history, and the share resting on signed documents alone, so readers can judge how much of each score depends on which kind of evidence.
At a glance
Scoring the benchmark without leaking today's hierarchy into old deals
- Entity match: exact contracting entity, scored against the signed order.
- Roll-up accuracy as of close date, scored against the dated parent chain.
- Conflict detection: whether the model flags cases where CRM and documents disagree.
- Stale hierarchy detection: cases closed after an acquisition, divestiture or merge where the CRM tree was not updated.
- Abstention: cases with missing field history or no external reference, where the correct output names the missing evidence.
- Split by time and by corporate group, so the same group never appears in both training and test data.
Preparing account and deal histories for an AI data license
Revenue records that link opportunities to signed orders, invoices and dated hierarchies are rare in public data, which is why they interest AI developers building revenue and procurement agents. Before any of it is shared, contract confidentiality terms with customers, personal data in contacts and activity notes, and third-party enrichment fields such as licensed firmographics each need review; holding the records does not by itself grant the right to license them.
Deal and hierarchy histories licensed to AI developers through SourceX go through a rights review, contracting, preparation and delivery that SourceX runs on the revenue team's behalf. A short assessment of the company, needing no CRM export, settles eligibility, and no opportunity record is delivered before the company approves the scope and terms and signs.
Frequently asked questions
Should a subsidiary's purchase be credited to the parent account?
For roll-up reporting it usually rolls up to the parent that owned the subsidiary on the close date, but the contracting entity remains the subsidiary if it signed. Sales credit is a separate policy, so record the facts and let the crediting rule apply on top.
What should an account hierarchy and evidence matching benchmark include?
One case per opportunity with the contracting entity, paying entity, CRM account at close, dated parent chain, governing agreement, signer evidence and conflict flags. Every label should cite a signed or dated record.
What happens to old deals when a customer is acquired?
Nothing should change for deals that closed before the acquisition; their roll-up stays with the former parent. Only later deals and renewals move, which is why the hierarchy must be stored as of each close date.
Can D-U-N-S or other enrichment data go into a shared dataset?
Only if the provider's license allows it, and many commercial terms do not. Use licensed identifiers for internal matching and exclude them from a shared dataset unless the terms clearly permit redistribution.
Is the CRM parent account field reliable enough to use as a label?
Not on its own. It is usually maintained by hand, carries no effective date and is often not updated after acquisitions or merges, so check it against signed documents and an external entity reference.
Sources
- Salesforce creates parent and child account relationships through the Parent Account field on account records. Source
- HubSpot links companies with parent company and child company association labels; a parent can have multiple children and a child only one parent. Source
- Microsoft Dataverse's account table has a ParentAccountId lookup for parent and child businesses and MasterId and Merged fields for merged accounts. Source
- GLEIF Level 2 data records direct and ultimate accounting consolidating parents of legal entities with an LEI, with reporting exceptions when a parent is not reported. Source
- Dun and Bradstreet defines family tree roles including global ultimate, domestic ultimate, headquarters, branch and parent. Source
- Regulation S-K Item 601(b)(21) requires registrants to list subsidiaries with their jurisdictions, with permitted omissions. Source
See if your company qualifies
A short company assessment. No data uploads are needed.