IB and affiliate infrastructure that survives an audit.
Partner networks are how most brokerages actually grow — and commission is the calculation partners check most closely. The structure has to be defined in the system, versioned over time, and explainable line by line when an IB disputes a statement.
Commission is an accounting system, not a marketing feature.
If a figure cannot be reconstructed from records, the relationship with the partner is already at risk.
Every commission figure has to be reproducible from the underlying records: which client, which account, which trades, which rate, which period, which level of the hierarchy. That requirement shapes the design more than any dashboard does.
Effective-dated rules, versioned hierarchies and a logged approval chain are what make the number defensible.
Recurring failure patterns
What the infrastructure covers.
Multi-Level Hierarchies
Master IBs, sub-IBs and further levels with their own rules, overrides and reporting scope. Moving a client or an IB inside the hierarchy is a recorded event, not a silent overwrite — because historical commission has to remain explainable.
Commission Rules
Rules defined per IB, per account type, per symbol group and per level, with effective dates so a rate change does not retroactively rewrite last month's statements.
Referral & Attribution
Referral links, codes and campaign parameters carried from first click through registration to account opening, so attribution survives the gap between marketing and funding.
Partner Dashboards
Each IB sees their own clients, volumes, accrued commission and payout history — scoped to their level of the hierarchy and nothing above it.
Payout Workflow
Accrual, statement generation, approval chain, payment execution and reconciliation, with the audit trail retained against each period.
Controls & Integrity
Self-referral detection, duplicate-client checks, adjustment logging and permissions that separate who calculates commission from who approves it.
Commission models and what each one demands.
The model is a commercial decision. What it demands from the system is not optional.
| Model | Basis | What it requires |
|---|---|---|
| Revenue share | A share of the revenue generated by referred clients | Requires an agreed, auditable revenue definition per account type |
| Rebate per volume | A fixed amount per lot or per million traded | Symbol-level and group-level rates diverge quickly; needs structured rate tables |
| CPA | A fixed amount per qualifying client | Qualification criteria must be defined in the system, not in the agreement only |
| Hybrid | CPA plus ongoing revenue share or rebate | Clawback and qualification windows have to be enforced automatically |
| Sub-IB / multi-level | Commission distributed across a hierarchy | Level rules, overrides and hierarchy changes must preserve history |
IB infrastructure — common questions.
Discuss Your IB Structure
Describe your partner model and hierarchy depth, and we will review how it should be represented in the back office.
Explore Client Portal & IB Research
Operator-level analysis supporting client portal & ib infrastructure.