Service Navigation

Excessive System Usage Fee

Excessive System Usage Fee

Eurex Exchange has introduced the Excessive System Usage Fee on 1 December 2013. In order to encourage a responsible attitude towards the use of the T7 system resources, Eurex Exchange defines daily limits for the number of transactions sent by a Participant. If a Participant exceeds the defined limits then fees for excessive system usage may apply.

The transaction limit is calculated per Participant, per product, per trading day and per limit type. There are two types of transaction limits: a transaction limit for the order type “standard orders” and a transaction limit for “all transactions”. Every day, for each Participant, the actual transactions are counted per product. If this transaction count exceeds the transaction limit, then such instance is considered to be a violation of the limit.

There are two different types of violations:

  • Accidental violation: A violation of the limit is considered to be “accidental”, if a limit is exceeded less than four times for a product in a calendar month. An accidental violation is not subject to the ESU Fee.
  • Systematic violation: A violation of the limit is considered to be “systematic”, if a limit is exceeded more than three times for a product in a calendar month. All systematic violations are subject to the ESU Fee. The ESU Fee is applied to all violations in that particular month.

Violations are counted per product across both limit types.

 

Fee calculation

The ESU Fee is calculated using the following equation:

ESU Fee = [ (number of transactions) - (transaction limit) ] * fee

A transaction is defined as a system message that reaches the matching engine and yields a response. Such a transaction can be identified by inspecting the system response. If the response contains a time stamp from the matching engine the message is added to the daily transaction count of the Participant for the respective product.

The transaction limit is comprised of two components:

  1. A volume component, which is calculated by multiplying the volume in the order book by a predefined volume factor, and
  2. a floor, which is set for each Participant regardless of any traded volume in the order book. A Market Maker can receive a higher floor, depending on its Market-Making performance.

Please find below a concept paper describing the calculation (including an example) in detail.

Limit parameter

The table below shows the parameters used to calculate the ESU Fee.


Please note: The limit is defined based on the product type of the product.

Fee parameter

The following table shows the fee parameters that will be used to calculate the ESU Fee. It is calculated separately for each systematic violation based on a sliding scale applied to the number of transactions that exceed the limit. The ranges of the sliding scale are defined by a percentage relative to the individual limit.

Reports

The following reports will be available for the Participants on the Common Report Engine:

  • CB069 (Transaction Report): Enhanced report, which will be generated on a daily basis. Additionally, intra-day versions of the report are available three times a day.
  • TD980 (Excessive System Usage Report): New report, which will be generated on a daily basis.
  • CB197 (Excess Transaction Limit Fees): New report, which will be generated at the month-end.
 
 

 

Market Status

XEUR

-

-

Trading System experiencing issues

Trading System experiencing serious issues

Production newsboard

The Market Status Indicator displays the current technical availability of the trading system.

It indicates whether Production Newsboard messages regarding current technical issues of the trading system have been published or will be published shortly.

We strongly recommend not to take any decisions based on the Market Status Indicator. Please, always check the Production Newsboard for comprehensive information.

An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.