Ask a partner why they left their last broker and you will rarely hear that the rate was too low. You will hear that the money came late, or that it came after they chased someone for it, or that one month it was short and nobody could explain why.
Partner commission is income. An IB running a channel or an agency has people to pay out of it. A broker who treats the monthly payout run as a back-office chore is quietly telling every partner in the network that their income is a low priority, and partners respond to that by moving their clients somewhere else.
This is the operational side of the partner program. How to set the rates is a separate question, covered in the commission structure guide. This one is about getting the money out the door.
What “paid on time” means to a partner
Two things happen in a partner program and brokers often blur them together. Commission accrues continuously as clients trade. Commission pays out on a schedule. Partners care about both, and for different reasons.
Accrual needs to be visible in real time. A partner who can open their dashboard mid-month and see what they have earned so far is a partner who trusts the number when it arrives. A partner who only sees a figure once a month has no way to tell whether it is right, which means every discrepancy becomes an argument instead of a question. Kenmore’s multi-level IB module calculates against live MT4 and MT5 trade data and shows the accrual in the partner portal as it happens, which removes most of the disputes before they start.
Payout then needs to be predictable. Not fast necessarily, predictable. A partner who knows money lands on the fifth of the month can plan around it. A partner who gets paid somewhere between the third and the twelfth cannot, and will start asking on the fourth.
Choosing the schedule
Monthly is the common default and it works for most programs. It also gives a partner a long wait after their first referral, which is why the first payout is where many new partners go quiet.
Weekly or every two weeks costs more in processing but pays for itself with newer partners and in regions where people operate on shorter cycles. A reasonable compromise is a faster cycle for the first few months of a partnership, then monthly once the relationship is established. The partner sees money early, which is the point.
Whatever you pick, publish it. The schedule belongs in the partner agreement and in the portal, with the next payout date visible on the dashboard.
Thresholds and carry-forward
A minimum payout threshold protects you from paying twelve dollars across an international wire that costs more than that to send. Partners accept thresholds without complaint as long as two conditions hold: the threshold is stated up front, and the balance carries forward rather than being written off.
Set the threshold per payout method rather than globally. A crypto payout can clear economically at a much lower amount than a bank wire, so a single threshold across all methods either blocks small payouts that could have gone out cheaply or pushes uneconomic wires through.
Show the carried balance in the portal. A partner who sees “below threshold, carried to next cycle” understands what happened. A partner who sees nothing assumes the commission vanished.
Currency
Commission accrues in your account currency. The partner wants it in something they can use.
Paying a Nigerian agent in dollars sounds generous until they lose a chunk of it converting at a rate they did not choose. Paying a European partner in dollars when their costs are in euros pushes the currency risk onto them for no reason.
Decide whether you absorb conversion or pass it on, write it down, and apply it consistently. Partners will tolerate either policy. What they will not tolerate is discovering it from a short payment.
Rails, by region
There is no single method that works everywhere, which is the same problem you already solved on the client side. The infrastructure for multi-PSP routing applies here with one difference: partner payouts are outbound, lower in volume, and larger per transaction.
Bank transfer works for established partners in well-banked markets, particularly for larger amounts. It is slow and it carries fees, and in some corridors it will simply fail.
Local payment rails are what regional agents actually want. A local bank transfer in the partner’s own country clears faster and cheaper than an international wire, and in several of the markets where IB networks grow fastest it is the only method that reliably works.
E-wallets cover partners in markets where card and bank infrastructure is thin, and they settle fast.
Stablecoin and crypto payouts have become the default for a significant share of partners, particularly community owners and anyone operating across borders. Settlement is fast, fees are predictable, and the partner is not waiting on a correspondent bank. The operational requirements around crypto settlement are covered in the crypto payment gateway guide, and most of it transfers directly to partner payouts.
Offering two or three methods and letting the partner choose costs little and removes a recurring source of friction. Our payment solutions work covers the provider side, and the aggregation model is worth understanding if you are routing across several providers.
Who pays the transfer fee
Decide this before your first payout, not after a partner questions a short payment.
Both policies are defensible. Absorbing the fee is cleaner and makes the partner’s reconciliation simple. Passing it on is reasonable for expensive methods, especially if the partner chose that method when a cheaper one was available.
What does not work is a fee that appears without warning. Put it in the agreement, show it as a line item on the payout record, and let the partner see the net amount before the payout runs.
What the partner should see
A partner reconciling a payout wants to answer three questions without contacting anyone: what period does this cover, which clients and which levels generated it, and how did the gross become the net.
That means the payout record needs the period, volume by client or by referral, commission by level for partners with a network under them, any threshold carry, any fee, and the net amount with the method and date. Partners with sub-partners need the level breakdown specifically, because they are paying attention to which part of their network is producing.
This is reporting work, and it sits alongside the rest of your CRM reporting. Building it once removes a standing load from your partner team.
Approval, compliance and the paperwork
Partner payouts are payments to a business, which puts them in a different category from client withdrawals.
Partners need to be verified before the first payout, not before the first referral. Running partner KYC at onboarding stalls recruitment for no benefit, since a partner who never produces never gets paid. Running it when the first payout is due catches everything you need without adding friction to signup. The document handling fits the same KYC and AML workflow you already run.
Decide whether partners invoice you or you self-bill, and be consistent. Larger partners operating as companies will usually want to invoice. Individual partners usually will not have the capacity, and a self-billed statement they can hand to their own accountant is more useful to them.
Keep an approval gate on payouts above a threshold you set. One person reviewing the run before it executes catches the configuration error that would otherwise reach fifty partners at once.
When a payout fails
It will. A bank rejects the transfer, a wallet address is wrong, a partner’s details changed and nobody updated them.
The failure mode that damages the relationship is silence. A partner whose payout bounced and who finds out by noticing an empty account assumes the broker did not pay. A partner who gets a message the same day knows the broker is on it.
Build the alert on the broker side, not just the partner side. Your partner team should see the failure before the partner does, and the failed amount should return to the partner’s balance visibly rather than disappearing into a reconciliation queue.
Run it on a schedule, not on requests
A partner program that pays when partners ask will spend an increasing share of its time on payout administration as it grows. The target is a scheduled run that executes without anyone opening a spreadsheet: commission calculates from live trade data, the tree allocates across levels, thresholds and fees apply, the run goes to one approval, and the money leaves.
That is achievable, and it is mostly a question of whether the commission engine is connected to the trading server directly or whether someone is exporting reports and reconciling by hand. The second approach survives at twenty partners and breaks at two hundred.
Kenmore Design has been building this layer for brokers since 2006. The multi-level IB module handles unlimited tiers, commission as pips, a percentage of spread, profit or deposit, or cash per lot, across regular and cent accounts, with partner-side reporting and MT4 and MT5 integration on a flat monthly fee. If you are recruiting partners now, the recruitment guide and the enablement guide cover what happens before the first payout.
Request a Consultation on Building an IB Payout Strategy
Get expert guidance on designing a reliable commission payout framework for your Introducing Broker network. We’ll help you evaluate payout schedules, minimum thresholds, currency conversion, payment methods, approval processes, and partner reporting to support predictable and transparent commission payments.
Together, we’ll review your current partner payment operations and outline a payout strategy aligned with your brokerage’s financial processes and long-term growth.
