Access Official Technical PDF

Share Summary:LinkedInEmail

Benchmark tracking error is one of the measures investors can use to understand how closely a passive fund’s returns move in relation to its index. Mercer UCITS Common Contractual Fund’s first annual report, covering its establishment on 20 February 2019 through 30 June 2019, illustrates why that measure should be read together with tracking difference, the fund’s measurement period and its reporting currency.

The report covers several newly launched sub-funds, including strategies tracking global real estate investment trusts (REITs), listed infrastructure, low-volatility equities, global small-cap equities and fundamental indexation. Its figures offer a useful example of how performance reporting separates a fund’s return from its benchmark return—and why those comparisons need context.

Benchmark tracking error and tracking difference are not the same

Tracking difference measures how much a fund’s return differs from its benchmark over a stated period. It is the direct gap between the two reported returns. Tracking error, by contrast, describes the variability among the observations that make up the fund’s average tracking difference. One summarizes the outcome over a period; the other describes the consistency of the relationship over the period.

That distinction matters when reviewing passive strategies. A small tracking difference for a period does not, on its own, explain how consistently the fund followed its index. Similarly, a tracking error figure is not the same as the return gap. The measures answer related but separate questions, so comparing them helps make performance tables more informative.

What Mercer UCITS CCF reported

The report’s benchmark tracking appendix presents sub-fund and benchmark returns in each sub-fund’s base currency and, for sub-funds launched during the financial period, from the launch date. For example, the Passive Global Listed Infrastructure sub-fund returned 4.24% against a benchmark return of 4.41%, a tracking difference of -0.17%. Its realised tracking error was 0.28%, compared with anticipated tracking error of 0.50%.

The Passive Low Volatility Equity sub-fund returned 4.88% against a 4.91% benchmark return, producing a -0.03% tracking difference. Its realised tracking error was 0.24%, also below the anticipated 0.50%. The Passive Fundamental Indexation Global Equity sub-fund reported a 0.16% return against 0.15% for its benchmark, a positive tracking difference of 0.01%, and realised tracking error of 0.03%.

Not every result was as close. The Global Small Cap Equity sub-fund returned 3.36% against 3.40% for its benchmark, for a -0.04% tracking difference. Its realised tracking error was 0.84%, above its anticipated 0.50%. The report attributed the tracking outcome to the sampling technique used and transaction costs. For the Global REITs sub-fund, the reported return was 1.47% versus 1.97% for the benchmark, a -0.50% difference; the appendix listed realised tracking error of 0.50%.

Why period and currency need to be clear

The sub-funds began operating at different times, so their results do not all cover the same dates. The report notes that performance tables in the manager’s overview may use the first month-end following inception, while the tracking appendix uses the launch date for sub-funds launched during the year. These are different measurement conventions, and a return cannot be interpreted properly without knowing which one applies.

Currency is another essential part of the comparison. The report presents performance in euros, pounds sterling and US dollars in its overview, while the benchmark tracking appendix reports results in the sub-fund’s base currency. Returns shown in different currencies are not directly interchangeable: the reporting basis must be identified before drawing conclusions across tables or share classes.

The report also flags a currency detail for the hedged fundamental indexation strategy: aggregate portfolio return was calculated using a GBP-hedged unit class, while the underlying manager was unhedged. That difference in measurement basis is important context when interpreting the figures, rather than a reason to treat the numbers as directly equivalent.

How to read passive-fund performance reports

A practical review of a tracking report should establish:

  • What is being compared: Identify the fund, its stated benchmark and the investment approach. The sub-funds in this report followed different indices and strategies.
  • When performance was measured: Check launch dates and the start and end dates used for each return.
  • Which currency is shown: Confirm whether results are reported in the fund’s base currency or another unit-class currency.
  • How large the return gap is: Read tracking difference as the period’s return comparison, not as a measure of variability.
  • How variable the gap was: Read tracking error alongside its anticipated level and any explanation provided for the result.

In the report, several sub-funds were described as performing within acceptable tracking of their benchmarks, and no sub-investment manager changes were reported during the period. Those statements sit alongside the detailed return and tracking figures; they do not replace them.

Conclusion: interpret the measures together

Benchmark tracking error is most useful when considered with tracking difference, the relevant index, the measurement window and the currency basis. Mercer UCITS CCF’s 2019 report demonstrates that passive-fund comparisons can show small return gaps alongside different levels of variability, and that implementation factors such as sampling and transaction costs may be relevant to the explanation. For decision-makers reviewing investment performance, the practical lesson is to read the definitions and reporting conventions before treating a headline return as a complete account of how closely a fund tracked its benchmark.

Access Official Technical PDF

About The Author