How to use this checklist

Ask each vendor to answer these questions in a demo, on your own data or a realistic sample — not in slides. Slides describe intended behaviour. A demo shows you what happens when a price is missing, a balance doesn’t match, or a share class needs its own NAV.

The questions are grouped in the order a hybrid fund usually feels the pain: first the book itself, then valuation, reconciliation, trading, connectivity, security and finally implementation and exit.

1. Book of record

2. Valuation and NAV

3. Reconciliation

4. Trading and compliance

5. Connectivity

6. Security and due diligence

7. Implementation and exit

Red flags

• The demo switches to a second screen, or a second login, for crypto.
• The crypto NAV comes from another system and is “combined” with the traditional NAV at month-end.
• Crypto balances are reconciled by exporting to a spreadsheet.
• The vendor can’t tell you which price source valued a given token yesterday.
• Security assurance is described as “in progress” with no date, or audit logs are described as immutable.
• Migration is offered only as a hard cutover, with no parallel run.

If the answer to “how do you produce one NAV?” involves combining two outputs, the fund is running two books.

Frequently asked questions

What is a hybrid fund in portfolio management terms?

A fund, or a group of funds run by one manager, that holds both traditional assets — such as equities, bonds, FX and derivatives — and digital assets such as spot crypto, stablecoins, perpetuals or staked positions.

Can a traditional PMS handle crypto?

Some add digital assets through a separate module or a third-party integration. The question to ask is whether crypto positions sit in the same book, valuation cycle and reconciliation workflow as everything else, or in a parallel system that has to be reconciled back.

What is the most important question to ask a PMS vendor as a hybrid fund?

Whether traditional and digital assets are valued and reconciled in the same daily cycle to produce one NAV per share class. If the answer involves combining two outputs, the fund is running two books.

Should vendors answer the checklist in a demo?

Yes. Ask them to demonstrate answers on your own data or a realistic sample. Slides describe intended behaviour; a demo shows how breaks, pricing sources and share-class NAV actually work.

The formula is the same. The inputs aren’t.

Net asset value is still assets minus liabilities, divided across share classes by units in issue. What changes in crypto is almost every input to that formula. There is no market close. The same token trades at different prices on different venues. Assets sit on exchanges, with custodians and in on-chain wallets at the same time. And some positions earn yield continuously.

The fund’s valuation policy defines how each of these is handled. The administrator and the auditor will test the NAV against that policy, so the goal isn’t a clever method. It’s a documented one, applied the same way every period.

This article describes common practice, not accounting or legal advice. Agree your valuation policy with your administrator and auditor.

1. Choose a valuation point

Crypto trades around the clock, so the fund has to choose the moment it values the portfolio: a specific time in a specific time zone, such as midnight UTC or 4pm London. That valuation point belongs in the offering documents and valuation policy, and it should be applied every period without exception.

Hybrid funds have an extra decision. If traditional assets are priced at their exchange closes and crypto at a different time, the NAV combines prices from different moments. On a volatile day that difference is material. Either align the crypto valuation point with traditional pricing, or document exactly how the two are combined.

2. Set a pricing-source hierarchy

Because venues disagree on price, the fund needs a rule for which price counts. Fair value standards (IFRS 13 and ASC 820) point to the price in the asset’s principal market — the market with the greatest volume and activity for that asset that the fund can access — or, where there is none, the most advantageous market.

In practice, the valuation policy records three things for each asset:

• A primary source — a named venue, or a reference rate or index.
• A fallback — what to use if the primary source is unavailable at the valuation point.
• A staleness rule — how old a price can be before it needs review.

Set the hierarchy per asset, not per fund. A large-cap token and a thinly traded one need different treatment.

3. Handle the awkward asset types

Stablecoins

Value them at their observable market price at the valuation point, not an assumed 1.00. The policy should say what happens if a stablecoin trades away from its peg.

Staked assets and rewards

Staked principal is valued like the underlying token, with any lock-up or unbonding period noted. Rewards need a clear policy on whether they are accrued as earned or recognised when received — practice varies, so agree it with the auditor up front.

DeFi positions

Liquidity-pool positions are usually valued through the underlying tokens the fund could claim at the valuation point. Lending positions carry principal plus accrued interest. Protocol risk is a separate question from valuation and belongs in the risk framework.

Derivatives

Perpetual futures are marked using a defined price — often the venue’s mark price, if that’s consistent with the policy — and funding payments must be booked as they accrue or settle. Options need either venue marks or a documented model.

Illiquid and delisted tokens

Don’t carry a last traded price indefinitely. Illiquid positions need a documented review, often by a valuation committee, with any adjustment recorded.

