Symphony Reporting

What it improves

Reporting packs are still mostly assembled. Numbers are pulled, adjusted, reconciled and pasted. Every change request triggers a chain of manual work. When a number is questioned, it can take days to trace where it came from.

What it does

• Templated reporting packs for IFRS 17, SAM, internal management, board and regulator audiences.
• Full lineage: every number on a page links back to the data, model output, assumption and adjustment that produced it.
• Variance explanation built in: differences between current and prior periods are decomposed automatically.
• Outputs to PDF, PowerPoint, Excel and the BI tools you already operate.
• BI-ready data models for downstream analytics.
• Sits alongside the actuarial engines you already operate and does the disclosure work they do not.
• Shares the common architecture across the platform: API, lineage, role-based access, observability.
• Available inside Excel, on the web, and via the API — actuaries work in the tool they already know, with full audit trail back to the platform.

Controls and audit

Every reporting cycle is a versioned artefact. The pack you produced last quarter can be regenerated bit-for-bit today, or rolled back to in a single step.

Engagement model

Deployed inside an engagement, on your environment, with documented handover. We do not licence this as a standalone product. In-engagement deployment of a first pack has typically landed inside 6 to 12 weeks on engagements we have run: scope, integrate upstream data and model outputs, automate, then add packs — actual timing depends on scope, source-system access and the team’s review capacity. If you want to take the component forward, you take it — full source, docs, supported handover.