Overview
Field Definitions

- View Data Requests
- Acknowledge Data Requests
- Upload SDR Files

Overview

SEC Rule 22c-2 is designed to provide fund companies with trade information, at their request, to monitor for market timing by shareholders within omnibus accounts. A shareholder is defined as the beneficial owner of securities held in a nominee's name.

When a fund company requests transaction data, Fidelity, as the first tier intermediary, forwards the request for detailed trade data to Fidelity clients who trade mutual funds in omnibus accounts held in Fidelity's books and records. These clients receive an email notifying them of a new request and directing them to the Omnibus SEC Rule 22c-2 functionality. The client acknowledges the request and assembles the underlying transaction data according to the request parameters. After formatting the transaction record, the client uploads a file.

If, after reviewing the transaction data response, a fund company determines that market timing is occurring, it can request that the recordkeeper restrict the underlying shareholder from trading for a period of time. Fidelity contacts the client via email or phone if a fund company wants a shareholder account restricted by the recordkeeper. Restrictions must be executed no later than five business days after receiving the request from Fidelity. Late responses or failure of a client to respond can result in the fund requesting that Fidelity restrict the entire omnibus account.

Upon request, Fidelity must provide the following:

• Individual/taxpayer identification number (SSN/TIN).
• International taxpayer or government user identifier, if known.
• All shareholders of the account.
• The amount, date, name or other identifier of any investment professionals associated with the shareholders or account, if known.
• Transaction type of every purchase, redemption, transfer, or exchange of shares held through an account maintained by the intermediary during the period covered by the request.

View Data Requests

View up to 150 Standardized Data Reporting (SDR) requests per page. Requests are sorted by Status, and the requests within each Status are sorted in order by timestamp.

To view data requests

1. Select Service > Omnibus > Data Requests SEC Rule 22c-2.

   The Data Requests window displays. (Field Definitions)

2. Enter criteria to locate a request and select Search.

3. In the Action column for a listed data request, select its View Details link.

   The SDR Data Requests Details window displays. (Field Definitions)

4. Select Return to Data Requests to go back to the first page of the Data Requests window.

   Go to: Acknowledge SDR Requests

Acknowledge Data Requests

To confirm receipt of an SDR request, you must acknowledge it. A record of acknowledgment provides a response back to the fund company and indicates an approximate length of time within which the fund company can expect to receive the SDR response file.

You can acknowledge all requests on the window (up to 150) or one or more individual requests at a time. Note that you can only acknowledge all requests on the current window; this feature does not extend beyond the current window of requests.

To acknowledge a data request

1. On the Data Requests window, in the right-most column:

   Select the check box of one or more requests to acknowledge.
   or
   Select the column's top-most check box to acknowledge all listed requests.

2. Select Acknowledge.

   - A confirmation displays the requests.
   - The status of these requests is now ACKNOWLEDGED.

3. Select Return to Data Requests.

   Go to: Upload SDR Files

Upload SDR Files

Upload an SDR file with a TXT extension. The filename must be between 1-104 characters. The maximum file size is 3 MB. Fidelity clients must gather and format the response data based on the parameters in the request details.

Further guidelines:

• The detailed transaction records must be formatted in the NSCC/DTCC SDR format.
• Fidelity agreed to transmit promptly (no later than 10 days after the receipt of the request) to the fund the requested summary information in its books and records or its designee.
• If the requested information is not in its books and records, Fidelity agreed to provide or arrange to provide to the fund the requested information regarding shareholders who hold an account with its indirect intermediaries or, if directed by the fund, block further purchases of fund shares from such indirect intermediaries. From a fund company's perspective, Fidelity is the direct, or first tier intermediary and its clients are indirect, or second tier, intermediaries.

To upload an SDR file

1. Select Service > Omnibus > Upload SDR Files.

2. Select Browse to locate the completed SDR file.

3. Select Upload File.

   - A confirmation displays.

Field Definitions

- Data Requests
- SDR Data Requests Details

Top

Data Requests

