Forex copy-symbol mapping and volume rounding
Record source and subscriber identifiers, contract multipliers and accepted quantities before calling two copied paths equivalent.
A matching display name is not the whole mapping
A copying workflow connects a source action to a subscriber account through a particular platform and broker configuration. Preserve the exact source symbol, subscriber symbol and product specification. Similar labels can still leave contract size, currency, trading session or permitted order behaviour unresolved.
MetaTrader's subscription documentation is a primary reference for that specific platform's copying workflow, not a universal rule for all services. Compare the product a consumer will actually use. A review should distinguish the documented route from a separately observed account path and avoid assigning a publisher execution automatically to every subscriber.
Volume transformation needs its own record
Save source quantity, the copying allocation setting, requested subscriber quantity and the accepted execution quantity. Any rounding, minimum, maximum or rejected action belongs in that chain. A small difference in lots can become a material difference in base units when the contract multiplier changes.
The teaching grid floors 0.035 requested lots to 0.03 on its entered zero-origin 0.01 step. It does not model a platform's allocation algorithm or guarantee acceptance. That calculation demonstrates why a review should retain both requested and transformed values, rather than overwrite the original request with the final quantity and hide the change.
Resynchronisation is not a new original idea
A later synchronization can adjust subscriber exposure without being another independently generated source signal. Identify the parent source position and the account event that changed quantity. Preserve the reason and effective time so the review can tell an original entry from a corrective action.
If additions occur at new prices, use separate entry lots or a documented account-level lot treatment. The new journal supports original lots and reductions only. It does not invent a blended price to imitate every copied net position. A platform record can be linked to the ledger when its economic fields are available, but the link must remain a declared relationship.
Stops and delivery do not disappear after mapping
Even when the symbol and volume align, the subscriber route can have different receipt times, order acceptance and executable prices. Keep stop amendments, rejected modifications and missed entries with the original lifecycle. A target reached on the source account does not establish the subscriber's realised gain.
Compare the copying documentation with an actual subscriber export when one is available. A document-only review can ask useful compatibility questions without claiming a paid test occurred. The existing provider profiles remain in place; these additions supply operational comparison fields rather than a new empirical ranking or an invented common execution record.
Make the source-to-account bridge inspectable
A bridge row can hold source original ID, source symbol, source action time, subscriber ID, mapped symbol, contract size, allocation version, requested lots, actual lots and account state. Include missed, rejected and unresolved relationships as well as successful joins. Do not reduce the population to the cases easiest to reconcile.
The packet's fictional rows have no source copying account or subscriber receipt. They teach quantity and conversion arithmetic after inputs have been supplied. Use the structure to organise a real comparison, while retaining the platform-specific rules and genuine account events needed to explain why two paths differ.
Reference documents
These references cover mechanisms and source definitions. The worked numbers on this page are invented teaching inputs, not provider or account records.