収益リスク(EaR)

Earnings-at-Risk (EaR) is a sensitivity measure that estimates how earnings change under rate or market shocks. It is typically measured by projected earnings impact under defined interest-rate or spread scenarios and is used to set hedging levels and risk limits. The concept makes the earnings stability versus hedging cost tradeoff explicit and supports policy or operational thresholds across planning, stress testing, and review cycles. Teams document assumptions, data sources, and update cadence so results remain comparable over time.

Earnings-at-Risk (EaR) needs a clear start point, end point, owner, and exception path. Start | Trigger condition and input | Prevents premature work End | Output and acceptance rule | Prevents unfinished handoff Exception | Escalation path and decision owner | Prevents stalled execution

Earnings-at-Risk (EaR) improves when ownership, cadence, and feedback loops are explicit. Ownership | One accountable owner | Reduces coordination loss Cadence | Regular review rhythm | Detects drift early Feedback | Clear signal from users or operators | Turns process into learning

Sets guardrails for set hedging levels and risk limits by interpreting projected earnings impact under defined interest-rate or spread scenarios under scenario analysis and stress tests. Signals when to adjust strategy because the earnings stability versus hedging cost balance is shifting in current conditions. Aligns stakeholders by turning Earnings-at-Risk (EaR) into a shared threshold for approvals and periodic reviews.

• Sets guardrails for set hedging levels and risk limits by interpreting projected earnings impact under defined interest-rate or spread scenarios under scenario analysis and stress tests.
• Signals when to adjust strategy because the earnings stability versus hedging cost balance is shifting in current conditions.
• Aligns stakeholders by turning Earnings-at-Risk (EaR) into a shared threshold for approvals and periodic reviews.

• Define calculation windows and inputs for Earnings-at-Risk (EaR) before comparing periods or peers.
• Track leading indicators that move projected earnings impact under defined interest-rate or spread scenarios so decisions are proactive, not reactive.
• Pair Earnings-at-Risk (EaR) with qualitative context to avoid one-number overconfidence.
• Use triggers and escalation paths so set hedging levels and risk limits changes happen on time.
• Revisit assumptions when business mix, regulation, or market conditions shift.

Treat Earnings-at-Risk (EaR) as an operating system, not a one-time activity. Do not add process without removing ambiguity. Do not measure activity if the output quality is unclear. Do not scale the process before the owner and exception path are stable.

• Do not add process without removing ambiguity.
• Do not measure activity if the output quality is unclear.
• Do not scale the process before the owner and exception path are stable.

Example: A treasury desk models a 200-bp shock and finds earnings volatility rising. The team calculates projected earnings impact under defined interest-rate or spread scenarios, compares it to an internal threshold, and discusses the earnings stability versus hedging cost implications. They decide to set hedging levels and risk limits with staged actions, document assumptions and data sources, and set a trigger for revisiting the decision. Over the next quarter, they monitor the metric alongside leading indicators and adjust the plan once the trigger is hit.

Compare Earnings-at-Risk (EaR) with adjacent concepts before deciding. Earnings-at-Risk (EaR) | Current concept | Use when the team needs the primary decision lens Adjacent metric or framework | Supporting lens | Use when the team needs evidence or process detail General vocabulary | Broad explanation | Use only for orientation, not final decision-making

• Earnings-at-Risk (EaR) is a fixed target; in practice, thresholds depend on risk tolerance and context.
• Improving Earnings-at-Risk (EaR) always means better performance; it can hide costs or tradeoffs.
• One snapshot is enough; trends and volatility often matter more for decisions.