Airdrops and forks

The policy should say when newly received tokens are recognised, and how they’re valued before a reliable market price exists.

4. Prove the assets exist

Valuation assumes the fund knows exactly what it holds. For a crypto fund that means reconciling the internal book, at the valuation point, against every place assets sit: exchange balances (including sub-accounts) through their APIs, custodian statements, and wallet balances read directly on-chain. Breaks get resolved before the NAV is struck, not after.

This is where crypto funds most often fall short of institutional standard. Balances copied by hand into a spreadsheet may be right, but they leave no evidence trail for the administrator or auditor to follow.

5. Accrue fees and liabilities

Management fees, performance fees (with high-water marks, hurdles and crystallisation), trading fees, funding costs, borrowing costs and fund expenses all accrue as they would in a traditional fund. Crypto volatility makes performance-fee accruals swing more, and share classes with different fee terms or currencies each need their own calculation — which is why the NAV should be struck at share-class level, not only at fund level.

6. Strike, check, publish

For most funds, an independent administrator strikes the official NAV. The manager keeps its own book, strikes a shadow NAV on the same policy, and compares the two at share-class level before publication. Variances beyond tolerance are attributed to a cause — pricing source, timing, fee accrual — and resolved before investors see the number.

The goal isn’t a clever valuation method. It’s a documented one, applied the same way every day.

A checklist for your valuation policy

• Valuation point and time zone, and how it lines up with traditional pricing
• Pricing hierarchy per asset, with fallbacks and a staleness rule
• Treatment of stablecoins, staking rewards, DeFi positions, derivatives, airdrops and forks
• Procedure for illiquid or delisted tokens, and who approves adjustments
• Reconciliation sources — exchanges, custodians, wallets — and when they run
• Fee methodology per share class
• Tolerance for variances against the administrator’s NAV, and the escalation route

Frequently asked questions

What time do crypto funds calculate NAV?

There is no market close, so each fund sets its own valuation point in its valuation policy — commonly a fixed time such as midnight UTC, or a time aligned with the fund’s traditional pricing. What matters is that the time is documented and applied consistently every period.

Which price should a crypto fund use for NAV?

The price set by the fund’s documented pricing hierarchy. Fair value standards point to the asset’s principal market — the market with the greatest volume and activity that the fund can access — with defined fallbacks when that source is unavailable or stale.

Should stablecoins be valued at 1.00?

Not automatically. A stablecoin should be valued at its observable market price at the valuation point, with a documented approach for periods when it trades away from its peg.

How often should a crypto fund strike NAV?

The official NAV follows the fund’s dealing frequency, often monthly or weekly. Many managers also run a daily shadow NAV internally, because crypto prices and positions move continuously and problems are cheaper to fix the day they appear.

Who calculates the NAV of a crypto fund?

For most funds, an independent fund administrator strikes the official NAV. The manager typically keeps its own book and a shadow NAV to check the administrator’s figures before publication.

Why the acronyms get confusing

Vendors use the same terms for different things, and one system often plays several roles. The clearest example is “PMS” itself. At a large asset manager, a portfolio management system often means a front-office tool for modelling and rebalancing portfolios against a benchmark. At a hedge fund, it usually means the system that holds positions, cash, P&L and NAV — the book of record the whole firm works from. Both uses are correct. They describe different products.

The simplest way through the confusion is to follow a single trade from idea to investor report, and ask which system is responsible at each step.

Follow the trade

1. Decision. A portfolio manager decides to buy, after checking current exposure and P&L in the PMS.
2. Order. The order is raised in the OMS, checked against pre-trade compliance rules, and allocated across funds or share classes.
3. Execution. The order goes to a broker or venue — directly, or through an EMS if the trader needs algorithms and direct market access.
4. Capture. Fills come back. Positions, cash and tax lots update in the IBOR.
5. Reconciliation. The middle office matches the internal book against the custodian, prime broker and administrator.
6. Accounting and NAV. The ABOR — for most hedge funds, the fund administrator’s — books accruals and fees and strikes the official NAV.
7. Reporting. Investor, regulatory and performance reports draw on the books.

Each step can sit in a separate system, or several can sit in one platform. What matters operationally is the number of hand-offs between them, because every hand-off is an interface to maintain and a reconciliation to run.

What each system does

Portfolio management system (PMS)

The PMS is where the investment team sees the portfolio: positions valued in real time, exposure by strategy, sector and asset class, P&L and attribution, and what-if analysis. For hedge funds and most mid-sized managers, the PMS also holds the authoritative record of positions and cash, which makes it the IBOR as well.

