Enterprise Intelligence for Fund Managers in NZ

You have Charles River, Bloomberg PORT, and APEX. You've invested significantly in these systems. And yet, if you walked the floor of your investment team right now, you'd find portfolio managers maintaining spreadsheets. Not because they enjoy it. Because nothing else gives them a single, live, trustworthy view of their book.

This is the shadow spreadsheet problem, and it's sitting at the centre of every fund manager's operational risk profile in New Zealand.

Why the Spreadsheet Persists

Charles River handles your order management and execution. Bloomberg PORT gives you analytics and benchmarking. APEX delivers your daily NAV and reconciled cash. In theory, you have everything you need. In practice, these systems don't talk to each other in real time, and none of them gives a PM the view they actually work from: a live, reconciled position book with scenario testing capability, cross-portfolio visibility, and attribution they can trust.

So the spreadsheet becomes the integration layer. A PM exports from Charles River, pulls data from Bloomberg, reconciles against APEX, and maintains a model that is always slightly out of date and entirely dependent on one person knowing how it works. That's key person risk. It's fat finger risk. And it's an audit and compliance problem waiting to happen.

The CIO situation is worse. Getting an aggregated view across all PM books means collecting individual spreadsheets and manually reconciling them. A cross-portfolio risk picture that should be available in seconds takes hours to compile, and by the time it's ready the underlying data has already moved.

What an Enterprise Intelligence Platform Actually Does

The platform we build for fund managers does one thing at the core: it creates a verified, unified data layer that sits above Charles River, Bloomberg, and APEX and makes that data queryable, auditable, and actionable in real time.

That means intraday positions from Charles River IMS via REST API. Daily reconciliation anchors from APEX fund admin via T+1 SFTP. Market data and rate curves from Bloomberg BLPAPI. Three-way automated reconciliation with exception reporting so your ops team spends time on genuine breaks, not routine matching.

On top of that data layer, we build six integrated modules:

• Unified Position View: A live, reconciled book for each PM, with a CIO-level aggregated view across all books in one interface. The spreadsheet is retired, not patched.
• Scenario Testing Engine: Parametric stress testing across rates, credit spreads, FX, duration, and inflation. Natural language queries run against live portfolio data. Bloomberg RBNZ and Fed rate curves integrated for realistic scenario calibration.
• Backward and Forward View: Full position history stored from day one in TimescaleDB. Any PM can reconstruct portfolio state at any prior date from transaction log. Historical attribution analysis covers any period, not just the current quarter.
• AI Intelligence Layer: Anomaly detection on position changes, concentration alerts, correlation shift flagging, automated rebalance triggers, and natural language queries over live portfolio data.
• Integration Architecture: Role-based access so PMs see their own book plus aggregated views, CIOs see everything. No manual data exports. No CSV files emailed around the office.
• Performance Attribution Engine: Brinson-Fachler decomposition for equity, duration and credit attribution for fixed income. Built on verified source data, which is the part that FactSet and PORT have consistently failed to deliver on.

The Attribution Problem

FactSet spent a decade trying to solve attribution for New Zealand and Australian fund managers. Bloomberg PORT has been at it for years. The core problem isn't the attribution methodology. The math is known. The problem is that nobody trusts the data going in.

If your position data is pulled from three different systems at different latencies, and the reconciliation between those systems lives in a PM's spreadsheet, then any attribution output built on top of that data is noise. PMs know this, which is why they default to gut feel and basic performance summaries rather than proper attribution analysis.

The solution is to solve the data layer first. Clean, reconciled, verified source data that the investment team actually trusts. Attribution built on top of that data is meaningful. Attribution built on messy source data is a compliance liability.

Build Timeline

We deliver a working prototype in eight weeks. That's enough to demonstrate the unified position view, prove the Charles River and APEX integrations, and replace one PM's spreadsheet with something better. Sixteen weeks gets you to a CIO dashboard with scenario testing. Twenty-four weeks is full team rollout.

This isn't a multi-year implementation project. It's a focused build with a working output at each stage.

Who This Is For

New Zealand-based fund managers with $500M or more in AUM running actively managed equity or fixed income mandates. If your team is using Charles River and Bloomberg and your PMs are still on spreadsheets, this is built for you.

If you want to understand what the build looks like for your specific systems and team structure, talk to us. We've mapped this architecture against the standard NZ fund manager tech stack and can show you exactly where the integration points are. You can also read more on the Enterprise Intelligence platform page.