Skip to content
GFS — Gayatri Financial Synergy
Index Funds

Tracking Difference vs Tracking Error: A Document-First Guide

Learn how to distinguish tracking difference from tracking error, align periods and plans, and audit passive-fund disclosures without turning one number into a verdict.

Reviewed by Team GFS Research DeskPublished 30 July 2026Updated 28 July 20267 min read

Tracking difference tells you how far a passive scheme’s return was from its stated benchmark return over one matched period. Tracking error describes how variable those return gaps were across a series of observations. They answer different questions, so neither should be read alone. First match the scheme, plan, benchmark variant, dates and return convention; then trace the number to the fund’s official disclosure.

Direct answer (52 words): Tracking difference is a period result: scheme return minus benchmark return, using like-for-like data. Tracking error is a consistency statistic: the dispersion of repeated return differences, often annualised under a stated method. A fair reading requires the same plan, benchmark, frequency, period and source—and still does not establish investor suitability.

Reviewed by GFS Research Desk.

Why two similar labels create a real reader problem

A passive fund seeks to follow an index, but an investor never owns the index directly. The scheme holds securities, handles subscriptions and redemptions, pays permitted costs, manages cash, applies index changes and values a portfolio. Those operational realities can create a gap between scheme and benchmark returns.

The confusion begins when a factsheet shows “tracking error” while a table elsewhere shows scheme and benchmark returns. A reader may subtract two numbers, call the result tracking error, and compare it with a published statistic calculated from daily observations. That comparison mixes a single-period outcome with the variability of many outcomes.

The safer habit is document literacy, not number hunting: identify exactly what each figure represents before interpreting it.

The core distinction

QuestionTracking differenceTracking error
What does it describe?The return gap over a specified periodThe variability of repeated return gaps
Basic expressionScheme return − benchmark returnDispersion of periodic scheme-minus-benchmark returns
Essential contextStart date, end date, plan, benchmark and return conventionObservation frequency, sample window, annualisation and formula
Can the sign matter?Yes; the gap may be negative or positiveUsually presented as a non-negative dispersion statistic
What can it settle alone?Neither quality nor suitabilityNeither future outcomes nor suitability

Suppose a hypothetical scheme return is 9.4% and its matched benchmark return is 10.0% for exactly the same year. The arithmetic tracking difference is −0.6 percentage points. That does not tell us whether the gaps were steady through the year. They might have stayed near the same level or moved widely before ending at −0.6 percentage points.

Now imagine twelve monthly return gaps. Their dispersion can be summarised as tracking error under a disclosed method. A lower number means the observed gaps clustered more tightly under that method and window; it does not mean the scheme delivered a higher return, avoided loss, or will repeat the pattern.

A six-field alignment test before any calculation

1. Scheme identity

Confirm the exact scheme name. ETF and index-fund versions of a similar exposure are separate products with different operational structures. Do not splice data from one into the other.

2. Plan and option

Confirm whether the return series belongs to the same plan and option throughout. Expense structures can differ across plans. A return from one plan and an expense figure from another do not create a valid explanation.

3. Benchmark identity and variant

Use the benchmark printed in the official scheme material. Similar index names may refer to different variants or return conventions. Do not silently replace the stated benchmark with a familiar index.

4. Matched dates

Both return series need the same start and end dates. A month-end factsheet value cannot be paired with a benchmark value taken on a different trading day without a documented treatment.

5. Return convention

Check whether the figures are point-to-point, annualised, calendar-period or another stated format. Percent and percentage points are not interchangeable: moving from 10% to 11% is a one-percentage-point increase, which is a 10% relative increase.

6. Method and source

For tracking error, record observation frequency, calculation window, annualisation convention and publication date. If the disclosure does not state enough to reproduce or understand the number, label that limitation rather than filling the gap with an assumption.

Where to look in the document stack

Start with the current official scheme factsheet or passive-fund disclosure for the reported statistic and its “as of” date. Next inspect the Scheme Information Document (SID) for the investment objective, benchmark and structural details. Use the Key Information Memorandum (KIM) for a concise scheme summary, but return to the SID where fuller wording is needed.

Then inspect the AMC’s official portfolio and expense disclosures for the same period and plan. AMFI also maintains industry access points for tracking-error information and scheme expense data. On 21 July 2026, the AMFI tracking-error page exposed month choices through June 2026, while its expense page exposed the 2026–27 reporting year. These observations establish availability only; they are not a comparison of schemes.

SEBI’s official legal circular repository is the appropriate place to check the current regulatory source trail. Rules and disclosure formats can change, so a dated article or screenshot should not substitute for the current official document.

Why the gap can exist