Order management system (OMS)

The OMS manages the life of an order: capture, pre-trade compliance against regulatory, prospectus and internal limits, routing to brokers and venues (typically over FIX), allocation of block trades across funds, and an audit trail of who did what and when. Its users are portfolio managers, traders and compliance.

Execution management system (EMS)

The EMS is the trader’s tool for how an order is worked in the market: execution algorithms, direct market access, real-time market data and transaction cost analysis. Funds whose edge depends on execution need one. Many mid-sized funds trading listed instruments and digital assets work orders through broker algorithms and venue connections from the OMS instead.

Investment book of record (IBOR)

The IBOR is the up-to-date record of positions and cash that the investment team makes decisions from. It is kept on a trade-date basis, updates throughout the day, and includes activity that hasn’t settled yet. The question it answers is: what do we hold right now, and what can we act on?

Accounting book of record (ABOR)

The ABOR is the official accounting record: accruals, fees, corporate actions booked on an accounting basis, and period-end closes. It produces the NAV that investors subscribe and redeem at. For most hedge funds the ABOR is maintained by the fund administrator; at many traditional managers it sits with an internal or outsourced fund accounting team. The question it answers is: what is the fund officially worth at the valuation point?

The IBOR and ABOR describe the same fund, but for different purposes and on different timetables, so they rarely agree to the cent during the day. Explained differences are normal. Unexplained differences are breaks.

Side by side

Where the systems overlap

PMS and IBOR are commonly the same system at hedge funds and mid-sized managers. Splitting them makes sense mainly at large institutions that run a central data platform feeding several front-office tools.

PMS and OMS can be separate or integrated, and the difference shows up in daily operations. When they’re separate, fills cross an interface before positions update, and pre-trade compliance may check an order against positions that are already out of date. When they’re integrated, an executed order updates positions and exposure immediately, and every compliance check runs against the live book.

IBOR and ABOR are the pair that should stay independent. The value of having two books is that each checks the other. The manager reconciles its IBOR to the administrator’s ABOR, and increasingly runs a shadow NAV to verify the official figure before it’s published.

The cost of a fund’s systems isn’t the licences. It’s the number of hand-offs between them.

Which systems does your fund need?

• Emerging or single-strategy funds typically need a PMS with an integrated OMS acting as the IBOR, and an administrator holding the ABOR. A separate EMS is only worth it if execution style demands one.
• Multi-fund and multi-strategy managers need the same core, plus allocation across entities and NAV oversight at share-class level. At this size the number of interfaces becomes the main operational cost.
• Funds with a digital-asset sleeve need an IBOR that holds exchange, custody and on-chain positions alongside traditional ones. Otherwise the fund is running two books and reconciling them against each other. Our hybrid-fund PMS checklist covers what to ask.
• Large institutions with internal teams to own the interfaces can justify separate best-of-breed systems for each role.

Frequently asked questions

Is an IBOR the same as a PMS?

Often, but not always. At hedge funds and many mid-sized managers, the PMS holds the positions and cash the firm trades from, so it effectively is the IBOR. At large asset managers, the IBOR is sometimes a separate data platform that feeds several front-office tools, including a PMS used for modelling and rebalancing.

What is the difference between IBOR and ABOR?

The IBOR is the up-to-date investment view of positions and cash, used to make decisions during the day. The ABOR is the official accounting record, with accruals, fees and period-end closes, used to strike the NAV. They describe the same fund for different purposes, so they are reconciled rather than merged.

Does a hedge fund need a separate OMS?

It needs OMS functionality — order capture, pre-trade compliance, routing and allocation — but not necessarily a separate system. When the OMS is part of the same platform as the book of record, executed orders update positions and exposure immediately, and compliance checks run against live positions.

When does a fund need an EMS?

When execution itself is a source of edge: algorithmic or high-frequency strategies, heavy use of direct market access, or detailed transaction cost analysis. Most mid-sized funds trading listed instruments and digital assets work orders through brokers or venue connections from the OMS without a separate EMS.

Who owns the ABOR at a hedge fund?

Usually the fund administrator, which maintains the official accounting record and strikes the NAV. The manager keeps its own IBOR and, increasingly, a shadow NAV to check the administrator’s figures independently before publication.

What shadow NAV is — and isn’t

A shadow NAV is the manager’s own calculation of the fund’s net asset value, built from its own book and its own valuation, and compared against the administrator’s figure before that figure is published.

It isn’t a replacement for the administrator. The administrator’s NAV remains the official one, used for subscriptions and redemptions. Nor is it a copy of the administrator’s work. Its value comes from independence: a separate data path, separate pricing and separate fee calculations, so that an error in one calculation shows up as a difference against the other.

