Skip to content
Genesis Ark

03 / Pre-trade risk

Available

Stop the bad order before it reaches the venue, not after

Qubit checks every order against your limits, your live positions and a reference price before it is routed. A failed check rejects the order with a specific reason, and every decision is logged. Run it inside the Qubit platform or as a gateway in front of your own OMS.

Layer
Core
Works on its own
Yes
Interfaces
Inside the core, or as a FIX and API gateway
Fig. 1. Limit utilization per account, with a price collar reject. Illustrative composition with sample data.

01 / The problem

One extra zero is all it takes

A trader types 1,000 instead of 100. A strategy loops and sends the same order a few hundred times. A client account trades past the credit it has. On most crypto venues, nothing stops these orders except the venue's own broad limits, which were not written for your firm. Post-trade monitoring tells you what went wrong. Pre-trade risk stops it from happening.

02 / What it does

The checks

  1. 01

    Order size

    Maximum quantity and maximum notional per order, per instrument and per account.

  2. 02

    Price collar

    Rejects a limit order priced further than a set distance from the reference price, in basis points or percent, and rejects market orders when no valid reference price exists.

  3. 03

    Credit and balance

    Checks the order's notional against the account's available credit or pre-funded balance, including orders already working.

  4. 04

    Position limits

    Maximum long and short position per instrument and per asset, and maximum gross and net exposure per account.

  5. 05

    Daily limits

    Maximum traded notional and maximum number of orders per account per day.

  6. 06

    Restricted instruments

    Blocks trading in instruments on a restricted or watch list, per account, client group or the whole firm.

  7. 07

    Message-rate throttle

    Caps orders and cancels per second per session or account, to stop runaway strategies and protect venue rate limits.

  8. 08

    Duplicate detection

    Flags or rejects an order identical to a recent one in the same account within a set window.

  9. 09

    Self-match prevention

    Prevents orders from the same beneficial owner from matching against each other.

03 / How it works

What happens in the check

Fig. 2. The stages below, in order. Each one writes to the audit trail.
  1. 01

    Identify

    The order is matched to its firm, desk, trader, account and instrument, and the limits that apply at each level are loaded.

  2. 02

    Check

    Each applicable check runs against the order and the live state: positions, balances, working orders and the reference price.

  3. 03

    Decide

    If all checks pass, the order is released to routing. If a hard limit fails, the order is rejected with the check name and values. If a soft limit fails, the order waits for an authorized override.

  4. 04

    Record

    The decision, the values used and the user who overrode a soft limit, if any, are written to the audit trail.

  5. 05

    Update

    When the order fills, positions and used limits update immediately for the next check.

04 / Specifics

Technical specifics

Limit hierarchy

Firm, desk, trader, account and instrument. The most restrictive applicable limit wins.

Limit types

Hard (reject, no override) and soft (hold for override by a permitted user, with a reason recorded).

Reference price for collars

Last trade, mid, or best bid and offer from the consolidated book, chosen per instrument, with a staleness threshold after which the reference is treated as invalid.

Limit administration

Limits are set in the admin console or over the API. Increases can require approval by a second user before they take effect. Every change is logged with old value, new value, user and time.

Kill switch

At firm, desk, trader, account, instrument or venue level. Activation cancels working orders in scope and blocks new orders until a permitted user releases it.

Gateway mode (standalone)

Qubit sits as a FIX acceptor for your OMS and a FIX or API initiator toward venues. Orders that pass are forwarded unchanged; rejected orders return an ExecutionReport (35=8) with OrdStatus (39) rejected and the reason in Text (58).

Reject reasons

Every reject carries a machine-readable code and a readable message. Illustrative example: PRICE_COLLAR: limit 71,250 is 6.1% above reference 67,150; maximum 5.0%.

05 / Controls and audit

What you configure, and what gets written down

Configurable

  • Limits at firm, desk, trader, account and instrument level
  • Hard or soft type per limit
  • Reference price source and staleness threshold per instrument
  • Restricted and watch lists per account, client group or firm
  • Second-user approval for limit increases
  • Kill switch scope and the users permitted to release it

Logged to the audit trail

  • check decision · pass, reject or hold, with check name and values
  • soft limit override · user and reason
  • limit change · old value, new value, user, time
  • limit increase approval · second user
  • kill switch activated and released
  • breach by fill flagged to risk users

06 / Where it fits

Works on its own
Yes, as the pre-trade risk gateway: a gateway that sits between your existing OMS and the venues.
Needs the core
No. Inside the core platform, pre-trade risk is a mandatory part and uses ledger positions in real time.
Who uses it
Brokers and banks with client flow, prop trading firms, funds with several traders or strategies, exchanges routing client orders externally.

FAQ

Questions we get asked

  • Does pre-trade risk add delay to every order?

    Every check adds some processing time, which is why the checks run in memory against cached limits and live positions, without a database read in the order path. We do not publish latency figures; we will measure them with you, in your environment.

  • Can we use it without changing our OMS?

    Yes. In gateway mode your OMS connects to Qubit instead of directly to the venues. Your OMS keeps its own logic; Qubit applies the checks and forwards orders that pass.

  • What happens when a limit is breached by a fill rather than an order?

    Fills are never rejected, because the trade has already happened. The position updates, the breach is flagged to risk users, and new orders that would increase the breach are blocked until it is resolved.

  • Can different clients have different limits?

    Yes. Limits are set at every level of the hierarchy, so each client account can carry its own credit, size, position and instrument rules.

  • Who can change a limit?

    Only users whose role allows it. Increases can be set to require a second approver, and all changes are in the audit trail.

Put a control between every order and the market

A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.