Workspaces in the sidebar menu > License Management > Compliances

The Compliance section in Raynet One provides the product-level compliance result for the managed software portfolio. It compares the effective entitlement quantity with the calculated license demand and displays the resulting balance and compliance status for each product.

The page is used to review whether a product is currently:

•Compliant

•Over-licensed

•Under-licensed

Compliance results depend on the underlying entitlement data and calculated software demand. Entitlements are typically derived from License Contracts. The assigned license model and license metric influence how entitlement quantities are formed and used in compliance calculation.

Access

Open the page from License Management and go to the section Compliances.

Overview

The Compliance overview displays all products included in compliance calculation in a single list. Each row represents one product and its current calculated license position.

The list shows:

•The product used for calculation

•The license model and metric

•The entitled quantity

•The calculated demand

•Adjustments from downgrade and upgrade handling

•The resulting balance

•The balance value

•The current compliance status

Columns

COLUMN	DESCRIPTION
Products	Product icon, if available.
Name	Product name used in the compliance record.
Model	License model used for entitlement and compliance processing, for example Perpetual or Subscription.
Metric	License metric used for entitlement and compliance processing, for example Core-based or Device-based.
Entitled	Quantity currently available from valid entitlements for the product.
Downgrade	Quantity adjustment caused by downgrade rights. A negative value indicates quantity transferred from the current product to an older compatible version. A positive value indicates quantity received from a newer version.
Upgrade	Quantity adjustment caused by upgrade rights. A negative value indicates quantity transferred from the current product to a newer compatible version. A positive value indicates quantity received from an older version.
Demand	Required license quantity calculated from discovered software usage.
Balance	ELP for the product. Calculated as Entitled + Downgrade + Upgrade - Demand.
Balance value	Financial valuation of the current balance position. Positive values indicate a license surplus and represent a potential cost optimization opportunity. Negative values indicate a license deficit and represent active financial exposure. The currency is inherited from the related license contract.
Status	Resulting compliance state of the product.

Compliance Status

The Status column shows the calculated compliance result:

STATUS	MEANING	REQUIRED ACTION
Compliant	Available quantity matches calculated demand.	Monitor regularly
Over-licensed	Available quantity exceeds calculated demand. License surplus present.	Review for reclamation or reallocation in Optimization
Under-licensed	Calculated demand exceeds available quantity. License deficit present	Immediate action required. Verify entitlement data and review demand

Be aware:
An Under-licensed status represents an active compliance risk. If a software audit is conducted while products remain in an under-licensed state, the organization may face financial penalties, retroactive license fees, or contractual violations. Under-licensed products must be prioritized for immediate remediation.

Calculation Note

The Balance column is the core result of the compliance calculation:

Balance = Entitled + Downgrade + Upgrade - Demand

RESULT	STATUS
Balance = 0	Compliant
Balance > 0	Over-licensed
Balance < 0	Under-licensed

Note:
Compliance accuracy depends on the quality of the underlying entitlement and demand data. Incorrect or incomplete contract data, entitlement assignments, license models, license metrics, or discovered demand values lead to incorrect compliance results.

Because product suites and entitlement quantities are derived from License Contracts and related entitlement records, changes in those source records can affect the values shown in the Compliance overview.

Be aware:
Before using compliance results for audit preparation or reporting purposes, always verify that entitlement data is complete and that demand data reflects the current discovered installation state. Compliance results based on incomplete or outdated data will produce a misleading ELP.

Available Actions

The toolbar provides the following actions:

ACTION	DESCRIPTION
Refresh	Reloads the compliance list
Add	Adds a new record, where supported by the workflow
Edit	Modifies the selected record
Remove	Deletes the selected record
Search	Filters the list by text input

What you see

When you open the Compliance section, you see a consolidated product list with the current calculated compliance position for each product. The list allows you to:

•Identify products with an active Under-licensed deficit requiring immediate action.

•Identify products with a surplus that represent cost optimization opportunities.

•Review the quantities, adjustments, and financial values that produced the current compliance result.

•Assess the impact of downgrade and upgrade rights on individual product positions.

The Compliance overview is the primary working tool for SAM teams during audit preparation, license renewal planning, and continues optimization activities. Under-licensed products should be investigated in the Entitlements section first to rule out missing or incorrect entitlement data before purchasing additional licenses. Over-licensed products should be reviewed in the Optimization section to identify reclamation or reallocation opportunities.

Best practice:
Review the Compliance overview regularly, not only during audit cycles. Products can shift from compliant to under-licensed as new software installations are discovered or existing entitlements expire. Always cross-reference Under-licensed products with the Entitlements section before purchasing additional licenses. In many cases, a license deficit is caused by missing or incorrect entitlement data rather than genuine over-deployment. Resolving data quality issues first avoids unnecessary license spend. For Over-licensed products, use the Optimization section to identify concrete reclamation or reallocation actions that convert the surplus into measurable cost savings.

Compliance Reconciliation and ELP

Compliance Reconciliation and ELP