12.07.2015 Views

ALFI UCITS IV implementation project – KID Q&A Document

ALFI UCITS IV implementation project – KID Q&A Document

ALFI UCITS IV implementation project – KID Q&A Document

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Q. Should average net assets be calculated on the basis of the published NAV or (in the case of swing pricing)the NAV before it was swung?A. Use the published NAV.Page 6, Para 15Q. For a <strong>UCITS</strong> that invests a substantial proportion of its assets in other <strong>UCITS</strong> or CIUs, must the regularcalculation of the ongoing charges figure take account of the evolution of the asset weights and the ongoingcharges of the underlying funds or may a simplified approach be used, in which the new asset weights arecounted but the underlying funds' ongoing charges are not researched anew unless the 5% test wouldindicate that the result would be published in a new <strong>KID</strong>?A. CESR 09/949, Box 7, Para 1 says that the "management company shall establish procedures to ensure that thecharges figures disclosed in the <strong>KID</strong> are kept under regular review, so that they remain fair, clear and not misleadingat all times". CESR 09/949, Box 7, Para 2(b) and 2(c) establish the principle that, if the ongoing charge changes by 5%or more, a new <strong>KID</strong> should be produced, showing the new ongoing charge. However, CESR 09/949, Box 8 Para 3says that that if the difference is less than 5%, the new ongoing charge figure "shall be published when the <strong>KID</strong> is nextrevised". Therefore, the issue is not whether it is acceptable to use latest asset weights and older ongoing chargesfigures for the underlying funds when recalculating a <strong>UCITS</strong>' ongoing charge solely for the purpose of testing if thethreshold has been crossed, but whether it is in any event acceptable to calculate and publish an ongoing chargefigure using older ongoing charges figures for the underlying funds.Partial view of the <strong>KID</strong> production processshowing ongoing charges figure ("OGC")calculations with respect to timeNew SRRI calculated(trigger for new <strong>KID</strong>)Time1% 7% 3% 1% 1% 2%Threshold crossed.Publish new <strong>KID</strong> withnew OGCThreshold not crossed but new <strong>KID</strong> mustanyway be published because the SRRI haschanged. Publish new <strong>KID</strong> with the lastcalculated OGCPercentage difference between published OGCand recalculated OGC in each cycle of theproduction process.OGC recalculation frequency may be decided bythe practitioner in accordance with CESR/09-949,Box 7, Para 1, to ensure that OGC is "fair, clearand not misleading at all times".Threshold not crossed but the recalculatedOGC is stored, ready for use when the <strong>KID</strong> isnext published. The stored figure may besuperseded by a new OGC figure in the nextcycle of the process, and so might not bepublishedWe think that the principal purpose of paragraph 15(a) of CESR/10-674 is to ensure that the latest asset weights areused when calculating the ongoing charges figure. We do not think that it means that ongoing charges figure of theunderlying CIU should be calculated as at the same date. For example, we do not think that it creates an obligation toapply paragraph 8(b), where relevant, with the same frequency. However, we do think that the latest available ongoingcharges for the underlying <strong>UCITS</strong> or CIU should be used in the case of all underlying <strong>UCITS</strong> or CIUs – cf. paragraph8(a), "its most recently available ongoing charges figure shall be used."Q. Does this mean that the latest available ongoing charge figure of an underlying <strong>UCITS</strong> or CIU should beused each time a synthetic ongoing charge is calculated?A. Yes. Note the word available.<strong>ALFI</strong> <strong>KID</strong> Q&A, Issue 1314, 11 April25 September 2012 Page 51

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!