# The Subsidiary Ownership Verdict: Parent Owner, Local Owner, or Split

*Score one disputed child entity on five evidence-backed dimensions and issue a Parent Owner, Local Owner, or Split verdict that a second analyst would match.*

- Canonical URL: https://www.refolk.ai/guides/subsidiary-account-ownership-verdict
- Pillar: Process, data, and compliance
- Format: Framework
- Published: 2026-10-23
- Last reviewed: 2026-10-23
- Reading time: 23 min
- Keywords: who owns a subsidiary account in salesforce, rules of engagement parent child account ownership, route subsidiary lead to parent account owner or regional rep, account ownership dispute between sales reps, acquired company account ownership after acquisition, global account vs regional account ownership rules

## Key takeaways

- In Refolk's index of professional profiles, the United Kingdom has 1.49 regional account managers and directors for every global one (2,236 against 1,504), so a default that routes subsidiary leads to the parent owner overrides the larger group of reps.
- A parent agreement that reaches a child entity proves the child can order on the parent's paper, not that the parent decides, so contract reach and buying autonomy have to be scored separately.
- Standard affiliate clauses define control as more than 50% of voting interests and cover a child only while it remains an affiliate, so control has to be confirmed on the day of the dispute.
- Acquisition markers move at different speeds: identity and email usually settle by around day 30, while identity and ERP consolidation typically runs 12 to 24 months, so a redirected domain alone does not prove integrated buying.
- Published inactivity windows differ even within one vendor's template (60 days in one version, 90 in an earlier one, three to six months elsewhere), so a tie-break has to name its window to be reproducible.
- Under this framework, a total of +4 or more is Parent Owner, -4 or less is Local Owner, and anything between is Split Coverage, with a fixed tie-break order naming the lead.

A lead, a rep's claim, or a new opportunity has landed on a subsidiary, regional entity, or acquired brand of an account someone else already owns, and two reps are about to collide in front of the customer. This guide is for revenue operations, recruiting operations, and deal desk staff who have to settle that dispute and defend how they did it. It gives you a five-dimension scoring rubric, a fixed tie-break order, and a dispute record that ends in one of three verdicts: Parent Owner, Local Owner, or Split Coverage. The aim is a verdict that a second analyst, scoring the same evidence, would reach too.

## What the subsidiary ownership verdict decides

The verdict decides who works one disputed child entity and who gets credit for it. That can be the rep who owns the parent account, the rep whose territory covers the child on its own merits, or both under a configured split. It is a call about one entity at one point in time. It is not a policy for the whole hierarchy.

The terms used throughout:

- **Child entity:** a subsidiary, regional entity, branch, or acquired brand that sits under an account someone already owns.
- **Parent owner:** the rep who holds the immediate or ultimate parent account, often a global account manager or director.
- **Local owner:** the rep whose region, territory, or segment would cover the child if the child were a standalone account.
- **Parent Owner verdict:** the parent owner works the child and takes full credit.
- **Local Owner verdict:** the child is worked as its own account by the local owner.
- **Split Coverage verdict:** both owners work the child, one is named as lead, and credit is split in the CRM.

So who owns a subsidiary account in Salesforce by default? Only whoever is set as owner on the child record. The native Parent Account field "is a lookup to one other account, one level up. That's the full extent of it." Nothing passes ownership down from the parent, and nothing finds the regional entity for you. That is why the first job in any dispute is to write the full path down.

#### The hierarchy path every dispute record needs

1. **Ultimate parent** - The top owning entity, where global account ownership usually attaches.
2. **Immediate parent** - The entity one level up, and the only link the native field stores.
3. **Nearest regional entity** - The country or regional company, where regional territories usually attach.
4. **Disputed child** - The subsidiary, branch, or acquired brand the lead or claim landed on.

*Record all four levels before scoring, because native Salesforce stores only the link one level up and cannot walk to the nearest regional entity.*

## Why parent and child ownership disputes keep happening

