Data preparation and controls
We collect the agreed exposure, policy, claims, and finance inputs, run quality checks, and freeze a versioned snapshot.
Firefly RiskOS · Risk and Actuarial Operations
Every cycle, we prepare the data, coordinate runs on your approved models, reconcile the results, and assemble the review pack.
The problem
Then finance and the reviewers ask what went in, what moved, and who signed it, and the answers sit in email.
Who it servesCRO offices, chief actuaries, controllers, and model-management teams
What the service includes
Your service schedule lists the tasks your operation includes.
We collect the agreed exposure, policy, claims, and finance inputs, run quality checks, and freeze a versioned snapshot.
Under your criteria for a significant increase in credit risk (SICR), we allocate stages by rule and list each transfer.
We coordinate expected credit loss (ECL) or CECL runs on your PD, LGD, and EAD models and approved scenarios.
Once the runs finish, we reconcile results to source and ledger, explain movements by stage, and prepare management overlay proposals for your approvers.
For insurers, we build reserving triangles and prepare incurred-but-not-reported (IBNR) runs on your methods.
We run the back-testing you approve and prepare inputs for your IFRS 17 and Solvency II engines.
How the service works
Each stage runs on the method that fits the cost of an error.
Approved rules
We validate and freeze the input set under your approved data-quality rules.
InputSource data and requirements
OutputA controlled data snapshot
Your systems
Your approved engine executes the model; we coordinate the run and record its context.
InputApproved model and parameters
OutputVersioned model outputs
AI agent
Between runs, an AI agent traces each difference and drafts the explanation.
InputOutputs and comparisons
OutputAn analytical review package
Your team decides
Your experts challenge the package and sign it off or ask for a rerun.
InputPackage and questions
OutputAn approved result or a rerun
Approved rules
We pass the approved figures to finance and reporting under your rules.
InputApproved figures and evidence
OutputA completed cycle with its evidence
What you receive
Unit of workA completed close or model cycle
Systems and technology
Risk and actuarial engines, data warehouses, loan and policy records, claims systems, ledgers, and model inventories.
Your teams can read the code of each module.
Measures
Scope, pricing, and growth
One recurring cycle on an engine you already use.
Per close cycle, portfolio cycle, or model-monitoring service, with a recurring commitment.
Add portfolios, reporting cycles, monitoring services, or ReconcileOS.
Questions
No. We coordinate runs on the engines and models you approve.
No. Independent validation is separate work. Running your models and documenting the runs does not validate them.
Yes, as two services. A bank’s IFRS 9 close and an insurer’s reserving cycle each have their own experts, inputs, and acceptance criteria.
Your first operation
Tell us the process, the volume, and what “done” looks like. We will come back with a scope, a deployment plan, and a proposal.