[SPONSORED CONTENT]
Across the asset management industry, a familiar pattern plays out. Firms invest heavily in technology, only to find themselves managing fragmented, high-maintenance systems that resist change and don’t scale. The problem rarely comes down to the technology itself. It comes down to a flawed framework for deciding what to build, what to buy, and what to outsource in the first place.
Nowhere is this more consequential than in investment accounting.
The Strategic Mistake Hiding in Plain Sight
Even historically sophisticated firms that built proprietary platforms are reconsidering those decisions. As the engineers who created legacy systems retire and the true cost of ownership becomes impossible to ignore, firms are revisiting assumptions they once treated as untouchable.
The underlying logic is straightforward. Successful firms reserve “build” for capabilities that genuinely differentiate them in the market. Investment accounting is not one of those capabilities.
Alpha comes from investment strategy, client relationships, and operational efficiency. The accounting calculations, reconciliation logic, and NAV processes your firm needs are fundamentally the same as every other firm in your market. Treating that infrastructure as strategic IP means pouring engineering resources into systems that generate no competitive advantage while accumulating technical debt year over year.
The True Cost of Building
Building a data platform typically requires multi-year commitments and dedicated engineering teams. That’s before ongoing support, change management, and integration work, which frequently exceeds the original implementation cost.
For investment accounting specifically, this plays out in predictable ways: constant catch-up on asset class coverage as portfolios expand into private credit, infrastructure, and digital assets; manual reconciliation between IBOR, ABOR, and downstream systems; delayed feature releases as teams prioritize maintenance over innovation; and growing integration complexity with each new custodian, pricing vendor, or risk system added to the stack.
The opportunity cost compounds quietly. Every engineer maintaining a bespoke accounting engine is an engineer not working on what actually distinguishes your firm.
Data Problems Dressed as Technology Problems
Most implementation failures trace back to data challenges, not technology limitations. Firms lose visibility into what data they maintain, what flows in from external sources, what they deliver downstream, and what transformations happen in between.
Legacy batch-based platforms compound this. When data processes overnight with manual reconciliation between books, data lineage becomes opaque. Modernization efforts become exponentially harder when no one can clearly trace what changed, when, and why.
Real-time, bitemporal accounting architectures change this by design. When every event processes immediately with complete audit trails and versioning, data lineage is transparent. You can trace every element through the system, which makes integration and legacy retirement significantly more manageable.
Strategic Hybridization Vs Accidental Fragmentation
Hybrid operating models are increasingly common across the industry: building where you differentiate, buying commoditized capabilities, outsourcing non-core operations. Applied deliberately, this works well.
The problem is when firms create fragmentation within their investment accounting stack itself. Separate systems for IBOR and ABOR. Different platforms for liquid and illiquid assets. Shadow systems for contingent NAV. Manual reconciliation processes stitching it all together.
This isn’t strategic hybridization. It’s fragmentation driven by legacy constraints, rationalized after the fact.
The alternative is a platform architected from the start to handle modern portfolio complexity: public and private markets on a single engine, real-time processing with as-of capabilities, multi-currency and multi-jurisdiction support from one dataset, and API-first connectivity to the broader tech stack. The speed-to-value advantage of buying only materializes when the platform was purpose-built for the domain. General-purpose systems adapted for investment accounting require the kind of customization that erodes any efficiency gain.
The Work That Doesn’t Go Away
Selecting a platform doesn’t transfer the hard work of transformation. Even with a modern cloud-native system, firms still own change management across front, middle, and back office teams; integration strategy with upstream and downstream systems; legacy retirement planning; and governance to ensure the platform operates according to investment accounting policies.
Firms that treat platform selection as a technology decision underestimate these costs. Firms that approach it as an operating model transformation, with executive sponsorship and cross-functional ownership, see faster time to value and lower total cost of ownership.
What This Means in Practice
For investment accounting leaders evaluating their infrastructure, a few principles hold:
- Investment accounting is commoditized infrastructure. Your investors don’t select you for sophisticated IBOR capabilities. Your accounting platform should enable your differentiators, not consume the resources that could drive them.
- Calculate the full decade-long cost of building. The initial build is the beginning, not the sum. Factor in ongoing support, feature development to keep pace with industry change, integration work as your ecosystem evolves, and the opportunity cost of talent tied to infrastructure.
- Treat integration and legacy retirement as first-class workstreams from day one. Most integration challenges stem from unclear data models, not technology limitations. Firms that do this work before selecting platforms make better decisions and move faster afterward.
- Evaluate platforms on architecture, not feature checklists. A platform built on batch processing with separate modules for each asset class recreates fragmentation with a different vendor’s name on it. Architecture matters more than feature lists.
Where Do You Want to Compete?
The firms pulling ahead have strategic clarity about where they differentiate and where they leverage best-in-class infrastructure. They are not building bespoke accounting engines to support the same IBOR, ABOR, and NAV calculations every other firm runs. They are partnering with platforms that handle those requirements at scale so they can focus on what actually distinguishes them.
For asset managers, that might be proprietary investment strategies or client experience. For fund administrators, it’s service quality and operational efficiency. For asset owners, it’s governance and risk oversight. None of those require custom-built accounting platforms. All of them benefit from modern, cloud-native systems of record that deliver real-time visibility, automated controls, and the flexibility to support new asset classes without re-platforming.
The question isn’t whether to modernize. It’s whether you’ll do it strategically or continue allocating resources to systems that don’t differentiate your firm.
FundGuard’s cloud-native, AI-enabled investment accounting platform unifies IBOR, ABOR, and NAV across public and private assets on a single real-time engine. To learn more about how FundGuard helps asset managers, fund administrators, and asset owners reduce complexity and focus on what differentiates them, request a personalized demo with the FundGuard team.
To read more articles from FundGuard, visit our content hub on Funds Europe
____________________________________________________________________
This article references insights from Fencore’s “Build vs Buy vs Outsource: Making the Right Call for Your Target Operating Model” webinar series. Learn more.
This article was originally published on the FundGuard blog. Read the original article.
