Trace the transformations between source and terminal
List the source connection, any normalisation or adapter layer and the platform-side receiving arrangement. Record where naming, precision, sessions or other fields are transformed. An issue at one layer can appear as a missing or incorrect chart elsewhere.
MT4 and MT5 environments may use different integrations, permissions and operating boundaries. Inventory the actual setup for each platform rather than assuming a single feed component can be reused unchanged.
Validate mapping and configuration together
| Review item | Evidence to retain |
|---|---|
| Instrument identity | Source identifier matched to the intended platform symbol |
| Numerical interpretation | Quote precision and relevant instrument specification checks |
| Time and session | Timestamp meaning, market schedule and inactive-state behaviour |
| Delivery observation | Source, adapter and platform samples from the same window |
| Exception handling | Response to an unknown symbol, stale input or interrupted source |
The test sample should cover each materially different instrument configuration. A successful update on one familiar currency pair does not establish the correctness of every mapped symbol.
Prepare separate acceptance records where needed
Illustrative dual-platform review: the same authorised source supplies an MT4 environment and an MT5 environment through agreed connections. The team checks each platform’s symbol mapping and observed result independently, then records differences that affect operations.
Keep the mapping register, configuration baseline, monitoring owners and approved change procedure in the handover. Confirm platform access and data-use rights with the responsible providers before implementation. To scope the work in a broader deployment, review MT4 White Label and MT5 White Label requirements separately.