How to Run a Value Chain Analysis

A value chain analysis maps the activities that create a group’s competitive advantage, weights their relative importance, and locates the people, assets, and risk control behind them, so the group can test whether its profit outcomes align with where value is created and controlled. This guide runs the analysis end to end on one worked example, from scoping through the value-driver map and the control assignment to the value-based allocation and the value contribution gap.

Scope the Exercise Before You Start

A value chain analysis is only as good as the evidence and judgment behind it, and the choices made at the outset shape everything downstream. Settle three things before mapping anything.

• Fix the purpose. The depth and emphasis of the analysis depend on why it is being run. Common purposes include building a pre-audit defense file ahead of an expected examination; supporting a restructuring business case, where the analysis documents the value drivers before and after the change; underpinning an advance pricing agreement or a mutual agreement procedure; testing whether an existing transfer pricing model still aligns profit with value after a business change such as an acquisition or a new product line; and refreshing routine documentation for the Master File. Each calls for a different level of rigor, so name the purpose, because it governs how far to push the weighting and substance work.
• Set the boundary. Decide which entities, business lines, and transactions are in scope. A group-wide analysis and a single-business-line analysis produce different value chains; mixing levels produces a map that supports neither.
• Line up the evidence. The analysis draws on interviews with the people who perform and control the activities, the group’s strategic and operational data, financial statements by entity, existing functional analyses, and intercompany agreements. Identify the sources and the interviewees before mapping, because the weighting later stands or falls on this evidence.

The Worked Example

The example carried through this guide involves an industrial-equipment group, analyzed at group level across its principal business.

Figures throughout are illustrative and expressed as a percentage of group EBIT.

The eight steps below run the analysis from the value-driver map through the control assignment and the weighting to the value-based allocation, the gap, and the application of the result.

A value driver is an activity or capability that creates the enterprise’s competitive advantage: the strategic decisions, intellectual property, production know-how, and customer relationships that let it earn more than a marginal return, as distinct from the routine activities every competitor must perform. Mapping the business by its value drivers, rather than by its legal entities or its supply chain, is what lets the analysis tie profit to where advantage is created: it locates each driver, and the substance behind it, so that later steps can test whether profit sits where the value-creating activities are controlled. The mapping phase produces the raw material for everything that follows: the value drivers, their component activities, and the entities that control them.

Identify the value drivers. Break the business into its value-driving families and arrange them along the chain. For the worked example the families are:

• Strategy and governance
• Research and development, and product technology
• Manufacturing and production
• Procurement and supply chain
• Sales, service, and customer relationships

Decompose each driver into activities. Each family breaks into the specific activities that deliver it. Strategy, for instance, covers group governance, portfolio and launch decisions, expansion planning, financing strategy, risk-management strategy, and pricing strategy. Do this for every family, because the control analysis operates at the activity level, not the family level.

Map assets and risks alongside activities. For each activity, record the key assets it uses and the economically significant risks it involves, and note the entity that manages each. This is what lets the later steps tie value to substance rather than to labels.

The result is a mapping table that runs one row per activity. A short extract for two activities in the worked example might look like this:

Building this table for every activity is what turns an abstract value chain into an evidenced record that the control assignment in Step 2 operates on.

Mapping who performs an activity is not enough; the analysis has to record who controls it, because control is what drives profit attribution. RACI is a responsibility-assignment tool borrowed from project management: for any given activity, it separates the party that does the work from the party that owns the decision, distinguishing four roles, Responsible, Accountable, Consulted, and Informed. Adapted to transfer pricing, it provides the discipline to record not just involvement but control. For each activity, record the four roles.

Three points on applying the RACI:

• The accountable role is the one that matters most. It corresponds to the control of economically significant risk that the post-BEPS framework treats as decisive. An accountable party can take on or decline a risk-taking opportunity and decide how to respond to and mitigate it.
• Record the controlling jurisdiction per activity. Tag each accountable role with the entity and country that holds it. The concentration of accountable roles by jurisdiction is the output that later drives the value-based allocation.
• Follow conduct, not the org chart. Credit an entity with control only where the people who exercise it are located there. Where the org chart and the actual conduct diverge, the conduct governs.