They keep happening because two large groups of account owners cover the same companies from different angles, and the tools and templates that route between them assume the ownership decision was already made. Neither the routing tools nor the published rules of engagement tell you how to decide whether a given child buys on its own.

### Two populations covering the same companies

In Refolk's index of professional profiles, global account roles are common in both large English-speaking markets, and regional account roles outnumber them.

| Market | Global AM/AD headcount | Employers seen in a 25-profile sample |
|---|---|---|
| United States | 5,257 | Intel, Dynatrace, AT&T, ArcelorMittal |
| United Kingdom | 1,504 | AWS, Snowflake, NVIDIA, ISS A/S |
| US to UK ratio | 3.5x | Derived |

| UK role | Headcount | Share |
|---|---|---|
| Global AM/AD | 1,504 | 40.2% |
| Regional AM/AD | 2,236 | 59.8% |
| Regional per global | 1.49 | Derived |

**1.49 - UK regional account roles for every global account role**

In Refolk's index, 2,236 people in the United Kingdom hold regional account manager or director titles, against 1,504 with global titles.

The collision shows up inside single companies. Intel appears both in the US sample of global account roles and in the UK sample of regional account roles. Read this as an illustration only. The employer lists come from 25-profile samples, and they cannot support a ranking of which employers run both models most.

### Why the published rules do not settle it

Published rules of engagement give you the frame but not the call. One common rule is customer precedence: "Leads from existing customers are assigned to the sales rep who is already managing that customer's account." Another is first-logged priority: "the rep who logs it in the CRM first gets priority." Neither one tells you whether the child is the same customer as the parent. No published template gives an opportunity-stage threshold for parent and child conflicts.

Routing playbooks state the conflict clearly and then leave it open. LeanData's hierarchy routing playbook puts it this way: "A lead from Waymo should probably go to the rep who owns Alphabet. A lead from a Sony subsidiary in Chicago might belong to a regional owner." The routing tools have defaults, though, and the defaults lean toward the ultimate parent. A data-quality writer, Formanorden, warns the other way: "A dashboard claiming a high match rate is insufficient if it attaches leads to parents while the selling entity is the subsidiary."

Put the [OURS] numbers next to that default and the cost is clear. Regional owners are the larger group in the UK, and they are the reps a parent-first default overrides most often, usually without anyone looking at the evidence.

## The five dimensions and what each one proves

Five dimensions decide the verdict: buying autonomy, contract reach of any parent agreement, integration status if the child was acquired, live engagement at either level, and segment and territory fit. Each one answers a different question, and each one can mislead in its own way. That is why none of them decides the verdict on its own.

| Dimension | What it proves | How it lies |
|---|---|---|
| Buying autonomy | Who decides and signs | Group portal covers other categories only |
| Contract reach | Child can order on parent paper | Divested child still listed as affiliate |
| Integration status | Acquired brand now buys as parent | Domain redirected, procurement still separate |
| Live engagement | Whose work is real right now | Automated activity, moved close dates |
| Segment and territory fit | Which coverage model fits the child | Headcount differs by source |

The trap people fall into most often is treating contract reach as if it proved autonomy. Standard affiliate clauses make an affiliate a customer when it signs its own order form. A child can therefore buy on paper the parent signed while still making the decision locally. The matrix below keeps the two apart.

#### Contract reach against buying autonomy

Horizontal axis runs from Parent paper does not reach the child to Parent paper reaches the child. Vertical axis runs from Child buys through the group to Child buys on its own.

| Quadrant | What it means |
| --- | --- |
| Standalone buyer | Lean Local Owner; the child decides and needs its own paper. |
| Local decision on parent paper | Lean Split Coverage; the local owner sells and parent terms apply. |
| Group buyer without paper | Lean Parent Owner; sell to group procurement on new paper. |
| Covered group buyer | Parent Owner; the child orders on what the parent signed. |

*A parent agreement that reaches a child shows the child can buy on the parent's terms, not that the parent decides, so the two are read on separate axes.*