Why funds run one

The administrator’s NAV is built largely from data the fund and its counterparties supply. A mis-booked trade, a missed corporate action or a fee accrued on the wrong base passes straight into the official number unless something independent catches it.

Three pressures push managers to run that check themselves:

• Allocators ask. Operational due diligence questionnaires routinely ask who independently verifies the NAV. “We rely on the administrator” tends to open the topic rather than close it.
• Timing. The official NAV may be monthly or weekly. A daily shadow NAV gives the manager a verified view in between.
• Cost of late discovery. An error found on the day it happens is a quick fix. The same error found after publication can mean restating NAVs and correcting investor dealings.

How it works

1. Keep your own book. Positions and cash, reconciled daily against custodians, prime brokers and — for digital assets — exchanges and wallets.
2. Value it on your policy. The same valuation point and pricing hierarchy the fund’s valuation policy sets out.
3. Accrue fees and expenses per share class. Management and performance fees, with crystallisation handled per class.
4. Compare. Match the shadow NAV to the administrator’s NAV at fund and share-class level.
5. Apply a tolerance. Differences within tolerance are signed off. Differences outside it are investigated.
6. Attribute and resolve. Each variance is traced to a cause, resolved with the administrator, and recorded as evidence.

Setting tolerances

Tolerances are usually expressed in basis points of NAV and set per fund and share class. A simple, liquid strategy can hold a tighter threshold than one with hard-to-price instruments. Whatever the level, write down three things: the threshold, who reviews a breach, and whether publication waits until it’s resolved.

A worked example

Illustrative figures for a fictional fund. A share class has a NAV of €50 million. The administrator’s figure and the shadow NAV differ by 6 basis points — €30,000 — against a tolerance of 2 basis points. The difference is attributed before publication:

After the reprice and the fee alignment, 0.3 basis points remain — within tolerance, explained, and recorded. The NAV is published on numbers both sides can account for. Without the shadow calculation, the stale bond price would have gone into the official NAV unnoticed.

Detection is only half the job. A variance isn’t closed until it has a cause.

What it catches most often

The variances that recur are ordinary: pricing differences between sources or cut-offs, trade-date versus settlement-date timing, corporate actions, and fee or accrual errors. For digital assets, add venue price divergence and inconsistent valuation points — covered in how crypto funds strike NAV.

Four ways to operate it

• Rely on the administrator alone. Cheapest, but offers no independent check and tends to raise due diligence questions.
• In-house, on spreadsheets. Independent, but fragile: dependent on one or two people and weak on evidence.
• In-house, on a platform. The book of record is reconciled daily, the shadow NAV runs on a schedule, and every check leaves an audit-ready trail.
• Outsourced. A middle-office provider runs it on the manager’s behalf. Make sure the provider is independent of the administrator whose NAV it checks.

Frequently asked questions

Is shadow NAV a regulatory requirement?

Rarely as such. Requirements depend on the fund’s regime — frameworks such as AIFMD set expectations for proper and independent valuation — but shadow NAV is mostly driven by allocators and operational due diligence teams, who expect an independent check on the administrator’s figures. Confirm what applies to your funds with your compliance adviser.

How is shadow NAV different from the administrator’s NAV?

The administrator’s NAV is the official figure used for subscriptions and redemptions. The shadow NAV is the manager’s own independent calculation of the same figure, used to check the official NAV before it is published.

What tolerance should a shadow NAV use?

Tolerances are usually expressed in basis points of NAV and set per fund and share class, depending on how complex and liquid the strategy is. The threshold, and what happens when it is breached, should be written into the fund’s NAV oversight procedure.

Can the fund administrator run the shadow NAV?

It defeats the purpose. A shadow NAV is valuable because it is independent of the official calculation, so it should be run by the manager or by a separate provider, not by the administrator whose NAV it checks.

Does shadow NAV work for crypto funds?

Yes, with two extra points of care: crypto trades continuously, so the valuation point must be fixed and documented, and venue prices diverge, so the pricing source for each asset must be defined. Digital assets are then valued and reconciled in the same cycle as the rest of the book.

Where institutional crypto operations are different

For an institutional investor coming from traditional finance, the temptation is to treat crypto as just another asset class. It isn’t. In fact, the fundamental operational primitives — custody, settlement, valuation, reconciliation — behave differently. The infrastructure question isn’t “how do we add crypto to our existing setup” but “what would we build if we were designing from scratch for both asset classes?”

