A portfolio management system (PMS) for digital asset derivatives is the system of record for what a desk holds, what it is worth, how much risk it carries and how much margin it uses on each venue. It takes every fill from every venue, keeps positions current, marks them, computes Greeks and PnL, and carries them through expiry, settlement and reconciliation. For a crypto derivatives desk trading options, futures and perps on several venues, the PMS is what turns a set of exchange accounts into one book.
PMS vs EMS vs OMS
The three labels describe different jobs in the same workflow. An EMS is built for the trader: market data, order entry, algorithms, RFQ and routing across venues. An OMS is built for the firm’s record of orders: approvals, pre-trade checks, allocations and audit trail. A PMS is built for the book: positions, valuation, risk, PnL and reporting after the trade. An OEMS combines the first two, and in crypto derivatives many desks want all three in one place so they are not reconciling fills between systems. For the execution side, see what is a crypto derivatives EMS.
This guide follows a trade through its lifecycle and looks at what the PMS has to do at each step. For the risk view itself (cross-venue Greeks, exposure and hedging), see cross-venue portfolio and risk for digital asset derivatives.
The derivatives trade lifecycle on crypto venues
1. Pre-trade risk check
Before an order leaves the desk, it should be checked against the current book: position and notional limits, Greeks limits, and the margin it will consume on the venue where it will execute. This only works if the check sees live positions across all venues. A delta limit checked against one exchange account says nothing about the offsetting or compounding position held on another.
2. Execution, including RFQ and blocks
Orders go to central limit order books, to RFQ networks such as Paradigm, or to the block and RFQ systems built into venues such as Deribit and Derive. Multi-leg packages may execute as one block or be legged across books. Each path produces fills in a different format, and the PMS has to capture all of them with the same fields: instrument, side, size, price, fees, venue, account and time.
3. Fills and allocation
Fills arrive asynchronously over WebSocket, sometimes partially and sometimes out of order. The PMS has to attach each fill to its parent order, and for a package, to the package. Where a desk runs several strategies, sub-accounts or funds, fills also have to be attributed to the right book so that PnL lands where the trade was intended.
4. Position keeping across venues
Positions are rebuilt from fills and checked against what each venue reports. The PMS needs a common instrument model so that a BTC call on one venue and a BTC call on another can be compared, aggregated and hedged against each other, even when strikes, expiries, contract sizes and settlement currencies differ.
5. Mark-to-market and Greeks
Every position is marked continuously. For options that means a mark price and a consistent set of Greeks. Venues publish their own marks and Greeks with their own conventions, so a PMS either normalizes venue Greeks or computes its own from a single model, and it has to be clear which one the desk is looking at. PnL should split realized from unrealized and include fees and funding.
6. Margin monitoring per venue
Each venue margins and liquidates only the positions in its own account. A desk can be flat delta across venues and still be close to liquidation on one of them. The PMS has to show margin used and available per venue and per account, in the venue’s own terms, so the desk can move collateral or reduce positions before the venue does it for them. Software cannot net margin across venues; that comes from a prime broker or credit intermediary.
7. Settlement and expiry handling
Dated futures and options expire on schedules and indices set by each venue. On Deribit, options expire at 08:00 UTC and settle on a 30-minute time-weighted average of the Deribit index from 07:30 to 08:00 UTC. Since April 2026 for USDC options and August 2026 for BTC and ETH options, in-the-money Deribit options first settle into the matching futures contract at the strike, which then cash settles, so the transaction log shows two entries rather than one. Event contracts on Kalshi and Polymarket resolve on their own sources and times. The PMS has to roll expired positions off, book the settlement cash, and show what is expiring next and how much it is worth at the current index.
8. Reconciliation against venue statements
The internal record has to match each venue’s record of trades, positions, balances, fees, funding and deliveries. Breaks come from missed fills during a disconnect, manual trades placed on an exchange screen, fee tier changes and settlement entries the desk did not expect. A PMS should make breaks visible quickly instead of leaving them for month end.
9. Reporting
Finally, the book has to be reported: daily PnL and attribution, risk snapshots, order and fill history for audit, and exports for fund administrators and accounting. In crypto there is no market close, so the desk also has to pick a snapshot time and apply it consistently.
What makes this hard in crypto derivatives
- Different contract specs. Contract size, tick size, multipliers and listing schedules vary by venue and change over time. A PMS that hardcodes them will drift.
- Inverse vs linear. Deribit lists both inverse BTC and ETH options, settled in the coin, and linear options settled in USDC. Inverse positions carry PnL and margin in BTC or ETH, so dollar PnL moves with the coin price as well as with the option. Aggregating both requires converting consistently.
- Settlement indices. Each venue settles on its own index and averaging window. Two contracts on the same underlying and the same date can settle at different prices, which is basis risk the PMS should show rather than hide.
- Perpetual funding. Perps have no expiry but pay or charge funding on a schedule. Funding belongs in PnL and in the carry view of a hedge.
- 24/7 markets. There is no close to reconcile against and no quiet window for batch jobs. Positions, marks and margin have to stay live through weekends and holidays.
- Per-venue margin. Margin models differ by venue, and portfolio margin rules group positions differently from one venue to the next. The desk needs each venue’s view, not a blended number that no venue uses.
What to require from a PMS for digital asset derivatives
- Direct connections to the derivatives venues you trade, named, with positions and fills streamed in real time rather than polled overnight.
- A normalized instrument model that handles inverse and linear contracts, multipliers and settlement currencies.
- Consolidated positions, Greeks and PnL across venues, with fees and funding included.
- Margin usage per venue and per account, in each venue’s own terms.
- Expiry and settlement handling that follows each venue’s schedule and delivery process.
- Complete order and fill history, available for reconciliation and audit.
- Integration with execution, so pre-trade checks and hedges use the same live book.
- An API covering the same data as the UI, so the PMS can feed risk models, accounting and AI agents.
- No custody. The system should work through the desk’s own venue accounts and never need to hold its assets.
Where Kemet fits
Kemet is execution and risk software for institutional digital asset derivatives and prediction markets, combining EMS, OMS and PMS functions in one platform. It connects to Deribit, Coinbase, OKX, Binance, Bybit, Bullish, Hyperliquid, Derive, Kalshi, Polymarket and Paradigm RFQ. Venue availability depends on the desk’s jurisdiction: Deribit direct, Binance, OKX and Bybit are not available to US persons.
Across those venues, Kemet keeps consolidated positions, Greeks and PnL, margin usage per venue, and the full order and fill history, alongside execution tools including multi-leg packages, algorithms and RFQ. That puts pre-trade checks, execution and position keeping on the same live book. Everything in the UI is available through a REST and WebSocket API and an MCP server for AI agents, so the data can feed a desk’s own risk models, reporting and accounting. See the platform overview, and for desks weighing an in-house system, build vs buy for crypto derivatives execution infrastructure.
Kemet is a technology provider, not an exchange, broker or counterparty, and never holds client assets. Clients trade through their own venue accounts and API keys. Kemet is SOC 2 Type II compliant.
FAQ
What is a portfolio management system for digital asset derivatives?
It is the system of record for a derivatives book: it collects fills from every venue, keeps positions, marks them, computes Greeks, PnL and margin usage, and carries positions through expiry, settlement, reconciliation and reporting.
What does a risk management system for digital asset derivatives need to show?
At minimum, consolidated positions and Greeks across venues, PnL including fees and funding, upcoming expiries, and margin used and available on each venue. Because each venue liquidates only its own account, a combined risk number is not enough on its own.
What is digital asset trade lifecycle management?
It is the handling of a trade from pre-trade checks through execution, fill capture and allocation, position keeping, mark-to-market, margin monitoring, settlement or expiry, reconciliation against venue records, and reporting. In crypto this runs 24/7 across venues with different contract specs and settlement rules.
What is an OEMS and PMS for crypto?
An OEMS records and executes orders across venues; a PMS tracks the resulting positions, risk and PnL. Running both in one platform means fills flow straight into the book, with no reconciliation step between an execution system and a position system.
What should a crypto order management system do for derivatives desks?
It should keep a complete record of orders and fills across venues, run pre-trade checks against the live book, link fills to parent orders and packages, and make that history available for audit and reconciliation through an API.
Can a PMS net margin across crypto venues?
No. Each venue margins only the positions in its own account, and cross-venue margin offsets come from a prime broker or credit intermediary, not from software. A PMS can show margin usage per venue and where a hedge or collateral move would relieve it.
To see how Kemet runs a derivatives desk across venues, Book a demo.