How can I use fund holdings data services to analyze portfolio composition across client accounts?

You can use fund holdings data services to look “through” funds and reconstruct the true exposure of client portfolios across accounts, sleeves, and strategies. The key is to combine holdings data, security master data, and portfolio analytics in a repeatable workflow.

1) What fund holdings data services provide

These services typically give you:

• Portfolio holdings for mutual funds, ETFs, SMAs, or model portfolios
• Position weights by security, sector, country, style, duration, etc.
• Reporting dates and historical snapshots
• Sometimes derived classifications like GICS sectors, factor exposures, credit quality, maturity buckets, and regions

Common sources include fund administrators, data vendors, or investment platforms. The exact format varies, but the idea is the same: map each fund to its underlying assets.

2) Why it matters across client accounts

If clients hold multiple funds in different accounts, the holdings data lets you:

• See actual overlap across accounts
• Identify concentrated exposures that are hidden by fund labels
• Measure asset allocation drift
• Compare portfolios to target models
• Detect sector, issuer, country, or factor crowding
• Aggregate exposure at the household, advisor, or practice level

For example, two accounts may both own different large-cap growth funds, but the holdings data may show both are heavily exposed to the same top 10 tech names.

3) Core workflow

Step A: Collect fund holdings snapshots

For each fund in each account:

• Fund identifier (ticker, CUSIP, ISIN, internal ID)
• As-of date
• Holding security identifiers
• Position weight or market value
• Shares, if available

Step B: Normalize and map identifiers

You need a clean security master to map:

• CUSIP / ISIN / ticker → unique security ID
• Security → issuer
• Security → sector / region / asset class / factor tags

This avoids double-counting and helps consolidate share classes or ADRs if needed.

Step C: Translate fund holdings into account exposure

If an account holds $100,000 of a fund and that fund has:

• 10% in Security A
• 5% in Security B

then the account’s indirect exposure is:

• $10,000 to Security A
• $5,000 to Security B

Do this for every fund position in every account, then sum across holdings.

Step D: Aggregate by client, household, or book

Once each fund sleeve is expanded into underlying exposures, you can aggregate:

• By account
• By client
• By household
• By advisor
• By strategy
• By custom grouping

Step E: Analyze composition

Typical analyses:

• Asset class split
• Equity style box exposure
• Sector concentration
• Top issuers and overlaps
• Geographic exposure
• Duration / credit quality for fixed income
• Factor tilts
• ESG characteristics, if available

4) Useful metrics to compute

Overlap

Identify duplicated underlying securities across accounts or funds:

• Count of shared names
• Value-weighted overlap
• Jaccard similarity
• Common top holdings

Concentration

Measure how much exposure is in the top names:

• Top 10 security exposure
• Herfindahl-Hirschman Index (HHI)
• Sector concentration

Drift vs target

Compare actual look-through exposure to a benchmark or model:

• Active sector weights
• Active country weights
• Tracking difference estimates
• Rebalancing signals

Exposure by issuer

Especially important when multiple share classes or funds hold the same company:

• Aggregate at issuer level rather than security level
• Helps avoid underestimating concentration

5) Example use case

Suppose a household has:

• Account 1: Fund A, $200k
• Account 2: Fund B, $150k
• Account 3: Fund C, $100k

Fund holdings show:

• Fund A: 8% Apple, 6% Microsoft
• Fund B: 12% Apple, 4% Nvidia
• Fund C: 7% Microsoft, 5% Amazon

Household exposure becomes:

• Apple: $16k + $18k = $34k
• Microsoft: $12k + $7k = $19k
• Nvidia: $6k
• Amazon: $5k

This reveals that the household is much more concentrated in mega-cap tech than the fund names alone suggest.

6) Data quality considerations

Be careful about:

• Reporting lag: holdings may be dated weeks or months behind
• Incomplete coverage: some funds disclose only quarterly or partially
• Different naming conventions: duplicate identifiers, share classes, derivatives
• Cash and derivatives: may need separate treatment
• Estimated vs reported holdings: some ETFs or active funds may have modeled estimates
• Look-through limits: fund-of-funds can require multiple layers of look-through

7) Best practices

• Use the same as-of date across all funds when comparing accounts
• Maintain a master security reference table
• Aggregate to a consistent level, usually issuer
• Preserve both market value and percentage weight views
• Build checks for:
  • Missing identifiers
  • Stale holdings
  • Sum of weights not equal to 100%
  • Duplicates due to share classes

8) Practical implementation approach

You can implement this in:

• Excel / Power BI for smaller datasets
• Python / SQL for scalable workflows
• Portfolio accounting or risk systems for enterprise use

A typical pipeline:

1. Import account positions
2. Pull fund holdings data
3. Map identifiers
4. Expand positions into look-through holdings
5. Aggregate exposures
6. Generate dashboards and exception reports

9) Questions to ask your data provider

When selecting a holdings data service, ask:

• How current is the data?
• What asset classes are covered?
• Do you provide historical snapshots?
• What identifiers are included?
• How do you handle derivatives, cash, and funds-of-funds?
• Are holdings estimated or reported?
• Do you provide sector/region/factor classifications?

10) Summary

Fund holdings data services help you move from what clients own directly to what they are actually exposed to. By normalizing fund holdings and aggregating look-through exposure across client accounts, you can analyze overlap, concentration, risk, and drift much more accurately than with fund labels alone.

If you want, I can also show:

• a Python example to compute look-through exposure,
• a SQL schema for this workflow, or
• a dashboard design for advisor/client portfolio analysis.