This guide walks through the five areas where the differences matter most, and what good institutional practice looks like in each.

1. Custody: the foundation question

For instance, in traditional finance, custody is mostly invisible. In fact, your prime broker or custodian holds the assets, you trust their controls, and operational risk lives in their systems. However, in crypto, custody is the whole game. The choices you make here determine your operational shape, your regulatory profile, and your insurance posture.

The institutional options:

• Qualified custodians (Coinbase Custody, Anchorage Digital, BitGo, Fireblocks). Regulated entities offering institutional-grade controls. Insurance available. The default choice for most regulated funds.
• MPC platforms (Fireblocks and similar). Multi-party computation for key management. Used both as standalone custody and as a layer over other arrangements.
• Self-custody with institutional controls. Direct on-chain holdings with hardware security modules, multi-sig wallets, and operational controls. Less common at institutional scale due to insurance and audit complexity.

The decision usually comes down to two factors: what your investor mandate requires (some LPs require qualified custodians), and what your reconciliation infrastructure can ingest. The custody platform’s API quality matters more than people initially expect — you’ll be pulling balances, transactions, and statement data continuously.

2. Multi-venue position management

A traditional fund holding equities might have positions across two or three execution venues. A crypto fund of comparable size routinely holds the same asset across five to ten venues — spot exchanges for liquidity, custodians for cold storage, DeFi protocols for yield, and staking infrastructure for proof-of-stake assets.

This creates a position-management problem that’s genuinely different from TradFi. Your BTC holdings might be split across Coinbase (active trading), Fireblocks (warm storage), Anchorage (cold storage), and a Lightning Network channel (operational liquidity). Knowing your “BTC position” means aggregating across all of these continuously.

3. Valuation: when the market never closes

Traditional NAV calculation has a clean primitive: the close. Markets close at a known time, prices are stamped, and NAV is calculated on those prices. Crypto markets don’t close. This creates two operational questions:

When do you strike NAV? The institutional convention is usually 4 PM ET or 5 PM London, mirroring TradFi cycles. But because crypto markets trade through these times, the “close” price is a snapshot, not a settled value. Some funds use VWAP across a window. Others use a single price point. Either is defensible; what matters is consistency and documentation.

Which venue’s prices? For BTC, you have dozens of price sources. The convention in institutional crypto is to use index providers (CME CF Reference Rates, CoinDesk Indices) that aggregate across multiple venues with rules-based methodology. This is what regulated products like spot Bitcoin ETFs reference, so it’s the lowest-friction choice for funds with TradFi audiences.

4. Compliance: an evolving regulatory landscape

Crypto compliance has more moving parts than TradFi compliance — and the parts are evolving faster. The institutional baseline:

• KYC/AML on all flows. Subscriptions, redemptions, and any movement of crypto in or out of fund custody needs to clear AML screening. Most institutional custodians provide this; some funds add additional layers (Chainalysis, Elliptic) for on-chain provenance checks.
• Travel Rule compliance. Where applicable, ensuring counterparty identity is exchanged for transfers above threshold. The implementation varies by jurisdiction.
• Sanctions screening. Both at counterparty onboarding and at the address level for on-chain transactions. OFAC and equivalents.
• Regulatory reporting aligned with fund structure (AIFMD, ERISA, etc.) — the requirements don’t pause because the underlying assets are crypto.
• Tax reporting with lot-level tracking. The wash-sale and tax-lot accounting rules for crypto are complex and jurisdiction-specific.

The operational discipline is the same as TradFi: every check must be evidenced, every decision must be logged, every audit trail must be exportable. The difference is volume — crypto operations generate more transactions per AUM dollar than most TradFi strategies.

5. DeFi positions: when the protocol is the counterparty

For funds with DeFi exposure, the operational model has another wrinkle: there’s no central counterparty. First, your position in Aave is an on-chain smart contract state. Second, your liquidity provision in Uniswap is two token balances with continuously-shifting composition. Third, your Lido staking position is a wrapped token representing claim on staked ETH plus accrued rewards.

When it comes to position tracking, this means parsing on-chain state continuously and translating it into accounting representations. Regarding valuation, it means using oracle prices that may differ from CEX prices. Finally for reconciliation, it means treating the blockchain itself as the source of truth — with custody-side records as confirmation, not contradiction.

Naturally, most institutional funds approach this conservatively: clear allocation limits to DeFi, hard-coded allowed protocols, and operational workflows that treat DeFi positions as higher-touch than spot crypto. The funds running DeFi at scale (yield strategies, market-making operations) have built more sophisticated infrastructure — usually with dedicated DeFi-specific tooling on top of their core PMS.

