Usage Exceptions

Last Updated: Sep 30, 2020

Usage exceptions occur when processing a configured usage data feed’s records. These records have passed through the Mediation Engine and have been placed into storage awaiting for the Rating Engine to process them. When mediation of a record completes it generates a Usage Data Record (UDR) that is ready for the system to calculate a fee.

Depending on the feed of data these records could have multiple different fields, values and identifiers that allow the Rating Engine rules to examine the record and look-up an associated charge.

These rated charges could be based on a certain classification of record (Data size, API count, length of time, geographic location etc.) and have an associated set of rates for their calculation.

There are times where data arrives in a usage feed that does not match what is in the billing system. This could be that the unique identifier for that record that should map it to an existing account cannot be found in the system. Or another example could be that it specifies a class of usage that is unknown to the system.

How To Handle Exceptions

When these situations arise you want to ensure that the exception record doesn’t go ignored. If that happened you could very well be leaking revenue for usage of your system where a charge could not be calculated.

LogiSense’s Rating Engine will determine the cause of the exception and group it into different classes of errors so that a system administrator can review any exception and take action. Once corrective action has been taken, the administrator can then reprocess the usage record to ensure that no revenue is lost.

This section of documentation goes over the different classifications of exceptions that can occur and corrective steps to be taken to ensure the usage record can be processed.