Not every activity creates competitive advantage, and treating them alike would overstate the profit that should follow routine work. Classify each driver by the kind of value it contributes.

Why the classification matters:

• It bridges the qualitative map and the quantitative allocation. Differentiators attract non-routine profit and point toward a profit split or residual analysis; must-haves are benchmarked against comparable service providers or distributors and earn a routine return.
• It produces the value heat map. Colour-coding the activity map by these three categories shows at a glance where, and in which jurisdictions, the differentiating activities are concentrated.
• Risk influencers need the most judgment. They sit between the two poles, and where they land materially affects the weighting in the next step.

Weighting turns the classified map into numbers, and it is the most sensitive step in the whole exercise. The importance of each driver is expressed as a share of group profit.

How the weights are derived. There is no single formula, and the weighting is a matter of reasoned judgment rather than calculation. In practice, taxpayers triangulate across several approaches and reconcile them:

• Structured interview scoring. Ask the executives who run each function to rank and score the value drivers by their contribution to competitive advantage, then aggregate the scores. Scoring by several independent interviewees and comparing the results guards against any one person’s bias.
• Financial proxies. Use objective financial data that correlates with value creation as a cross-check on the interview scores: the R&D spend behind product technology, the marketing investment behind brand, the gross-margin contribution of each product line, or the capital employed in production. These do not set the weights on their own, but they discipline them.
• Industry benchmarks. Compare the provisional weighting against how value is understood to be created in the industry. A pharmaceutical group would expect R&D and regulatory drivers to carry heavy weight; a consumer-brand group would expect marketing intangibles to dominate. A weighting that departs sharply from the industry pattern needs a specific reason.
• Functional-contribution analysis. Where a driver can be tied to a measurable output, for example the incremental margin a differentiating activity generates over a routine baseline, use that to anchor its weight.

The weights are a reasoned estimate supported by this evidence, not a precise measurement, and the documentation should present them that way: the approaches used, the data behind them, and the judgment applied to reconcile them.

How to weight.

• Assign each value driver a weight equal to its estimated share of the profit the group’s competitive advantage generates. The weights sum to 100 percent.
• Ground each weight in evidence: the interviews, the group’s strategic and operational data, and an understanding of the industry. Do not assert weights.
• Document the basis for each weight. The defensibility of the entire analysis rests on this documentation, because a reviewer will probe the weighting before anything else.

The worked example assigns the following weights to the five drivers:

With drivers weighted and control mapped, each driver’s weight is spread across the entities that control its activities. Summing down the entities gives the value-based allocation of group EBIT.

The mechanics. For each driver, distribute its weight across entities in proportion to where its activities are controlled, then total each entity’s column.

In the worked example the distribution produces the following value-based allocation:

The value-based allocation shows where profit would sit if it followed the controlled value drivers: the R&D centre’s control of product technology gives it 23 percent, close to the manufacturing operation and not far behind the principal.

The value-based allocation only becomes useful when set against what the group reports. The difference is the value contribution EBIT gap.

Determine the as-is allocation. The as-is allocation is each entity’s actual share of group EBIT, expressed on the same percentage basis as the value-based allocation so the two are comparable. Take each entity’s reported operating profit (EBIT) from the segmented financials for the business under analysis, then divide it by group EBIT for that business to convert it into a percentage. The result is what the group’s current transfer pricing outcomes deliver, entity by entity, ready to be set against the value-based picture. Constructing both figures the same way, as a share of the same group EBIT, is what makes the comparison meaningful; a value-based share built on one basis and an as-is share built on another would not be comparable.

Compute the gap. For each entity, subtract the as-is allocation from the value-based allocation. The gaps sum to zero by construction, because profit reallocated toward one entity comes from another.

