Partner Networks and Closed-Volume Qualification Rules

Partner-growth programmes can measure two different things at once: the structure of an approved network and the eligible trading activity completed through that structure. A large contact list does not prove a verified network, and a platform volume total does not prove eligible closed volume. Each record must pass the definition in the current partner agreement before it contributes to qualification.

A partner network is usually a traceable set of approved relationships. The governing terms should explain which direct partners, sub-brokers or other permitted participants can sit beneath the primary partner, how each relationship is attributed and whether a member can belong to more than one network.

An application is not a verified member

An application records intent. Verification may also require identity checks, approval under the responsible entity, an accepted agreement, an issued tracking route and permitted activity in an eligible territory. Pending, duplicated, inactive, suspended or rejected records may not contribute to a network threshold.

Referral Attribution, Qualified Clients and CPA Rewards explains why attribution, approval and qualification should remain separate states.

A direct member is connected to the primary partner through the approved first-level relationship. An indirect member may sit under another verified participant. Whether indirect levels count, how many levels are recognised and which party owns the relationship are programme-specific decisions. The portal hierarchy should match the agreement rather than an offline spreadsheet.

Prevent duplicates and self-referrals

Names, companies and accounts can appear more than once through different links or introductions. Programmes can apply duplicate, related-party, self-referral and reassignment rules. A network total should count only the distinct relationships accepted by the controlling record.

Trading platforms distinguish orders, executed deals and positions. Closed volume normally depends on an executed transaction that reduces or removes an open position, but the promotion can define the exact counting event. A cancelled order, an unfilled request or an open position does not become closed volume merely because it appears in an activity view.

Partial closes and round turns

If a 1-lot position is reduced by 0.4 lot, the record can show 0.4 lot closed and 0.6 lot still open. A programme might count the completed portion, require a fully closed position or use a round-turn convention. It should also state whether opening and closing sides are added or whether the completed pair is treated as one unit.

Open, Closed and Hedged Volume in Promotion Rules sets out the trading states that sit beneath this calculation.

Closed does not automatically mean eligible. The calculation may filter by participating account, instrument, minimum holding period, measurement window, server time, transaction type and account status. Corrections, reversals, excluded strategies, prohibited activity and trades outside the governed route can be removed during validation.

How Promotional Trading Volume Is Calculated provides a step-by-step framework for applying these filters to platform history.

Gross volume and network contribution

A dashboard may display gross activity, eligible activity and credited network contribution as different measures. The programme might attribute volume to the executing member, roll it into an approved parent network or apply another hierarchy. Partners should not add the same transaction at more than one level unless the terms expressly define that treatment.

A two-dimensional pathway may require both a verified-network band and an eligible closed-volume band. Reaching one threshold does not replace the other. Confirm that both tests use the same monthly or campaign period and that the final tier is based on completed, validated records rather than forecasts.

Thresholds can change by schedule

Network bands, volume bands, eligible products, rates and caps can change between programme versions. Save the schedule that applies to the measurement period. A previous month’s threshold or a public planning example should not be applied to a later reconciliation without confirmation.

Assume a monthly planning band asks for ten verified network members and 3,000 eligible closed lots. The offline network list contains twelve names, but one application is pending and one record is a duplicate. The verified network total is therefore ten. The platform report shows 3,450 closed lots, but 200 lots belong to an excluded product, 150 fall outside the measurement cut-off and 250 fail the required holding test. Eligible closed volume is 2,850 lots.

In this illustration, the network band is reached but the volume band is not. The pathway therefore remains below the combined qualification point. The example shows why neither the contact-list total nor the unfiltered platform report can be used on its own. Actual programme definitions, bands and calculations must come from the current agreement and portal.

Why the dashboard total can move

Provisional records can change when identity checks finish, relationships are reassigned, trades settle into the correct period or reversals are processed. A movement is not necessarily an error. Review the status history and adjustment reason before comparing snapshots taken at different stages.

• Which network levels are recognised, and when does membership become verified?
• Which deal state produces closed volume, and how are partial closes treated?
• Which accounts, instruments, territories and activity types are excluded?
• Do the network and volume tests use the same dates and time zone?
• Can a later correction, inactivity event or reassignment change the result?
• Which portal statement or approval marks the qualification as final?

1. Save the current agreement, schedule, entity and measurement period.
2. Export the approved network hierarchy from the secure portal.
3. Separate pending, verified, inactive, duplicated and excluded members.
4. Match each counted member to its approved attribution route.
5. Reconcile eligible closing deals for the same period and network scope.
6. Compare both thresholds with the portal-confirmed outcome and raise supported differences.

Network targets and volume thresholds do not change the risks of CFDs or leveraged foreign-exchange products. They should not encourage a partner or client to increase position size, frequency or exposure solely to reach a programme band. Promotion communications should also make the commercial relationship clear and avoid claims the partner cannot substantiate.

A reliable qualification result can be traced from an approved relationship to an eligible completed transaction and then to the governing schedule. Where any link is pending, the amount should remain pending rather than being presented as achieved.