The actuary's month-end, solved
The problems valuation actuaries face every month-end, and how AutoImpact answers each one.
Read the story as text
- Month-end lands on your desk. Month-end: policy extracts, unit prices, fund maps, exchange rates, last year's model points and a chain of emails, all landing on you.
- Reconciling by hand. Then the reconciliation: does the new model point file tie to production, field by field, in a spreadsheet?
- Three bases, three models. Lux GAAP, Solvency II and IFRS 17 each live in their own model and spreadsheets, and the numbers still have to agree.
- Then audit asks. And then audit asks you to prove it: who changed the basis, where a figure came from, and whether anyone checked it.
- AutoImpact. AutoImpact does that work in one application your team controls, without code and without a black box: TRACE for the data, PRISM for the modelling.
- TRACE builds and reconciles. TRACE checks every file against the interface specification, builds the model point file and reconciles it to production, with every exception listed.
- PRISM values it every way. PRISM projects the cash flows once and values them on each approved basis: Lux GAAP, the Solvency II best estimate and the IFRS 17 CSM.
- Checked, signed, locked. Doer, checker and reviewer each sign; nobody checks their own work. The reviewer workbook rebuilds every figure in Excel and agrees to the cent.
- Reconciled, valued, signed off. Reconciled, valued, signed off. The same day, on your own machines, with every step open to review.
New Reporting cycles
A reporting period, step by step
Each period runs through the same five steps. Every step is done, checked and reviewed by three different people, with a note and the files or runs it rests on, and the whole record stays in AutoImpact.
In order, by three people
In a production cycle a step starts once the one before it is reviewed, and one person can't do two stages of a step. Each stage can be recorded once, so a double click can't skip one.
Evidence that holds
The data step rests on the uploaded files and the model step on the run. A file is kept with its fingerprint; one with blocking findings, a replaced file or a failed run is refused.
Sent back, not patched
A checker or reviewer can send a step back with a reason. It starts again, and so does every later step that rested on it. Nothing is changed or deleted, and the activity log exports as CSV.
Testing without the risk
A testing cycle keeps the same record but lets one person try every step, warning where production would refuse. It is never closed, so it can't pass for a sign-off.
What needs you
The cycle page leads with what needs you, steps in progress and checkpoints closed. Your next stages also wait in My tasks.
Closed when complete
Once all fifteen checkpoints are closed, the reviewer closes the cycle. Its record can be read and exported, never added to.
See it in the application
The data step done, checked and reviewed; the doer attaches the data-layer run to the next step and confirms it.
Problem and answer
| The problem | What it costs you | How AutoImpact solves it |
|---|---|---|
| Data arrives in a dozen files | Policy extracts, unit prices, fund maps, exchange rates and last year's model points, in different formats, with questions over email. | TRACE checks every file against the interface specification as it arrives, and builds one model point file from them. |
| Reconciliation by hand | Proving the model point file ties to production means field-by-field comparison in spreadsheets, under time pressure. | TRACE reconciles every field to production against your success criteria and lists every exception for you to explain. |
| A model per basis | Lux GAAP, Solvency II and IFRS 17 sit in separate models and spreadsheets whose numbers still have to agree. | PRISM projects the cash flows once and values them on each approved basis, so the figures tie up. |
| Audit asks you to prove it | Who changed the basis, where a figure came from, whether anyone checked it, and whether it can be re-performed. | Every change is a recorded version with a second-person approval; doer, checker and reviewer sign; the reviewer workbook re-performs every figure in Excel. |
| Sign-off lives in email | Who did each step of the period, who checked it and what it rested on is spread over emails, spreadsheets and memory. | A reporting cycle records every step done, checked and reviewed by three people, with notes and evidence, in order, and nothing is ever deleted. |
| The methodology drifts from the model | The written methodology describes last year's rules, and nobody can say which version applied at the time. | The methodology document is written from the definitions in force, with a fingerprint, and any two versions of a rule can be compared. |
See the features
Nine treatments and the features behind them. Features and treatments
Try it yourself
Ten steps from installation to IFRS 17 disclosures. Get started
What comes next
The 2027 Solvency II review, SCR, QRTs, ORSA and embedded value. Roadmap
See your month-end in AutoImpact
Tell us how month-end runs today, and we'll show the same steps in TRACE and PRISM on the demo book.
Or email hello@autoimpact.co.uk · Ask for the brochure