Fund accounting platforms don’t get replaced often — the migration cost and operational risk are high enough that most administrators live with a platform decision for a decade or more. Five choices determine whether that decade goes well, well beyond what a vendor demo shows.
The market has genuine depth: SS&C Advent Geneva ties valuation, investment accounting, and investor or regulatory reporting into configurable workflows built around consistent NAV production; SimCorp’s Dimension and Coric platforms emphasise an integrated, front-to-back operating model with strong data lineage and reconciliation controls; Investran and FundCount serve private markets and multi-currency, multi-asset operations with configurable fee and allocation logic. For a Luxembourg fund administrator, the decision isn’t which platform has the deepest feature list — it’s which platform’s operating model actually matches the administrator’s fund mix and CSSF reporting obligations.
Who this is for
- The COO or CTO at a Luxembourg fund administrator evaluating a platform replacement or a greenfield build.
- The board reviewing a fund accounting platform business case before signing off on a multi-year commitment.
Decision one: multi-ledger depth versus configuration overhead
SimCorp’s platforms offer genuine multi-ledger accounting with controlled journal workflows, which suits an administrator that needs separate ledger control across genuinely distinct fund structures. That depth comes with configuration and governance overhead — parameter changes typically require documented approval and testing workflows, which protects against uncontrolled drift but slows routine operational changes. An administrator running a relatively homogeneous fund book gains less from this depth than one running genuinely heterogeneous structures across UCITS, AIFs, and fund-of-funds simultaneously — the decision should be driven by actual fund mix complexity, not by the platform’s reputation for depth in the abstract.
Free · 4 minutes
If your most senior engineer left tomorrow, would anyone still understand the system?
Fourteen questions on documentation, dependencies, and the gap between how the architecture works and how many people know it. Banded finding on screen, full sheet by email.
Decision two: migration reality versus vendor migration claims
Migration tooling quality varies genuinely across platforms, but the recurring lesson across implementations is the same regardless of which platform is chosen: data cleansing and migration complexity is consistently underestimated relative to what vendors suggest during the sales process. An administrator’s own historical data — years of reconciliation exceptions, manually corrected entries, inconsistently structured legacy records — is rarely as clean as the migration plan assumes, and the resulting delay and cost overrun is one of the most common and most avoidable sources of implementation pain. A realistic migration budget and timeline, built from an honest assessment of the administrator’s own data quality rather than the vendor’s stated migration tooling capability, should be a gating input to the platform decision itself.
Decision three: audit trail and data lineage as a CSSF-facing requirement
CSSF inspections, as covered elsewhere, examine delegation oversight and genuine local control as much as technical accuracy — which means the platform’s audit trail needs to demonstrate not just that a number is correct, but who changed it, when, and under what approval. Platforms with strong native audit history for security master data and key accounting fields, and clear segregation-of-duties permissioning, produce this evidence structurally. An administrator choosing a platform primarily on NAV calculation speed or user interface quality, without weighing this audit and lineage depth specifically, is optimising for the wrong criterion given what Luxembourg supervision actually tests.
Decision four: total cost of ownership beyond the licence
Public reporting on large-scale core and fund platform modernisation programmes shows total spend reaching nine figures once migration, testing, and operating-model transformation are included — even where the software licence itself is a modest fraction of that total. An administrator evaluating a fund accounting platform against the headline licence quote alone, without a full multi-year projection including implementation, data migration, parallel-run costs, and ongoing specialist staffing, will materially understate the actual commitment being made.
Decision five: specialist talent availability, not just platform capability
The more configurable, deeply capable platforms consistently draw the same criticism in practitioner reviews: specialised implementation and ongoing configuration expertise is genuinely scarce, and local support availability varies significantly by jurisdiction. An administrator should assess, honestly, whether Luxembourg-based (or genuinely accessible) specialist talent exists for the platform under consideration — a platform that’s technically excellent but effectively unsupportable locally creates an ongoing operational dependency on a small pool of specialists, with all the key-person risk that implies.
What a defensible selection process covers
- An honest match between the platform’s multi-ledger depth and the administrator’s actual fund structure complexity, not the platform’s general reputation.
- A migration budget and timeline built from the administrator’s own data quality assessment, not the vendor’s stated migration capability.
- Explicit evaluation of audit trail and data lineage depth against what CSSF inspections actually test, not just NAV production speed.
- A full multi-year total cost of ownership projection presented to the board, not a licence quote alone.
- A realistic assessment of specialist talent availability in Luxembourg specifically for the platform under consideration.
How we engage with this
We read fund accounting platform shortlists against an administrator’s actual fund mix, CSSF-facing audit requirements, and realistic total cost of ownership — not vendor positioning — as an Architecture Review. The output is a written assessment of platform fit before the board commits.
We don’t sell or implement fund accounting platforms. We don’t take vendor referral fees. We read what’s on the shortlist, assess it against the administrator’s real requirements, and write it down for the people who have to decide.
Pricing is published at /pricing/. If you’re evaluating a fund accounting platform decision, the place to start is a conversation.
Sixteen Pillars is a technology governance consultancy based in Cyprus. Engagements run remote across the EU, UK, and Middle East, with on-site time where the engagement requires it.
Build and rescue work
Hands-on delivery of this kind is handled by Sixteen Pillars Studio.
Free interactive tool
Website compliance checklist
What your site has to do, based on what it actually does
Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.
Everything that applies
Ordered by what to do first: legal requirements you can close quickly, then larger pieces of work, then what is expected rather than required. Not exhaustive, and not a legal audit.
Dated PDF, yours to keep or circulate.
Can you trust the architecture you have?
Architecture diagrams rarely show the reality of how systems actually operate. An independent review establishes what is really there.