Say "AI in the OMS" on a trading floor and someone immediately starts costing a new security assessment. Whether AI trading compliance is genuinely harder depends entirely on where the AI sits.
The concern is reasonable. AI implies decisions being taken without proper controls, and preventing exactly that is what a compliance function exists to do. But the anxiety usually comes from collapsing two very different architectures into a single word.
Recommendation is not execution
The distinction that matters is whether the AI is making decisions or informing them.
If AI produces recommendations, and those recommendations feed into an existing platform that already carries the controls you would expect on any desk, the additional overhead is minimal. Nothing has changed about how an order is checked, limited, routed or recorded. What changed is the quality of the input arriving at the top of that pipeline.
The overhead appears when the AI is the execution path — when a model's output becomes an action without passing through the controls governing every other action on the desk. That is a genuinely new risk surface, and it deserves the scrutiny it will get. The European Securities and Markets Authority has been explicit that existing conduct obligations apply regardless of whether a decision was machine-assisted.
AI trading compliance is a layering problem
So the important question in designing an AI trading solution is not which model you chose. It is how cleanly you have separated the AI decision from the risk controls and the data controls that already exist.
Every individual AI, every AI operation, every AI agent must have its own layer of data protection and security.
Medan Gabbay, CEO, Quod Financial
Each agent gets its own data protection and security boundary rather than inheriting broad access by default. An agent built to analyse historical fills does not need, and does not get, the permissions of one that surfaces counterparty exposure. Scoping access per agent is unglamorous work, and it is what keeps a security assessment from becoming an open-ended exercise.
And every action the AI initiates runs through what is otherwise entirely normal trading infrastructure.
The same accountability a trader has
The test we hold ourselves to is straightforward. An action originating from AI should carry exactly the accountability and auditability the same action would carry if a trader had taken it. Same controls, same record, same ability to reconstruct months later why it happened and what information was in front of the system at the time.
This is not a special regime invented for AI. It is the core design principle behind everything Quod Financial builds, and introducing an intelligence layer does not change it. The reason it holds is architectural rather than procedural — the model never reaches execution, as set out in our piece on AI trading architecture.
Framed that way, most of the AI trading compliance conversation resolves itself. You are not asking your compliance team to evaluate a black box that trades. You are asking them to confirm that a new source of analysis feeds a control framework they already approved — a materially smaller question, and one with a defensible answer.
More in this series
-
Where the AI stops and the software takes over
-
What actually changes on the desk
-
Can AI touch our data without it leaving?
-
Not another AI bolt-on
Learn more about Quod IQ.