What it is
An order management system is where a manager's investment decisions become orders — checked against mandate and regulation, routed to the market, and allocated back to the funds that placed them. finnerve's OMS does that with the compliance check as a hard gate in the path: mandate limits, concentration rules and regulatory restrictions are evaluated before an order can route, not reconciled after it fills.
Most order systems treat compliance as a module you switch on and a report you read on Friday. The OMS treats it as a wall the order has to pass through — there is no path around it. And it is deliberately agnostic about where the order goes: it interoperates with the brokers, custodians and execution venues you already run rather than forcing a rip-and-replace, so the trading relationships you have built stay exactly where they are. The machine carries the clean flow end to end and escalates only the exceptions — a mandate breach, a block that won't allocate cleanly, a broker that rejects — and your desk takes it from there.
Who it's for
The OMS runs in production for desks that consolidate across several managers and won't trade oversight for speed — from a single-fund manager placing fifty tickets a day to a multi-manager platform blocking orders across a dozen books.
- Asset managers & multi-manager platforms — several portfolio managers whose orders consolidate into broker blocks daily, each held to its own mandate.
- Funds — mutual, public and private — per-vehicle limits and regulatory restrictions enforced before the order routes, not after the fill.
- Wealth managers — multi-custodian routing from a single ticket, with the audit trail intact.
- Family & multi-family offices — cross-asset orders split across custodians and venues, each held to its own restrictions.
- Investment advisors (RIAs & independent advisors) — bank-grade order controls and a defensible trade record without standing up an institutional trading desk.
What it covers
The OMS owns the path between the decision and the fill: compliance, consolidation, routing and write-back.
- Pre-trade compliance (hard gate) — mandate limits, concentration and regulatory checks evaluated before an order can route; a breach is stopped at the desk, not caught at reconciliation.
- Block consolidation & allocation — a multi-PM order book that turns 12 individual orders into 4 broker blocks and allocates each fill back down by average price, pro-rata to the funds that placed them — no manual ticket-stitching.
- FIX 4.4 routing — straight-through sessions to brokers, venues and your external EMS, with multi-broker and smart-routing rules and full message audit.
- Counterparty & settlement rules — broker limits, routing preferences and settlement instructions encoded once and applied to every order.
- Execution write-back & audit — fills reconcile straight back into the PMS, with an immutable order-to-fill trail behind every ticket.
How it fits your stack
The OMS sits one layer above execution and one layer below the decision. Your PMS feeds it live positions and the mandate each order is held to; the OMS gates, blocks and routes; and it hands execution to the EMS, brokers and FIX venues you already clear through — then writes the fills back to the PMS. It is passthrough on the order side and a hard wall on the compliance side.
Live order flow in weeks
Implementations are led by people who have sat on a trading desk. Pre-built session templates for the regional brokers. Mandate-rule libraries you tune, not author. A paper-trade environment on your test broker before a single live ticket moves.
From there, AI agents monitor session health, reconcile allocations and clear the routine exceptions a manual desk would leave for a person — surfacing only the ones that need a trader's judgment. The goal of every engagement is the same: the shortest defensible path to a live, compliance-gated order flow you can stand behind, then we compound from there. Bring us a day of your order book and we'll scope it honestly.
An AGF in Chile pushed STP from 71% to 99.4%.
Replaced an in-house ticket-stitching workflow with the OMS's allocation and routing engine. Pre-trade compliance moved from end-of-day reconciliation to a real-time gate in the order path.
The Friday apology to compliance stopped. The audit trail simply exists now. We'll put you on a call with them.
Frequently asked questions
We already run an EMS and our own broker relationships. Does the OMS replace them?
No — and that's deliberate. The OMS is an order-management layer, not an execution venue: it sits upstream of your EMS and routes to it over FIX 4.4, alongside the brokers and venues you already clear through. Nothing about your execution relationships changes; what changes is that every order reaching them has already passed the mandate check and been blocked and allocated correctly. It interoperates with your stack — it doesn't ask you to tear it out. We'll route a paper-trade environment to your own test broker in a working session so you can see the passthrough for yourself.
A hard compliance gate on every order — doesn't that slow the desk down?
The gate is real, but it isn't a bottleneck: the median pre-trade check runs in 0.4 seconds, evaluated inline before the order routes. Traders feel a confirmation, not a wait — and the orders that do stop are the ones you'd want stopped anyway. Compare that to catching a breach at end-of-day reconciliation, when the fill already happened. Bring us your mandate rules and we'll show you the check running against live tickets in a demo.
How does block allocation actually work — do we lose control of average price?
You don't. The OMS consolidates orders across every PM into broker blocks, executes the block, and allocates each fill back down by volume-weighted average price, pro-rata to the funds that placed the orders — with the full allocation logic on the audit trail. Twelve tickets become four blocks without anyone stitching them by hand, and every fund gets the same execution price it would have contested for.
What happens when an order breaches the mandate, or a broker rejects the block?
The machine handles the clean flow and escalates the exceptions — it doesn't silently drop them. A breach is stopped at the gate with the reason attached; a broker rejection or a block that won't allocate cleanly lands in an exception queue for a trader on your desk to clear. Nothing routes on a guess, and every exception and its resolution is on the audit trail.
When a regulator asks us to prove an order path, can we?
Yes, to the message. Every order carries an immutable order-to-fill trail — the pre-trade check and its result, the block, the allocation, the FIX messages and acknowledgements, and every override with who authorised it and when. There's no reconstructing the story after the fact, because the story was recorded as it happened. Bring your compliance lead to a working session and we'll pull a full order path in front of them.