> **Rule:** Score contract reach and autonomy separately
>
> Never let a yes on contract reach fill in the autonomy score. Record the clause and the procurement evidence in separate fields, each with its own source.

## How to score each dimension

Score each dimension from -2 to +2. A positive score pulls toward Parent Owner and a negative score pulls toward Local Owner. Where you find no evidence, the score is 0, not a guess. Every score cites a source the second analyst can open.

### Buying autonomy

Buying autonomy asks whether the child picks its own suppliers and signs its own contracts. The published definitions are clear. Decentralized purchasing means "each location or functional unit manages its own supplier relationships, buying decisions and contracts." Centralization depends on "eProcurement, supplier portals, master-data management, analytics." The hybrid, center-led model is "especially common in large enterprises (>1 billion dollars)." Decentralized buying suits firms with "scattered business units that maintain separate profit and loss accounts."

Groups have a reason to push toward centralization. One procurement benchmark cites centralized purchasing at $4.92 per $1,000 of revenue, against $6.10 for decentralized. That tells you which way the pressure runs. It does not tell you where any particular child stands.

Signals pointing to the group:

- A group supplier portal that lists the child as a group company.
- Group procurement or category roles at the parent that cover the category you sell.
- A shared-services centre that buys on behalf of the group.

Signals pointing to the child:

- A separate P&L, such as separately reported results or the child's own finance lead.
- A procurement or contracting contact employed by the child itself.

There is no published, documented method for checking each of these signals. What I describe here is a convention, not a standard. Record every signal with a URL, and note the category each one covers. A group portal for direct materials says nothing about software.

The people-based signals take the longest to check by hand, because you have to find who holds procurement roles at each level. In [Refolk](/) I ask for the group procurement roles at the parent and the procurement roles at the child, one plain-English sentence each, and compare where the buyers sit.

### Contract reach

Contract reach asks whether the child can order under an agreement the parent already signed. The usual wording, taken from the Salesforce MSA, defines an affiliate as any entity that "directly or indirectly controls, is controlled by, or is under common control with the subject entity." It defines control as "direct or indirect ownership or control of more than 50% of the voting interests." Coverage lasts only while the relationship holds: Customer includes Affiliates "(for so long as they remain Affiliates) which have entered into Order Forms."

Two variations change the score:

- **After-acquired coverage.** Everbridge's MSA states that "an entity that becomes an Affiliate after the execution of this Agreement will be deemed to be an Affiliate." A newly acquired child may already be covered.
- **Vendor discretion.** Some agreements say "All Affiliate orders are subject to Company's acceptance." Covered still means a separate order with separate approval.

Minority stakes and joint ventures fall outside the 50% clause. Deal desk or legal should read the clause. Ops should not interpret it.

### Integration status (acquired entities only)

Integration status asks whether an acquired brand now buys as part of the parent. Score it only for acquisitions. For any other child, score 0. The markers move at different speeds, so measure each one against the close date.

| Marker | Typical window | Source type |
|---|---|---|
| Identity and email stabilized | By day 30 | IT integration guide |
| Average integration | 8 months | Unit4 research |
| Vendor and email migration | Months 4 to 12 | Integration timeline guide |
| Brand transition | 12 to 18 months | Rebranding guide |
| Identity and ERP consolidation | 12 to 24 months | IT integration guide |

The same Unit4 research found that 20% of firms needed more than a year. The markers to check:

- A 301 redirect from the acquired domain to the parent's.
- Staff email addresses on the parent's domain.
- The careers page folded into the parent's.
- Leadership reporting into a parent function.
- Supplier onboarding running through the parent's procurement process.

Weight the slow markers more heavily. Email settles early and costs little to change, so it is weak evidence about buying. Brand and domain changes are also separate events: "Brand consolidation and domain consolidation don't have to happen on the same day." Redirects tend to stay up for a long time, since Google, as reported by WebFX, recommends waiting a year before removing them. The specific gap between close and procurement consolidation is not established publicly. Treat the 12-month threshold in the rubric as a convention and re-check it against your own closed deals.