6. Investor reporting: the trust question

Crypto investors, particularly institutional ones, come into the asset class with a baseline of skepticism. In fact, your investor reporting has to do more work than equivalent TradFi reporting. The standard:

• On-chain proof of holdings. Many institutional crypto funds publish wallet addresses (or merkle proofs) so investors can verify holdings independently. This is a transparency standard TradFi doesn’t typically meet, and it’s now table stakes in crypto.
• Multi-source NAV evidence. Not just the NAV number, but the price sources, exchange rates, and timing windows that produced it. Investors want auditability.
• Detailed exposure breakdowns. By asset, by venue, by protocol category (CEX spot, custody, DeFi, staked). The level of detail that’s standard in crypto reporting would be unusual in a typical TradFi statement.
• Independent audits. Third-party verification of holdings, controls, and operational integrity. Becoming standard at institutional scale.

One NAV, one reconciliation, one investor letter. Adding our crypto strategy didn’t add an operations team.

— CFO, multi-strategy fund

7. The build-vs-buy question

Admittedly, most institutional funds approaching crypto operations face an early decision: build infrastructure internally, or buy from a specialized provider. Of course, both have legitimate cases:

Building makes sense when crypto is the strategic differentiator, when in-house expertise is deep, and when the fund has a long enough runway to absorb a multi-year build cycle. The funds doing this well usually started as crypto-native operations with engineering DNA.

Buying makes sense when crypto is one strategy of several, when ops is a cost center rather than a differentiator, and when the priority is operational reliability over architectural control. For most institutional funds adding a crypto allocation, this is the right call — provided the platform is dual-native rather than a TradFi system with a crypto module bolted on.

8. The path forward

Institutional crypto operations are still maturing. In reality, the infrastructure that’s production-ready today — qualified custody, institutional-grade exchanges, mature reporting tools — was experimental five years ago. Similarly, the infrastructure that’s emerging now — tokenized funds, on-chain settlement, programmatic compliance — will be production-ready in the next few years.

For institutional investors, the key principle is structural: the infrastructure you choose now should be flexible enough to absorb what’s coming. Treating crypto as “TradFi with extra steps” will create technical debt. Treating it as a first-class asset class in a dual-native platform — with the same valuation, reconciliation, and reporting discipline as your other holdings — will scale.

The big shifts everyone’s talking about

Read any industry publication and you’ll see the same headlines: T+1 settlement, tokenized assets, AI in operations, real-time risk, the death of the overnight batch. The risk for fund operations leaders is treating all of these as equally pressing — they aren’t. Some are real structural shifts that demand investment now. Others are interesting but don’t require immediate action. Knowing which is which is the actual work.

1. T+1 settlement is real — and your ops model probably wasn’t built for it

The shift to T+1 settlement in major US equity markets is the most concrete operational change of the past 18 months. It compressed the entire post-trade workflow by 24 hours. For most funds, this didn’t just mean “reconcile faster” — it exposed every dependency in the workflow that assumed there was a second day of buffer.

Funds that handled the transition well had three things in common: continuous (not batch) reconciliation, automated affirmation workflows with their brokers and custodians, and middle-office teams that were already running same-day cycles before the regulatory deadline. Funds that struggled were the ones running on overnight-batch infrastructure trying to fit the new cycle into the old shape.

2. Tokenization is happening — but not where most people are looking

Tokenized assets get a lot of headline attention. The reality on the ground is more nuanced. The first wave of tokenization isn’t in equities or crypto-native assets — it’s in money-market funds, treasury bills, and short-duration credit instruments. BlackRock’s BUIDL is the most visible example, but it’s not alone.

For most asset managers, this changes the integration question. A tokenized treasury fund needs the same operational treatment as a traditional money-market fund: NAV calculation, subscription/redemption processing, investor reporting. But the custody, settlement, and on-chain transparency layer is different. Funds that already have crypto-native infrastructure can absorb tokenized assets natively. Funds that don’t are going to face the bolt-on problem again.

3. Hybrid strategies are graduating from novelty to default

Two years ago, “hybrid fund” (TradFi + crypto) meant a long/short equity manager with a small crypto sleeve, run as an experiment. Today, hybrid is increasingly the default for new launches and a meaningful portion of existing books.

The operational pattern matters: the funds that have done this well have built (or selected) infrastructure that treats both asset classes as first-class. They have one consolidated NAV. One investor letter. One reconciliation team. The funds that bolted crypto onto legacy infrastructure are now paying the integration cost — and it’s usually visible in the operational team’s headcount growth.

