TSG SERVERBroker technology

Home / A-Book vs B-Book: compare operating responsibilities.

OPERATING MODEL COMPARISON

A-Book vs B-Book: compare operating responsibilities.

A brokerage’s execution and risk policy determines which events must be routed, monitored and reconciled. This comparison focuses on the systems and operating evidence needed after that policy has been chosen.

Separate a business policy from its implementation

Labels such as A-Book, B-Book and hybrid do not describe a complete technology specification. Record what happens for each relevant account, instrument and order condition: which system makes a routing decision, who can change it and where the decision is logged.

A technology review does not select a risk model or establish the permissions required to operate it. Those responsibilities remain with the brokerage and its advisers. The implementation brief translates approved workflows into observable system behaviour.

Compare the evidence each workflow needs

Review areas by operating workflow
AreaExternal-routing workflowInternal-dealing workflow
Order lifecycleTrace acknowledgements, fills and rejections across counterpartiesTrace accepted instructions and internal state changes
PricingCheck the pricing source and execution-side dependencies separatelyCheck the approved pricing rules and their change history
Operator controlsDefine counterparty interruption and reconciliation proceduresDefine permissions, intervention records and escalation
Mixed workflowRecord routing selection and fallback conditionsReconcile internal and external records without losing the decision trail

The table identifies review topics rather than asserting that every platform or provider exposes the same controls. Verify each required function in the proposed environment.

Use scenario testing rather than a label

Illustrative test: two approved account groups follow different execution paths. A reviewer submits representative test instructions and checks whether the resulting records show the intended path and consistent final states. The test also covers a denied configuration change and an unavailable dependency.

The useful output is a responsibility matrix, sample event traces and a list of unresolved limitations. A sales description saying “hybrid supported” is insufficient without that evidence. If existing workflows must be preserved, collect the current configuration and the rights available to inspect or modify it before planning a transition.

YOUR NEXT STEP

Bring your requirements.
Leave with a clearer project scope.

Tell us your platform, current setup and the workflow you want to review.

WhatsApp Telegram