Managing separate risk limits in MAM accounts

A shared manager or order source does not mean every MAM subaccount has the same risk capacity. Balances, base currencies, margin and obligations can differ. An independent limit becomes operationally meaningful only when its measure, enforcement location and response to a breach are defined.

A label does not define a limit

An account risk limit might concern quantity, exposure, used margin or drawdown from a reference. That reference might be the start of the day, the start of cooperation or a previous peak. These are different measures. Document resets, deposits and withdrawals, and included costs. A number without those definitions cannot be reliably reconciled.

A hypothetical difference between subaccounts

For illustration, suppose an exposure rule is defined as 10 percent of each account’s reference value. A basis of 1,000 gives a numerical ceiling of 100, while 2,000 gives 200. This only demonstrates differing bases; it is not a recommended risk percentage or a universal exposure formula. Different instruments may require different exposure definitions and units.

Pre-order and post-execution checks differ

One control may restrict new instructions, while another may only issue an alert after the state changes. Pending orders, partial fills or price moves can later change the account’s position relative to the limit. Ask where enforcement occurs and whether it is active. A field on a form is not proof that the rule is being enforced.

Define the response separately

Stopping new allocations, cancelling pending orders and closing positions are different actions. Stopping incoming instructions does not necessarily close existing trades. Attempted closure can face slippage or insufficient liquidity. Do not describe a software threshold as a certain loss ceiling without conditions and supporting evidence.

Create a control matrix for each subaccount

• Measurement basis, currency and covered instruments.
• Threshold, reset time and treatment of cash movements.
• Enforcement location: host, manager software or manual monitoring.
• The defined response and who is authorised to perform it.
• Existing-order treatment and discrepancy recording.

Review effects on the combined position

If a subaccount refuses some instructions, its proportions of related positions may diverge from the master. Less quantity alone does not establish less risk: the missing leg may have been a hedge. Read the actual rules for unallocated remainders rather than assuming they are automatically transferred elsewhere.

Test and document changes

Before activation, review calculations and boundary cases without live trades. Test-environment results do not guarantee live execution. Every threshold change needs a date, reason and required approval. Changing the reference after an event must not conceal a past breach. Monitoring should also show missing data and disconnections explicitly.

In a manager cooperation inquiry, describe the scope and limitations of controls. When browsing trading accounts, distinguish claimed capabilities from tested enforcement. This article sets no personal risk level, recommends no additional capital and does not claim every host implements these controls.