### Live engagement

Live engagement asks whose work at the child is real right now. Count only human-logged calls and meetings at child contacts within a named window, and record any open opportunity scoped to the child along with its stage.

The window needs a name because the published ones disagree. Gradient Works' template treats a lead as expired after 60 days of inactivity, and an earlier version of the same template used 90 days. Amplify reassigns accounts after "no meaningful engagement within three to six months." Channel deal registration usually protects for 60 to 90 days. This framework uses 60 days. If your organization uses a different window, write that into the rubric. Do not leave each analyst to pick one.

### Segment and territory fit

Segment and territory fit asks which coverage model the child would fall into if it stood alone. Compare the child's headcount band and geography with the parent's segment and the territory definitions.

Segment break points are not standardized. One commonly cited set, attributed to TSIA but available only second-hand in a vendor glossary, puts the lines at "around 250-500 employees (SMB to mid-market) and 1,000-2,500 employees (mid-market to enterprise)." Other published bands put mid-market at 100 to 999 employees. Use your own company's bands. Read headcount as a band from at least two sources, because the exact counts differ between sources. No published rule covers a child that sits in a different segment from its parent. The rubric below supplies one.

**Subsidiary ownership scoring rubric**

```
Score each dimension -2 to +2. Positive pulls to Parent Owner, negative to Local Owner. No evidence = 0.

A. BUYING AUTONOMY
+2  Two or more group signals (group procurement role covering the category, shared-services centre, group supplier portal) and no separate P&L
+1  One group signal, nothing pointing local
 0  Center-led, mixed, or no evidence found
-1  One local signal (separate P&L or child-employed procurement contact)
-2  Separate P&L and a child-employed procurement or contracting contact

B. CONTRACT REACH OF THE PARENT AGREEMENT
+2  Agreement in force, affiliate clause reaches the child, parent control above 50% confirmed today
+1  Reaches the child, but affiliate orders need vendor acceptance or eligibility confirmation
 0  No parent agreement in force
-2  Parent control 50% or less, joint venture, or divested

C. INTEGRATION STATUS (acquired entities only, otherwise 0)
+2  Three or more markers flipped, including procurement onboarding or leadership reporting line
+1  Two independent markers flipped
 0  One marker or none, 12 months or less since close
-2  One marker or none, more than 12 months since close

D. LIVE ENGAGEMENT (human-logged calls and meetings at the child, last 60 days)
+2  Parent owner has an open opportunity scoped to the child; local owner has no human activity
+1  Only the parent owner has human activity at the child
 0  Both or neither
-1  Only the local owner has human activity at the child
-2  Local owner has an open opportunity scoped to the child; parent owner has no human activity

E. SEGMENT AND TERRITORY FIT
+2  Child in the parent's segment band and inside the parent owner's territory
+1  Same band, outside the parent owner's home territory but inside a global remit
 0  Band unclear (sources straddle a break point)
-1  Child one band below the parent
-2  Child one or more bands below and inside a named regional territory

VERDICT
Total +4 or more  -> Parent Owner
Total -4 or less  -> Local Owner
Total -3 to +3    -> Split Coverage (tie-break names the lead)

OVERRIDES
A = -2 caps the verdict at Split Coverage.
A = +2 and B = +2 together rule out Local Owner.
```

*Keep the scores and thresholds fixed across analysts; change the 60-day window only if your written rules of engagement use another.*

