Key takeaways
- Liquidity provider due diligence should cover commercial terms, credit, margin, execution rules, reporting, and support, not only spreads.
- Test the operating model before first client flow: symbols, trading hours, rejects, margin calls, rollovers, and reconciliation.
- Start live routing in phases, with clear exposure limits, monitoring, and fallback procedures.
Liquidity provider due diligence before you sign
Liquidity provider due diligence is the work a broker does before committing client flow, credit, and operational dependency to an LP. It is not paperwork. Weak onboarding can lead to disputed fills, wrong symbols, margin surprises, reconciliation breaks, and pressure on the dealing desk.
Start with the job the LP must do. You may need deeper top of book pricing, wider product coverage, a specific account structure, or a backup venue. A prop firm may care more about stable pricing, predictable rejects, and clean reporting than broad product range.
Do not judge an LP by a demo spread snapshot. Review the full commercial and operating model: commissions, financing, markups if any, margin rates, negative balance treatment, last look or rejection rules where applicable, trade reporting, and dispute procedures. If terms depend on volume, account type, jurisdiction, or flow profile, document those conditions before signing.
Confirm who you contract with, who supports you, and who can make decisions during incidents. Sales responsiveness matters, but the real test is how the LP handles volatile markets, tight credit, and disputed trades.
Define the flow and account model
Map how client flow will reach the LP. A simple A-book broker has different needs from a broker using hybrid execution, multiple books, or separate brands. The LP should understand your products, order types, average trade size, peak load, regional trading patterns, and whether flow may include high-frequency, news, arbitrage-sensitive, or prop challenge activity.
Be precise about account structure. You may use one omnibus account, separate accounts by brand, segregated accounts by product, or different accounts for coverage and testing. Each choice affects reporting, exposure, margin usage, and reconciliation.
Decide the LP role in your routing logic. It may be primary, backup, product-specific, or one source in an aggregated book. Your bridge and platform must support that role. Review LP and platform connectivity early, before legal approval runs ahead of technical setup.
For each flow type, define operating rules:
- Maximum exposure before routing pauses
- Whether partial fills are acceptable
- How rejected orders are handled
- Which products can route automatically
- Which products need manual approval or lower limits
- How weekend, holiday, and session-close trading should behave
These rules give dealing, risk, and operations a shared standard before volume starts.
Test credit, margin, reporting, and controls
Credit and margin terms need the same attention as execution. Good pricing is not enough if the margin model does not fit your client base or house risk limits. Ask how margin is calculated across asset classes, how financing is charged, how open positions are valued, and when margin calls or liquidation events may occur.
Model stress cases, not only normal trading days. Test large exposure in one symbol, fast gaps, wider spreads, suspended products, off-market ticks, and one-way flow after a news release. The point is to know what happens next, who decides, and what controls apply.
Write operational controls into the onboarding plan:
- Who can enable or disable the LP connection
- Who can change routing weights or symbol permissions
- Who receives margin, reject, and connection alerts
- How trade breaks are investigated
- How end-of-day reports are reconciled
- Who can escalate a dispute
Reporting is often where problems appear. LP reports should include the fields operations and finance need: execution time, symbol, side, size, price, commission, swaps or financing, account, order reference, and trade status. If bridge, platform, and LP reports cannot be reconciled cleanly, small issues will accumulate.
Validate symbols, trading hours, and lifecycle rules
Symbol setup is a common source of avoidable onboarding errors. Similar names do not mean the same contract size, tick size, precision, session time, swap rule, or margin treatment. One wrong multiplier can create a material P&L issue.
Create a symbol checklist before production routing. For each instrument, confirm:
- Contract size and lot step
- Minimum and maximum trade size
- Tick size and decimal precision
- Trading sessions and breaks
- Holiday handling
- Swap or financing timing
- Margin group
- Close-only conditions
- Whether the symbol can be disabled independently
This matters for indices, metals, crypto CFDs, and custom symbol names on MT4 or MT5. The LP product may be valid while your platform symbol is still wrong. Use a controlled symbol mapping process and test every product you plan to enable.
Lifecycle rules also need review. Ask how expiries, corporate actions if relevant, contract changes, trading halts, and abnormal market conditions are handled. If a symbol is suspended, know whether prices stop, orders reject, positions become close-only, or manual intervention is required. Client-facing product rules should match what your infrastructure can support.
Run a controlled go-live plan
Do not move from paperwork to full production in one step. Use phased go-live with volume limits, symbol limits, and named owners. The first live phase should prove that orders, fills, rejects, swaps, commissions, and reports behave as expected under real conditions.
Start with a small set of liquid, well-understood instruments. Route limited flow, compare platform and LP reports, and review fills daily. Watch reject reasons, execution timestamps, margin utilisation, feed stability, and differences between expected and actual commissions or financing.
Monitoring must be active from day one. Your team should see connection state, price freshness, execution rejects, abnormal spreads, and account exposure before clients report problems. If you need structured alerting across LP and feed health, see monitoring and alerts.
Prepare fallback actions before launch. These may include switching routing to another LP, setting symbols to close-only, reducing maximum trade size, pausing new exposure, or moving flow to a house book temporarily if your risk policy allows it. The right action depends on your licence, client terms, risk limits, and platform setup.
After the first phase, hold a review with dealing, risk, operations, finance, and technical staff. Confirm what worked, what failed, and what must change before increasing volume. If you use a liquidity bridge, XiroLink can support LP aggregation, markups, Centroid compatible FIX, market data, and monitoring, but the broker still owns the due diligence process.
The best LP relationship is not simply the tightest indicative spread. It is the one your team can operate, monitor, reconcile, and control under real market conditions.
Frequently asked questions
What should a broker check before signing with a liquidity provider?
Check the legal entity, products offered, credit terms, margin rules, execution model, reporting, support process, and operational controls. Also confirm that the LP can support your symbols, trading hours, account structure, and expected flow profile.
How long should LP onboarding testing run?
It depends on the broker, provider, and product set. A sensible process includes connection testing, symbol validation, order testing, reject handling, reporting reconciliation, and a controlled live phase with limited volume.
Should a broker connect to more than one liquidity provider?
Many brokers use more than one LP to reduce dependency and improve routing flexibility. The decision depends on volume, credit availability, client flow, product coverage, and operational capacity.