Skip to content

Solutions

Insurance fund

Assets held by an insurer to meet policyholder obligations and generate returns.

No credit card. Nothing is charged until your first 30 days are over.

What this kind of fund is

An asset pool whose value has to be established reliably each period, and whose administration sits alongside a much larger regulatory reporting obligation.

An umbrella held open against rain on a city street

What the administration actually involves

An insurer's asset pool sits inside a much larger reporting obligation, and FundFlow only touches one part of it. It administers the asset side: unit positions, the period valuation, fees and reporting. It has no model of technical provisions, no solvency capital calculation and no regulatory returns, and it would be a poor idea to pretend otherwise.

Within that scope, the properties that matter for a valuation you intend to cite are structural. The calculation is deterministic, so the same stored inputs produce the same NAV to the cent, and re-running it on an open month cannot change the answer. Once a month is locked the database refuses to change it. Four database-enforced roles separate who prepares from who reviews, with optional two-person confirmation of the monthly NAV.

What makes it hard

  • A valuation that changes when you recalculate

    Floating-point arithmetic and a recalculation in a different order can move a total by cents. For a figure that feeds a regulatory report, cents that move are a problem out of proportion to their size.

  • No hard boundary around a closed period

    If a reported period can still be edited, its value as a reference point is gone, and so is the ability to explain a restatement.

  • The same person preparing and approving

    Separation of duties is a control the framework assumes exists. A shared file cannot enforce it, and a screen that merely hides a button does not either.

How FundFlow fits

  • Period valuation that reproduces

    The calculation is deterministic: the same stored inputs give the same NAV to the cent, and re-running it on an open month cannot change the answer.

  • Immutable closed periods

    Once a month is locked the database refuses to change it, which is the property that makes a historical valuation worth citing.

  • Separation of duties

    Four database-enforced roles, plus optional two-person confirmation of the monthly NAV.

Where FundFlow stops

FundFlow administers the asset side: unit positions, NAV, fees and reporting. It does not model insurance liabilities, technical provisions or solvency capital, and it produces no regulatory returns.

Questions managers ask

Does this produce Solvency II reporting?

No. FundFlow administers the asset side only: unit positions, NAV, fees and reporting. It does not model insurance liabilities, technical provisions or solvency capital, and it produces no regulatory returns. Those stay in the systems you already use for them.

Is the valuation reproducible to the cent?

Yes. Money arithmetic runs in the database in exact decimal, not binary floating point, and the calculation derives everything from stored inputs and fully replaces its own output. Change an input after computing and the period is flagged as needing recomputation rather than quietly showing the old answer.

All questions and answers

Value one pool and try to break the result

Close a month, note the NAV, and recompute it. Then lock the month and try to edit it. Those two tests tell you most of what you need to know.

In your first session

  1. Create the fund for the asset pool and register the accounts it is held in.
  2. Set the four roles so whoever prepares the valuation is not whoever confirms it.
  3. Close a month, recompute it to confirm the figure does not move, then lock it and try to change it.

No credit card. Nothing is charged until your first 30 days are over.