Capital markets infrastructure providers build the technology and operational backbone serving institutional securities trading, post-trade processing, market data distribution, clearing, settlement, and market access. The customer base is institutional: banks, broker-dealers, asset managers, hedge funds, exchanges, and the broader wholesale financial services industry. The model differs from retail-facing WealthTech platforms serving end investors, from RegTech firms selling compliance automation, and from embedded finance providers serving non-financial software platforms. Capital markets infrastructure firms operate at the wholesale layer of finance, with deal sizes, sales cycles, and operational expectations specific to institutional buyers. The accounting and finance work centers on multi-element revenue under institutional contracts, market data licensing economics, customer concentration on Tier 1 financial institutions, and the audit-grade operational evidence sophisticated institutional buyers require. This page covers what makes capital markets infrastructure accounting distinct, and the services available to address it.

Executive Summary

• Capital markets infrastructure firms sell to institutional financial firms with high deal sizes (typically hundreds of thousands to millions per customer) and long sales cycles measured in quarters rather than weeks.
• Multi-element pricing combining software subscriptions, per-transaction fees, market data licensing, professional services, and connectivity fees creates revenue recognition complexity under ASC 606.
• Market data licensing from exchanges, Bloomberg, Refinitiv, and other data sources carries pass-through and markup considerations that affect both gross-versus-net revenue presentation and contract economics.
• Customer concentration on Tier 1 banks and asset managers is structurally common, with the top handful of customers representing a meaningful portion of revenue for most platforms.
• Tokenized securities platforms operating at the intersection of capital markets and blockchain create additional accounting considerations spanning both traditional securities frameworks and digital asset infrastructure.

What Capital Markets Infrastructure Looks Like as a Business

Capital markets infrastructure providers operate the technology layer underneath institutional securities markets. The category includes:

• Electronic trading venues and ATS operators running matching engines, RFQ platforms, and electronic markets across asset classes
• Order management and execution management systems (OMS/EMS) used by buy-side and sell-side institutions for trade workflow
• Post-trade processing platforms handling allocation, affirmation, confirmation, and settlement workflow
• Market data and reference data providers distributing real-time and historical data, corporate actions, and security identifiers
• Clearing technology vendors providing reconciliation, netting, and clearing infrastructure
• Securities lending technology platforms automating securities finance workflows
• Institutional brokerage infrastructure providers powering broker-dealer back offices and clearing operations
• Tokenized securities platforms issuing and managing security tokens, tokenized treasuries, or tokenized funds on blockchain rails
• Trade reporting and regulatory connectivity providers handling FINRA TRF, CAT, MiFID II, and other regulatory reporting infrastructure

What distinguishes capital markets infrastructure from other fintech is the institutional customer base and the wholesale market positioning. Customers are sophisticated financial institutions with their own internal technology teams, security review processes, vendor risk management programs, and procurement bureaucracy. Sales cycles run twelve to twenty-four months for sophisticated institutional integrations. Annual contracts with multi-year commitments are common. Switching costs are substantial once infrastructure is operationally embedded. Revenue mechanics typically combine recurring software subscriptions, per-transaction or volume-based fees, market data licensing, professional services for implementation, and connectivity fees. The unit economics reflect this reality: high CAC, very high LTV, long payback periods, and deal sizes that make each customer relationship strategically important.

What Makes Capital Markets Infrastructure Accounting Distinct

Institutional B2B SaaS unit economics

The unit economics of selling to Tier 1 banks, asset managers, and hedge funds differ from typical B2B SaaS. CAC is elevated by twelve-to-twenty-four-month sales cycles, security review requirements, vendor risk management processes, and the cost of enterprise sales coverage. ACV (annual contract value) is correspondingly high, often in the hundreds of thousands to low millions per institutional customer. LTV is substantial because once embedded, capital markets infrastructure rarely gets ripped out. Net revenue retention runs strong on retained customers due to expansion through new modules, additional users, additional venues, or additional asset classes. Payback periods extend further than typical SaaS but the long-term economics support the model. The accounting captures each metric with adjustments reflecting actual capital markets economics rather than generic SaaS benchmarks.

Multi-element revenue under ASC 606

Institutional capital markets contracts typically combine multiple components: software subscription, per-transaction or volume-based fees, market data licensing, connectivity fees, professional services for implementation, and ongoing managed services. Each component has different revenue recognition mechanics under ASC 606. Subscriptions recognize over the contract period. Per-transaction fees recognize as activity occurs. Implementation services may be one-time or amortized depending on whether they have standalone value. Market data licensing has its own pass-through versus markup analysis. Bundled contracts require explicit allocation across performance obligations using standalone selling prices. The technical accounting work documents allocations in memos that support both internal financial reporting and external audit response.

