Quod Financial: modular trading, FX aggregation and workflow controls

Quod Financial builds trading technology for banks, brokers, asset managers, hedge funds and other institutional desks. Its front-to-middle architecture connects order handling, execution and operational processing across asset classes. A brokerage can select a particular execution or control layer, while a broader deployment can consolidate multiple desks and regions on the same configurable framework.[2]

The listed FX instruments include spot, forwards, swaps, NDFs and non-deliverable swaps. The same offering also lists metals, commodities and crypto; enabled instruments and counterparties remain part of the implementation scope.[6]

Unity maps orders, executions and fills into common states, timestamps and identifiers, then passes normalized outputs to reporting and other downstream consumers. Its dashboards and exception handling expose mismatches across connected systems. This is useful when the existing OMS, EMS, reporting and custody feeds use different representations of the same trade: connecting them and reconciling their lifecycle semantics are separate tasks. Quod markets the layer as vendor-neutral and suitable for staged modernization.[5]

Quod lists .NET, Java and REST trading/administration APIs, FIX connectivity and real-time data access through APIs or files. These interfaces support integration with an institution’s own applications; the published list is an interface family, rather than a specification of permissions or message coverage for every installed module.[2]

Market Making can receive prices or derived inputs such as volatility and Greeks from external engines and feeds. A C++ API allows clients to extend quoting logic, while FIX and open APIs connect other systems. An Excel plug-in can consume live prices and publish two-sided quotes or limit orders. It is consequently an active pricing interface, not merely a spreadsheet report.[7]

The middle-office page names CTM, ALERT, OASYS, SWIFT and FIX connectivity, with client-specific files and custom APIs. It also lists multiple CTM BICs, DTC affirmation states and Traiana workflows. Downstream connectors and message formats need to match the actual booking and settlement architecture; a supported connection does not make Quod the custodian or settlement counterparty.[9]

The public sales route is a consultation and demonstration. No standard currency-denominated tariff for production licences, hosting, implementation or minimum commitments is published in the reviewed product material. A commercial proposal therefore needs to identify the selected modules and delivery responsibilities; the breadth of the product catalogue is not an inclusive price package.[16]

For FX Taker, Quod advertises an optional sell-side charging arrangement as a zero-cost solution. It supplies no public rate, qualifying volume or allocation of ancillary costs on that page. The claim is specific to that charging route, not a statement that the entire Quod suite is free.[6]

The automation page says monthly releases are included in its software subscription. QuantReplay is separately available under Apache 2.0 as open-source software; that licence concerns the simulator, rather than commercial OMS/EMS access or support.[10][22]

EMS delivery can be deployed, managed or hosted. It may be installed as an execution layer connected to the existing OMS, workflows and market connectivity, or combined with Quod’s routing, algorithmic and analytics modules. This modular approach makes the division between vendor-operated infrastructure and the institution’s own systems a central implementation decision.[4]

The middle-office migration sequence starts with workflow mapping, connects upstream and downstream endpoints, validates output and exceptions in a parallel run, then cuts over by desk or asset class. Allocations, confirmation formats, fee exceptions and replay/re-push behaviour are the practical acceptance criteria described by Quod.[9]

Unity’s product page advertises an operational timeline of four to eight weeks. This is a published delivery claim, not an agreed deadline for an unspecified integration. Its emphasis is on retaining existing systems during a phased transition, rather than requiring a simultaneous replacement of the whole trading estate.[5]

Automation responds to market data, order state and execution outcomes using configurable rules. The documented controls include pause, resume and override, alerts for stalled orders or rejects, and live parameter changes without restarting the platform. Monitoring is therefore part of the operating model: changing a rule can affect active trading immediately, while exception screens give traders a means to intervene.[10]

Quod advertises 24/6 support for its OMS, with teams in the US and Europe, plus training and documentation during integration. The automation page describes a 24/6 third-line helpdesk using telephone and chat. Neither description supplies a universal incident-response, resolution or service-credit schedule.[3][10]

Support uses Jira for tickets and Confluence for project tasks, deliverables and acceptance/testing goals. The public support page also describes documentation embedded in each deployment and matched to its product version. This matters when a public feature page describes a capability newer than the installed release; the deployment’s documentation is the relevant operational reference. The separate documentation hub requires login.[15]

