A MAM or PAMM demonstration should show how an instruction becomes account records under an agreed allocation rule. This checklist turns that discussion into observable tests.
Name the account roles first
Describe the master account, sub-accounts, manager, investor and staff roles in your intended workflow. Record which role can instruct, inspect, change settings or reconcile results. An account diagram with named responsibilities is a better starting point than assuming the terms MAM and PAMM describe an identical implementation everywhere.
The published TradeToolsFX Multi-Account Trader materials describe master/sub-account allocation and related allocation inputs. Ask our team to demonstrate the supported rules for your proposed MT4 or MT5 configuration.
Make the allocation rule explicit
Write the chosen method, the inputs it uses and when those inputs are evaluated. Include account eligibility, instrument volume increments and the treatment of quantities that cannot be distributed exactly. Confirm how the configured system handles these cases; do not infer executable volume from a simple ratio alone.
For an arithmetic illustration, weights of 1 and 3 represent 25% and 75% of a hypothetical allocatable quantity. If that quantity is 4 units, the arithmetic shares are 1 and 3 units. Actual executable quantities depend on the instrument, the chosen method and the configured volume and rounding rules. This example explains proportions; it is not a promised execution result.
Keep a test log
| Scenario | Expected rule to agree | Evidence to record |
|---|---|---|
| Simple master instruction | Eligible accounts and allocation inputs | Master instruction and resulting sub-account records |
| Volume increments | Rounding and remainder treatment | Calculated and executable quantities |
| Account unavailable | Eligibility and exception handling | Status, logs and any required follow-up |
| Partial or full close | Position and allocation handling | Before/after records and reconciliation |
| Reconnect or retry | Recovery and duplicate-prevention behavior | Observed records and an exception owner |
Inspect exceptions deliberately
Ask what should happen if an account lacks the required resources, becomes ineligible or cannot receive the expected quantity. Include a partial-close scenario where relevant. Write down the proposed behavior first, then compare it with the demonstration result.
For reconnect and retry scenarios, agree a controlled demonstration environment. Identify the records that distinguish an accepted instruction, an incomplete operation and a follow-up action. Record who is responsible for investigating discrepancies.
Reconcile the records
Use one scenario identifier across the master instruction, allocation inputs, account records and support notes. Review the observed outcome rather than relying only on an aggregate dashboard. Agree which reports and logs will be available to the operating team.
Include the surrounding CRM and client-account workflow if clients need access to related information. Review server operations when defining monitoring, access and support responsibilities.
Distinguish allocation from a terminal interface
If the task is to operate several accounts from one interface, review the separate Multi-Account Terminal. If the task concerns a master/sub-account allocation workflow, start with MAT. Describe the intended process before selecting the product.
For background, read PAMM Account Concept. To prepare the broader operating setup, use the brokerage blueprint configurator. The test checklist concerns software behavior and operational evidence, not investment returns.
Bring your scenarios to a demonstration.
Share the platform, account structure, allocation requirements and records your team needs to inspect.
Discuss MAM/PAMM on Telegram ↗