MAM is an operating workflow as much as a software feature. The broker and manager need to understand exactly how instructions, allocations and account-level controls interact.
Follow the evidence
Trace how the event could reach markets, then inspect a competing explanation.
Compare explanations
Switch lenses to see what each account explains—and what remains uncertain.
Review who can create, amend or close an allocation, what clients can see and how risk limits are enforced. Permissions should be tested for both normal workflows and exceptions such as rejected orders or disconnected accounts. Reconcile orders, allocations, fees and balances against the platform record. Keep an auditable trail that explains which instruction applied, when it was received and how any discrepancy was resolved.
Review who can create, amend or close an allocation, what clients can see and how risk limits are enforced. Permissions should be tested for both normal workflows and exceptions such as rejected orders or disconnected accounts. Reconcile orders, allocations, fees and balances against the platform record. Keep an auditable trail that explains which instruction applied, when it was received and how any discrepancy was resolved.
The software does not determine whether an arrangement is permitted in a jurisdiction. Clarify who makes discretionary decisions, what authority each participant has and which disclosures or approvals apply to the relationship. Before selecting a vendor, test allocation behavior with representative accounts and failure scenarios. Request documentation for data access, recovery, version changes and support escalation rather than relying only on a product demonstration.
One instruction can produce different account-level results
A manager may place an order that is distributed to several client accounts under configured allocation rules. Those rules can use equity, balance, lot size or another method, depending on the platform and agreement.
Small differences in account settings, available margin, symbol specifications or execution timing can produce different fills. A shared master instruction does not mean every account receives the same price or outcome.
Treat permissions and reconciliation as core design choices
Review who can create, amend or close an allocation, what clients can see and how risk limits are enforced. Permissions should be tested for both normal workflows and exceptions such as rejected orders or disconnected accounts.
Reconcile orders, allocations, fees and balances against the platform record. Keep an auditable trail that explains which instruction applied, when it was received and how any discrepancy was resolved.
Confirm the legal role and client disclosures
The software does not determine whether an arrangement is permitted in a jurisdiction. Clarify who makes discretionary decisions, what authority each participant has and which disclosures or approvals apply to the relationship.
Before selecting a vendor, test allocation behavior with representative accounts and failure scenarios. Request documentation for data access, recovery, version changes and support escalation rather than relying only on a product demonstration.