KOR utilizes Airtable to organize and publish information arounds KOR's technical specifications and other services like reports.
The below links help with different views of SEC data in KOR's SBSDR:
- Public
SEC Regulator Reports:
The SBSDR must provide a daily file that contains all “open swaps”, in the SBSDR as of the end of the day. There should be a separate file for each day and each supported asset class. The open swaps files are expected to include all “live”[1] UTIs for the given day. The open swaps file must also include all valuation related fields and contain the most recent valuation data for the given transaction for the given day.
[1] The swap has not reached maturity or expiration, and that have not been fully exercised, closed out, or terminated, as described in parts 49.2(a) and 49.9(a).
Each SBSDR must provide a daily file that contains the trade activity (required swap creation data and required swap continuation life-cycle event data) received from their participants for that Report date. Each file should include data received by the SDR from 12:00:00 AM (in the SDR’s time zone) up to the last instant before midnight (in the SDR’s time zone) for the Report date based on the “SDR receipt timestamp”.
The SBSDR must provide a file that contains all transactions disseminated to the public in real-time for a given Report date. This file should include all data disseminated to the public in the time frame between 12:00:00 AM (in the SDR’s time zone) up to the last instant before midnight (in the SDR’s time zone) for the Report date. Each record in this file should include all fields disseminated to the public. If certain values for these fields are disseminated with adjusted or modified values in accordance with part 43(e), the adjusted or modified value should be included in this file for those fields. For example, each of the notional or principal amount fields should contain only the disseminated value. Additionally, this file should include some regulatory fields the SDRs receive from their participants for public reporting (these fields are marked ‘N’ in the disseminated column).
It is expected the SDRs will disseminate all messages requiring dissemination, even if there is an error received before the time delay expires for a given swap transaction. For example, if a new transaction received has a public dissemination time delay, and the subsequent transaction received is a cancelation by error (message with [Action type] = ‘EROR’) before the time delay expires, both new and error messages should be disseminated after the time delay expires.