Field	Definition
Request Date	The original data request date, in MM/DD/YYYY format.
Account #	The Fidelity brokerage account number.
Symbol	The mutual fund security's identifier on its exchange.
CUSIP	The identification number assigned to the mutual fund security by the Committee on Uniform Security Identification Procedures (CUSIP).
SDR Control #	The unique number that identifies the fund's request for data.
# of Records	The number of records contained in the SDR file.
Last Updated	The most recent status update, in MM/DD/YYYY format.
Class	The five classes associated with the data request sent by the fund company via an NSCC request message: One-Time The fund company has requested data to be submitted for this request only. Recurring The fund company has requested daily data until a STOP RECURRING request is sent by the fund company to the Fidelity client. Stop Recurring The fund company has requested cancellation of daily responses requested by a previously sent RECURRING request. No Longer Recurring The fund company sent a STOP RECURRING request to cancel a previous RECURRING request. SDR Rejected The NSCC issued a rejection when the response sent to Fidelity violates NSCC business or formatting rules. The reject codes are included in the request.
Status	The status of the data request, which varies according to Class: Class Statuses One-Time or Recurring New The SDR request was received from NSCC and an acknowledgement was sent back to them. Acknowledged The Fidelity client viewed the request for Rule 22c-2 data by selecting the request and selecting the Acknowledge button. Transmitted The SDR response file was transmitted to NSCC and the Fidelity Request/Response system received a valid echo response from NSCC. Uploaded The Fidelity client uploaded an SDR response file containing the SDR Control # for the given request. Stop Recurring New The SDR request was received from NSCC and an acknowledgement was sent back to them. Acknowledged The Fidelity client viewed the request for Rule 22c-2 data by selecting the request and selecting the Acknowledge button. No Longer Recurring Stopped The SDR request was received from NSCC with a Request Type = 06 ( STOP RECURRING ) and the original SDR Control # matches this request. Transmitted The SDR response file was transmitted to NSCC and the Fidelity Request/Response System (mainframe) received a valid echo response from NSCC. Uploaded The Fidelity client uploaded an SDR response file containing the SDR Control # for the given request. SDR Rejected New The SDR rejected file was received from NSCC. Acknowledged The Fidelity client viewed the rejected response by selecting the response and selecting the Acknowledged button.

Top

SDR Data Requests Details

Field	Definition
Last Updated	The most recent status update in MM/DD/YYYY format.
Status	New The SDR request was received from NSCC and an acknowledgement was sent back to them. Acknowledged The Fidelity client viewed the request for Rule 22c-2 data by selecting the request and selecting the Acknowledged button. File Uploaded The Fidelity client uploaded an SDR response file containing the SDR Control # for the given request. Transmitted The SDR response file was transmitted to NSCC and the Fidelity Request/Response System (mainframe) received a valid echo response from NSCC. Stopped The SDR request was received from NSCC with a Request Type = 06 (STOP RECURRING) and the original SDR Control # matches this request.
Recurring	Indicates whether the request is recurring: Yes Request is recurring. No Request is not recurring.
SDR Control #	The unique number that identifies the fund's current request for data.
Request Date	The original data request date in MM/DD/YYYY format.
SDR Request Type	Indicates the party responsible for replying to a data request: FUND ACCOUNT LEVEL PLAN LEVEL INVESTOR OMNIBUS ACCOUNT LEVEL FUND/SERV CONTROL NUMBER REQUEST REP LEVEL STOP RECURRING
Original SDR Control #	The unique number that identifies the fund's original request for data.
Firm #	The four-character alphanumeric number of the broker-dealer, trust, or recordkeeper, to which the fund is routed initially, based on one of the following three indicators: NSCC number OTC symbol BTRK identifier
Underlying Firm #	The four-character alphanumeric number of the broker-dealer, trust, or recordkeeper, to which the fund company wants the request routed (if first passed to a firm), based on one of the following three indicators: NSCC number OTC symbol BTRK identifier If the firm identified in the Firm # field is different than the Underlying Firm # field, the firm is an intermediary acting as a conduit to the fund for the underlying firm.
Firm Account #	The Fidelity brokerage account number.
Fund #	The four-digit industry standard number identifying the fund.
Underlying Firm Indicator	The indicator associated with the Underlying Firm # field. NSCC number OTC symbol BTRK identifier
Fund Account #	The account number that the fund company maintains for mutual fund trading. This number specifies how the intermediary can find the account and shareholder in question and determines the level of data that can be returned to the fund. Depending on the account setup, this number identifies the level of plan data, such as super omnibus level, plan or investor account level, or individual shareholder level.
Symbol	The mutual fund security's identifier on its exchange.
SSN/TIN	The Social Security number (SSN) or tax identification number (TIN) identifying the participant or shareholder (specifies additional search criteria for the SDR Request Type).
RR #	The code of the registered representative.
Security Issue ID	The CUSIP (specifies additional search criteria for the SDR Request Type).
Includes Category 2	Indicates whether the data request includes both Category 1 and Category 2 transactions: Yes Both Category 1 and Category 2 are included. No Only Category 1 is included. Category 1 Activities directed either by the shareholder, financial advisor, or investment fiduciary. This can include other transactions where investors have sufficient control to perform market timing activities. Category 2 Activities that occur via systematic or automated investment elections.
RR Branch	The Fidelity brokerage branch prefix.
Transactions From	The starting date range for the search in MM/DD/YYYY format.
Threshold Amount	The dollar amount (specifies additional search criteria for the SDR Request Type).
RR Firm	The first three characters of the Fidelity brokerage account number.
Transactions To	The ending date range for the search in MM/DD/YYYY format.
Transaction Type	Indicates whether the transaction is a buy or a sell (specifies additional search criteria for the SDR Request Type).
Fund/SERV/Ctrl #	The control number identifying the records requested from Fund/SERV®, which is a service provided through the Depository Trust and Clearing Corporation (DTCC).

883090.2.0