Read the gap as a diagnostic. The story here is the Israel R&D centre: it controls the activities behind the group’s most heavily weighted differentiator, product technology, yet reports only 7 percent of group EBIT against a value-based share of 23, a positive gap of sixteen points. The German principal and, to a lesser degree, the Polish manufacturer and Brazilian distributor report more than their value contribution supports.

What the gap does and does not do:

• It flags misalignment and points to what to examine. Here: whether the product-technology IP and the decisions developing it are in fact controlled in Israel, and whether the principal’s reported return reflects functions and risk control it actively exercises.
• It does not set an arm’s length price. The weights rest on judgment, and the gap identifies the transactions that need closer delineation rather than delivering a number.

Is the value-based allocation an arm’s length result?

No, and this distinction is the one most often misunderstood, so it is worth stating plainly. A value chain analysis is not one of the transfer pricing methods, and its output is not, by itself, an arm’s length allocation that a tax authority will accept as the basis for taxing profit.

• It is a diagnostic and framing tool, not a pricing method. The recognized methods (CUP or CUT, resale price, cost plus, the transactional net margin method, and the profit split) are what produce an arm’s length price. The value-based allocation is a reasoned estimate built on judgment-based weights; it shows where profit would sit if it tracked the controlled value drivers, which is a hypothesis to be tested, not a defensible transfer price.
• The gap points to work; it does not complete it. Where the analysis reveals a material gap, the response is to revisit the delineation of the affected transactions and apply the most appropriate method to price them. The arm’s length outcome comes from that method, informed by the value chain analysis, not from the percentage split the analysis produced.
• Where its framing does carry weight with authorities. Tax authorities increasingly expect the whole-value-chain view and use value chain analysis themselves in risk assessment; a well-constructed analysis supports the Master File, frames a defense, and helps in APA and mutual-agreement discussions. But it supports and contextualizes a position priced by a recognized method. It does not replace that pricing, and presenting a value-based percentage split as though it were the arm’s length answer invites challenge.

The practical takeaway is that the value chain analysis tells you where to look and what story the numbers should tell; the transfer pricing method tells you what the arm’s length number is. The profit split is the method that most often does the pricing where the analysis has surfaced unique contributions on more than one side, but selecting and applying it is a separate exercise from the value chain analysis itself.

The analysis earns its place by what it supports. Match the application to the purpose set in Step 1.

• Model design and DEMPE. Test whether profit sits where value is created and controlled. Where it does not, evaluate realignment options before an authority raises them. The same evidence supports a DEMPE analysis by making explicit which entities perform and control the development, enhancement, maintenance, protection, and exploitation of the group’s key intangibles.
• Documentation. Use the analysis to drive consistency across the Master File (a coherent account of group value creation), each Local File (a group-anchored functional analysis), and the reconciliation against Country-by-Country Reporting.
• Controversy and APAs. Prepare the analysis as part of a pre-audit defense file. It lets the group present its global business coherently, defend a local position in the context of the whole, and cut through differences of language and perspective in APA and dispute-resolution discussions.
• Business restructuring. Where the analysis points to realignment, use it as the evidentiary backbone: it documents the value drivers before the change, the reference point for assessing exit charges and for characterizing the post-restructuring profiles of the affected entities.

Before relying on the result, test it, then record it so a reader can reconstruct the analysis.

Stress-test the weighting. Because the gap is driven by the weights, recompute the allocation under a plausible alternative weighting and see how far the gap moves. A gap that survives reasonable alternative weightings is far more defensible than one that depends on a single set of assumptions.

Cross-check for reasonableness.

• Substance. Confirm each entity’s value-based share is consistent with the people, decision-making, and risk control located there.
• Coherence. Confirm the allocation tells a consistent story with the group’s business model and any existing functional analysis.

Document the analysis. Record the scope and purpose; the value-driver map with activities, assets, and risks; the RACI assignments and controlling jurisdictions; the classification and heat map; the weights with their evidential basis; the value-based allocation; the as-is comparison and the gap; the stress-test; and the conclusions drawn. Keep the underlying interview notes and data so the weighting can be supported if challenged.

A consolidated worklist for the full analysis. Each item should be completed and evidenced in the documentation file.