Tenant License Usage

Tenant License Usage is used to load monthly product license allocation and consumption data at the tenant level.

Use this page when you need Yarken to track how many licenses are available, how many are consumed, and how much capacity remains for each tenant and product. This data supports SaaS license reporting, TBM allocation, mapping, analytics, planning, and software license governance.

Tenant License Usage sits under Yarken Designer > Consumption > Tenant License.


What Tenant License Usage helps you do

Use Tenant License Usage to:

  • Load monthly tenant-level license usage data

  • Track total, consumed, and available licenses by product

  • Associate license usage data with a vendor

  • Support license allocation and availability reporting

  • Prepare license data for Analytics and Software License Intelligence

  • Provide monthly usage inputs for TBM allocation and mapping

  • Review tenant-level license capacity before renewal or planning decisions

Tenant-level license data gives administrators and finance teams a clear view of license capacity across products and tenants.


When to use Tenant License Usage

Use Tenant License Usage when the data describes license allocation at the tenant and product level.

Typical examples include:

  • Total licenses available for a product in a tenant

  • Licenses consumed for that product in a reporting month

  • Licenses still available for allocation

  • Product SKU-level entitlement and capacity data

  • Monthly license snapshots by tenant

Use Individual License Usage when the data is tied to specific users.

Use Product Usage when the data describes application or product activity.


How Tenant License Usage fits the consumption model

Tenant License Usage is part of the broader Consumption area in Yarken Designer.

The typical flow is:

  1. Select the reporting year

  2. Open Consumption > Tenant License

  3. Upload tenant license usage for the relevant month

  4. Review the upload in Uploaded Files

  5. Check any errors or mapping issues

  6. Use upload rules where transformation is required

  7. Review the data in License Usage analytics and related reporting

The uploaded data becomes available for downstream reporting once the file is loaded and processed successfully.


Page layout

Tenant License Usage includes three tabs.

Tab

Use it to

Overview

Upload or review monthly tenant license usage by month

Uploaded Files

Review uploaded files, load status, record counts, errors, and mapping fields

Upload Rules

Create and manage rules that transform data during upload

Use Overview for month-based upload activity. Use Uploaded Files when checking what has already been loaded.


Overview tab

The Overview tab shows the selected year as monthly upload tiles.

Each month represents a reporting period. Use the relevant month tile to upload the tenant license usage file for that month.

Before uploading, confirm that:

  • The selected year is correct

  • The file represents the month you are uploading into

  • The report date in the file matches the month and year selected

  • Tenant identifiers already exist in Yarken

  • Product names and SKU values match the expected source structure

This helps avoid failed uploads and incorrect reporting periods.


Uploaded Files tab

The Uploaded Files tab shows the files that have been loaded for Tenant License Usage.

Common columns include:

Column

Description

Year

Reporting year for the upload

Month

Reporting month for the upload

File Name

Name of the uploaded file

Destination

Destination area, such as Tenant License Usage

File Type

Upload file type

File Status

Current load status, such as Loaded or Error

Loaded Records

Number of records successfully loaded

Total Records

Total records detected in the file

Errors

Upload or validation errors where applicable

Mapping fields

Mapping information for the uploaded file

Uploaded On

Upload timestamp

Use this tab to confirm whether a file loaded correctly and whether the expected record count was processed.


Uploaded file actions

Each uploaded file can include file-level actions.

Common actions include:

Action

Use it to

Delete

Remove an uploaded file where appropriate

Download

Download the uploaded file for review

Reload

Reload the file using the existing mapping

Re-map and reload

Update mapping before reloading the file

Automate

Automate recurring load behavior where supported

Use Re-map and reload when a file loaded with incorrect field mapping or needs mapping correction before processing again.


Upload Rules tab

The Upload Rules tab lets administrators create rules that transform data during upload.

Upload rules are useful when source files need controlled cleanup or standardization before the data is loaded.

Rules can help with tasks such as:

  • Assigning default values

  • Standardizing field values

  • Updating target fields during upload

  • Supporting consistent mapping across recurring files

Use upload rules carefully. They affect how uploaded data is transformed and can change downstream reporting results.


Required data checks

Before uploading tenant license usage data, confirm these checks.

Check

Why it matters

Tenant ID exists in Yarken

The upload can fail if the tenant identifier is not recognized

Report Date matches the selected month and year

Prevents data from loading into the wrong reporting period

Product values are consistent

Supports cleaner analytics and product-level reporting

SKU values are consistent

Helps distinguish products with similar names

Record count is expected

Helps identify incomplete or duplicate files

Strong source data improves license reporting quality.


Relationship with License Usage analytics

Tenant License Usage feeds license reporting in the License Usage analytics cube.

In Analytics, tenant license data can help teams review:

  • Product Name

  • Product SKU ID

  • Total Licenses

  • Total Consumed

  • Total Available

  • Report Date

  • Tenant dimensions

  • Vendor context

Use Analytics to compare tenant-level license allocation and consumption across products, vendors, tenants, and reporting periods.


Relationship with Software License Intelligence

Tenant License Usage supports software license intelligence by providing the tenant-level entitlement and consumption view.

This helps teams:

  • Review unused license capacity

  • Identify products that may require renewal review

  • Compare consumed and available licenses

  • Support reclaim and right-sizing conversations

  • Improve SaaS governance and planning decisions

Tenant-level data is most useful when it is reviewed alongside individual license usage and product activity.


Use these practices when managing Tenant License Usage:

  • Load files consistently for each reporting month

  • Confirm the selected year and month before uploading

  • Keep tenant identifiers consistent across files

  • Keep product and SKU values consistent across months

  • Review uploaded file status after each load

  • Check loaded records against the expected record count

  • Resolve errors before using the data in reporting

  • Use upload rules only when the transformation is required and repeatable

  • Review tenant-level usage with individual usage and product activity where available

Consistent monthly uploads improve trend analysis and renewal planning.


Common issues

If a tenant license usage file does not load correctly, check:

  • Whether the Tenant ID exists in Yarken

  • Whether the report date matches the selected upload month and year

  • Whether required fields are populated

  • Whether product or SKU values are formatted consistently

  • Whether the file has duplicate or incomplete records

  • Whether the uploaded file mapping is correct

  • Whether upload rules changed the expected field values

  • Whether the file status shows an error in Uploaded Files

If results look incorrect in Analytics, start by checking the uploaded file status, record count, and reporting period.


Next step


Related content