Coordinated hedging detection looks for relationships between accounts that take opposing positions in a connected pattern. For a forex brokerage, the investigation is about more than whether the trades offset. The team needs to understand who is linked, how the activity was coordinated and what the pattern means for the brokerage.
Opposing trades, shared IP addresses and zero net exposure are not proof of abuse. Each can arise for legitimate reasons. A defensible review combines several signals, preserves their source records and distinguishes a pattern alert from a confirmed finding.
Define the pattern before setting the alert
Specify the activity you are looking for: related accounts, the same or economically related instruments, opposing directions, a time window and a defined relationship between volumes. State whether the rule applies across servers and how partial or repeated trades are grouped.
Also identify the operating concern. Potential bonus exploitation, coordinated account activity and execution-related concerns need different supporting evidence. A generic “hedging abuse” label should not replace an explanation of the actual pattern and the policy being reviewed.
Read the trade sequence before interpreting the result
One account buys 1.00 lot of EURUSD, a second buys 1.50 lots, and a third sells 2.50 lots within two seconds. Gross volume is 5.00 lots and signed net volume is zero, assuming comparable contracts. That arithmetic describes the offset; it does not establish improper coordination.
Preserve the original execution times, source servers, account identifiers and contract context. Check whether the timestamps are comparable and whether they represent requests or completed executions. Similar-looking events can be misleading when their clocks or record types differ.
Inspect what happened before and after the sequence as well. Repeated matching patterns may warrant closer review than a single coincidental offset. Partial closes and later adjustments can change the economic picture.
Corroborate the relationship between accounts
Review shared devices, IP addresses and relevant network relationships alongside the trading sequence. Record when a relationship was observed, which accounts it connects and whether it appears repeatedly. Preserve missing or inconsistent evidence rather than silently replacing it with an assumption.
Shared networks can occur in offices, households, mobile networks or hosted environments. Geographical similarity is context, not identity. A “same country” flag should carry less explanatory weight than a well-supported combination of infrastructure and repeated trading behaviour.
The linked accounts and coordinated trading guide explains the wider network review. Use it to distinguish evidence of a relationship from a claim about who controls an account.
Measure impact separately from the pattern score
A zero net position across a group can coexist with gross trading activity, execution costs and exposure in individual books. Examine the allocation of each trade and any external hedge before interpreting the brokerage impact. Do not infer the desk result from the group’s net lots alone.
Review realised and unrealised market P/L, charges and relevant incentives on a consistent basis. Where activity crosses A-Book and B-Book, retain that distinction. The broker revenue guide helps separate retained market P/L from other revenue and costs.
If a tool displays a confidence score, ask how it is constructed and calibrated. A 92% pattern score is not automatically a 92% probability of misconduct. The score should direct attention to evidence, not substitute for the reviewer’s conclusion.
Build a reviewable incident record
The incident should bring together the trade sequence, relationship evidence, affected accounts and the reason the configured rule triggered. Record the rule version, review time, owner and outcome. Let the reviewer identify both supporting and contradictory evidence.
- Confirm the original trades, volumes and timestamps.
- Inspect infrastructure links and plausible alternative explanations.
- Check for repeated coordination over a relevant period.
- Measure the book-level and brokerage-level impact.
- Record the finding and the reason for any operational action.
Sequence automated actions after the evidence review
Separate detection, notification and any action affecting an account. A system can notify the risk team or flag a case for review without treating every alert as a confirmed violation. Define which controls require approval and how exceptions are handled under the brokerage’s policies.
Monitor the quality of alerts over time. Track dismissed cases and the reasons for dismissal so the team can refine thresholds and reduce repetitive noise. Keep an audit trail when a rule or response changes.
The BrokerCNC Toxic Trading Detection demo illustrates how incoming trades become a potential coordinated-hedging incident with linked evidence and response workflows. Read the broader toxic trading detection guide, or request a live demonstration around the patterns your risk team investigates.
Common coordinated-hedging questions
Is zero net exposure itself suspicious?
No. It is a description of offsetting positions within the selected scope. The relationship evidence, timing, recurrence and operational context determine whether further investigation is warranted.
Can a shared IP address confirm coordination?
Not on its own. Treat it as one signal and review it with device relationships, repeated trade patterns and legitimate explanations for shared infrastructure.
See the workflow in BrokerCNC.
Explore the platform with our team and discuss your MT4/MT5 servers, books and operating priorities.
Book a Live Demo →





