Requesting Bill Determinants for Summary Billed Accounts

Usage requests for summary billed accounts are handled as follows:
  • On the first night of the billing window usage requests are created for each SA and sent to Oracle Utilities Meter Data Management (MDM). MDM then checks what the next schedule read date is for each service point.
  • Assuming Oracle Utilities Meter Data Management owns meter read schedules; when batch billing executes Oracle Utilities Customer Care and Billing (CCB) cannot determine whether a summary account’s service agreement should be included on the bill or not.
  • If MDM determines that an SA/usage subscription should be skipped from billing, it notifies CCB by including a skip indicator and reason on the usage response, as well as the SA’s next scheduled read date. This date is captured as a MDM Next Scheduled Read Date characteristic on the SA, and the usage request is cancelled. The system still attempts to complete the bill since this might be the last outstanding usage request for the bill
  • When billing next runs, the base Get bill segment consumption using a usage request algorithm first checks if the SA should be skipped as follows (Note that this check is also performed in first billing run):
  • Get the MDM Next Scheduled Read Date characteristic on the SA. If this date is after the bill segment end date, we’ll skip the SA from billing

If your implementation would like to wait until the bill cycle window end date before attempting to complete summary account’s bills, ensure that the Complete Summary Bill at End of Bill Cycle pre-bill completion algorithm is defined on customer class. This is useful if scheduled reads are expected in the bill cycle window, but not necessarily on the window start date.