| • |
Connects Participant into SDRs/TRs and updates SDRs over the lifecycle of the trade |
| • |
Send trades: New, Amend, Cancel |
| • |
Receive Trades/USIs from other reporting parties |
| • |
TR Connect maintains static data on you and your clients |
| • |
Data used for enriching messages before sending to SDR, counterparties, etc. |
| • |
TR Connect to provide USI/UPI/LEI Enrichment, data normalization and routing/rules |
| • |
Repository Submission |
| • |
TR Connect transforms all messages to FPML 5.3 compliant submissions |
| • |
Status can be viewed in TR Connect, or returned via messages back into participants’ systems |
| • |
Errors can raise alerts, exception notifications, etc. |
| • |
End of Day Reconciliation Report |
| • |
Match participants internal systems versus TR Connect |
| • |
To the extent participant is obligated to report to multiple repositories, TR Connect will provide the routing/rules to allow participant to submit trades once, and feed any/all relevant repositories |
| Dodd-Frank requires positive affirmation or confirmation within 24 hours and confirmation status must be appended to the SDR records once confirmed or not confirmed |
| • |
TR Connect will provide clients a copy of the block trade by message API, email or portal |
| • |
Client can affirm the trades in a blotter or click to accept pop-up UI |
| • |
Confirm trades by sending in their own trade details to a confirmation utility (use their treasury provider, RTNS, FXConnect, etc.) |
| • |
Bank |
| • |
Dashboard to oversee process |
| • |
Exceptions-based model |
| |
Stale and Suspect matches to help resolve trade discrepancies, reporting issues |
| |
|
