Developing a fund manager's portfolio management system

Portfolio management systems in fund management companies rarely grow to plan. They emerge over years, from the requirements of individual funds, from regulatory retrofits, and from whatever the tool of the day happened to allow. At some point the system no longer steers, it merely administers. A German fund manager (KVG) commissioned a conceptual overhaul at exactly that point – deliberately as a business project, not an IT one.

Starting position

The existing system covered day-to-day administration but reached its limits in steering: metrics were defined inconsistently, some reporting was produced manually, and regulatorily relevant analyses had to be assembled laboriously.

Systems like this rarely fail outright – they simply become increasingly expensive to run. The effort shifts into manual rework, and with it the risk of error grows in precisely those places where traceability is required.

The brief

A conceptual overhaul aimed at improving steering capability, transparency and regulatory coverage:

• Analysing the existing system landscape and the business and regulatory requirements
• Identifying optimisation potential in data structure, reporting logic and steering metrics
• Developing a target concept for an integrated portfolio management system under the requirements of the German Capital Investment Code (KAGB)
• Refining KPIs as well as steering and reporting structures
• Aligning business requirements with fund management, risk management and controlling
• Translating business requirements into technical specifications
• Supporting implementation and ensuring consistency between system, processes and reporting

How the overhaul was approached

The analysis starts with the metrics

Before any system question came the business one: which metrics actually drive decisions, how are they defined, and do those definitions match across departments? In practice this is where the real finding regularly surfaces – the same metric is calculated differently in fund management, risk management and controlling.

Data structure before user interface

The optimisation potential lay predominantly in the data structure, not in usability: inconsistent master data, missing historisation, analyses built on derived rather than primary data. A target concept that does not address this simply moves existing problems into a new interface.

Regulation as a design principle

KAGB requirements were not treated as a downstream checklist but built into the target concept: which evidence must be producible at any time, which processes need documented controls, how are outsourced functions represented? Regulation implemented after the fact creates parallel structures alongside the actual system.

Which metrics a portfolio management system has to carry

For the target architecture a binding metrics catalogue was defined, separated by level. At asset level: occupancy, WAULT, passing versus market rent, maintenance backlog, energy performance. At fund level: return after costs, loan-to-value, liquidity runway, valuation movement and utilisation of the investment limits set out in the fund rules.

What mattered was less the selection than the commitment: for each metric one definition, one data source, one calculation date and one business owner. Only that assignment turns an analysis into a steering instrument – and ends the debate about which figure applies in case of doubt.

Translating substance into specifications

The frequently underestimated part: formulating requirements so developers can implement them without having to make business decisions themselves. Implementation support ensured that system, processes and reporting stayed consistent – even where compromises became necessary during the project.

Outcome

The result is a solid foundation for more efficient, more transparent and regulatorily consistent portfolio management. The value lies less in individual features than in the standardisation: shared metric definitions, a clean data structure and reporting that works without manual intermediate steps.

What fund managers take from this

• Metric definitions are a leadership matter. Inconsistent definitions are a steering problem, not an IT problem.
• Regulation belongs in the concept. Retrofitted, it creates parallel structures and permanent extra effort.
• The specification determines the result. Whatever is left open on the business side gets decided by developers.

The profile this mandate requires

What was required was the combination of fund expertise, regulatory confidence in the KAGB environment and experience in requirements analysis. Classic IT consultants bring the method but not the subject matter; experienced fund managers know the subject matter but not the craft of specification.

These interface profiles are almost exclusively filled on a project basis. The services page shows the fields we cover; our process describes the steps.

Related project stories: rebuilding reporting for a mezzanine lender and portfolio analysis and strategic realignment.