Source-aware field guide · 20 answers
A-Book, B-Book and Hybrid Routing
Operational answers for documenting internalization, external hedging, hybrid routing rules, conflicts, testing and execution evidence.
Published · reviewed for scope, source visibility and answer ownership
How to use this guide
Operational answers for documenting internalization, external hedging, hybrid routing rules, conflicts, testing and execution evidence. It is written for broker founders, dealing leaders, risk managers, compliance reviewers and execution technology teams. The labels are industry shorthand rather than proof of a legal role, execution quality or customer outcome, and this collection does not prescribe a routing model. Use it to turn a sales conversation into a responsibility map, evidence request and acceptance plan that named reviewers can approve.
Each answer supports one operating decision: For each accepted order, what documented rule determined internal handling or external routing, which price and capacity applied, and which record proves the outcome? Applicable duties depend on product, jurisdiction, client category and legal capacity; qualified advisers must review the actual arrangement. Work from the actual entity, instruments, client locations, counterparties and deployment design because the same label can describe materially different services.
The primary reference set is Global Foreign Exchange Committee — FX Global Code; Global Foreign Exchange Committee — Disclosure Cover Sheets; FINRA — Rule 5310 Best Execution and Interpositioning; EUR-Lex — Delegated Regulation (EU) 2017/565. These sources define standards, regulatory expectations or official operating concepts; they do not endorse FxTrusts or prove a feature in any deployment. Recheck the current source, signed order form, technical specification, permissions and test record before a production, trading or compliance decision.
What Do A-Book and B-Book Mean Operationally?
A-book commonly describes externalizing exposure and B-book commonly describes internalizing it, but the labels do not specify legal capacity, venue, counterparty or execution method.
- Use it to
- Replace each label with an order-and-hedge flow showing entities, systems, counterparties, timing, prices, ownership and resulting exposure.
- Check the boundary
- Marketing terminology can conceal mixed handling, delayed hedging or different treatment by product, account and market condition.
How to Document Customer Order and Hedge Flows
An order-and-hedge flow distinguishes the customer transaction from any separate risk-reducing transaction executed by the broker with an external counterparty.
- Use it to
- Record identifiers, timestamps, quantities, prices, fees and state transitions that link or deliberately separate the two transactions.
- Check the boundary
- A hedge executed near a customer order should not be represented as the same transaction unless the legal and operational design establishes that relationship.
How to Define a Broker Routing Policy
A broker routing policy states eligible destinations, decision inputs, hierarchy, exceptions, conflicts, approvals and review standards for each order category.
- Use it to
- Write deterministic rules where possible and require reason codes plus authorized review for manual or discretionary overrides.
- Check the boundary
- A policy that only names A-book or B-book cannot explain how an individual order was treated or why.
Does A-Book Routing Guarantee External Execution?
A-book routing is evidenced by an accepted external order and execution record, not merely by sending a request toward a bridge or counterparty.
- Use it to
- Reconcile the client order to outbound messages, acknowledgements, fills, rejects, cancellations, allocations and counterparty statements.
- Check the boundary
- Connection availability or a routing flag does not prove that an external counterparty accepted and filled the intended quantity.
How Does B-Book Internalization Work?
B-book internalization means customer exposure remains within the broker or designated principal entity until it is offset, hedged or otherwise managed under policy.
- Use it to
- Map the booking entity, pricing source, exposure ledger, risk limits, hedge authority and financial reconciliation for internalized transactions.
- Check the boundary
- Internalization does not by itself establish unfair treatment, while a technology setting cannot resolve legal duties or conflicts.
What Is Hybrid Broker Routing?
Hybrid routing applies documented internalization and externalization rules to different orders, accounts, products, exposures or market conditions within one operating model.
- Use it to
- List every decision input, its authoritative source, evaluation time, fallback and change approval so outcomes can be reproduced.
- Check the boundary
- Opaque segmentation can create conduct, discrimination and disclosure risk when criteria affect customer outcomes without proper governance.
Should Routing Be Set by Account or by Order?
Account-based routing assigns a standing treatment, while order-based routing evaluates each instruction or current exposure against approved criteria and controls.
- Use it to
- Compare explainability, control, latency, exception handling and monitoring needs before choosing or combining the approaches.
- Check the boundary
- A static account category can become stale, and dynamic order rules can become unpredictable if inputs or precedence are unclear.
How to Govern Routing Conflicts of Interest
Routing conflict governance identifies financial incentives, principal exposure, rebates, markups, affiliate relationships and discretion that could influence customer order handling.
- Use it to
- Document the conflict, control owner, disclosure, monitoring measure, escalation threshold and evidence reviewed by independent oversight.
- Check the boundary
- Disclosure alone may not manage a conflict when incentives continue to shape routing or execution without effective controls.
How to Set Pre-Trade Routing Controls
Pre-trade routing controls validate account status, symbol, order type, size, price, margin, limits, market state and destination availability before release.
- Use it to
- Define ordered checks, rejection codes, timeout behavior, operator permissions and safe handling when a required input is unavailable.
- Check the boundary
- Silent fallback to a different destination or internal handling can produce an outcome the customer and control owners did not expect.
How to Choose Eligible Routing Destinations
Eligible routing destinations are approved counterparties or venues whose instruments, capacity, rules, credit, connectivity and operating status fit a defined order category.
- Use it to
- Maintain a versioned eligibility matrix and link each addition or suspension to due diligence, testing and authorized risk decisions.
- Check the boundary
- A live price feed does not establish executable access, sufficient credit or contractual permission to route orders.
How to Design Exposure-Based Hedge Triggers
An exposure-based hedge trigger initiates review or external action when measured position, concentration, loss or sensitivity crosses a governed threshold.
- Use it to
- Specify calculation inputs, netting logic, evaluation frequency, hysteresis, stale-data handling, authority and evidence for each trigger.
- Check the boundary
- Threshold automation cannot guarantee a hedge fill and may amplify risk when prices, positions or counterparty capacity are stale.
How to Govern Routing Rule Changes
Routing rule change control records the business reason, affected flows, risk assessment, testing, approvals, activation window and rollback for modified logic.
- Use it to
- Compare simulated and observed outcomes across normal, volatile, disconnected and limit-bound scenarios before production release.
- Check the boundary
- An apparently minor threshold or destination-priority change can materially alter exposure, conflicts and customer execution outcomes.
How to Handle Routing Timeouts and Rejects
Timeout and reject handling defines whether an order waits, retries, cancels, routes elsewhere or returns a controlled response after an external destination fails.
- Use it to
- Set time budgets, idempotency rules, state ownership, customer messages and reconciliation steps for every failure branch.
- Check the boundary
- Blind retries or ambiguous acknowledgements can create duplicate external orders while the client sees a failure.
How to Handle Partial Fills Across Destinations
Partial-fill handling tracks executed and remaining quantity, average price, destination state, cancellation rights and client reporting across one or more destinations.
- Use it to
- Test concurrent fills, late messages, cancel races and disconnect recovery with unique order and execution identifiers.
- Check the boundary
- Assuming an unacknowledged remainder is cancelled can leave open exposure or create a later overfill.
How to Separate Markups From Routing Decisions
Markup governance distinguishes the customer price construction from destination selection, hedge price, commissions and other charges applied to the transaction.
- Use it to
- Preserve raw source prices, transformation rules, effective settings and customer-facing prices so reviewers can reconstruct the result.
- Check the boundary
- A final spread alone cannot show whether price differences arose from markets, aggregation, markup, delay or data quality.
How to Monitor Hybrid Routing Outcomes
Hybrid routing monitoring compares intended and actual handling by rule, destination, account class, product, size, market condition and exception reason.
- Use it to
- Review fill rates, rejects, slippage, delay, price construction, exposure and override patterns with statistically appropriate context.
- Check the boundary
- Average results can hide materially different outcomes for specific cohorts, order types or stressed periods.
What Routing Evidence Should a Broker Retain?
Routing evidence should support reconstruction of the instruction, decision inputs, rule version, destination messages, executions, pricing, overrides and subsequent reconciliation.
- Use it to
- Set retention, integrity, access and retrieval requirements for application events, configuration histories, counterparty records and operator actions.
- Check the boundary
- Logs that record only the final state cannot explain competing messages, transient failures or the rule used at decision time.
How to Test A-Book and B-Book Routing Logic
Routing logic testing verifies approved treatment across account, order, exposure, destination and market-state combinations before the rules handle production activity.
- Use it to
- Use boundary values, contradictory inputs, unavailable data, delayed acknowledgements, manual overrides and restart scenarios with expected outcomes.
- Check the boundary
- Happy-path orders do not reveal unsafe fallbacks, race conditions or configuration precedence at routing boundaries.
How to Review Broker Routing Governance
A routing governance review evaluates policies, approvals, conflicts, rule changes, exceptions, destination quality, exposure outcomes, complaints and control effectiveness.
- Use it to
- Give an independent forum complete data and authority to require remediation, suspend a rule or demand additional analysis.
- Check the boundary
- A periodic report has limited value when reviewers cannot reproduce decisions or challenge the inputs and incentives behind them.
Does Routing Technology Prove Best Execution?
Routing technology can implement and record decisions, but it does not by itself prove that applicable execution duties were identified, monitored and satisfied.
- Use it to
- Have qualified advisers define the obligation, then connect policy, comparative data, review frequency, exceptions and remediation to system evidence.
- Check the boundary
- Claims of best execution require jurisdiction-specific analysis and should not be inferred from connectivity, speed or the number of destinations.
Primary and official references
These sources establish definitions, standards or official product behavior used across this guide. Follow the exact source and check its current version before a live implementation.