Workspaces in the sidebar menu > License Management > Compliance

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 Purchases. 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 Compliance.

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

•Adjustments from maintenance downgrade and upgrade handling

•The resulting balance

•The balance value

•The resulting maintenance balance, evaluated independently from the regular license balance

•The current compliance status

Columns

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 purchase.

Status: Resulting compliance state of the product.

Maintenance entitled: Quantity currently available from valid maintenance entitlements for the product. This column is hidden by default and can be enabled through the column chooser.

Maintenance downgrade: Maintenance quantity adjustment received from, or lent to, a compatible product version, mirroring the perpetual license Downgrade transfer. This column is hidden by default and can be enabled through the column chooser.

Maintenance upgrade: Maintenance quantity adjustment received from, or lent to, a compatible product version, mirroring the perpetual license Upgrade transfer. This column is hidden by default and can be enabled through the column chooser.

The columns Maintenance entitled, Maintenance downgrade, and Maintenance upgrade are hidden by default and can be enabled through the column chooser. Maintenance demand and Maintenance balance are not available as columns in the Compliance overview. These values are shown on the Compliance Details page.

Compliance Status

The Status column shows the calculated compliance result. A surplus up to the compliance threshold (default 5 % of the entitled quantity, configurable in the License Management settings) is still reported as Compliant:

STATUS	MEANING	REQUIRED ACTION
Compliant	Available quantity covers calculated demand. A surplus up to the compliance threshold is still Compliant.	Monitor regularly
Over-licensed	Available quantity exceeds calculated demand by more than the compliance threshold. License surplus present.	Review for reclamation or reallocation in Optimization
Under-licensed	Calculated demand exceeds available quantity, or required maintenance is not covered. 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 = Entitlement + Downgrade + Upgrade - Demand

RESULT	STATUS
Balance = 0, or a surplus up to the compliance threshold	Compliant
Balance above the compliance threshold	Over-licensed
Balance < 0, or required maintenance not covered	Under-licensed

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

Maintenance

In addition to the regular license Balance, products with an active Maintenance or Software Assurance entitlement have a separate Maintenance position. Maintenance determines whether enough active maintenance or subscription coverage exists to support the calculated demand, independent of the perpetual license balance.

Maintenance entitled: Quantity currently available from valid maintenance entitlements for the product.

Maintenance downgrade: Maintenance quantity adjustment received from, or lent to, a compatible product version, mirroring the perpetual license Downgrade transfer between family members. Maintenance downgrade and upgrade are transferred automatically together with the corresponding perpetual license downgrade or upgrade when the receiving family member receives a perpetual allocation in the same calculation pass and the source has a Maintenance quantity greater than zero.

Maintenance upgrade: Maintenance quantity adjustment received from, or lent to, a compatible product version, mirroring the perpetual license Upgrade transfer between family members.

Maintenance demand: The Maintenance quantity required for the product. It is calculated as the greater of:

•the Maintenance requirement forced by virtual device demand, and

•the regular demand capped at the available Maintenance quantity.

Maintenance demand = MAX(VM-forced maintenance requirement, MIN(regular demand, available maintenance))

Regular demand alone can reduce the Maintenance balance to zero but cannot make it negative. A VM-forced Maintenance requirement is not capped at the available Maintenance quantity and can therefore result in a negative Maintenance balance.

Maintenance balance: Maintenance entitled + Maintenance downgrade + Maintenance upgrade − Maintenance demand. Can become negative when virtual device demand forces more maintenance than is available.

Maintenance balance = Maintenance entitled + Maintenance downgrade + Maintenance upgrade − Maintenance demand

Virtual device maintenance

Some products require maintenance coverage specifically for virtual devices (configured on the product as VM maintenance required). For these products, license demand originating from virtual devices is always covered by maintenance, regardless of how much maintenance is otherwise available. If the virtual device demand exceeds the available maintenance quantity, the Maintenance balance becomes negative and the product is flagged as maintenance under-licensed — even if the regular license Balance is positive. Regular (non-virtual) demand never forces the Maintenance balance negative by itself; it is only ever consumed up to the amount of maintenance actually available.

Note:
A product can be fully compliant on regular licenses (Balance ≥ 0) while still being maintenance under-licensed (Maintenance balance < 0), or the reverse. Both positions are evaluated independently and both should be reviewed.

Because product suites and entitlement quantities are derived from Purchases 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 the User Sees

When opening the Compliance section, the user sees a consolidated product list with the current calculated compliance position for each product. The list allows the user 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-lincensed 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