Analysis of change · the engine
Explain the change
A balance moved. Why? This module answers that question the way IFRS 17 requires and every financial report needs: it decomposes the movement into steps — cash flow, interest accretion, assumption changes, yield-curve update, experience, FX — and proves the steps add back to the independently valued closing balance.
What this solves
IFRS 17 is the demanding case, not the only one. Any business with an economic model of its future cash flows faces the same reporting problem: a balance computed at two dates, and an obligation to explain the difference in terms a reader can audit.
The mechanics here are the general answer:
- a cash-flow cube,
- hierarchical dimensions,
- steps as data,
- discounting and currency translation,
- a reconciliation that must hold.
IFRS 17 is what happens when a standard-setter writes that answer down.
What ships
- The dimension model —
AocType,Novelty,AmountType,EstimateType,EconomicBasis,LiabilityType,ValuationApproach,LineOfBusiness,ReportingNodeand the rest, hierarchical where the domain is hierarchical. - The AoC configuration — one row per (step, novelty) saying how that step is valued, which yield curve and FX rate it uses, and where it sorts. Steps are data: adding one is adding a row.
- The cash-flow cube —
RawVariable(what was imported) andIfrsVariable(what was computed), keyed by group of contracts, step, novelty, estimate type and amount type. - The calculation chain — nominal cash flows → discounting on the relevant curve → the telescopic difference that turns a revaluation into a step → interest accretion → currency translation → the movement report.