Overview

Usage Detail Records provide information on the use of subscription services ordered by clients.   The information is used for billing purposes and consists of records of individual events.  For example:

• Watching a movie
• Placing a telephone call
• Playing a game 
  
• Filling up a vehicle with petrol
  

Usage Detail Records (UDRs) Features

• UDRs are generated by the system, when usage services are ordered for a subscription through the Add Service Usage subscription action.
• UDRs are processed by the billing engine, in real-time or during billing runs.
• Billing information for usage services is sourced from usage service catalogs.
• UDRs can be adjusted or cancelled before and after they have been processed for billing.
• Processed UDRs can be imported into CRM.COM from third-party systems in order to apply additional discounts. Usage services billed by another system are defined as 'Rated' in usage service catalogs.

Setting Up UDRs

Types

Types are used to classify UDRs and group them based on their business application. They can be used to define constraints.  For example, defining a UDR source category as 'mandatory' ensures the user will select one of the allowed categories when ordering the service.  Types must be selected when new usage services are added to a subscription through the Add Service Usage action. 

Configure the following entities before creating UDR types; then add those that you would like to make available for each type.

Source systems: Used to identify the system from which the usage service was ordered and which triggered the creation of the UDR (e.g., decoder, IVR, laptop).

Usage methods: Used to identify how the service was used (e.g., streamed or downloaded). 

Devices: Used to identify the devices on which the UDR will be provisioned (e.g., from a laptop, smartphone, television)

Source categories: Classify the UDR source that initiated the service into generic groups with similar attributes. Source categories can be copied from existing destination categories that are already configured in the system.

Destination categories: Classify the UDR destinations into generic groups with similar attributes. Destination categories can be copied from existing source categories already configured in the system.

Unit of measurement: Configures the unit that expresses the quantity of the service (e.g., minutes, seconds, kilos or liters).

Type fields

The table describes the sections of the Usage Detail Record Types Data Entry page and explains how the fields in the page are used.

 Mandatory   Configurable

Back to top 

Related configuration areas

Mandatory modules must be configured for the Usage Detail Records module to work.

Optional modules may be configured for the Usage Detail Records module to operate at its full capacity. 

Using UDRs

Usage Detail Records are created by the system.  The UDR Data Entry screen is a read-only page (for information).

UDR fields

The table describes the sections of the Usage Detail Records Data Entry page and explains how the fields in the page are used.

 Mandatory   Configurable

Back to top 

Creating and processing UDRs

Selecting and creating a UDR

Specify the criteria that match the Usage Detail Record you are interested in to view the available information.

Adjusting a UDR

Adjust incorrect information captured on the UDR before or after it is billed. If already billed, the system will handle the adjustment by debiting or crediting the associated account with the adjusted UDR. 

Billing UDRs creates rated billing items (RBIs), which have to be cancelled (by creating an identical RBI of opposite value) when a billed UDR is adjusted.  When the adjusted UDR is billed, a new RBI is created.

A UDR can be adjusted from the Data Entry page by using the respective action available from the Actions menu.

1. Adjust the following as necessary:
   • Product: the service that was used
   • Usage Amount: the quantity consumed
   • Source: the system that generated the UDR (filtered on UDR Type)
   • UDR Type
   • UDR Billing Effective Date
   • From and To Date: the period during which the service was used
2. Click on SAVE on the Modal.

Cancelling a UDR

Billed UDRs can be cancelled, debiting or crediting the associated account in the process (a UDR that credited an account will debit it when cancelled and vice versa).  Cancellations can be used to settle a customer complaint by offering a usage service free of charge. 

A UDR can be cancelled from the Data Entry page by using the respective action available from the Actions menu. 

Additional Information

The billing of UDRs creates rated billing items (RBIs).  These have to be cancelled when a billed UDR is cancelled (by creating identical RBIs of opposite value).

Changing the billing directive of a UDR

The billing directive is set by the system and instructs the billing engine on how to handle the UDR, providing it with three options:

• Not To Be Billed (exclude the UDR from billing)
• To Be Billed (debit the related account)
• To Be Credited (credit the related account)

The user can update the directive to manage billing, by using three actions available from the Data Entry page Actions menu: 

• Set As Billable   
  
• Set As Creditable
• Set As Not To Be Billed
  
  

Additional Information

The billing of UDRs creates rated billing items (RBIs).  These have to be cancelled when the billing directive changes.   Once the action is submitted an identical RBI of opposite value is created and handled in the next billing run.

Billing of usage services details

The procedure for billing usage services involves processing UDRs and is different in Prepaid and Normal Subscriptions.

In prepaid subscriptions, billing of usage services results in debiting a wallet associated with the subscription.  UDRs are processed as soon as the Add Service Usage subscription action is submitted.  The service can be added, provided there are sufficient funds in the subscriber's wallet.

In normal subscriptions, billing of usage services results in debiting of the accounts receivable associated with the subscription.  UDRs are processed either during the next billing run or as soon as the maximum number of unbilled UDRs or maximum unbilled amount is reached, as configured in the Billing Term Scheme.

Already processed UDRs can be imported into CRM.COM from third-party systems using the WEB API.  In this case, CRM.COM only handles the provision of additional discounts (not the billing).  Usage services billed by another system are defined as 'Rated' in usage service catalogs.  Refer to Usage Service catalogs for more information.

Back to top 

UDR Business Examples