{
    "ucits": true,
    "type": "ETF",
    "leverage": false,
    "derivatives": true,
    "swaps": false,
    "inverse": false,
    "replication_method": "physical",
    "complex_factors": "FX forwards for currency hedging, securities lending",
    "classification": "non-complex",
    "supporting_data": "The iShares S&P 500 GBP Hedged UCITS ETF is a UCITS-compliant, physically replicated ETF that tracks a transparent, well-documented equity index (S&P 500). Under MiFID II, UCITS ETFs are generally presumed non-complex, provided they do not employ complex portfolio management techniques or structured features that make the product difficult for retail investors to understand[1]. This ETF uses FX forward contracts solely for currency hedging to reduce the effect of exchange rate fluctuations between the index constituents and the fundu2019s base currency (GBP). Such use of derivatives for efficient portfolio management (EPM)u2014specifically, to hedge currency risku2014does not, by itself, trigger a complex classification under MiFID II, as the derivatives are not central to the investment objective but are ancillary to risk management[1]. The ETF may also engage in securities lending, a common practice for UCITS funds to generate additional income, which is well-regulated and does not, in itself, make the product complex[1]. There is no evidence of synthetic replication, embedded derivatives, contingent convertible bonds, or other complex features that would override the UCITS presumption of non-complexity. The risks disclosed (market risk, counterparty risk from derivatives and securities lending, residual currency risk) are standard for equity ETFs and are clearly explained in the Key Investor Information Document (KIID). The structure, objective, and risks of the ETF are transparent and can be readily understood by a retail investor with basic knowledge, supporting a non-complex classification under MiFID II[1]. If the ETF used derivatives integrally (e.g., for synthetic replication or to achieve leveraged/inverse returns), or if the index itself were complex or opaque, the classification might differ, but this is not the case here."
}