Your latest round of updates and improvements to KOR Reporting Services last week!

Released Features

• Large SFTP File Sizes: Now accepting up to 5GB files via secure FTP. Learn more
• Multi-Select for Eligibility Reprocessing: Reprocessing from the Eligibility Screen now supports multi-select.
• Dashboards: Disable auto-refresh if a custom range is selected on the processing or reconciliation dashboards.
• MI Reports: Added Jurisdiction and User Identifier filtering parameter options to the Processing, Timeliness and Accuracy reports definitions.

We're committed to continuously improving your experience.

Your feedback is invaluable to us. Please don't hesitate to share your thoughts and suggestions with our support team at support@korfinancial.com.

We're pleased to announce the latest round of updates and improvements to KOR Reporting Services last week (4th-11th Nov)!

Released Features:

• Parked Messages Enhancements: Quickly access related messages to a parked message and view full details all from Parked. Learn more
• Ignoring Eligibility Check Issues: Ignore global eligibility check issues when addressed/resolved . Learn more
• Trade State Report Reconciliation Date Setting: Select Last Business Day or Last Calendar Day for the TSR report definition or select a Custom Date for ad-hoc reconciliations.
• Pre-Validate without UTI: Process a regulatory message through KOR pre-validation without a UTI to obtain quality feedback while the final UTI is pending.

We're committed to continuously improving your experience. Your feedback is invaluable to us. Please don't hesitate to share your thoughts and suggestions with our support team at support@korfinancial.com.

We're pleased to announce the latest round of updates and improvements to KOR Reporting Services! Last week's (Oct 21st-27th) releases focused on new REMIT regime support and Management Information reports.

Regulatory Support:

• REMIT Launched: Reporting of wholesale natural gas and power markets under ACER REMIT is now supported across all Reporting Services components with data submitted to ICE Trade Vault RRM (Registered Reporting Mechanism).

Features:

• Accuracy Summary: New report to access summary accuracy statistics by data range. Available for all supported regimes. Learn more
• Timeliness Summary: New report to timeliness summary accuracy statistics by data range. Available for all supported regimes. Learn more
• Reg Messages By Validation Status: Regulatory Messages by Date Range now supports a Validation Status parameter. Filter your results by Validated or Rejected status.

We're committed to continuously improving your experience. Your feedback is invaluable to us. Please don't hesitate to share your thoughts and suggestions with our support team at support@korfinancial.com.

We're pleased to announce the latest round of updates and improvements to KOR Reporting Serices! Last week's (Oct 14-20) releases focused on new ASIC and MAS support and user experience.

Regulatory Support:

• ASIC and MAS Rewrite Go Live: On Oct 20th we launched production support across all Reporting Services components for the ASIC and MAS reporting re-write.

Features:

• Currency Conversion Function: Now convert global currencies within KOR using our new built-in conversion tool and FX cross-currency references data. Learn more
• Position Management: Creation of reporting events from position management now supported. Create termination, new trade and other events/actions on the KOR platform based on configurable rules.
• Expanded Data in Reports: Now access all applicable data fields in each report type.

Usability Improvements:

• Show Row Number: Quickly identify and reference specific rows on any message screen with the addition of row numbers. Also handy for quick counts. Learn more
• Related Activity Filter: Save time and effort by using the Related Activity Filter to instantly view all the related regulatory messages associated with a selected message version. Learn more
• Regulatory Specific Column Views: Access pre-configured columns tailored to specific data relevent to the jurisdictions within the Regulatory Messages screen when filtered for a single jurisdiction. Learn more

We're committed to continuously improving your experience. Your feedback is invaluable to us. Please don't hesitate to share your thoughts and suggestions with our support team at support@korfinancial.com.

What

We introduced 2 new views in the reports section of the Reporting application:

• Group by Status
• Group by Type

In the “Group by Type” view all report definitions are grouped within their own report type.

In the “Group by Status” view all report definitions are grouped based on the status of the last job of each report definition. This leads to potentially 5 groups:

