You can set up Bill Processing to show local per minute and per call usage on separate lines in applicable reports (see below). For this to occur, Include Separate Local Per Minute vs. Per Call must be enabled in the Config Console. This feature is disabled by default. To configure this feature, see XML Invoice Service Settings.
In addition to the Config Console setting, the usage record must meet the following criteria in order to have local per minute and per call usage reported separately:
Usage Type = Local
Distance Type = IntraLATA
If all three criteria are met, Bill Processing examines the Rate Detail and then the Pricing Plan Detail (A Leg) for the usage record as follows to classify the usage as Per Minute or Per Call:
If the Rate Detail (or Pricing Plan Detail) has a value in the both Initial Incr Duration and Additional Incr Duration fields, the record is classified as Per Minute.
If the Rate Detail (or Pricing Plan Detail) has a value in the Initial Incr Duration field and does NOT have a value in the Additional Incr Duration field, the record is classified as Per Call.
For any other combination of values in these fields, Bill Processing will not distinguish between Per Minute or Per Call usage for the record.
Note
Rate Detail settings for Initial Incr and Additional Incr override the corresponding settings in the Pricing Plan detail when the settings are different.
Applicable Reports
The following reports show Per Minute and Per Call usage on separate lines when the above criteria are met:
Usage Type and Distance Type Summary Report
Local Usage Summary Report. This is a sub report included in the Usage Detail, Account Code Usage Detail, and Department Usage Detail Reports.
The XML definition does not change based on the Separate Local Per Minute vs. Per Call setting. The only change will be the distance attribute value of the usg_sum_item element. The distance will be extended to included “ – Per Minute” or “ – Per Call” for local intralata summary items.