FundGuard vs SS&C Geneva vs SimCorp One: Investment Accounting

Compare investment accounting software by books of record, reconciliation, NAV controls and migration evidence, including tokenized-fund requirements.

Reviewed by FluidRWA Research Team · October 22, 2026

Short answer

FundGuard documents a multi-book accounting engine; SS&C Geneva documents portfolio and investor accounting, reconciliation and shadow accounting; SimCorp One combines investment accounting, fund accounting and reporting. Compare them with the same fund-close test. Public product pages do not establish native support for your token contracts, custodian feeds or share-register arrangement.

Reviewed byFluidRWA Research TeamResearch standardPublic vendor materials and buyer-fit analysisExplore the vendor directory
Illustrative accounting and reporting infrastructure

Start with the close, not the dashboard

A tokenized fund can have a perfectly readable token balance and still have an unresolved accounting break. A subscription might be paid but not allocated, an expense might arrive after the valuation point, or a corrected trade might change yesterday's figures. The accounting system must explain those differences, not merely display another balance.

This article compares investment accounting software. It is not another crypto tax-tool ranking or a comparison of outsourced fund administrators. The buyer task is to produce, reconcile and reproduce the fund's books.

An accounting book of record (ABOR) supports the accounting view; an investment book of record (IBOR) supports investment-position views. Ask which books the proposed system will maintain and how differences between them are explained.

Comparison: what each company documents

QuestionFundGuardSS&C GenevaSimCorp One
Public product scopeInvestment accounting, fund accounting/ABOR and private-markets accountingPortfolio and investor accounting, reporting and shadow accountingInvestment accounting, fund accounting and regulatory reporting
Control descriptionsMultiple books, historical views and continuous reconciliationReconciliation, exception workflows and data managementNAV/close monitoring, exception alerts and audit trails
Demonstration to requestA late correction across two accounting booksA position break traced to investor reportingA failed close check resolved and reproduced
Do not assumeNative support for every token or feedEvery service or module is includedManaged services are included with technology
Pricing and exact deploymentNot verified for a common buyer configurationNot verified for a common buyer configurationNot verified for a common buyer configuration

The pilot requests are FluidRWA's evaluation criteria, not features we have benchmarked. The three companies were selected because their official pages describe investment-accounting workflows; this is not a market ranking.

FundGuard: examine the relationship between books

FundGuard's product documentation describes an accounting engine covering investment accounting, fund accounting and private markets. It also describes multiple books, bitemporal views and continuous reconciliation. Those descriptions are company evidence, not proof of a particular implementation's results.

For the demonstration, provide a transaction booked on Monday and corrected on Wednesday with a Monday effective date. Ask the team to show both what the business believes happened on Monday and what it knew before Wednesday's correction. Then ask which downstream reports must be reissued.

The useful result is not simply a revised balance. It is an understandable link between the original input, correction, approval and affected reports.

SS&C Geneva: specify the product and service package

SS&C Advent's Geneva page describes portfolio and investor accounting, multi-currency reporting, shadow accounting and reconciliation. Its Geneva Elements brief describes a combination of software, cloud delivery and co-sourcing components.

Ask which components are in the proposal and who operates them. A package with a service team has a different responsibility split from software run entirely by your staff. Have the provider reproduce an investor statement from the portfolio, allocation and fee records used in the accounting run.

For a tokenized structure, add a custody export and the transfer agent's register. Ask the provider to identify missing interfaces explicitly. A portfolio-accounting product description is not evidence that a particular blockchain connector is included.

SimCorp One: test the integrated operating model

SimCorp's accounting page describes integrated investment accounting, fund accounting and reporting. It distinguishes technology operated by the customer from Investment Accounting Services delivered as a managed solution.

Ask the provider to show the same close under the proposed operating model: who imports the data, clears exceptions, approves adjustments and releases outputs? Establish where responsibility remains with the fund manager or administrator.

Do not treat broad coverage statements as approval of your precise accounting policy or legal structure. Request a signed scope covering the relevant entities, instruments, books and reporting outputs.

Run the same fund-close exercise for all three

Use synthetic or appropriately protected records. Include a subscription awaiting allocation, a redemption crossing the cutoff, an expense correction, an FX observation and an unmatched custody position. Give every provider the same opening balances and expected control totals.

Require these outputs:

  • A reproducible trial balance and share-class calculation.
  • An exception register distinguishing missing inputs from genuine financial differences.
  • A record of adjustments, approvals and the reporting version released.
  • An export usable without the provider's dashboard.
  • A recovery demonstration after an input file or integration fails.

For tokenized funds, reconcile token units, book-entry shares and investor entitlements separately. Do not multiply contract supply by a price and label it total fund NAV without establishing which shares and liabilities the calculation covers.

What should the proposal include?

Specify software, managed services, migration, interfaces, environments, data history, support, retention and exit exports separately. Ask who will own instrument mapping and who fixes a broken custodian feed after go-live. Set acceptance criteria before agreeing an implementation timetable.

Existing fund operations also matter. Our fund-administrator comparison concerns service providers; our crypto-accounting comparison concerns another accounting workflow. Neither should be treated as interchangeable with the systems reviewed here.

For the inputs to the valuation process, use the fund NAV pricing-data checklist.

Sources and review scope

Official product pages and the Geneva Elements brief were checked 22 October 2026. This is a public-documentation review, not a hands-on performance test. No implementation price, customer outcome or token-specific integration has been assumed. Send a fund-operations brief or a documented correction to contact@fluidrwa.com.

FAQ

Which is the best accounting system for a tokenized fund?

There is no universal winner in this documentation review. Require a proof of concept using the fund's instruments, share classes, custody records and approved accounting policies. Token support must be demonstrated, not inferred from multi-asset marketing.

Does an accounting platform replace the transfer agent?

Not automatically. Fund accounting, investor allocations and the legally authoritative ownership register are different responsibilities. Specify which organization and system owns each record.

Are prices or implementation times comparable publicly?

The reviewed sources do not establish comparable customer-specific prices or implementation times. Request itemized proposals for the same scope, history, interfaces and support arrangement.

Build a focused vendor brief

Share the workflow, systems and responsibilities you need to cover. Prefer email? contact@fluidrwa.com.

Submit requirementsEmail FluidRWA