MT5 WHITE LABEL IMPLEMENTATION BRIEF

Project / company:
Contact:
Current environment:
Instruments and account currencies:
Intended markets:
CRM / client portal:
Execution connections:
Required timing and dependencies:

PLANNING WORKSTREAMS

1. Define the scope and dependencies
Decisions: Record instruments, account currencies, intended markets, integrations and existing systems. Identify who supplies each component and which approvals or agreements are prerequisites.
Evidence: Signed scope, supplier contacts and a dependency list.
Owner:
Status / open questions:

2. Confirm the platform arrangement
Decisions: Identify the contracting parties, permitted branding, access and responsibilities. Obtain written confirmation that the proposed arrangement can support your use case before making a launch commitment.
Evidence: Commercial scope and rights confirmed by the relevant suppliers.
Owner:
Status / open questions:

3. Design account groups and access
Decisions: Specify demo and live groups, account currencies, permissions, leverage rules and who can approve changes. Separate ordinary operational access from administrative access.
Evidence: Approved group matrix and named access owners.
Owner:
Status / open questions:

4. Approve instrument specifications
Decisions: Document symbols, mapping, contract size, digits, trading sessions, commissions, swaps and margin settings for the selected instruments. Reconcile platform settings with the execution connection.
Evidence: Instrument sheet reviewed by the responsible operations team.
Owner:
Status / open questions:

5. Agree the client experience
Decisions: List the approved brand assets, domains, available client access methods and support contacts. Confirm what the supplier can deliver instead of assuming every client or application can be rebranded.
Evidence: Approved branding scope and client access instructions.
Owner:
Status / open questions:

6. Map CRM and account workflows
Decisions: Define identifiers and states shared by the CRM, client portal and platform. Cover account creation, demo-to-live transitions, permission checks and error handling. Identify separate verification and payment dependencies.
Evidence: Workflow map with test cases and ownership of failed requests.
Owner:
Status / open questions:

7. Map execution connectivity
Decisions: List bridges or gateways, instruments, quantity mapping, execution routes and available test environments. Specify what should happen during disconnects and rejected requests.
Evidence: Connection diagram, mapping sheet and operational escalation path.
Owner:
Status / open questions:

8. Reconcile balances and reporting
Decisions: Define which system owns each record and how account balances, transactions, fills and reports are checked. For a migration, specify the cutover boundary and reconciliation before reopening activity.
Evidence: Reconciliation procedure and exception log.
Owner:
Status / open questions:

9. Run acceptance tests
Decisions: Test account creation, quotes, order processing, charges, reports, reconnect behaviour and recovery in the agreed environment. Record expected and observed results; assign an owner to every unresolved issue.
Evidence: Test evidence with explicit pass/fail results and issue owners.
Owner:
Status / open questions:

10. Review monitoring and recovery
Decisions: Identify alerts, backup ownership, restore procedures and recovery dependencies. Review the agreed support coverage and escalation process. A backup plan needs a tested restore procedure.
Evidence: Monitoring contacts and a recorded recovery exercise.
Owner:
Status / open questions:

11. Prepare operational handover
Decisions: Document routine tasks, access changes, maintenance windows and approved configuration changes. Confirm who supports the CRM, platform, execution connection and infrastructure after handover.
Evidence: Operating runbook and a responsibility matrix.
Owner:
Status / open questions:

12. Make the release decision
Decisions: Review unresolved issues and prerequisites with the responsible owners. Agree release timing, communications and rollback criteria. Completing this worksheet is not regulatory approval or a substitute for acceptance sign-off.
Evidence: Release decision, rollback plan and sign-off by the responsible owners.
Owner:
Status / open questions:

ACCEPTANCE RECORD
Scenario:
Environment and configuration version:
Expected result:
Observed result:
Evidence:
Issue owner / follow-up:

A planning worksheet; not a supplier quote, licence confirmation or launch approval.