Pre-Trade Risk
Manage risk with a series of comprehensive checks, verifications, and control actions.
The modular architecture of PTR and its hierarchy of user permissions greatly simplifies enterprise management of trading desks.
Pre-trade risk controls are a fundamental capability in any automated trading solution today with the increasing complexity of electronic order execution, new regulatory requirements, and internal risk management concerns.
The challenge firms face is to protect themselves from the risks of errant trades without introducing unwanted latency in their trading systems.
The Redline Pre-Trade Risk (PTR) analytics engine performs a comprehensive and configurable series of risk checks, verifications, and control actions that provide reliable results facilitating compliance with U.S. SEC Rule 15c3-5 and European MiFID II mandates. These checks are available across equities and FX markets.
Features
Compliant
Mitigate risk with order and position checks
Efficient
Uncompromised performance, reducing latency impact on outbound orders.
Transparent
Intuitive interface to administer/monitor risk checks and trading activity across users
Multi-Asset Class
Applicable risk checks across all major asset classes
Pre-Trade Risk solution provides the scalability, flexibility, and accuracy needed to maximize trading profits while minimizing risk exposure.
In addition to all risk checks currently supported, Redline’s PTR solution also supports a tiered system of permissions with administrator, client and read-only all being supported. This allows for absolute limits to be set globally (or on a per client basis) that cannot be exceeded with clients also having the ability to control their own limits, albeit without overriding those set by the administrator. Furthermore, read-only is provided for those users with applications that require transparency of risk check thresholds and real-time client trading activity without the need to modify.
Pre-Trade Risk Capabilities
Due to specific characteristics of each trading venue, contact Redline to confirm the mapping of these checks to the venues of your choice.
Order Checks | Description | Asset Classes | Control Parameter | Control Action |
|---|---|---|---|---|
Single Order Quantity | The quantity of securities in a single order is verified to be less than or equal to the maximum allowed | Equities, FX | Maximum Order Quantity | Order is rejected |
Limit Price Difference | The price per security of each limit within a specified percentage of the "best" price (e.g. , for U.S. equities, current NBBO) | Equities, FX | +/- Limit Percentage | Order is rejected |
Limit Order Price Tier | The incoming limit order price is checked against a configurable percentage plus or minus the reference price using a configurable number of price percentage tiers | Equities, FX | +/- Limit Percentage | Order is rejected |
Trading State | Trading is either: | Equities, FX | TRADING_STATE parameters | Order is rejected |
Maximum Notional Per Minute | Verifies each order against a defined maximum notional order quantity per minute (sliding window) per symbol | Equities, FX | Maximum Notional Per Minute | Order is rejected |
Max Position Quantity | The quantity of the order is verified to not exceed a set maximumnumber of maximum net/gross quantity/value | Equities, FX | Max Position | Order is rejected |
Average Daily Volume Limit | The volume of the order is verified to not exceed a set percentage of the average daily volume of the symbol | Equities | Limit ADV Difference | Order is rejected |
Average Daily Volume Percentage | The incoming order quantity is checked against the Average Daily Volume Percentage value times the symbol''s Average Daily Volume quantity | Equities, FX | Average Daily Volume Percentage | Order is rejected |
Parent/Child Order Quantity | The summation of child order quantifies does not exceed the remaining open order quantity of the parent order | Equities, Futures, Option, FX | Parent Order Quantity | Order is rejected |
In addition to the atomic risk checks, Redline’s PTR also supports the concept of hierarchical limits. If set, this configures PTR to run multiple hierarchical levels of checks on each order. If this value is not set, only the most specific check is run for each order.