What should a VaR framework actually do if a pricing library already exists?

Question

AcadiFi · Accepted Answer

A pricing library is only one component of a VaR framework. The VaR framework must define scenarios, map positions to risk factors, call pricing or approximation logic, calculate P/L, aggregate losses, store results, and support validation and reporting. Pricing functions answer "what is this instrument worth under these inputs?" The risk engine answers "what happens to the whole portfolio across many scenarios?"

Suppose Cedar Point Analytics uses a pricing library for interest-rate instruments. The VaR system still needs to generate curve shocks, map each trade to the right curve nodes, reprice or approximate values, convert P/L into base currency, and rank the simulated losses. It also needs exception reports, audit trails, and model-version controls.

The FRM lesson is that implementation risk matters. A strong pricing library does not guarantee a strong VaR process if mapping, data, aggregation, or controls are weak. Conversely, a well-designed risk engine can reuse pricing tools efficiently while keeping scenario governance and reporting separate. In practice, VaR is an architecture problem as much as a formula problem. On the exam, also state the horizon, confidence level, data source, modeling assumption, and validation step, because those choices usually explain why two reasonable VaR answers differ materially. Practice more in our FRM question bank.

What should a VaR framework actually do if a pricing library already exists?

Master Part II with our FRM Course

Related Questions

Practice Questions