ETF Agents, also known as Index Receipt Agent, have actions to take and reports to monitor during each phase of the ETF process. Review the ETF timeline from T-1 through T+1 (Settlement Day), including responsibility for each role and the reports that you should monitor. Log in, if necessary, to view all the content available in the Learning Center.
| Sequence | Role | Responsibility on T-1 |
| 1 | Fund Manager /Issuer/Sponsor | Fund Manager or Issuer sends a Portfolio Composition File (PCF) to the ETF Agents, also known as an Index Receipt Agent. |
| 2 |
ETF Agent (Index Receipt Agent) |
On the evening of T-1, the ETF Agent, sometimes referred to as an ETF Agent, sends NSCC a portfolio composition file (PCF) for each ETF for the following trade day using one of these protocols:
The PCF displays the individual securities and the weightings that make up one ETF basket for the following trade day. For most ETFs, one basket equals 50,000 shares. The PCF also includes cash amounts in the fund for each basket unit, such as accrued and balancing amount. For example, 50,000 ETF shares =
The ETF Agent sends the portfolio composition file listing the securities in each ETF to the Authorized Participants. The PCF file also contains the estimated cash amount in each portfolio. Transactions eligible for cash creates and redeems show a cash creation amount on the portfolio composition file. |
| 3 | NSCC | Distributes the portfolio composition files on T-1 to members, nonmembers, and the listing exchanges. |
The T0 Same Day Settlement Create/Redeem cycle includes the submission of a Cash Collateral Amount (buffer) and EOD Collateral Cash Adjustment (true-up).
The following table shows the Trade Date timeline with all times reported in Eastern Time.
| Sequence | Role | Responsibility on Trade Date |
| 1 | Authorized Participant |
|
| 2 | Distributor |
|
| 3 |
ETF Agent (Index Receipt Agent) |
After receiving the order from the distributor, the ETF Agent sends NSCC ETF creation instructions on behalf of its Authorized Participant using one of the following protocols:
ETF Agents can also download print image reports through the ETF Dashboard through the MyDTCC portal. |
| 4 | NSCC |
Using the example of the 50,000 ETF shares:
|
The following table shows the T+1 timeline:
| Sequence | Role | Responsibility on T+1 |
| 1 | Authorized Participant | Delivers the underlying components to CNS. |
| 2 | NSCC | CNS delivers underlying components to the ETF Agent. |
| 3 |
ETF Agent (Index Receipt Agent) |
Delivers the ETF shares to CNS. |
| 4 | NSCC | CNS delivers the ETF to the Authorized Participants. Deliveries are made through DTC book entry with CNS. |
During T+1, NSCC distributes the following reports that you should monitor:
The following guidelines apply to the create/redeem input cycles for ETF Agents only:
The following table shows the Create/Redeem input cycles for ETF Agents only.
|
DATATRAK ID |
Description |
Intraday Cycle SDS T0 |
Primary |
Supplemental |
Closed |
|
Enhanced ETF Create and Redeem Instruction Data Input MRO file. |
12:30 AM – 1:30 PM (T) |
2:30 PM – 8:45 PM (T) |
9:00 PM – 11:29:59 PM (T) |
11:30 PM–12:29:59 AM (T+1) |
The following table shows the Create/Redeem output cycles for ETF Agents and Authorized Participants with all times reported in Eastern Time:
|
AutoRoute ID |
Description |
Intraday Cycle Activity |
Primary Cycle Activity |
Supplemental Cycle Activity |
|
02260291 |
Enhanced Create/Redeem Instruction Print Image Report (ETF Agents and Authorized Participants) |
12:30 PM on T |
9:00 PM on T (Cycle 1) |
11:30 PM on T+1 (Cycle 2) |
|
End-of-Day Instruction Create/Redeem Receipt/Reject Report (ETF Agents only) |
12:30 PM on T |
9:00 PM on T (Cycle 1) |
11:30 PM on T+1 (Cycle 2) |
|
| 02261254
|
Enhanced ETF Create and Redeem Instruction Output Data file (Agents and Authorized Participants) |
12:30 PM on T |
9:00 PM on T (Cycle 1) |
11:30 PM on T+1 (Cycle 2) |
|
Enhanced Intra-Day Create/Redeem Receipt/Reject Print Image Report (ETF Agents only) |
Immediately After Validation |
Immediately After Validation |
Immediately After Validation |
|
|
UTC Contract Data File (Agents and Authorized Participants - Results of Create/Redeem) |
Immediately After Validation |
Near Real-Time starting at 6:30 PM |
Near Real-Time |
Click to expand and view information about the ETF Regular Way and Shortened Settlement Instructions, including logic.
Important:
Create or Redeem instructions are accepted by NSCC for same day settlement (SDS) where the trade date equals the date of receipt of the instruction. NSCC accepts and processes orders for "As Of" and SDS in the Intraday cycle. Status is immediately reported on the Enhanced Intraday Receipt/Reject report (AutoRoute 02261954) and is also included on the End of Day Instruction Create/Redeem Receipt/Reject report (AutoRoute 02120098) Cycle 1 at the end of the Primary cycle on the date of receipt.
Note: All times are reported in Eastern Time.
|
Description |
Status |
Report |
Intraday Create/Redeem Cycle (12:30 AM – 1:30 PM) |
||
|
Instructions received are immediately subject to existing edits. |
PROVISIONALLY ACCEPTED (PRV) |
Immediately reported in the Enhanced Intraday Receipt/Reject report (AR 02261954) |
Primary Create/Redeem Cycle (2:00 PM – 8:45 PM) |
||
|
Pricing is available at approximately 6:30 PM. Any instructions where the trade date equals the date of receipt and pass the following reasonability check edits, are streamed in near real-time to Universal Trade Capture (UTC):
|
PROVISIONALLY ACCEPTED (PRV) |
|
|
Instructions received, where pricing is available upon receipt, are subject to all reasonability check edits, including:
|
ACCEPTED (ACP) |
|
|
Instructions fail the Negative Settlement Value reasonability check edit. |
REJECTED (REJ) and cannot be reinstated. |
|
|
Instructions fail the Threshold Value reasonability check edit, but successfully pass all other edits. |
PENDED (PND) Note: ETF Agents can reconcile any PENDED (PND) status instruction with NSCC Support and request reinstatement of the instruction. This request must be received prior to the end of the Supplemental cycle. |
|
Supplemental Create/Redeem Cycle (9:00 PM – 11:29:59 PM) |
||
|
Instructions pass the reasonability check edits, including:
|
ACCEPTED (ACP) |
|
|
Instructions fail the Negative Settlement Value reasonability check edit |
REJECTED (REJ) and cannot be reinstated |
|
|
Any newly received instructions that fail the Threshold Value reasonability check edit, but successfully pass all other edits. |
PENDED (PND) Note: ETF Agents can reconcile any PENDED (PND) status instruction with NSCC Support and request reinstatement of the instruction. This request must be received before the end of the Supplemental cycle. |
Enhanced Intraday Receipt/Reject Report (AR 02261954) |
|
PENDED (PND) status instructions that were not reinstated by the end of the Supplemental cycle. |
REJECTED (REJ) and cannot be reinstated |
|
Closed to All Submissions (11:30 PM – 12:29:59 AM) |
||
|
During this cycle:
|
REJECTED (REJ) |
No UTC contract output is produced for any submitted instructions. |
Click to expand and view the business rules and logic explaining the As/Of Create/Redeem instructions.
The business logic for handling as/of create/redeem instructions is different from the logic applied to other create/redeem instruction. Here are some guidelines for the instructions:
Note: To receive the contract output on an intraday basis requires a subscription to receive market code 920 UTC contracts in the Financial Information eXchange (FIX) message output format. The FIX message output is available through either FIX Engine or MQ. To enable this subscription, contact your DTCC relationship manager.
|
Description |
Status |
Report |
Intraday Create/Redeem Cycle (12:30 AM – 1:30 PM) |
||
|
Instructions pass the reasonability check edits, including:
|
ACCEPTED (ACP) Note: If instructions are marked as ACP and received:
|
|
|
Instructions fail the Negative Settlement Value reasonability check edit. |
REJECTED (REJ) and cannot be reinstated |
|
|
Instructions fail the Threshold Value reasonability check edit, but successfully pass all other edits. |
PENDED (PND) Note: ETF agents can reconcile any PENDED (PND) status instruction with NSCC Support and request reinstatement of the instruction. This request must be received before the end of the Supplemental cycle. |
|
Primary Create/Redeem Cycle (2:00 PM – 8:45 PM) |
||
|
Instructions pass the reasonability check edits, including:
|
ACCEPTED (ACP) |
|
|
Instructions fail the Negative Settlement Value reasonability check edit. |
REJECTED (REJ) Cannot be reinstated. |
|
|
Instructions fail the Threshold Value reasonability check edit, but successfully pass all other edits. |
PENDED (PND) Note: ETF Agents can reconcile any PENDED (PND) status instruction with NSCC Support and request reinstatement of the instruction. Ensure this request is received before the end of the Supplemental cycle. |
Note: The final status of an instruction is reported on the End of Day Instruction Create/Redeem Receipt/Reject report (AR 02120098) report. |
Supplemental Create/Redeem Cycle (9:00 PM – 11:29:59 PM) |
||
|
Instructions pass the reasonability check edits, including:
|
ACCEPTED (ACP) |
|
|
Instructions fail the Negative Settlement Value reasonability check edit. |
REJECTED (REJ) Cannot be reinstated. |
|
Closed to All Submissions Cycle (11:30 PM – 12:29:59 AM) |
||
|
During this cycle:
|
REJECTED (REJ) |
No UTC contract output is produced for any submitted instructions. |
The following table shows the PCF submission and PCF output on T-1 with all times reported in Eastern Time:
|
Role |
Responsibility on T-1 |
Report/Output |
|
Fund Manager/ Issuer/Sponsor |
Fund manager or issuer sends the Portfolio Composition File (PCF) to the ETF Agent. |
- |
|
Index Receipt Agent (ETF Agent) |
Cutoff times for ETF Agent to submit the PCF is 8:00 PM ET.
|
Enhanced Consolidated Portfolio Composition Input MRO (DATATRAK 11301) |
|
NSCC |
NSCC edits each PCF submission in near real-time and sends the Enhanced Consolidated Portfolio Composition Receipt Reject report to the ETF Agent in the existing print format, machine readable output (MRO), or both formats. |
Enhanced Consolidated Portfolio Receipt Reject MRO (AR 02261255) |
|
NSCC |
T-1 Consolidated Output cutoff times:
|
Enhanced Consolidated Portfolio Composition Output MRO (AR 02261256). |
|
ETF Agent |
Supplemental process is open. 12:30 AM to 12:00 PM on T.
Note: If an ETF Agent submits an Enhanced Consolidated Portfolio Composition Input MRO file during the supplemental T process, the DATATRAK header sequence number should be set to 1. Subsequently, if the ETF Agent submits other supplemental files or primary / (T-1) files on the evening of the same processing day, increment the DATATRAK header sequence number accordingly. |
Enhanced Consolidated Portfolio Composition Input MRO (DATATRAK 11301). |
|
NSCC |
|
Enhanced consolidated portfolio composition receipt reject report. (AR 02260421) |
The following table shows the PCF submission and PCF output on T with all times reported in Eastern Time.
|
Role |
Responsibility on T |
Report/Output |
|
NSCC |
12:00 PM
1:00 PM
|
Enhanced consolidated Portfolio Composition Output MRO (AR 02261256) |
Log in, if necessary, to learn about the ETF processing.
For Options Clearing Connect initiative resources, see ETF Release:
{docmanlist orderByOrder 1095}
{docmanlist orderByOrder 1655}
{docmanlist orderByOrder get_subfolders 1755}
Access the NSCC file formats for ETF, including record layouts and canned test data files. Log in to view all of the content available in the Learning Center.
{docmanlist orderByOrder 1100}
View these canned sample output data in a text editor with Word Wrap turned off.
{docmanlist orderByOrder 1101}
To view the Historical Portfolio Composition output record layout and canned sample for AutoRoute 02262222, see ETF Portfolio Data Service.
The Obligation Warehouse Web system is a secure, efficient obligation entry and management system that incorporates robust search capabilities, statistical reporting, and exception processing. Eligible member can use the service to access real-time information along with input and response capabilities. The commands and data are validated in real-time, input errors are reported immediately, and invalid data elements are returned directly on the entry page. Every obligation submitted, as well as the subsequent related events, are sent to the Contra to provide both parties with the most updated status. All output files are parsed into sections and defined as reports readily available for up to two years in the Report Center.
Using Obligation Warehouse Web, participants can enter ex-clearing broker-to-broker obligations, obtain real-time matching, clean up exceptions, store open obligations, check for CNS eligibility daily, and run RECAPS frequently. The Obligation Warehouse Web feature allows you to:
Log in, if necessary, to view information about how to access and use the Obligation Warehouse Web system, including avoiding fee guidelines available in the Avoiding Disincentive Fees resource. You can also access the Obligation Warehouse Help to learn more about process rules, input and output features, RECAPS, REORGs, and using the Obligation Warehouse Web service.
{docmanlist orderByOrder 1107}
The Obligation Warehouse service is a common repository for trade capture and clearing transactions from the marketplaces, including the listed exchanges and alternative trading platforms collectively. The service consolidates those transactions to reduce the burden of trade-for-trade settlement for each transaction.
Log in, if necessary, to view the input and output message layouts, MRO files, sample reports, and SWIFT messaging specifications.
{docmanlist orderByOrder 1768}
Input and output formats for the Obligation Warehouse service:
{docmanlist orderByOrder 1110}
Machine readable output (MRO) files for the Obligation Warehouse service:
{docmanlist orderByOrder 1111}
{docmanlist orderByOrder 1112}
Obligation Warehouse SWIFT MT509 messages:
{docmanlist orderByOrder 1114}
Obligation Warehouse SWIFT MT515 messages:
{docmanlist orderByOrder 1115}
Obligation Warehouse SWIFT MT518 messages:
{docmanlist orderByOrder 1116}
Obligation Warehouse SWIFT MT598 messages:
{docmanlist orderByOrder 1117}
Obligation Warehouse SWIFT MT599 messages:
{docmanlist orderByOrder 1118}
Related Content
Page 5 of 7