Market data licensing and pass-through economics

Capital markets infrastructure providers frequently bundle or pass through market data from exchanges, Bloomberg, Refinitiv, FactSet, and other primary data sources. The market data licensing economics depend on whether the platform is acting as principal (purchasing data and reselling at marked-up rates) or agent (facilitating customer access to data they license directly). Principal-versus-agent analysis under ASC 606 drives gross-versus-net revenue presentation. Exchange data fees, redistribution licenses, and entitlement frameworks add operational complexity to billing and compliance. Audit attention to market data accounting has tightened as platforms scale and the licensing economics become more material to reported revenue.

Tier 1 customer concentration risk

Capital markets infrastructure customer bases often concentrate on a small number of large financial institutions where each customer represents disproportionate revenue. The top handful of customers (money-center banks, large asset managers, major exchanges) may collectively account for the majority of revenue. Loss of one major customer can materially affect financial performance. The accounting tracks revenue concentration with disclosure flagging customers above defined thresholds. Concentration risk affects valuation discussions and acquisition diligence, with concentrated revenue typically receiving valuation discounts. Diversification strategy across customer tiers, geographic markets, and asset class verticals becomes part of strategic financial planning.

Long sales cycle and bookings-revenue gap

Institutional capital markets sales typically take twelve to twenty-four months from initial contact through contract signing. After signing, implementation runs another three to nine months for sophisticated integrations. The gap between bookings and revenue affects financial reporting, fundraising narratives, and operational cash planning. Bookings reporting becomes important because it provides the leading indicator that subscription revenue won’t show for quarters. Investor reporting typically includes annual contract value (ACV), total contract value (TCV), and remaining performance obligations (RPO) alongside revenue. The relationship between sales activity and recognized revenue requires explicit modeling for forecasting accuracy.

Implementation revenue and milestone-based recognition

Institutional capital markets implementations involve substantial professional services: integration with customer systems, custom configuration, security review response, parallel testing, and production cutover. Implementation work often runs in defined phases with milestone-based revenue recognition. The accounting captures implementation work separately from ongoing subscription revenue, with appropriate ASC 606 treatment for whether implementation has standalone value or is amortized over the subscription period. Cost of implementation work flows through cost of services rather than R&D. Implementation profitability analysis (revenue versus the staff cost of delivering the implementation) determines whether the work supports overall product economics or operates at a loss for strategic customer acquisition.

Tokenized securities platform accounting

Tokenized securities platforms operate at the intersection of traditional capital markets and blockchain infrastructure. Security tokens, tokenized treasuries, tokenized money market funds, and tokenized private fund interests all fall under existing securities frameworks (Securities Act, Investment Company Act, Investment Advisers Act) while being issued and traded on blockchain rails. The accounting captures both traditional securities reporting requirements and the on-chain mechanics that handle issuance, transfer, and redemption. Issuer service fees, transfer agent functions, and platform fees all need explicit revenue recognition. Custody arrangements for tokenized securities require both qualified custodian relationships (under traditional rules) and smart contract or wallet infrastructure (for the on-chain side). The intersection creates audit-grade documentation requirements that span both regulatory frameworks.

R&D capitalization for trading systems

Trading systems, post-trade platforms, and market infrastructure software involve substantial development cost. ASC 350-40 governs internal-use software capitalization, with specific rules about development phase costs versus preliminary project and post-implementation phases. Capital markets infrastructure complicates this because products evolve continuously to handle new asset classes, new venues, regulatory updates, and customer-driven feature requests. The line between major new functionality (potentially capitalizable) and ongoing maintenance (expensed) requires explicit policy and project-level monitoring. Inadequate documentation has been a recurring audit finding in technology platforms with continuous product evolution. Regular reassessment of project status and capitalization criteria becomes part of routine accounting work.

Operational evidence for institutional buyers

Institutional capital markets buyers require extensive operational evidence before integrating with vendors. SOC 1 (specifically SOC 1 Type II for financial reporting controls), SOC 2 Type II, ISO 27001, and asset class-specific certifications represent baseline expectations. Annual penetration testing, ongoing security monitoring, and detailed vendor questionnaires add operational obligations. SOX compliance readiness becomes relevant as platforms approach public-company status or when major customers’ financial reporting requires the platform’s controls to support the customer’s own SOX obligations. The accounting captures certification costs, ongoing compliance infrastructure, and operational evidence required to support the institutional procurement process. Certifications gate access to enterprise budgets and become competitive assets.

Services for Capital Markets Infrastructure Providers

