How to Choose a Capital Markets Platform: A Buyer's Checklist

Short answer: choose a capital markets platform by first asking whether trading, risk, settlement, custody and the general ledger run on one record or on separate systems joined by interfaces. Then test every vendor against the same checklist: asset classes and markets, front office, back office, custody, risk, connectivity, regulation, deployment, security, AI, implementation and total cost. The right platform covers your whole operation today and the markets and products you plan to add next.

Brokers, banks, custodians and asset managers rarely replace their core platform, so the decision tends to outlive the people who make it. A wrong choice shows up years later as reconciliation teams, delayed product launches and integration projects that never end. This guide sets out what to check, what to ask and what to watch for, so that every vendor on your shortlist is measured against the same standard.

Why the Choice Matters: One Record or Stitched Systems

Most institutions grew their technology one need at a time: an order management system from one supplier, a back office from another, a general ledger from a third, and spreadsheets in between. Each system may be good at its own job, but every hand-off between them creates a file to send, a break to investigate and a delay before the numbers agree.

A front-to-back platform works differently. When a trade is filled, the same step updates positions, cash, fees, the ledger and custody. Operations, finance, risk and compliance all read from one record, so there is no end-of-day batch to wait for and nothing to reconcile between internal books. The practical difference is felt every day: fewer breaks, faster month-end, cleaner audits and new products that can launch without a new integration project.

Not every firm needs every module on day one. What matters is that the platform can grow into the whole operation without changing the underlying record.

The Buyer's Checklist, Area by Area

1. Asset Classes and Markets

• Which asset classes trade in one workflow: equities, fixed income, funds, FX, derivatives, digital assets?
• Which of your home exchanges are connected today, and how are new markets added?
• Are Islamic finance, securities lending and repo handled on the same platform, if you need them?

2. Front Office

• Do web, mobile, dealer terminal, FIX and API orders share one order book and one set of risk checks?
• Can you run your own book (internalise) as well as route to the market, per client or instrument?
• Are algorithms, baskets and advanced order types available without a separate execution system?
• Can client-facing screens run fully under your own brand?

3. Back Office and Finance

• Do trades, fees, commissions and VAT post to the general ledger as they happen, or overnight?
• Are statutory reports such as the trial balance and balance sheet produced from the same ledger?
• Are fees and commissions configured as rules, or calculated by hand and corrected later?

4. Custody and Settlement

• Are DVP, RVP and free-of-payment settlement supported, with cycles set per market?
• Are settlement instructions generated and sent over SWIFT automatically, with statuses tracked?
• Is reconciliation against custodians, depositories and client money run daily, with breaks flagged?
• Are corporate actions processed against the positions the trades created, with a second user approving?

5. Risk and Margin

• Are buying power, limits and restricted lists checked before an order leaves, or reported afterwards?
• Is margin recalculated as prices move, with automatic margin calls and a defined liquidation method?
• Is there a single control to stop order flow across the desk when needed?

6. Connectivity, FIX and Market Data

• Is FIX supported in every direction: routing out, client orders in, and drop copy?
• How many brokers, banks and venues can you reach, and is adding one configuration or a project?
• Is market data normalised into one feed, with entitlements per user, market and instrument?

7. Regulation and Reporting

• Which regulatory reports are produced from the book of record, without a separate extract?
• Are client statements available in the languages your clients read?
• How long is the audit trail kept, and can auditors get what they need without a ticket to the vendor?

8. Deployment and Hosting

• Can the platform run as cloud SaaS, on-premise or hybrid, to meet data-residency rules in your market?
• Is a fully managed service available, hosted close to your exchanges?
• Is every function available over API, so you can integrate it with your own systems?

9. Security

• Is the vendor certified to a recognised information-security standard such as ISO 27001?
• Are role-based access, multi-factor authentication, encryption and maker-checker approval built in?
• Is every operational action timestamped and attributable to a named user?

10. AI

• Does the AI assistant work inside the platform, on your live data, within each user's permissions?
• Does a person approve every action the AI prepares, and is every action audited?
• Can your administrators switch it on or off and decide who uses it?

11. Implementation and Support

• Can you go live in phases, starting with core trading and back office, then adding markets and products?
• Is training included, and is support available around the clock once you are live?
• Can you add your own rules at defined extension points without forking the core platform?

12. Total Cost

• What does the platform cost over its full life, including integrations, reconciliation staff and upgrades?
• Is pricing by module, users and deployment model, so you pay for what you use?
• How many other systems, interfaces and vendor contracts would this platform replace?

Questions to Ask Every Vendor

Brochures tend to look alike. These questions separate a platform that runs the operation from one that describes it:

• Show me one trade end to end: from order entry to settlement, ledger posting and the client statement, live, on one system.
• Who runs on it today? Which institutions of our type, in our region, use the platform in production, and can we speak to one?
• How do you connect to our markets? Which exchanges, depositories and custodians do you connect to directly today?
• What happens when a regulation changes? How are new reports and rule changes delivered, and who maintains them?
• How is an upgrade done? Do our configurations and extensions carry over without rework?
• Where is our data, and who can see it? Where is the platform hosted, and how is access controlled and logged?
• What does a phased go-live look like for us? Which modules first, which later, and what runs in parallel during cutover?

Red Flags

• "Integrated" means nightly files: if positions and the ledger agree only after an overnight batch, you are buying stitched systems under one name.
• Every asset class is a separate module with its own book: each new product then becomes a new reconciliation.
• Risk checks run after the trade: post-trade reports do not stop a breach.
• Each new broker or venue is a custom project: connectivity should be configuration, not development.
• No reference clients in your markets: local settlement, depository and regulatory rules are where generic platforms struggle.
• Customisation means a private copy of the code: forks make every future upgrade a project.
• AI that acts without a person approving: in a regulated business, every action needs an accountable human and an audit trail.

How ZagTrader Answers the Checklist

ZagTrader is a front-to-back capital markets platform in production since 2009. More than 100 institutions run on ZagTrader technology, with $500B+ in client assets, 10M+ daily transactions and 25+ markets and exchanges. In brief:

• One record: each fill updates positions, cash, fees, the general ledger and custody in the same step, from Trading & Execution through Custody & Back Office.
• Multi-asset: equities, fixed income, FX, listed and OTC derivatives, funds and digital assets trade through the same engine, with margin financing, securities lending, repo and Islamic finance on the same platform.
• Risk before the order leaves: user, broker, instrument and market checks at order entry, live margin with automatic calls, concentration limits and a kill switch, described in Risk & Compliance.
• Settlement and SWIFT: DVP, RVP and FOP on per-market cycles, SWIFT MT54x instructions, and daily custodian and client-money reconciliation, on the Settlement page.
• Connectivity: FIX routing out, DMA in and drop copy, with 1,100+ destinations through ZagFN, ZagTrader's managed network.
• Reporting: regulatory filings, FATCA/CRS, bilingual client statements and statutory financials from one book of record, with a searchable audit trail, on Reporting & RegTech.
• Deployment: cloud SaaS, on-premise or hybrid, API-first over REST, WebSocket and FIX, under your own brand, on Integration & Hosting.
• Security and AI: ISO 27001 certified, and an AI assistant for staff and clients that answers within each user's permissions, where a person approves every action.

Implementation is phased, typically core trading and back office first, then more markets, products and channels, with training and around-the-clock support included.

Related products: see Trading & Execution, Custody & Back Office, Finance & Accounting and FIX & Market Connectivity. For your type of institution, see ZagTrader for Brokers, ZagTrader for Custodians and ZagTrader for Asset Managers.