1. No Job run yet
2. Job in progress
3. Last Job successful
4. Last Job failed
5. Last Job timed out

There are view options available like:

• Table column customization
• Display options to update the sorting to “by last job”
• Filtering
• etc ..

For more information please check our updated knowledge base article.

A new field, [Additional Price Unit Of Measure] has been added, if you trade virtual currencies where the price unit of measure is required on the submission and it is not an ISO unit, then this field will impact your submissions.

Validation:
WHEN [priceUnitOfMeasure] = 'LOTS'
AND [underlyingAssetOrUnderlyingContractType] = ‘VIRT’
THEN [additionalPriceUnitOfMeasure] is mandatory
ELSE [additionalPriceUnitOfMeasure] is NR

WHEN [priceUnitOfMeasure] != populated
THEN [additionalPriceUnitOfMeasure] is invalid

Allowed Values List

Related Info
How do I submit virtual currency products?

Go Live Date
Integration Environment: 2022-09-05
Production Environment : TBD

What
KOR has more reports ready!

This link has an overview of the reports. (we recommend you set up a free airtable acount)

This link describes the UI functionality.

Please try them out and provide your feedback. We will continually be adding more reports that are listed over the coming weeks.

What

1. [Reference Rate] and [Other Reference Rate] values added (link)
2. [Additional Quantity Unit of Measure Leg 1] and [Additional Quantity Unit of Measure Leg 2] values added. (link)
3. [Underlying Asset Subtype Or Underlying Contract Subtype] values added. (link)
4. Added the below fields. All have the same allowed value list (link). And the validations are: The “additional” currency field is optional when “standard” currency field is populated and asset class is “CO”, otherwise NR.
   • Additional Notional Currency Leg 1
   • Additional Notional Currency Leg 2
   • Additional Call Currency Leg 1
   • Additional Call Currency Leg 2
   • Additional Put Currency Leg 1
   • Additional Put Currency Leg 2
   • Additional Package Transaction Price Currency
   • Additional Package Transaction Spread Currency
   • Additional Other Payment Currency
   • Additional Price Currency
   • Additional Spread Currency Leg 1
   • Additional Spread Currency Leg 2
   • Additional Strike Price Currency/Currency Pair
   • Additional Option Premium Currency
   • Additional Settlement Currency Leg 1
   • Additional Settlement Currency Leg 2
   • Additional Valuation Currency

Why
Added new fields and allowed values to support virtual currency products

Related Info
How do I submit virtual currency products?

What
KOR API UUID searches have been updated to be case insenitive.

What
KOR has updated the allowed values for the field Exempt Public Related Message (list)

Why
KOR found misreporting on the term NOT_APPLICABLE” and so we updated it to “IS_PUBLICLY_REPORTABLE” to avoid confusion for the definition of the field.

What does this mean for me?
To better understand this field and how it is used, KOR recommends you review the knowldge base article: How does KOR identify missing public messages?

What:
Modify Boolean fields in the API to follow industry standard Boolean format requirements.

Why
The CFTC Tech Spec specifies the values as True and False, but KOR has made the decision to follow technical standards based on client feedback.

What does this mean for me?
Fields that you submitted as strings with a value of "True" or "False" should be updated to a boolean type with a value of "true" or "false". This will also impact how data and reports are returned.

Example:
Field value in the API submission will change…..

• From : "nonStandardizedTermIndicator" : “False”
• To : "nonStandardizedTermIndicator" : false

Impacted fields:

• mandatoryClearingIndicator
• counterparty1FinancialEntityIndicator
• counterparty2FinancialEntityIndicator
• counterparty1FederalEntityIndicator
• counterparty2FederalEntityIndicator
• customBasketIndicator
• amendmentIndicator
• packageIndicator
• postPricedSwap
• nonStandardizedTermIndicator
• blockTradeElectionIndicator
• largeNotionalOffFacilitySwapElectionIndicator
• registeredPlatformIndicator
• anonymousExecutionIndicator
• primeBrokerageTransactionIndicator