The links below provide access to the Reporting Services Airtable interface, a comprehensive resource designed to assist clients with their data submission process into KOR. This interface outlines the applicable fields, formats, and validations required for each jurisdiction, enabling clients to understand precisely what fields need to be submitted from their systems into KOR.
For reference:
- Hub Fields: These are the fields that clients can submit directly into KOR.
- Reg Fields: These represent the fields that appear on the KOR-generated regulatory message after the necessary configuration transformations have been applied.
This guide ensures clarity and alignment, helping clients efficiently meet jurisdictional reporting requirements through KOR.
KDM Specific Views
These views outline the fields required to generate CFTC regulatory messages and assess submission eligibility
- CFTC KDM Fields - Hub Transaction + Public + Droit Submittable
- Includes all fields which clients submit to KOR and used to generate CFTC Transaction and Public Regulatory Message and assess eligibility for submission.
- Includes all fields which clients submit to KOR and used to generate CFTC Transaction and Public Regulatory Message and assess eligibility for submission.
- CFTC KDM Fields - Reg KDM Transaction Submittable
- Includes all Regulatory message fields that appear on KOR generated Regulatory message and link to corresponding HUB transaction fields. It also provides logic used to determine Regulatory field ie. derived, direct mapping.
- CFTC KDM Fields - Hub KDM Valuation
- CFTC KDM Fields - Reg KDM Valuation
- Includes all Regulatory message fields that appear on KOR generated Regulatory message and link to corresponding HUB transaction fields. It also provides logic used to determine Regulatory field ie. derived, direct mapping.
- CFTC KDM Fields - Hub KDM Collateral Submittable
- CFTC KDM Fields - Reg KDM Collateral
- Includes all Regulatory message fields that appear on KOR generated Regulatory message and link to corresponding HUB transaction fields. It also provides logic used to determine Regulatory field ie. derived, direct mapping.