Usage record call start time is after configured load date for all open billing periods.
Common Cause
This is a very recent usage record and no billing period has been set up yet to accept it.
Common Resolution(s)
Actions you can take to resolve the problem:
Compare the call start time of the usage record with the dates of the billing periods in the subscriber’s billing cycle (Tools/ References/ Billing Cycle Detail Table). If a new billing period is needed, contact IDI BCT to setup a new billing period.
The subscriber may be assigned to the wrong billing cycle. If so, edit the account and change the bill cycle to fix this problem.
If this usage record contains a bad call start date (in the future), purge the record.
If this usage record has a valid future date (for some reason), no action is necessary. It will remain in Unguidables until it fits into the date range of a [new] billing period, at which point it will process and be billed.
If this is future dated but must be billed now, change the billable range of the latest unbilled billing period in that billing cycle. This is usually done be changing the end grace on the newest unbilled period in the subscriber’s billing cycle to accept this record (permissions required): In CostGuard Client, select Applications/ BackOffice Management/ RateBill/ RateBill Request Center; click Bill Periods; right-click on the current unbilled bill period for the cycle of this service and select Properties; under Bill Cycle Overrides, check End Grace, and enter a number of days appropriate to include this usage record.
Details
Each usage record is ‘guided’ to a billing period (database) based on that subscriber’s billing cycle and the call start time of the usage record. Each billing period has a start and end date (and grace days) that specifies the call start times that are allowed into that period. In this case, there was no appropriate billing period to send this usage record to, because the call start time of this usage was after any open billing period.