Platform Platform overview Modules Solutions Industries Commodities Roles Quant More Pricing Customers Knowledge Center Blog Company Request Demo
Knowledge Center · Learn

Value at Risk (VaR) explained

Value at Risk answers a deceptively simple question: how bad could a normal bad day be? This guide explains what VaR measures, how it is calculated, and where it helps, and misleads.

14 min read · Updated 2026 · ETRM glossary

What Value at Risk measures

Value at Risk (VaR) estimates the maximum loss a portfolio is expected to suffer over a given time horizon, at a given confidence level, under normal market conditions. A one-day 95% VaR of $1m means: on about 19 days out of 20, losses should not exceed $1m.

VaR compresses the whole distribution of possible outcomes into a single, comparable number, which is why risk managers, regulators, and boards all use it. It reads off the left tail of the P&L distribution, the region of unusually bad days.

$$ \mathrm{VaR}_\alpha(L) = \inf\{\, \ell \in \mathbb{R} : P(L > \ell) \le 1-\alpha \,\} $$ VaR as a quantile of the loss distribution L at confidence alpha

In words: VaR is the smallest loss level such that the probability of losing more than it is at most 1 minus the confidence. At 95% confidence, that is the loss exceeded on only 5% of days.

VaR cutoff (e.g. 95%) worse P&L better P&L →

VaR reads off the loss distribution: at 95% confidence, losses are expected to exceed the VaR level on only about 1 day in 20.

A worked intuition

Suppose a desk’s daily P&L, gathered over the last 500 trading days, ranges from large gains to large losses. Sort those 500 outcomes from worst to best. The 95% one-day VaR is, roughly, the loss at the 25th worst day (5% of 500), because 5% of days were worse than it. That is the entire idea of historical VaR: let the past distribution speak, and read the quantile directly.

Quantile. the value below which a given fraction of outcomes fall. The 5% quantile of losses is the loss that only 5% of days are worse than, which is exactly the 95% VaR.

The three ways to calculate VaR

There is no single correct method; each trades off intuition, speed, and fidelity differently.

  • Historical simulation, re-price the current portfolio using actual historical market moves and read the loss at the chosen percentile. Intuitive and assumption-light, but limited by the history you have.
  • Parametric (variance-covariance), assume returns are normally distributed and compute VaR from volatilities and correlations. Fast, but the normality assumption understates tail risk.
  • Monte Carlo simulation, generate many random market scenarios, re-price under each, and read the percentile. The most flexible, and the most computationally demanding.
Historicalapply past movesto today’s bookno distributionassumptionParametriccovariance matrix+ sensitivitiesfast, assumesnormalityMonte Carlosimulate manypaths, revalueflexible, heavycomputeintuitivequickmost accurate
The three ways to compute VaR trade off intuition, speed, and fidelity. A mature desk often uses a fast method for live checks and Monte Carlo for the thorough end-of-day and regulatory numbers.

Here is historical VaR in a few lines of Python, computed by full revaluation across historical scenarios and reading the quantile, with Expected Shortfall as the mean of the tail beyond it:

pythonimport numpy as np

def historical_var_es(scenario_pnl, alpha=0.95):
    """scenario_pnl: array of P&L outcomes, one per historical scenario."""
    losses = -np.asarray(scenario_pnl)      # losses are negative P&L
    var = np.quantile(losses, alpha)        # the VaR quantile
    tail = losses[losses >= var]            # everything beyond VaR
    es = tail.mean() if len(tail) else var  # Expected Shortfall
    return var, es

The Risk module supports these approaches against live positions rather than end-of-day snapshots.

The parametric formula

When returns are assumed normal, VaR has a closed form: it is the portfolio’s volatility scaled by the number of standard deviations that corresponds to the confidence level.

$$ \mathrm{VaR}_\alpha = z_\alpha \, \sigma_P \, \sqrt{h}, \qquad \sigma_P = \sqrt{\mathbf{w}^{\top} \Sigma \, \mathbf{w}} $$ Parametric VaR: z-score times portfolio volatility over horizon h

Here z is the standard-normal quantile (about 1.65 for 95%, 2.33 for 99%), the portfolio volatility comes from the sensitivity vector w and the covariance matrix of risk factors, and h scales a one-day figure to an h-day horizon. The elegance is also the weakness: real commodity returns have fatter tails than the normal distribution, so this formula understates how often large losses occur.

Confidence levels and horizons

Two parameters define any VaR number. The confidence level (commonly 95% or 99%) sets how far into the tail you look, 99% VaR is larger than 95% VaR because it captures rarer, worse days. The horizon (one day, ten days) sets the period over which loss is measured. Always quote both: "$1m" is meaningless without "one-day, 95%".

Square-root-of-time scaling. a common shortcut that scales a one-day VaR to h days by multiplying by the square root of h. It assumes returns are independent across days, which is only approximately true, so long-horizon VaR is treated with more caution than the formula suggests.

What VaR does not tell you

VaR is powerful but has well-known blind spots, and treating it as the whole picture is a classic mistake:

  • It says nothing about how bad the bad days are beyond the cutoff. A 95% VaR is silent on the worst 5%. Expected Shortfall (the average loss in the tail) addresses this.
  • It assumes normal conditions. In a crisis, correlations converge and losses exceed VaR far more often than the confidence level implies.
  • It is backward-looking when built from history that did not contain the shock you now face.
  • It is not sub-additive in general, meaning the VaR of a combined book can exceed the sum of its parts, which perversely penalises diversification.
$$ \mathrm{ES}_\alpha(L) = \mathbb{E}\!\left[\,L \mid L \ge \mathrm{VaR}_\alpha(L)\,\right] $$ Expected Shortfall: the average loss given the VaR threshold is breached

Because Expected Shortfall averages the tail rather than reading a single point on its edge, it describes severity, not just frequency, and it is coherent (in particular, sub-additive). This is why regulators have increasingly favoured it. A mature desk computes both, and pairs them with scenario and stress testing, deliberately asking what happens under specific severe moves.

VaR tells you the edge of a normal bad day. Expected Shortfall tells you how bad it gets beyond that edge, and stress testing tells you what specific event would take you there. A risk function needs all three.

Why live positions matter

Every VaR number is computed on a set of positions against a set of market data. If those positions are last night’s, taken from an overnight extract, then the VaR describes last night’s risk, not the risk the desk actually carries now. In a fast-moving market that gap is largest exactly when it matters most. This is why a modern platform computes risk on the same live positions and governed market data as valuation, so the VaR on the screen is the risk in the book, and so risk ties out to P&L rather than drifting from it.

Frequently asked questions

What does a 95% one-day VaR of $1m mean?

It means that under normal conditions, over a one-day horizon, losses are expected to exceed $1m on only about 1 day in 20 (5% of the time).

Which VaR method is best?

There is no single best method. Historical simulation is intuitive, parametric is fast, and Monte Carlo is flexible. Many desks compute more than one and compare. The right choice depends on the portfolio and the compute available.

What is the difference between VaR and Expected Shortfall?

VaR is the loss threshold at a confidence level; Expected Shortfall (also called CVaR) is the average loss given that you are beyond that threshold, so it describes the severity of tail events VaR ignores.

Why isn’t VaR enough on its own?

Because it assumes normal conditions, says nothing about losses beyond the cutoff, and depends on the history used. It should be paired with scenario and stress testing.

Keep exploring

See it on your own trades

The fastest way to understand this in practice is a working walkthrough mapped to your desk.

Request a demo Platform overview