The only PMS we found that handles crypto baskets, staking, and TradFi funds — all in one place.

— Fund COO, $1.7B AUM

4. AI in ops: mostly hype, with two real use cases

The genuine usefulness of AI in fund operations is narrower than the marketing suggests. Two areas where it’s actually working today:

• Break investigation. When a reconciliation break surfaces, the analyst’s first task is figuring out the cause. ML-assisted categorization (likely root cause: corporate action, FX mark, settlement timing) speeds this up materially. The analyst still makes the call — but starts with a shortlist instead of a blank slate.
• Document extraction. Pulling structured data out of custodian PDFs, trade confirmations, and corporate action notices used to require either manual entry or brittle OCR. LLM-assisted extraction handles this reasonably well now.

Where AI hasn’t delivered yet (despite vendor claims): autonomous trading decisions, “intelligent” risk models that beat well-built deterministic ones, and natural-language interfaces that replace dashboards. Operations leaders should be skeptical of any pitch that assumes AI fixes a process that’s structurally broken.

5. The middle-office outsourcing shift

One trend that’s less visible in the headlines but more impactful in practice: more funds are outsourcing middle-office operations to specialized providers rather than building in-house teams. The driver isn’t just cost — it’s access to expertise that’s hard to hire at fund-internal scale.

A specialist middle-office team that operates across multiple funds builds pattern recognition that no individual fund’s analyst pool can match. They’ve seen 30 corporate action scenarios you haven’t. They know which custodian-broker pairs have which historical settlement quirks. For funds where ops isn’t a strategic differentiator, this is increasingly compelling.

What doesn’t change

For all the headlines about disruption, three things remain constant in fund operations — and getting them right still matters more than any trend:

1. Reconciliation discipline. The fundamentals haven’t changed: match positions, cash, and NAV against independent sources. The technology improved; the principle didn’t.
2. Audit trail integrity. Regulators and investors will continue to ask “show me the evidence.” Every match, every break, every resolution needs to be logged with timestamp and attribution.
3. Investor trust. No amount of AI or tokenization replaces the trust built by transparent, timely, accurate reporting. The fund that consistently delivers operational clarity wins allocation conversations.

What this means for your 2026 planning

The trends that actually require structural change in the next 12 months are concentrated in two areas: compression of post-trade cycles (T+1, eventually T+0) and hybrid asset support (whether crypto, tokenized TradFi, or both). If your operational infrastructure handles these natively, the rest of the trends — AI assistance, outsourced middle office, real-time reporting — layer on top of solid foundations.

If your infrastructure was built before these shifts, the right question isn’t “which trend do we react to first” — it’s whether the underlying platform is the constraint. Sometimes the most expensive trend to chase is the one that’s just exposing a deeper structural problem.

The problem isn’t the technology. It’s the assumption.

Most funds running on a legacy portfolio management system don’t hate their PMS. They’ve learned to work around it. Analysts get hired to bridge the gaps. Spreadsheets get built to do what the system can’t. And the whole day gets scheduled around when the overnight batch finishes.

This is the quiet cost of legacy infrastructure: not that it doesn’t work, but that it shapes how you work. The system was designed for a different era of asset management — one where T+3 settlement was normal, where crypto didn’t exist, where investors received quarterly PDFs and that was enough. Funds running today on those same systems aren’t getting what they need; they’re getting what was acceptable in 2008.

The hidden cost isn’t the license fee. It’s the operating model the platform forces you into.

The four shapes legacy drag takes

When we talk to ops teams about migration, the same operational frustrations come up almost every time. They cluster into four patterns:

1. The manual reconciliation tax

To begin with, most legacy PMS platforms run a single nightly reconciliation cycle. Custodian feeds arrive overnight, the system runs its match, breaks surface in the morning, and analysts spend the first three hours of every day chasing them down in spreadsheets. As a result, multiply that across a team of five and you’re looking at 15 hours of analyst time per day — before any value-added work happens.

In practice, the fix isn’t faster spreadsheets. It’s continuous reconciliation: matching positions, cash, and NAV against multiple sources of truth throughout the day, with automated break detection and an SLA-driven workflow.

2. The T+1 NAV problem

By design, legacy systems batch their NAV calculation overnight. You close the books at 5 PM, the batch runs, and you see the position-level NAV at 7 AM the next day. In a world where markets move continuously and crypto trades 24/7, that’s a 14-hour blind spot. By the time you can act on what you saw at close, the market has moved twice.

Funds running real-time NAV systems don’t just “know sooner.” They restructure how they make decisions: position management becomes intraday, risk monitoring becomes proactive, and the morning meeting starts with “here’s where we are right now” instead of “here’s where we were last night.”

