B2BROKER has announced a B2CONNECT update that expands supported margin-account currencies and provides clearer order attribution. The supplier describes it as its September release in a product notice dated 23 October. For an FX or multi-asset broker, the consequential detail is how orders originating from several underlying accounts remain distinguishable when they use shared liquidity infrastructure.[1]
The company's technical product documentation describes a multi-account FIX connector that accepts the owning margin account in standard FIX Tag 1, Account. B2CONNECT routes the incoming order against that account and returns the same value on subsequent execution reports. The arrangement allows a platform serving multiple white labels or clients to operate one connector rather than configuring an entirely separate connector for every margin account.[2]
B2BROKER describes a second layer of attribution: an end-client reference sent in FIX Tag 526 is stored with the execution and appears in the Trading Report under Hub Reports in TRAM. Its current connector page also says Account (Tag 1), and where enabled SenderSubID (Tag 50) and OnBehalfOfCompID (Tag 115), can travel to the liquidity provider and return in execution reports. These fields serve related but distinct purposes: margin-account identity, client reference and downstream participant identification.[2]
The September release allows the main asset of a new margin account to be selected from assets enabled on its hub, including specified fiat currencies and crypto assets. That denomination applies to balances, equity, margin and profit and loss, with automatic price conversion; deposits and withdrawals use the selected asset. USD remains the default and existing accounts are unaffected. The update also extends Swap Profiles beyond CFDs and fixes a rare recovery case in which a filled order could be reported as expired.[1]
Reconciliation rather than headline connectivity
Two FIX fields with different reporting roles
| Field | Purpose in B2CONNECT |
|---|---|
| Tag 1 — Account | Names margin account used for routing and reports |
| Tag 526 — SecondaryClOrdID | Carries client reference when taker supplies it |
| TRAM Hub Reports | Displays retained reference for trade reconciliation |
| Shared FIX connector | Can serve multiple separated margin accounts |
A shared connection can reduce the number of session configurations and lower operational complexity, but it also increases the importance of correct field mapping. If the source platform omits Tag 526, B2BROKER's documentation does not imply that the hub can reconstruct an absent end-client reference. If Tag 1 is misassigned, apparent consolidation could instead misattribute risk and margin.[2]
For broker back offices, the proposed check is concrete: select an order in the front-end platform, follow its Account and reference tags through routing, compare the returned execution report and reconcile the resulting trade in TRAM. A clean sequence would be evidence of traceability for that transaction. It would not by itself prove every exceptional state, partial fill, disconnection or correction has been handled.[2]
B2BROKER’s announcement and documentation do not publish measured latency changes, independent load tests or a quantified saving from account consolidation. The release is relevant because it exposes the operational mechanics of managing many separated accounts through shared market access; the business case remains dependent on the individual broker's connectivity and reporting design.[1]
Sources & further reading
- New in B2CONNECT: More Margin Account Currencies And Clearer Order Attribution B2BROKER · 23 Oct 2026 · Accessed 30 Oct 2026
- One FIX connector for multiple margin accounts B2BROKER · 30 Oct 2026 · Accessed 30 Oct 2026