I ran this search: `Global procurement directors at UK-headquartered groups with 5,000+ employees that run a shared-services centre` - [see the full result list](https://www.refolk.ai/s/0w0t859wmp).

*Returns named group procurement leaders with their employer and title, which shows whether category buying sits at group level before you score autonomy.*

## How the scores become a verdict

Add the five scores, apply the two overrides, and read off the verdict. A total of +4 or more is Parent Owner, -4 or less is Local Owner, and anything from -3 to +3 is Split Coverage, with the tie-break order naming the lead. These thresholds are this framework's convention. No published standard sets them. Keep them fixed so verdicts stay comparable.

The overrides exist because autonomy is the dimension that tells you who actually buys:

- **Autonomy veto.** If autonomy scores -2, the child picks its own suppliers and signs its own contracts. Strong engagement and contract reach on the parent side can still earn a Split, but they cannot make the parent owner the only seller.
- **Covered group buyer.** If autonomy and contract reach both score +2, the child buys through the group on paper the group signed. A local owner's activity can earn a Split, but not a Local Owner verdict.

### The tie-break order

A Split verdict still needs a lead, and a contested verdict needs a rule that decides it the same way every time. Work through the rules in order and stop at the first one that decides.

#### Tie-break order for a Split or contested verdict

1. **Expire stale claims** - Drop any claim with no human-logged call or meeting at the child in 60 days.
2. **Customer precedence** - If the child already buys under its own account, that account's owner leads.
3. **Older live opportunity** - Otherwise the owner of the older open opportunity scoped to the child leads.
4. **First logged** - Otherwise the rep who logged the child in the CRM first leads.
5. **Log the rule** - Record which rule decided, and the date, in the dispute record.

*Apply the rules in this order and stop at the first one that decides, so two analysts name the same lead.*

The third rule uses opportunity age, not stage, on purpose. No published template gives a stage threshold for parent and child conflicts, and stages are easier to move than creation dates.

> A routing rule that defaults to the parent is a verdict issued before anyone looked at the evidence.

### Configuring a Split in Salesforce

A Split only counts once the CRM records it. In Salesforce, team selling has to be enabled first: "In Setup, go to Opportunity Team Settings and enable Team Selling." Then enable opportunity splits. Revenue splits must total 100%, and overlay splits can go above 100%. Integration documentation from Celigo notes "You can have a maximum of 5 split types," so check how many your organization already uses before you add one for subsidiary coverage.

> **Tip:** Keep the lead's revenue split whole
>
> If your comp plan allows it, credit the supporting owner through an overlay split rather than a share of the revenue split. Overlay splits can exceed 100%, so the lead's number stays intact and the argument usually ends there.

## Step by step: settling one disputed child entity

The procedure runs in seven steps, from resolving the entity to logging the verdict. Each step has a named owner and a clear done state. No source publishes how long these steps take. A rough internal estimate of 10 to 20 minutes for entity resolution is unverified, so time your own first ten disputes before you promise reps a turnaround.

Sources disagree about the starting point. Routing tools start by sending the lead to the parent automatically. This procedure starts by writing down the full hierarchy and scoring before anything is routed, because routing first biases the result toward Parent Owner.

#### Settling a subsidiary ownership dispute

1. **Resolve the entity** - Match the lead to an account and write the immediate parent, ultimate parent, and nearest regional entity into the dispute record, with the date the hierarchy data was last refreshed.
2. **Check contract reach** - Deal desk or legal reads the affiliate definition and any after-acquired clause in the parent agreement and confirms parent control is above 50% today. Record a yes or no on whether the child can order on parent paper.
3. **Score buying autonomy** - Look for group signals (supplier portal, group procurement roles, shared-services centre) and local signals (separate P&L, child-employed procurement contact). Record each signal with a URL and score it on the rubric.
4. **Score integration status** - For acquired entities only, check the domain redirect, email domain, careers page, leadership reporting line, and procurement onboarding, each dated against the close. Record months since close and which markers have flipped.
5. **Score live engagement** - From the CRM, count human-logged calls and meetings at the child in the last 60 days for both owners, and note any open opportunity and its stage.
6. **Score segment and territory fit** - Place the child and parent in your segment bands using at least two headcount sources, then check the child's geography against territory definitions. Record fit or mismatch.
7. **Issue the verdict and apply the tie-break** - The ops lead totals the scores, applies the overrides, names the verdict, and cites the tie-break rule where needed. For a Split, enable team selling and set revenue splits that total 100%.

Record every dispute in the same format so that a second analyst can re-score it from the record alone.

**Subsidiary ownership dispute record**

```
Child entity:
Immediate parent:
Ultimate parent:
Nearest regional entity:
Hierarchy data last refreshed (date):
Parent owner:
Local owner:
Date scored:

A. Buying autonomy - score:      Evidence and URLs:
B. Contract reach - score:       Agreement, clause, control above 50% confirmed on (date):
C. Integration status - score:   Close date, months since close, markers flipped with dates:
D. Live engagement - score:      Last human-logged activity (parent / local), open opportunity and stage:
E. Segment and territory - score: Headcount band per source, child geography, territory name:

Total:
Override applied (none / autonomy veto / covered group buyer):
Verdict (Parent Owner / Local Owner / Split Coverage):
Tie-break rule that decided the lead:
Lead owner:
Split configured (revenue totals 100%): yes / no / not applicable
Re-score trigger and date:
Scored by:             Second scorer:             Match: yes / no
```

*One record per disputed child entity; paste into the dispute ticket or a CRM note and fill every line, writing "none found" rather than leaving a blank.*

## How the verdict goes wrong

Most bad verdicts come from evidence that looks solid and is not. These are the known failure modes, what each one looks like, and the check that catches it.

1. **The divested affiliate.** The affiliate clause covers a child only "for so long as they remain Affiliates." A child that has been sold off still scores as covered if you read the agreement as it stood at signing. Confirm current ownership on the day of the dispute.
2. **Covered, but not automatically.** The clause is there, but the vendor "may request reasonable information to confirm the Affiliate's eligibility," or every affiliate order needs acceptance. Covered can still mean a separate order with separate approval. Score +1, not +2.
3. **The redirect read as integration.** A domain redirect gets read as full integration, even though brand and domain changes are decoupled and email, procurement, and SSO can stay separate for a year or more. Require at least two independent markers, and weight procurement and reporting-line markers above web markers.
4. **Automation counted as engagement.** Activity counts get inflated by workflows. One Zoho user reports that "whenever there are workflows or automatizations this is logged as activity." Count human-logged calls and meetings only, and filter by activity type, not by total.
5. **Moved close dates.** Gradient Works documents reps "changing opp dates to hold onto them longer than the normal ownership time." Audit the field history on close dates for any opportunity that decides a tie-break, and use the creation date for the age rule.
6. **The stale hierarchy.** Custom text fields that store hierarchy data as static values "will not update automatically," and when parent ownership changes, nothing passes down to the children. A verdict built on an old structure routes to the wrong owner. Record when the hierarchy data was last refreshed, and treat anything older than your last reparenting run as suspect.
7. **The exact headcount.** Headcount differs between data sources, and a child of 980 in one source and 1,040 in another sits on either side of a common break point. Use bands, and score 0 when the sources straddle a line.
8. **The default that decided for you.** Routing tools whose main use case is sending subsidiary leads to the ultimate parent owner will produce a Parent Owner verdict without any check of autonomy. If the lead was routed before scoring, score it as if it had not been, and do not count the routing outcome as evidence.
9. **The sample read as a ranking.** The employer lists behind the [OURS] tables come from 25-profile samples. They show that a company runs both global and regional account roles. They do not show which companies run them most.

> **Watch out:** Absence of evidence is not local autonomy
>
> An analyst who finds no group procurement signal and scores autonomy -2 has made the parent look absent when it was only unsearched. No evidence scores 0, and the record says what was searched.

The best guard against all nine is the second scorer. If two analysts working from the same record disagree by more than one point on any dimension, the evidence is ambiguous. Fix the record before you issue the verdict.

## Keeping verdicts current

A verdict is valid only as long as its evidence. Set a re-score trigger on every record when you issue it, and re-run the full rubric rather than patching one score when a trigger fires.

Re-score when any of these happens:

- **Ownership changes.** A divestiture, a minority sell-down, or a reparenting changes contract reach immediately.
- **The 12-month mark after an acquisition.** Brand transitions most often finish within 12 to 18 months, and identity and ERP consolidation runs 12 to 24 months. The integration score is likely to move in that period.
- **A claim expires.** Once 60 days pass without human-logged activity, the engagement score and the tie-break can both flip.
- **The parent agreement renews.** Affiliate definitions and after-acquired clauses change between versions.
- **The hierarchy refreshes.** Every reparenting run can move a child under a different regional entity.
- **Segment bands change.** Re-band the child whenever your company redraws its segments.

Write the window and the thresholds into your rules of engagement, not just into this rubric. Published windows have changed even within a single vendor's template, and the only way two analysts stay consistent is to work from the same written number. For an ops team that needs to staff this work, I find the reviewers fastest by searching Refolk for revenue operations managers who mention account hierarchy or territory design in their profile, since they already think in parent and child paths.

#### Before you log the verdict

- [ ] The dispute record names the immediate parent, ultimate parent, and nearest regional entity, with the hierarchy refresh date.
- [ ] Parent control above 50% was confirmed on the date of scoring, not taken from the date the agreement was signed.
- [ ] Every autonomy signal has a URL and a category, and missing evidence is scored 0.
- [ ] Integration status cites at least two independent markers, each dated against the close.
- [ ] Engagement counts exclude workflow and automation activity, and close-date field history was checked.
- [ ] Headcount was read as a band from at least two sources.
- [ ] The total, any override, and the tie-break rule that decided the lead are written into the record.
- [ ] A second analyst scored the same record and matched the verdict, or the disagreement is logged.
- [ ] For a Split, team selling is enabled and revenue splits total 100%.
- [ ] A re-score trigger and date are set on the record.

## Frequently asked questions

### Who owns a subsidiary account in Salesforce by default?

Whoever is set as owner on the child record, and nothing more. The native Parent Account field is a lookup to one account one level up, it cannot walk the hierarchy to the nearest regional entity, and an ownership change at the parent does not pass down to child accounts. Any rule linking parent and child ownership has to come from your routing logic or a written policy, and that is why disputes need a scored verdict.

### Does a parent company's master agreement cover purchases by its subsidiaries?

Often it does, but only under conditions. Typical affiliate clauses cover entities under more than 50% common control, and only for as long as they stay affiliates. Some agreements also cover affiliates acquired after signing, and some make every affiliate order subject to the vendor's acceptance. Minority stakes and joint ventures usually fall outside the clause. Read the definition and confirm current ownership before scoring.

### How long should an acquired company stay a separate account after the deal closes?

No published rule sets a fixed period, and the gap between close and procurement consolidation is not established publicly. Published ranges put identity and email at around day 30, average integration at eight months, brand transitions at 12 to 18 months, and identity and ERP consolidation at 12 to 24 months. Score the markers that have actually flipped rather than the calendar, and re-score at the 12-month mark.

### What inactivity window should rules of engagement use for parent and child disputes?

Pick one, write it down, and use it every time. One widely shared template expires a lead after 60 days of inactivity, an earlier version of the same template used 90 days, and another playbook reassigns accounts after three to six months without meaningful engagement. This framework uses 60 days of human-logged calls and meetings. What matters most is that the window is named, so two analysts reach the same verdict.

### Should leads from a subsidiary always route to the global account owner?

No. Routing to the ultimate parent owner is the default in common routing tools, but that settles the dispute before anyone checks whether the child buys on its own. A subsidiary with its own P&L and its own procurement contact may belong to the regional owner even when the parent agreement reaches it. Score buying autonomy first and let the evidence decide the verdict.

### How do you split credit when a global rep and a regional rep both work a subsidiary?

Issue a Split Coverage verdict, name the lead with the tie-break order, and set up the split in the CRM. In Salesforce, team selling has to be enabled first. Revenue splits must total 100%, and overlay splits can go above 100%, so a supporting owner can get overlay credit without reducing the lead's revenue split if your comp plan allows it.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/subsidiary-account-ownership-verdict*