Expense ratio is an intuitive contributor because scheme expenses affect the NAV-based investor return while an index is a constructed benchmark. But it is not a complete bridge from benchmark to scheme performance.

Other possible contributors include cash held for flows, timing of purchases and sales, index rebalancing, transaction and statutory costs, valuation timing, corporate-action handling, and taxes or withholding relevant to the portfolio. Their importance varies by structure and period. A visible difference should therefore prompt a source check, not an unsupported causal story.

For an ETF, market-price behaviour adds another layer. Tracking statistics based on NAV are not the same thing as the investor’s exchange execution price. Bid–ask spread and premium or discount to NAV concern trading experience; they should not be folded into NAV tracking difference without saying so.

A reproducible reading workflow

  1. Save the source files. Record URLs, filenames, publication dates and “as of” dates. A later factsheet may replace the file at the same URL.
  2. Write the identity line. Scheme, plan, option, benchmark, structure and currency belong on one line.
  3. Write the period line. Start date, end date and return convention belong on another.
  4. Transcribe, do not paraphrase, the inputs. Preserve the displayed precision and units.
  5. Calculate only a matched tracking difference. Label it as your arithmetic if the source did not publish it.
  6. Copy tracking error with its method. Never reverse-engineer an unstated frequency or annualisation factor.
  7. Read related disclosures. Expense, portfolio, cash, rebalancing and corporate-action context may explain part of the outcome, but causation needs evidence.
  8. State unknowns. Missing method notes, stale files or unmatched dates are findings, not invitations to guess.

This workflow creates an audit trail. Another reader should be able to locate the same documents, see the same inputs and understand why two figures were or were not compared.

Common interpretation traps

Trap: “The difference equals the expense ratio.” Expenses may contribute, but the realised gap can reflect several operational items. Compare matched periods and avoid forcing an accounting identity that the documents do not support.

Trap: “Lower tracking error means higher returns.” Dispersion and return level are different properties. A series can be consistently below its benchmark and still have low dispersion.

Trap: comparing numbers with different windows. A one-year tracking difference and a tracking-error statistic based on another window answer different questions.

Trap: ranking from one snapshot. A single month can be affected by flows, rebalancing or timing. One snapshot does not establish persistence.

Trap: treating missing data as zero. Blank, unavailable and zero are distinct states. Preserve the source’s status.

What this analysis cannot tell you

Even perfectly aligned historical data cannot determine future tracking, liquidity at the time you trade, tax consequences for a particular person, or whether a scheme fits a household’s goals and risk capacity. It also cannot establish why a gap occurred unless the relevant documents provide enough evidence.

The purpose is narrower and useful: to stop unlike numbers from being compared and to make every interpretation traceable to an official document.

FAQs

Is tracking difference always negative?

No. Under scheme return minus benchmark return, it can be negative, zero or positive. Always state the sign convention because some sources may display the gap differently.

Is tracking error the same as standard deviation of scheme returns?

No. It concerns the dispersion of return differences between the scheme and benchmark under a stated method, not the dispersion of scheme returns by themselves.

Can I compare two published tracking-error numbers directly?

Only after checking benchmark, period, frequency, annualisation and calculation method. Different methods can make a direct comparison misleading.

Does expense ratio fully predict tracking difference?

No. It may contribute, but cash, flows, implementation, rebalancing, transaction effects and other items can also matter.

Should ETF market price be used in NAV tracking difference?

Not unless the analysis explicitly studies investor trading experience. Market price and NAV are different data series and answer different questions.

Where should I verify a published number?

Use the AMC’s current official factsheet and disclosures, the SID/KIM, relevant portfolio and expense files, AMFI’s official data access points, and SEBI’s current legal source trail.

What if the methodology is missing?

Do not infer it. Record the number as non-comparable or method-limited until an official methodology can be located.

Suggested GFS reading

> Mutual fund investments are subject to market risks. Read all scheme-related documents carefully.

> This content is educational and is not investment advice or a recommendation. Verify independently before acting.

> Past performance is not indicative of future returns.

Gayatri Financial Synergy is an AMFI-registered Mutual Fund Distributor (ARN-169480), held by Roohani Bangia, not a SEBI-registered Investment Adviser. GFS distributes Regular Plans and may earn commission on them; analytics tools use Direct-Growth facts and do not accept transactions. Content here is for information only and is not investment advice.

Mutual fund investments are subject to market risks. Read all scheme-related documents carefully.

Team GFS Research Desk
Editorial review and publication by Gayatri Financial Synergy
Book a free consultation

Ready to put your money to work?

Book a free consultation with our AMFI-registered team in Faridabad / Delhi NCR.