3. Investor reporting that lags the conversation

For years, quarterly PDFs were industry standard for a reason — they were what legacy systems could produce. But investor expectations have moved on. Allocators want on-demand transparency. Family offices want to see exposure today, not next quarter. LPs evaluating a fund expect to drill into performance attribution, not flip pages of a static report.

Today, the teams that win allocation conversations are the ones who can pull an exposure snapshot mid-meeting, show tax-lot detail on a position, and answer “what would your VaR look like if we added another $50M?” in real time. In short, legacy systems can’t do this. So the workaround bolts a separate BI tool onto the PMS via overnight exports — which means the data is always at least a day stale.

4. Crypto as a bolt-on

Perhaps the most expensive legacy decision a fund can make today is adding crypto through a third-party module. The architectural problem is simple: now you have two books, two NAV calculations, two reconciliation streams, and two reporting outputs to consolidate by hand. Consequently, the operational team spends a meaningful fraction of its week just keeping the two systems in sync.

By contrast, crypto-native platforms treat digital assets as first-class — in the same valuation engine, the same reconciliation flow, the same investor letter. The hybrid fund operating model becomes coherent: one book, one set of analytics, one team.

The migration isn’t the scary part

When funds first consider moving off a legacy system, the fear is usually the migration itself. What if positions don’t reconcile? What if the cutover fails? What if we lose a quarter of work to data quality issues?

Admittedly, these are legitimate concerns — but they’re also solvable. The modern migration pattern looks like this:

1. Discovery — full audit of data, workflows, and integrations on the legacy system. The output is a precise mapping of what gets moved, what gets deprecated, and what gets re-implemented.
2. Mirror — the new platform runs in parallel with legacy for 30–45 days. Same trades, same positions, same NAV. You validate every workflow against legacy output before anyone switches.
3. Cutover — once the team has confidence (and the data confirms it), the new platform becomes primary, and legacy goes into read-only mode as the historical archive.
4. Optimize — after cutover, you put the new platform’s capabilities to work. Workflows that legacy forced into manual steps become automated, and the team repurposes its time to higher-value work.

The risky migration is the one that tries to go straight from legacy to new without the mirror phase. Hence, the safe migration validates everything in parallel.

By the time we cut over, the team had been running on HedgeGuard for a month in parallel. The decision was risk-free.

— Catherine Berjal, CEO/CIO, CIAM 

The opportunity cost of staying

The argument for staying on legacy is usually one of risk: the system works (mostly), the team knows it, and migration is disruption. These are real considerations. But they’re usually weighed against an implicit assumption that doing nothing is free.

In fact, it isn’t. The legacy operating model carries an ongoing cost — one you pay in:

• Analyst time spent on reconciliation, manual reporting, and system workarounds — time that could be invested in process improvements, allocator relationships, or new strategy development.
• Lost allocation conversations where you couldn’t answer a real-time question, where the investor went with a more transparent operator instead.
• Limited strategy options — the new crypto sleeve you didn’t launch, the multi-asset structure you didn’t pursue, the new venue you didn’t connect because the legacy integration took six months.
• Compounding tech debt — every workaround you build today is a workaround the next ops hire has to learn.

What to look for in a replacement

If you’ve decided the legacy operating model isn’t serving you anymore, the choice of replacement matters as much as the decision to move. Therefore, here are a few things to evaluate:

• Firs, architecture is single, not bolted. Crypto and TradFi should be in the same engine, not parallel modules. Multi-asset means one valuation, one reconciliation, one P&L.
• Second, API-first matters. Adding a new venue, integrating a new BI tool, or feeding data to a custom dashboard should be a config change, not a custom development project.
• Third, pay-as-you-scale pricing. Upfront six-figure license deals don’t fit how modern funds operate. Pricing should scale with you.
• Forth, built by practitioners. The vendor’s leadership should include former portfolio managers, risk officers, and middle-office leads who’ve actually operated funds. Otherwise the product reflects what software people imagine fund operations to be — not what they actually are.
• Fifth, white-glove onboarding. The vendor should walk you through migration, not hand you a setup wizard. Six- to nine-figure decisions deserve human attention.

The bottom line

Notably, funds that have moved off legacy don’t describe it as “upgrading their PMS.” They describe it as changing how they operate. In practice, the morning meeting starts at a different point. Reconciliation stops dominating the team’s calendar. Subsequently, investor conversations get easier. Finally, new strategies become viable.

Ultimately, the legacy operating model is the cost — not the license fee. Thus, the longer you operate inside it, the more it shapes your fund.