{
    "type": "ETF",
    "ucits": true,
    "fund_name": "AMUNDI MSCI EUROPE MINIMUM VOLATILITY FACTOR UCITS ETF - EUR",
    "investment_objective": "Track the performance of MSCI Europe Minimum Volatility Index with minimized tracking error",
    "primary_asset_class": "Equity",
    "geographic_focus": "Europe",
    "replication_method": "synthetic",
    "swaps": true,
    "derivatives": true,
    "leverage": false,
    "inverse": false,
    "complex_factors": [
        "Synthetic replication via total return swaps",
        "Counterparty risk exposure",
        "Use of derivatives integral to strategy"
    ],
    "classification": "complex",
    "supporting_data": "The ETF uses an indirect replication methodology via total return swaps (financial derivative instruments) to achieve exposure to the MSCI Europe Minimum Volatility Index. The KIID explicitly states that derivatives are integral to the investment strategy, and the fund invests in total return swaps delivering the index performance against the assets held. This introduces counterparty risk, which is disclosed as a material risk. The replication is synthetic rather than physical, confirmed by the factsheet. There is no leverage or inverse exposure, and the risk rating is moderate (4 out of 7). The fund is UCITS compliant. The complexity arises primarily from the synthetic replication using swaps and the associated counterparty risk, which under MiFID II classifies the ETF as complex despite the absence of leverage or structured capital protection. The underlying index is a minimum volatility equity index, which is straightforward in terms of asset class but the synthetic replication method and derivative use drive complexity. No capital protection or contingent bonds are involved. Costs are straightforward with no performance fees, but swap usage implies derivative costs. The PRIIPs KID does not include a comprehension warning but confirms derivative use and counterparty risk. Overall, the synthetic replication and swap exposure are the key complexity drivers under MiFID II rules."
}