Start with the workflow, not the acronym
MAM generally refers to coordinating trading across individual accounts through an allocation mechanism. PAMM refers to a percentage-based management and accounting model, whose exact fund structure and fee rules depend on the provider. Copy trading replicates supported source positions under subscription settings.
These names do not define every implementation. Ask where balances reside, how trades are recorded, who can submit orders and what happens after a failed execution. A provider’s actual specifications matter more than a generic label.
What to compare in an MT5 environment
Compare account ownership, allocation rules, instrument compatibility, margin checks and result verification. Then examine operational details: adding or excluding accounts, pausing execution, partial fills, unknown responses and manual reconciliation.
For copy trading, also check polling frequency, symbol mapping, source-position lifecycle and entry-age rules. For PAMM, review the accounting model and fee calculation. A statement that a product supports MAM does not establish that it includes PAMM accounting or performance fees.
| Model | Operating logic | What to confirm |
|---|---|---|
| MAM | Account-level allocation of an execution plan | Supported allocation rules and per-account results |
| PAMM | Percentage-based accounting under a provider’s model | Fund structure, accounting and fee rules |
| Copy trading | Replicating supported positions from a source account | Polling, symbol mapping and execution differences |
How the current TGS CRM is structured
The multi-connection workspace organizes authorized broker connections and account oversight. Trading MAM handles administrator-confirmed market batches using equal or predefined weighted allocation. Copy trading handles supported position replication through configured subscriptions and routes.
Automatic balance/equity allocation and PAMM fee accounting are not part of the current trading MAM. Choose the relevant workflow, test it on demo accounts and define the acceptance criteria before production.
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