From the Rules section of the Unbillable Rules window, you can set the Default Action and Default Threshold for unlocked Unbillable Codes. These Actions and Thresholds are used by the system if the Rule Details do not cover the situation.
To set default actions and thresholds for an Unbillable Code:
Access the Unbillable Rules window.
Access
To access the Unbillable Rules window:
From the Applications menu, select BackOffice Management > Usage Management > Unbillable Rules.
OR
From the Unbillable Analyzer window, right-click a row and select Go To Rule.
OR
From the Unbillable Usage Records window, right-click a row and select Go To Rule.
This displays the Unbillable Rules window which is divided into three sections.
(Show picture)
.png?sv=2026-02-06&spr=https&st=2026-09-24T21%3A18%3A55Z&se=2026-09-24T21%3A40%3A55Z&sr=c&sp=r&sig=DePDG0zmWYNGltFa21grvpD5Q6ihlcVSZkCzy6P%2B54s%3D)
Group Name
The Group Name section of the Unbillable Rules window lists the names of all the unbillable rule code groups.
The Group Names are based on the functional area where validation failed:
CDR Validation (CDRxxx) - If a record does not pass validation during the derivation phase, it is given a CDR Validation unbillable code.
Rating (RTExxx) - If a record does not pass validation during the rate phase, it is given a Rating unbillable code.
Bill Period Guidance (BCGxxx) - If the call start date of a record does not fall within the dates for an available bill period, it is given a Bill Period Guidance unbillable code.
Service Guidance (SVCxxx) - If the service number, IMSI, or MIN on a record cannot be found in the IDI platform, it is given a Service Guidance unbillable code.
Billable Scenario (BILxxx) - If a record does not pass validation during the billing phase, it is given a Billable Scenario unbillable code.
Custom Group - Rules created specifically for your company are listed in a customized group.
Filter by Group Name
To see only the Rules of a specific group, click the Group Name. The list under Rules change to show only those rules. Click All to see all unbillable rules.
See:
Rules
The Rules section of the Unbillable Rules window displays the following columns:
Unbillable Code
The ID of the Unbillable Rule that was not validated.
CDRxxx (CDR Validation)
RTExxx (Rating)
BCGxxx (Bill Period Guidance).
SVCxxx (Service Guidance)
BILxxx (Billable Scenario)
See also:
Name
Name of the Unbillable Code, which is a short description of the why validation failed. For example, "Charge less than accepted minimum value."
Default Action
If none of the Unbillable Code Rule Details are applicable, the Default Action describes the action the system performs on an unbillable usage record.
Note
You can only change an action if the Unbillable Code is not locked.
Only three actions are accepted:
Ignore Rule - Validation of the rule is ignored and the record is loaded even though it would not pass validation.
Bypass Record - The system moves the record to the parse database with a notation that it was bypassed. Bypassed records are not displayed within Usage Management.
Spin Record - Records violating the rule are added to a usage database with the Unbillable Code that it violated. A spun record is displayed in Usage Management and must be worked to resolve the problem.
Note
Not all Actions are accepted by all Unbillable Codes. Only the accepted actions are displayed in the drop-down list for each code.
Default Threshold
If values specified in Rule Details don't apply, the system uses the default value to determine whether the specified action must be taken. The threshold value depends on the particular rule. For example, if you want to bypass all Mobile Voice records with less than $1.00 of chargeable usage, you would enter 1 in the Threshold field of the "RTE079, Charged units below minimum accepted value" Unbillable Code. If you do not specify a value, the threshold value is set to unlimited.
Locked
Certain rules cannot be modified because they indicate unrecoverable errors or violations, such as failing to find account to guide the usage to. You cannot ignore this type of error. Locked rules are identified by a padlock icon.
.png?sv=2026-02-06&spr=https&st=2026-09-24T21%3A18%3A55Z&se=2026-09-24T21%3A40%3A55Z&sr=c&sp=r&sig=DePDG0zmWYNGltFa21grvpD5Q6ihlcVSZkCzy6P%2B54s%3D)
Allows Override
You can override the Default Action of many rules and allow calls to load, even if they fail one or more unbillable rules. These are identified by a white check mark within a green circle.
.png?sv=2026-02-06&spr=https&st=2026-09-24T21%3A18%3A55Z&se=2026-09-24T21%3A40%3A55Z&sr=c&sp=r&sig=DePDG0zmWYNGltFa21grvpD5Q6ihlcVSZkCzy6P%2B54s%3D)
Rule Details
The Rule Details section of the Unbillable Rules window displays the following columns:
CDR File Format
Code assigned by CostGuard to a CDR file when it is processed, such NOK, CLS, NOG.
Event Type
Classification of a CDREvent. Valid Event Types: MobileVoice, MobileMessage, MobileData, MobileContentDownload.
Threshold
The Threshold value is the value the system uses to determine if the specified action must be taken. The threshold value depends on the particular rule. For example, if you want to bypass all Mobile Voice records with less than $1.00 of chargeable usage, you would enter 1 in the Threshold field of the "RTE079, Charged units below minimum accepted value" Unbillable Code. If you do not specify a value, the threshold value is set to unlimited.
Action
Action describes the action the system performs on an unbillable usage record.
Note
You can only change an action if the Unbillable Code is not locked.
Only three actions are accepted:
Ignore Rule - Validation of the rule is ignored and the record is loaded even though it would not pass validation.
Bypass Record - The system moves the record to the parse database with a notation that it was bypassed. Bypassed records are not displayed within Usage Management.
Spin Record - Records violating the rule are added to a usage database with the Unbillable Code that it violated. A spun record is displayed in Usage Management and must be worked to resolve the problem.
Note
Not all Actions are accepted by all Unbillable Codes. Only the accepted actions are displayed in the drop-down list for each code.
For the Unbillable Code, select the Default Action from the drop-down list.
(More)
If none of the Unbillable Code Rule Details are applicable, the Default Action describes the action the system performs on an unbillable usage record.
Note
You can only change an action if the Unbillable Code is not locked.
Only three actions are accepted:
Ignore Rule - Validation of the rule is ignored and the record is loaded even though it would not pass validation.
Bypass Record - The system moves the record to the parse database with a notation that it was bypassed. Bypassed records are not displayed within Usage Management.
Spin Record - Records violating the rule are added to a usage database with the Unbillable Code that it violated. A spun record is displayed in Usage Management and must be worked to resolve the problem.
Note
Not all Actions are accepted by all Unbillable Codes. Only the accepted actions are displayed in the drop-down list for each code.
Click in the Default Threshold field and enter a value to be used by the Unbillable Rule, if appropriate.
(More)
If values specified in Rule Details don't apply, the system uses the default value to determine whether the specified action must be taken. The threshold value depends on the particular rule. For example, if you want to bypass all Mobile Voice records with less than $1.00 of chargeable usage, you would enter 1 in the Threshold field of the "RTE079, Charged units below minimum accepted value" Unbillable Code. If you do not specify a value, the threshold value is set to unlimited.
Enter specific Actions and Thresholds as needed in the Rule Details section.
(More)
When an Unbillable Code is not locked, you can configure valid actions by the Event Type and file format. This lets you decide to only validate a particular type of record (voice, message, data, and content download) as well as what CDR File Formats to act on. If no actions are specified for a particular event type, the system uses the default action. (See Configuring Default Actions and Thresholds)
You can configure the Rule Details based on CDR File Format and Event Type. Either or both can be specified. If you specify details for only one, that detail is in effect for all records that match it. If you specify both CDR File Format and Event Type, that detail is in effect for all records that match both.
The Rule Details let you control what happens to specific types of records if they fail to meet the rule.
To set specific actions and thresholds for an Unbillable Code:
Access the Unbillable Rules window.
Access
To access the Unbillable Rules window:
From the Applications menu, select BackOffice Management > Usage Management > Unbillable Rules.
OR
From the Unbillable Analyzer window, right-click a row and select Go To Rule.
OR
From the Unbillable Usage Records window, right-click a row and select Go To Rule.
This displays the Unbillable Rules window which is divided into three sections.
(Show picture)
Group Name
The Group Name section of the Unbillable Rules window lists the names of all the unbillable rule code groups.
The Group Names are based on the functional area where validation failed:
CDR Validation (CDRxxx) - If a record does not pass validation during the derivation phase, it is given a CDR Validation unbillable code.
Rating (RTExxx) - If a record does not pass validation during the rate phase, it is given a Rating unbillable code.
Bill Period Guidance (BCGxxx) - If the call start date of a record does not fall within the dates for an available bill period, it is given a Bill Period Guidance unbillable code.
Service Guidance (SVCxxx) - If the service number, IMSI, or MIN on a record cannot be found in the IDI platform, it is given a Service Guidance unbillable code.
Billable Scenario (BILxxx) - If a record does not pass validation during the billing phase, it is given a Billable Scenario unbillable code.
Custom Group - Rules created specifically for your company are listed in a customized group.
Filter by Group Name
To see only the Rules of a specific group, click the Group Name. The list under Rules change to show only those rules. Click All to see all unbillable rules.
See:
Rules
The Rules section of the Unbillable Rules window displays the following columns:
Unbillable Code
The ID of the Unbillable Rule that was not validated.
CDRxxx (CDR Validation)
RTExxx (Rating)
BCGxxx (Bill Period Guidance).
SVCxxx (Service Guidance)
BILxxx (Billable Scenario)
See also:
Name
Name of the Unbillable Code, which is a short description of the why validation failed. For example, "Charge less than accepted minimum value."
Default Action
If none of the Unbillable Code Rule Details are applicable, the Default Action describes the action the system performs on an unbillable usage record.
Note
You can only change an action if the Unbillable Code is not locked.
Only three actions are accepted:
Ignore Rule - Validation of the rule is ignored and the record is loaded even though it would not pass validation.
Bypass Record - The system moves the record to the parse database with a notation that it was bypassed. Bypassed records are not displayed within Usage Management.
Spin Record - Records violating the rule are added to a usage database with the Unbillable Code that it violated. A spun record is displayed in Usage Management and must be worked to resolve the problem.
Note
Not all Actions are accepted by all Unbillable Codes. Only the accepted actions are displayed in the drop-down list for each code.
Default Threshold
If values specified in Rule Details don't apply, the system uses the default value to determine whether the specified action must be taken. The threshold value depends on the particular rule. For example, if you want to bypass all Mobile Voice records with less than $1.00 of chargeable usage, you would enter 1 in the Threshold field of the "RTE079, Charged units below minimum accepted value" Unbillable Code. If you do not specify a value, the threshold value is set to unlimited.
Locked
Certain rules cannot be modified because they indicate unrecoverable errors or violations, such as failing to find account to guide the usage to. You cannot ignore this type of error. Locked rules are identified by a padlock icon.
Allows Override
You can override the Default Action of many rules and allow calls to load, even if they fail one or more unbillable rules. These are identified by a white check mark within a green circle.
Rule Details
The Rule Details section of the Unbillable Rules window displays the following columns:
CDR File Format
Code assigned by CostGuard to a CDR file when it is processed, such NOK, CLS, NOG.
Event Type
Classification of a CDREvent. Valid Event Types: MobileVoice, MobileMessage, MobileData, MobileContentDownload.
Threshold
The Threshold value is the value the system uses to determine if the specified action must be taken. The threshold value depends on the particular rule. For example, if you want to bypass all Mobile Voice records with less than $1.00 of chargeable usage, you would enter 1 in the Threshold field of the "RTE079, Charged units below minimum accepted value" Unbillable Code. If you do not specify a value, the threshold value is set to unlimited.
Action
Action describes the action the system performs on an unbillable usage record.
Note
You can only change an action if the Unbillable Code is not locked.
Only three actions are accepted:
Ignore Rule - Validation of the rule is ignored and the record is loaded even though it would not pass validation.
Bypass Record - The system moves the record to the parse database with a notation that it was bypassed. Bypassed records are not displayed within Usage Management.
Spin Record - Records violating the rule are added to a usage database with the Unbillable Code that it violated. A spun record is displayed in Usage Management and must be worked to resolve the problem.
Note
Not all Actions are accepted by all Unbillable Codes. Only the accepted actions are displayed in the drop-down list for each code.
Click an Unbillable Code.
In the Rule Details section, right-click and select Add Detail. A row is added under Rate Details.
Enter the
CDR File Format.
Code assigned by CostGuard to a CDR file when it is processed, such NOK, CLS, NOG.
Select an
Event Type.
Classification of a CDREvent. Valid Event Types: MobileVoice, MobileMessage, MobileData, MobileContentDownload.
Note
If you select All under Event Type, you must add a CDR File Format.
Enter a Threshold value, if required.
(More)
The Threshold value is the value the system uses to determine if the specified action must be taken. The threshold value depends on the particular rule. For example, if you want to bypass all Mobile Voice records with less than $1.00 of chargeable usage, you would enter 1 in the Threshold field of the "RTE079, Charged units below minimum accepted value" Unbillable Code. If you do not specify a value, the threshold value is set to unlimited.
Select the Action.
(More)
Action describes the action the system performs on an unbillable usage record.
Note
You can only change an action if the Unbillable Code is not locked.
Only three actions are accepted:
Ignore Rule - Validation of the rule is ignored and the record is loaded even though it would not pass validation.
Bypass Record - The system moves the record to the parse database with a notation that it was bypassed. Bypassed records are not displayed within Usage Management.
Spin Record - Records violating the rule are added to a usage database with the Unbillable Code that it violated. A spun record is displayed in Usage Management and must be worked to resolve the problem.
Note
Not all Actions are accepted by all Unbillable Codes. Only the accepted actions are displayed in the drop-down list for each code.
Click Save.
Removing a Rule Detail
To remove an existing Rule Detail, right-click the row to delete and select Remove Detail. The selected row is deleted.
See:
Click Save.
See: