Accountable publisher
Published under the RTX5 Editorial Team byline. It identifies the responsible publishing organization; it does not imply that a named lawyer, regulator, financial adviser, or licensed expert approved this page.
Evidence-led commission guide: Multi-Tier IB Commission and Rebate Models Explained. Review decision criteria, limitations and next steps.
Trust and methodology
We want you to be able to identify who owns the page, inspect the evidence, understand how tools were used, and challenge anything that looks wrong or out of date.
Published under the RTX5 Editorial Team byline. It identifies the responsible publishing organization; it does not imply that a named lawyer, regulator, financial adviser, or licensed expert approved this page.
2 primary references are listed on this page with context about what each one supports. The source set was checked on . The page also includes an original working artifact: Multi-tier IB commission trace.
Automation and AI may help organize research, outline a page, or edit language. They are not treated as sources, are not presented as human experts, and do not remove the publisher's responsibility for the final page.
If a statement is incomplete, unsupported, or outdated, send the exact URL, sentence, and supporting evidence through our contact route. Read the full editorial and corrections policy.
Direct answer
An introducing-broker commission model defines which partner receives credit for a client or event, which economic activity is eligible, how gross revenue or volume is measured, how tiers and overrides apply, which adjustments reduce the amount, when the commission becomes payable, and how reversals or disputes are handled. Multi-tier structures add parent, master-IB, sub-IB, and direct-client relationships, so the system must prevent double payment and preserve the hierarchy that applied when the event occurred.
A robust rebate engine is ledger-based and versioned. It stores attribution evidence, hierarchy, plan and rule version, source trades or revenue events, currency conversion, calculation steps, caps, exclusions, adjustments, approval, payable state, payout, reversal, and final accounting reference. The commercial model must also pass legal, regulatory, tax, privacy, and financial-promotion review in every market where partners solicit or refer clients.
Original commission example
A partner statement should reproduce each step from eligible client activity to approved payable amount. The values below are illustrative.
Twenty standard lots × assumed $10 pip value × 1.0-pip eligible markup = $200 gross eligible revenue.
Primary IB share 30% = $60. If an approved sub-IB receives 40% of the primary share, allocate $24 to the sub-IB and retain $36 for the primary IB.
Apply documented exclusions, reversals, fraud or chargeback holds, currency conversion, tax, minimum payout, approval, payment status, and later adjustment as separate ledger events.
Contract definitions control. Specify whether the basis is spread, commission, net revenue, fixed lot, deposit, qualified account, or another event, and never infer one model from a dashboard label.
Words such as CPA, revenue share, lot rebate, and sub-IB override are incomplete until the eligible event, amount, timing, hierarchy, and correction behavior are specified.
Define referral link, code, campaign, first or last touch, manual assignment, existing client, cross-device identity, cookie or consent, attribution window, parent and child relationships, hierarchy effective dates, reassignment, and evidence for disputes.
Specify opened, verified, funded, activated, traded, retained, or net-revenue events; product and account eligibility; minimum deposit or volume; canceled or abusive activity; spread, commission, swap, fees, bonuses, chargebacks, and negative adjustments.
Document fixed, percentage, per-lot, instrument, volume-band, cohort, region, campaign, and negotiated rates; progressive versus retroactive tiers; parent overrides; maximum chain depth; caps; floors; and precedence when rules overlap.
Define pending, approved, held, payable, paid, reversed, disputed, expired, and forfeited states; validation period; minimum payout; currency; conversion time; payout method; fees; tax documents; approvers; and accounting date.
Address self-referral, duplicate identity, collusion, misleading advertising, prohibited territories, trademark bidding, incentive abuse, churn, artificial volume, unauthorized advice, complaint history, and partner suspension or clawback.
Assign an immutable plan version with effective dates, rates, eligible products, hierarchy rules, examples, exclusions, hold periods, currencies, and approval. Store the version on each attributed relationship.
Capture referral, client, verification, funding, trading, revenue, adjustment, chargeback, and account-status events with durable IDs, timestamps, source, account, entity, and currency.
Determine eligibility, economic base, direct commission, tier adjustment, parent overrides, caps, exclusions, conversion, withholding, prior corrections, and net payable. Persist every intermediate value.
Route duplicate identity, missing attribution, unusual volume, self-referral, conflicting rules, negative revenue, chargeback, manual reassignment, and complaint cases to controlled review.
Match calculation ledger, broker revenue source, partner statement, payment record, general ledger, and tax or withholding records. Carry forward adjustments explicitly rather than overwriting history.
Partners need understandable statements, while brokers need enough detail to detect error, abuse, and unauthorized promotion.
Retain source, campaign, consent or permitted basis, client identifier, timestamps, device or session evidence where lawful, hierarchy, reassignment, and plan version.
Store source-event IDs, eligible base, rates, tier, overrides, exclusions, currency, conversion rate, adjustments, output, state, and code or configuration version.
Explain period, client or privacy-safe reference, eligible activity, calculation, pending amounts, holds, reversals, prior corrections, paid amount, currency, and dispute route.
Preserve approved content, jurisdiction, channel, audience, risk wording, approver, version, expiry, partner acknowledgment, monitoring, and takedown actions.
Connect approved liability, payment batch, provider reference, bank or wallet settlement, failed or returned payment, withholding, and accounting entry.
Sources were checked on 21 September 2026 and support the stated context; they do not certify RTX5, replace product testing, or provide individual legal or financial advice.
It is an amount a parent or master partner receives based on eligible activity attributed to a child partner. The rate, base, hierarchy date, cap, and effect on the child payment must be explicit.
The program must define whether reassignment is permitted, its effective time, approval, history, open positions, prior activity, and dispute evidence. Never rewrite old attribution silently.
Technology can calculate it, but the incentive, conflict, client outcome, promotion, tax, and legal implications require jurisdiction-specific review.
Review the planning cluster, follow another published reference, or discuss the exact product and deployment evidence your team needs. A contact request is not a promise of regulatory approval, market access, or universal availability.