Unbillable Codes

An Unbillable Code on a record indicates a problem that needs to be fixed before it can be billed.

(More)

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:

Unbillable Codes

Resolving Unbillable Usage

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

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

For information about how to resolve unbillable usage, see Resolving Unbillable Usage.

Unbillable Rule Code	Name	Group	Default Action	Is Locked	Allow Override	Allowed Operations	Description
CDR000	Internal Error	CDR Validation	Spin	Y	N	Spin	Assigned to a call when the derivation engine hits an unhandled exception.
CDR001	Start time for calls configured for 'Send Key', but insufficient data provided	CDR Validation	Spin	Y	N	Spin	Setting for voice calls, start time configured as 'Send Key' but VoiceChannelAllocationTime and at least one of DisconnectTime or VoiceChannelElapsedTime was not provided.
CDR002	Start time for calls configured for 'Answer Time', but insufficient data provided	CDR Validation	Spin	Y	N	Spin	Setting for voice calls, start time configured as 'Answer Time' but AnswerTime and at least one of DisconnectTime or AnswerElapsedTime was not provided.
CDR003	Chargeable units below minimum accepted value	CDR Validation	Ignore	N	Y	Bypass, Spin, Ignore	Usage record does not contain at least the minimum number of acceptable chargeable units defined by this rule.
CDR004	Chargeable units above maximum accepted value	CDR Validation	Ignore	N	Y	Bypass, Spin, Ignore	Usage record contains the maximum number of acceptable chargeable units defined by this rule.
RTE005	Charge less than minimum accepted value	Rating	Ignore	N	Y	Spin, Ignore	Charge associated with this call record is less than the minimum value configured by this rule.
RTE006	Charge greater than maximum accepted value	Rating	Ignore	N	Y	Spin, Ignore	Charge associated with this call record is greater than the maximum value configured by this rule.
CDR007	CDR EventType specified in the parsed record must be a known value	CDR Validation	Spin	N	N	Bypass, Spin	CDREventType found in the parsed record is not one of: Mobile Voice (1), Mobile Message (2), Mobile Data (3), Mobile Content Download (4).
CDR008	UsageRecord TermPlace is not populated	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	The TermPlace is not populated, the call had a termcountrycode of 0, and is not an 8xx call.
CDR009	Usage record requires a terminating number	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	UsageRecordCall TermNumber is not populated.
CDR010	Usage record requires an originating number	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	UsageRecordCall OrigNumber is not populated.
CDR011	NANP Terminating numbers must have a valid NPA NXX	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	NANP phone numbers are required to have valid NPA NXXs. Calls which cannot be validated may not be eligible for certain rating methods.
CDR012	NANP Originating numbers must have valid a NPA NXX	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	NANP phone numbers are required to have valid NPA NXXs. Calls which cannot be validated may not be eligible for certain rating methods.
CDR013	Non-NANP Terminating Numbers must have a valid Country Code	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Non-NANP TermNumbers are required to have a valid Country Code in the Country Band tables in the IDI platform.
CDR014	Non-NANP Originating numbers must have a valid Country Code	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Non-NANP Originating numbers are required to have a valid Country Code in the Country Band tables in the IDI platform.
CDR015	Cellsite lookup failed	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Call records originating on the home network must have cellsite information.
CDR016	Serving SID assigned to serving cellsite not found.	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	All wireless usage records should have a serving SID associated with them. The serving SID must exist within the SID table in the IDI platform.
CDR017	wireless usage records require a valid Serving PMN	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	All GSM usage records should have a serving PMN associated with them. The PMN must exist within the PMN table in the IDI platform.
CDR018	Cannot determine Home PMN from IMSI	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	All GSM usage records should have a home PMN associated with them. The PMN must exist within the PMN table in the IDI platform.
CDR019	MIN must have a corresponding entry in the SIDNpaRange table	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	All CDMA usage records should have a Home SID associated with them. The SID must exist within the SID table in the IDI platform.
BCG020	Usage record call start time is before configured load date for all open bill periods	Bill Period Guidance	Spin	Y	N	Spin	The call start time on a usage record must be within the loadable dates for a bill period. The CustID and callstarttime can be used to figure out what cycle and or bill periods need to be examined.
BCG021	Usage record call start time is after configured load date for all open bill periods	Bill Period Guidance	Spin	Y	N	Spin	The call start time on a usage record must be within the loadable dates for a bill period. The CustID and callstarttime can be used to figure out what cycle and or bill periods need to be examined.
BCG022	There exists no open bill period within the target Bill Cycle	Bill Period Guidance	Spin	Y	N	Spin	Usage records can only be placed into Open bill periods.An open bill period does not exist within the target bill cycle.
BCG023	Customer must be assigned to a valid billing cycle	Bill Period Guidance	Spin	Y	N	Spin	In order to load usage against a customers account, that customer must be assigned to an existing bill cycle. This covers the case where a customer is assigned to a bill cycle that does not exist within the system.
SVC024	Service number must exist within the IDI platform	Service Guidance	Spin	Y	N	Spin	All call records which are guiding by service number, must contain a service number that is assigned to a service within the system. The service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC025	MIN must exist within the IDI platform	Service Guidance	Spin	Y	N	Spin	All call records which are guiding by MIN, must contain a MIN that is assigned to a service within the system. The service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC026	IMSI must exist within the IDI platform	Service Guidance	Spin	Y	N	Spin	All call records which are guiding by IMSI, must contain a IMSI that is assigned to a service within the system. The service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC027	A usage record cannot guide by service number to an ambiguous service	Service Guidance	Spin	Y	N	Spin	Service Number ambiguity. The service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC028	A usage record cannot guide by MIN to an ambiguous service	Service Guidance	Spin	Y	N	Spin	MIN ambiguity. The service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC029	A usage record cannot guide by IMSI to an ambiguous service	Service Guidance	Spin	Y	N	Spin	IMSI ambiguity. The service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC030	Roaming agreement must exist within the IDI platformto process calls for a roaming partner	Service Guidance	Spin	Y	N	Spin	In order to process outcollect usage, a roaming agreement must exist within the IDI platform for the concerned networks.
SVC031	Roaming agreements must be configured for data usage in order to process data outcollect events	Service Guidance	Spin	Y	N	Spin	In order to process data outcollect usage, a roaming agreement with data processing enabled must exist.
CDR032	No entry in SID table for SID from SIDNpaRange lookup	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	All CDMA usage records should have a MIN which can be looked up in the SIDNpaRange table.
RTE033	No retail pricing plan defined for this call type	Rating	Spin	Y	N	Spin	"Call type" references the usage type. The pricing plan associated to the service must define a way to rate the usage type of the usage record.
RTE034	No retail rating method defined for this call type	Rating	Spin	Y	N	Spin	The call’s usage type can match a record in the ProgramRateLink table but when looking up RatePlanDetails none of them may match the criteria in the usage record. Usually this is fixed by adding the default rating method to the rate plan detail. Rating methods are stored in the Rating Methods table in .
RTE035	No retail time of day entry	Rating	Spin	Y	N	Spin	The usage record’s call start time does not fall into the times set up in the Time Of Day table in the IDI platform.
RTE036	No retail rate plan	Rating	Spin	Y	N	Spin	Can’t find a rate plan to match the criteria in the usage record based on the associated pricing plan assigned to the service.
CDR041	Start time for calls configured for 'Send Key', cannot determine duration	CDR Validation	Spin	Y	N	Spin	Cannot determine a call's duration if this condition is not met. Similar to the call start time code (CDR001).
CDR042	Start time for calls configured for 'Answer Time', cannot determine duration	CDR Validation	Spin	Y	N	Spin	Cannot determine a call's duration if this condition is not met. Similar to the call start time code (CDR002).
CDR044	GSM Outcollect data events require a Transfer duration be specified	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Data session records should specify a data transfer duration in seconds.
CDR045	Data events that are to be outcollected to a GSM roaming partner require an AccessPointName	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Data outcollects would be rejected if this information is not provided.
CDR046	Data events that are to be outcollected to a GSM roaming partner require a GGSN address	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Data outcollects would be rejected if this information is not provided.
CDR047	Data events that are to be outcollected to a GSM roaming partner require a SGSN address	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Data outcollects would be rejected if this information is not provided.
CDR048	Data events that are to be outcollected to a GSM roaming partner require a PDP Address	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Data outcollects would be rejected if this information is not provided.
CDR049	Data events that are to be outcollected to a GSM roaming partner require a ChargingID	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Data outcollects would be rejected if this information is not provided.
CDR050	Event direction specified in parsed record must be a known value	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore
CDR056	Network Type specified in parsed record must be a known value	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore
CDR057	Parsed record must contain enough information to determine serving cellsite	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Record is missing enough information to look up a cellsite.
CDR058	Valid IMSI required to determine HomePMN for wireless usage	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	IMSI is either not present when required, or does not contain enough digits to be considered valid.
CDR059	Valid MIN required to determine HomeSID for wireless usage	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	MIN is either not present when required, or does not contain enough digits to be considered valid.
BCG060	Customer type is invalid for specified billing cycle	Bill Period Guidance	Spin	Y	N	Spin	CustID and callstarttime can be used to figure out what cycle and or bill periods need to be examined.
SVC061	Guiding by service number, call start time is before service's effective date minus grace	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC062	Guiding by service number, call start time is after service's disconnect date plus grace	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against
SVC063	Service number does not exist, call falls outside loadable window	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC064	Guiding by MIN, call start time is before service's effective date minus grace	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC065	Guiding by MIN, call start time is after service's disconnect date plus grace	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC066	MIN does not exist, call falls outside loadable window	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC067	Guiding by IMSI, call start time is before service's effecitve date minus grace	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC068	Guiding by IMSI, call start time is after service's disconnect date plus grace	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC069	IMSI does not exist, call falls outside loadable window	Service Guidance	Spin	Y	N	Spin	Service identifier and type along with callstarttime can be used to determine what service the call should have loaded against.
SVC070	Outcollect record cannot guide to an ambiguous roaming agreement	Service Guidance	Spin	Y	N	Spin
SVC071	Outcollect record before roaming agreement's effective date minus grace	Service Guidance	Spin	Y	N	Spin
SVC072	Outcollect record after roaming agreement's disconnect date plus grace	Service Guidance	Spin	Y	N	Spin
SVC073	Roaming agreement does not exist, call falls outside loadable window	Service Guidance	Spin	Y	N	Spin
CDR074	UsageRecord OrigPlace is not populated	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore
CDR075	Default Serving SID not found.	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Default Serving SID defined in Admin Console does not exist. Submit a Clerk Request to have this corrected.
CDR076	Serving SID in parsed record not found.	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	CDREvent record contained a specific Service SID value that ins not in the IDI platform SID table.
SVC077	Roaming Agreement must allow voice event transfer	Service Guidance	Spin	Y	N	Bypass, Spin	GSM roaming agreements must be configured to transfer voice calls for a voice call to load against a GSM roaming partner.
CDR078	Incomplete phone call	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	CDREventCall.CompletionIndicator set to IncompleteCall
RTE079	Charged units below minimum accepted value	Rating	Ignore	N	Y	Spin, Ignore	Minimum value is set up in the UnbillableRule table the DefaultThreshold column. This value can be overridden in Rule Details.
RTE080	Charged units above maximum accepted value	Rating	Ignore	N	Y	Spin, Ignore	Maximum value is set up in the UnbillableRule table the DefaultThreshold column. This value can be overridden by in Rule Details.
RTE081	All chargeable instances for a UsageRecord must rate without error	Rating	Spin	Y	N	Spin	If one instance of a UsageRecord does pass validation, all associated instances cannot be loaded.
BIL082	Voice mail deposit	Billable Scenario	Bypass	N	Y	Bypass, Spin, Ignore	Determines if voice mail deposit calls should be loaded. If set to Bypass, no voice mail deposit calls are loaded into the system.
CDR083	Content Type specified in the parsed record must be a known value	CDR Validation	Spin	N	N	Bypass, Spin	ContentTypeID specified in the CDREvent record is not a known value; therefore, the UsageType cannot be determined.
CDR084	Serving Cellsite must have a valid Toll NPA NXX	CDR Validation	Spin	N	Y	Bypass, Spin, Ignore	Cellsite, as set up in Admin Console > Data Management > Cellsites, has a TollNPA and TollNXX that does not exist in the NPANXX table.
CDR085	Usage record must have at least 1 chargeable instance	CDR Validation	Spin	Y	N	Spin	All usage records must contain at least a single Chargeable instance to be guided to a customer account. The call passed all validations but did not contain any usage types.