Fractional CFO leadership

Senior finance leadership for capital markets infrastructure operations. Institutional sales pricing strategy, customer concentration management, multi-element contract structuring, market data licensing economics, capital planning, fundraising support, M&A diligence response, and the institutional readiness work that scaled capital markets infrastructure firms need. For our general fractional CFO services, see the fractional CFO services page.

Accounting and bookkeeping

Day-to-day accounting work for capital markets infrastructure operations. Multi-element ASC 606 revenue recognition across subscriptions, transaction fees, market data, connectivity, and services. Market data licensing pass-through tracking. Implementation revenue with milestone-based recognition. Customer concentration reporting. R&D capitalization under ASC 350-40. Deferred revenue and remaining performance obligations reporting. Consolidated financial reporting that supports both internal management and the institutional diligence requirements that come with strategic transactions. See startup accounting services for broader scope.

Consulting and advisory

Project-based engagements for specific capital markets infrastructure challenges. ASC 606 multi-element revenue analysis for institutional contracts. Market data principal-versus-agent analysis. R&D capitalization policy design and project-level monitoring framework. Customer concentration risk analysis and revenue diversification strategy. Tokenized securities platform accounting framework. SOC 1 Type II and SOC 2 Type II readiness preparation. Internal controls framework design for institutional customer requirements. SOX compliance readiness. BSA/AML compliance program design where applicable. Audit readiness for capital markets infrastructure firms preparing for first audit, IPO, or M&A diligence. See accounting consulting services for additional detail.

Frequently Asked Questions

How is capital markets infrastructure different from RegTech or embedded finance?

Capital markets infrastructure serves institutional financial firms (banks, broker-dealers, asset managers, hedge funds, exchanges) with trading, post-trade, market data, and clearing technology. RegTech serves regulated businesses with compliance and risk automation. Embedded finance serves non-financial software platforms wanting to add financial product features through APIs. The customer profile, sales motion, and product domain differ substantially across the three categories.

How is multi-element institutional revenue recognized?

Through explicit allocation across performance obligations under ASC 606 using standalone selling prices. Subscriptions recognize over the contract period. Per-transaction fees recognize as activity occurs. Implementation services may be one-time or amortized depending on whether they have standalone value. Market data licensing has its own pass-through versus markup analysis. Bundled contracts that combine multiple components require explicit allocation. The technical accounting work documents allocations in memos that support both financial reporting and audit response.

How is market data licensing accounted for?

The accounting depends on whether the platform is acting as principal (purchasing data and reselling at marked-up rates) or agent (facilitating customer access to data they license directly). Principal-versus-agent analysis under ASC 606 drives gross-versus-net revenue presentation. Exchange data fees, redistribution licenses, and entitlement frameworks add operational complexity to billing and compliance. Audit attention to market data accounting has tightened as platforms scale.

Why is Tier 1 customer concentration a structural challenge?

Capital markets infrastructure customer bases often concentrate on a small number of large financial institutions where each customer represents disproportionate revenue. The top handful of customers may collectively account for the majority of revenue. Loss of one major customer can materially affect performance. The accounting tracks revenue concentration with disclosure flagging customers above defined thresholds. Concentrated revenue typically receives valuation discounts during fundraising and acquisition diligence.

How are tokenized securities platforms accounted for?

Tokenized securities platforms fall under traditional securities frameworks (Securities Act, Investment Company Act, Investment Advisers Act) while operating on blockchain rails. The accounting captures both traditional securities reporting requirements and on-chain mechanics that handle issuance, transfer, and redemption. Custody arrangements require both qualified custodian relationships (traditional rules) and smart contract or wallet infrastructure (on-chain side). Audit-grade documentation spans both regulatory frameworks.

How does R&D capitalization work for trading systems?

ASC 350-40 governs internal-use software capitalization with specific rules about development phase costs versus preliminary project and post-implementation phases. Capital markets infrastructure complicates this because products evolve continuously to handle new asset classes, new venues, regulatory updates, and customer-driven features. The accounting requires explicit capitalization policy, project-level monitoring, and regular reassessment as projects move between phases.

What certifications do institutional buyers expect?

SOC 1 Type II (for financial reporting controls), SOC 2 Type II (security, availability, processing integrity, confidentiality, privacy), ISO 27001, and asset class-specific certifications are baseline expectations. Annual penetration testing, ongoing security monitoring, and detailed vendor questionnaires add operational obligations. SOX compliance readiness becomes relevant as platforms approach public-company status or when major customers’ financial reporting requires the platform’s controls to support customer SOX obligations.

Reviewed by YR, CPA
Senior Financial Advisor