Liquidity Risk Results

Liquidity risk refers to the risk of not being able to buy or sell an investment in time to cover a loss.

The SAP Financial Services Data Management data model enables you to store calculation results that were created to measure, analyze, and control liquidity risks.

Data Model

In the conceptual data model (CDM), liquidity risk results are modeled with a generic parent entity called Liquidity Risk Result that holds most of the key attributes and has the necessary relationships with other entities that define the granularity of the results.

The following figure shows an example of how liquidity risk results can be modeled in the CDM:

Most liquidity risk results are calculated for maturity bands whereby the timeline is partitioned using time buckets. In the CDM, time buckets are represented by the Time Bucket entity. This entity has a relationship with the Liquidity Risk Result entity to cover the case of dynamically generated time buckets. To cover the case of static time buckets, the Time Bucket entity has also additional relationships to some of the result tables.

Instead of storing liquidity results on contract or instrument level, you can also use risk reporting nodes. You can model a hierarchy with the Risk Reporting Node and use the Risk Reporting Node Hierarchy Relationship entity to specify which risk reporting nodes (children) are hierarchically below another risk reporting node (parent).

The Result Group entity enables you to represent a group of results that were created in one calculation. Technically, the calculation can be done in one or more calculation runs. This can be used for additional granularity of the calculation results and is relevant if more than one calculation was done for the same business date.

The result tables are represented by the following entities in the CDM:
  • Liquidity Gap

    This entity represents the most important way of analyzing idiosyncratic liquidity risk. Expected cash flows (inflows and outflows) are aggregated in time buckets to enable the calculation of marginal and cumulative gaps.​

    Most important key attributes:

    • Cash Flow Item Type

      Enables you to distinguish interest and principal cash flows​

    • Posting Direction

      Enables you to distinguish inflows and outflows

    • Time Bucket Start/End Date

      These dates correspond to the additional relationship to the Time Bucket entity (without a specific role), and are needed as a regular time dimension in a static analysis or for a second time dimension in a dynamic analysis.

  • Liquidity Coverage Ratio

    This entity represents one of the liquidity ratios defined by Basel regulations. It is used to ensure that the bank holds sufficient high-quality liquid assets (HQLA) to cover the total net cash outflows over the next 30 days.​ In addition to the attributes for HQLA, net cash outflows, and liquidity coverage ratio, there are also amount fields for the different levels of HQLA.

    This entity uses the second relationship to time buckets also.​

  • Repo Analysis

    For repurchase agreements, the following key figures are determined:​

    • Encumbered Position​

      The market value of collateral legs

    • Collateral Variation

      • Positive value = value of securities encumbered in the transaction greater than cash value

      • Negative value = debt is not fully covered by the collateral

  • Stock Flow Analysis

    This entity enables you to discover mismatches between currently available financial instruments and those that are required in future time buckets.

  • Net Stable Funding Ratio

    This entity represents one of the liquidity ratios defined by Basel regulations. It is used to support funding stability for banks.

More Information

  • For more information, see the related entities and their definitions in the data model represented in SAP PowerDesigner.

  • Net Stable Funding Ratio (NSFR)