Additional Validation Measures for Fund Request - Effective 11/8/19

As of Friday, November 8^th, additional validation measures will be rolled out to the New FIGI Request form for All Funds submissions in an effort to inform users of logic violations prior to submission.

All fields will remain the same. The following additional checks will run upon ‘Publish’ for Single and Bulk Submissions and prevent submission if violated:

Requested Ticker

For Open End Share Class and Hedge Share Class Submissions, the Requested Ticker field will be limited to 7 characters to conform to ticker generation conventions. For funds domiciled in Mexico, 8 characters are permitted as well.

The Requested Ticker must not already exist on Bloomberg.

Security Identifier

Any SEDOL, ISIN, CUSIP, or Valoren Number must not already exist on Bloomberg.

An ISIN must be submitted for all funds domiciled in Luxembourg, Ireland, United Kingdom, or France.

Attachments

A .pdf, .doc, or .docx file must be included in all submissions.

Pricing data must be submitted for all previously launched funds. The thresholds that are enforced are the following:

• Launch Date or First NAV Date more than one week prior to submission date for funds with ‘Daily’ Valuation Frequency.
• Launch Date or First NAV Date more than two weeks prior to submission date for funds with ‘Weekly’ Valuation Frequency.

In either of these cases, a .csv, .xlsx, or .xls file must be attached containing pricing data.

--

The structure of the form has not changed and no fields were added or removed.

Please reach to the OpenFIGI Team with any questions or concerns at gfunds@bloomberg.net.