Define the relationship between the parties
Identify which organisation holds the client relationship, which organisation supplies trading accounts and which systems record referral attribution. Confirm the permissions available to the introducing business before designing dashboards or automation. A commercial relationship does not automatically grant access to all account or transaction data.
Translate the intended service into tasks: register a referral, associate an approved client, view permitted status and review agreed reporting. Keep account changes, financial operations and other restricted actions with the authorised party unless specific access has been agreed.
Create a permissions and reporting map
| Workflow | Boundary to establish | Acceptance check |
|---|---|---|
| Referral attribution | Which system records the referral and agreed changes | A test referral is matched once to the correct relationship |
| Client status | Which fields the introducing business may see | The portal exposes only the approved client view |
| Reporting | Which record defines the agreed commercial calculation | The sample report can be reconciled by both parties |
| Support handoff | Which team handles account or trading issues | A sample case reaches the responsible team |
Commercial calculation rules and any compensation terms belong in the parties’ agreement. This blueprint does not define a compensation model or entitlement.
Test disputed and incomplete states
A useful portal must handle more than a successful referral. Review duplicate records, a client missing required approval, changed attribution and delayed reporting. Decide how a discrepancy is raised and which party can correct the authoritative record.
- Use test identities and avoid copying unnecessary live personal data.
- Validate the approved role and field visibility.
- Reconcile a reporting sample with the executing broker.
- Document the review path for exceptions before exposing the workflow to users.
Keep the operating model distinct
An introducing workflow may use a CRM or portal without requiring the same infrastructure as a brokerage operating its own platform environment. Scope the actual role first; do not purchase or advertise an undefined “broker package” that obscures the executing relationship.
If the business later considers a different model, review MT4 White Label or MT5 White Label as a separate project. The change would require a fresh review of platform rights, operational ownership and the relevant external approvals.