Define the account and connection scope
List the MT5 servers, exact account groups, manager permissions and instruments used by the proposed pool. Check each account with its connection context. A pool may span authorized connections, but every instrument and receiving account needs its own validation.
The current TGS implementation supports up to 20 members per pool and 100 pools. Allocation uses equal shares or configured integer weights. Balance-based or equity-based allocation is not part of this MAM module.
Validate lot steps and the prepared plan
Review minimum and maximum volume, volume step, available margin and supported execution settings per participant. A prepared plan records the account snapshot and calculated volume. Each share rounds down to the receiving instrument’s step; a remainder is left unallocated.
For example, 1.00 lot split equally across three accounts with a 0.01 step produces 0.33 lots each and a 0.01 remainder. This calculation alone sends no orders. Reject or revise any plan that violates participant limits.
Confirm the batch and reconcile results
An operator reviews and explicitly confirms a market BUY or SELL batch. The execution process checks conditions again and records actual requests and deals for each account. Across brokers, execution is sequential and has no common transaction or automatic rollback.
A partial or unknown result stops the batch for review. Reconcile broker evidence before preparing a replacement action. Test denied access, a changed margin, incompatible symbols and an interrupted response in a demo environment.
Accept operations before going live
Confirm staff permissions, account isolation, logging, recovery and ownership of the execution service. Check that the operator can distinguish prepared volume, submitted requests and confirmed execution.
For continuous position copying, configure the separate Copy Trading workflow and its worker. For investor shares and performance fees, validate PAMM separately. A MAM acceptance result does not establish that either additional workflow is ready.
Implementation workflow
- 01
Define connections and account scope
- 02
Validate permissions and instrument settings
- 03
Test workflows in a demo environment
- 04
Agree production rollout and operations