MULTI-BROKER OPERATIONS / 7 MIN READ

Multi-broker IB operations: adding a second FX broker

Set up a second FX broker relationship without mixing account IDs, partner programmes, reporting cutoffs or currencies. Includes a practical handover worksheet.

Before combining reports, establish which relationship each row belongs to and what its dates and amounts mean. One shared review process can still preserve separate broker identities, terms and currencies.

A familiar account number can belong to a different relationship

Consider a fictional introducing broker with one spreadsheet and one partner portal. Every row marked 1042 belongs to the same relationship, so nobody needs a longer label. The IB adds a second FX broker, whose export also contains account 1042. A lookup built around the account number alone now has two possible answers.

The practical fix comes before the first combined report. Give each commercial relationship its own internal reference. Keep the broker brand, contracting entity, partner programme and partner ID alongside it. Where the source uses a trading server, preserve that too. A friendly broker name helps people read the sheet; it should not carry the entire identity.

MetaTrader 5's official help describes accounts from different brokers grouped by their server names. That is a useful reminder to retain the source context. It does not make a trading login a partner-programme identifier, or give an IB permission to retrieve every account on that server.

Write a relationship register that someone else can use

Make one record per approved programme and entity, even when two relationships share a brand. Keep the agreement version and effective date with that record. If a partner manager sends revised terms, retain the earlier version and record when the new terms start; do not silently replace the rate attached to older activity.

The worksheet below is an operating note you can maintain in your own secure records. It is not a claim that every field is available from every portal, or that your statement-review tool has a dedicated field for each one. An unanswered item remains an open question.

Relationship setup worksheet: complete separately for each broker programme
RecordWhat to captureEvidence or question
Relationship identityBrand, contracting entity, programme, partner IDApplicable agreement and approval
Account contextClient ID, trading-account ID and server where suppliedWhich identifiers does this report actually contain?
Commercial scopeAccount types, instruments, territories and referral levelDated schedule; list exclusions explicitly
Reporting clockDate field, timezone, cutoff and update delayReport definition or written clarification
MoneyCommission currency and settlement currencyKeep source amounts; identify any conversion separately
Access and ownershipWho can obtain the report and who reviews itApproved access; next owner when someone is away

Keep the client, trading account and partner link distinct

A client can have more than one trading account. Counting accounts as people inflates one number; joining everything on the person's name can erase the account-level detail needed to explain a reward. Preserve the identifiers supplied by the source and document which field identifies which object.

Exness's IB reporting help makes this distinction explicit: its client report counts unique clients, while its client-account report counts individual trading accounts. The same page describes an allocation-check tool. These are examples from that provider's reporting, subject to the applicable programme and access; they do not establish another broker's attribution rules.

Before using the new referral link, record where it is approved for use and how the broker confirms attribution. If an existing client opens an additional account, ask which relationship that account belongs to. Do not infer a transfer from a conversation or edit the reporting label to make an unconfirmed assignment appear settled.

Put the report's clock on the calendar

Two exports called October can cover different events. One may select orders closed in October; another may select rewards credited during October. Ask what the date filter means, which timezone it uses and whether later adjustments can change an earlier period. Save those answers next to the report name rather than relying on memory.

For example, Exness describes Reward History by payment date, while its Performance Statistics profit uses trading activity timing. Even within one provider, similarly sized figures need not describe the same slice of activity.

In a fictional setup, Broker A exports by closing date in UTC and Broker B exports by reward-credit date in its stated portal timezone. Create a separate collection task for each. The handoff should say which file is ready, which cutoff it covers and whether a later refresh is expected. A missing Broker B report should remain missing when Broker A is ready.

Record the earning period, portal credit date and bank settlement date separately when available. Keeping those meanings visible is more useful than forcing every event into a single month column.

Separate the currencies and the access permissions

If Broker A reports USD and Broker B reports EUR, keep two subtotals. USD 900 and EUR 700 do not form a meaningful 1,600 commission balance. A management report that needs one reporting currency should retain the original amounts and separately document the conversion source, date, rate and rounding policy. Do not relabel one currency as the other.

The permission to view a partner report is also separate from permission to trade, withdraw or see a client's personal details. Collect only the data needed for the review. Keep sensitive account-to-client mappings in an appropriately restricted record, and use anonymized extracts when asking for help.

Do not solve a reporting gap by collecting a client's trading password. Start with the broker's approved partner export and establish what it covers. A report can be operationally useful without becoming a live integration.

Hand over the first report before building a larger dashboard

Run the new relationship through one small, authorized reporting sample. Confirm that the reviewer can identify its entity and programme, read the original IDs, interpret the date filter and reproduce the source totals. Record anything the export omits. This checks the handoff; it does not prove a commission entitlement or complete account coverage.

IBDock's public file preview currently accepts USD only. It processes the supported file in your browser tab; export your review before refreshing or leaving. Keep EUR reports and the relationship register in your own records. An import does not convert currencies, establish broker API access, synchronize reports or execute a payout.

Once the operating setup is clear, use the commission reconciliation guide for the separate work of comparing expected, reported and received amounts. The second broker then joins a defined process instead of inheriting the first broker's assumptions.

  • Relationship and applicable terms identified
  • Source IDs preserved without cross-broker collisions
  • Date meaning, cutoff and currency recorded
  • Attribution questions assigned to a named owner
  • First reporting handoff checked against the original export

Put the method to work.

Try the sample workspace. No broker password required.

Review a fictional USD statement

Sources and scope

Editorial scope: product reporting guidance with fictional examples. No paid broker placement, investment recommendation or independent audit claim. Product capabilities are described as of the update date shown above.

Report a guide issue or suggest a correction →

Continue reading

Comparing forex IB programmes: look beyond the advertised rate ↗

How to map broker commission CSV and Excel statements ↗

How to reconcile IB commissions across multiple brokers ↗