Quod is profiled here as a software provider. Order-routing, pre-trade controls and reporting are functions used by the customer institution; a software licence does not supply brokerage, custody or market-access permissions. OMS controls include configured quantity, value, price, position, velocity and margin checks, with logging and decision traceability.[3]

QuodIQ is described as a containerized Model Context Protocol layer connecting the OMS/EMS to an approved language model. Quod, the institution or an approved cloud provider may host the model. Its design keeps access within the chosen security environment and allows model substitution. Those deployment choices need to be fixed in the implementation: the public architecture description alone is not a customer-specific data-processing or model-training agreement.[11]

Quod reports ISO/IEC 27001:2022 certification and a SOC 2 Type II audit in its company material. These statements describe the supplier’s security assurance, rather than an individual deployment’s operating performance.[2]

The privacy policy covers personal information supplied through services and the website, including credentials, communications, usage and device information. Retention lasts for the relevant purpose, followed by deletion or anonymization; rights requests use the privacy address. It does not specify a production order-history export period or a contractual exit timetable. Those records and exit obligations need to be established in the service agreement rather than inferred from this personal-data policy.[17]

Quod describes its origins as an innovation lab in 2004 and dates its initial data-driven SOR and algorithmic solution to 2008. The development from execution technology into order management and middle-office workflows explains the modular portfolio now offered.[2]

Companies House lists Quod Financial Limited, number 05957359, as active, incorporated on 5 October 2006. Its registered office is 55 Baker Street, London. Quod’s own contact page gives 17 Dominion Street, Moorgate, as the operating contact address; the two address roles should be kept distinct.[18][16]

A March 2025 announcement appointed Medan Gabbay co-CEO effective 21 March, alongside founder Ali Pichvai. The announcement describes his previous revenue and implementation responsibilities and the shared leadership arrangement. It is a leadership transition, rather than evidence of a sale or change of corporate owner.[19]

Operator

Quod Financial Limited

Service scope

Institutional order, execution, FX aggregation, market-making and post-trade software, with white-label retail interfaces and modular integration.

Customer types

Banks; Brokers and broker-dealers; Asset managers; Hedge funds; Proprietary trading firms

Delivery

Hosted; Managed service; API

Pricing publication

Public and quoted pricing

Headquarters

London, United Kingdom

Platforms

OMS; EMS; Unity; Market Making; Middle Office; Retail Trading System; QuodIQ; QuantReplay

Integrations

FIX; Java / .NET / REST APIs; CTM / ALERT; SWIFT

Pricing scope

Production scope is quoted; FX Taker has an optional sell-side charging route. QuantReplay is separately open source.

Implementation

Modular deployment with integration, parallel validation and phased migration; operating responsibilities depend on the delivery model.

Support

Published 24/6 support, Jira tickets, project resources and version-specific documentation.

Permissions and regulatory scope

Technology supply; the customer institution retains responsibility for its financial permissions and configured trading controls.

Provider metadata checked 20 Oct 2026Source 1Source 18Source 4Source 9Source 16Source 15Source 3

Quod’s AEP transaction-cost analysis combines order and execution records with market snapshots. At venue level it reports latency, hit ratios, rejections, spreads and algorithm performance; at order level it reconstructs the decision sequence and associates benchmarks such as calculated VWAP, slippage and spread capture. The practical value is the connection between a routing choice and the market conditions available at that time, rather than a single average execution score. The page describes both pre-trade and post-trade analysis and feedback into routing or algorithmic strategies.[20]

Observe’s report builder lets users describe and refine an execution report, save its profile, then schedule delivery after the close or send it through SFTP. This adds a repeatable reporting route to its interactive queries. The described reports still depend on the underlying data and access rights; the read-only trading boundary does not mean that reports cannot be generated or distributed.[12]

QuantReplay provides a separate environment for testing order-driven markets. Each simulated venue uses a native C++ process with a shared PostgreSQL database, FIX for trading/market data and REST for administration. It supports generated activity or historical playback and save/restore of simulator state. This allows an integration team to exercise order handling without using production execution; it is a simulation environment, not a production liquidity source.[21]

The current official QuantReplay repository also lists scheduled closed, pre-open, pre-close and auction phases, including indicative auction prices and randomized uncrossing. That is more specific than the older setup guide’s auction-roadmap wording. For implementation, the selected repository version and its FIX dictionaries should govern the tested behaviours.[22]