Usage record call start time is before configured load date for all open billing periods.
Common Cause
This usage record is too old to bill.
Common Resolution(s)
Actions you can take to resolve the problem:
If the call start time of this usage record indicates that it is, in fact, too old to be billed, it can be left alone (it will eventually age and no longer be visible) - or it can be purged immediately if desired.
If this rarely occurs, the CDR may be bad or malformed. If so, it can be left alone (it will eventually age and no longer be visible) - or it can be purged immediately if desired.
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 record must be billed, change the billable range of the earliest unbilled billing period in the billing cycle. This is usually done by changing the start grace on the oldest unbilled period in the subscriber’s billing cycle to accept this record (permissions required): In CostGuard Client, selectApplications/ 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 Start 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 prior to any open billing period.