About Customer Settlement Transactions

Customer settlement transactions represent credits that will be applied to customer's bill based on all of the events in which the customer participated during a given time period. In other words, customer settlement transactions represent the total of all of the customer's event settlement calculations for a given time period.

Customer settlement transactions are created upon requests from a customer information system. Customer settlement transaction requests are sent in a file which is processed by a batch process which creates the individual customer settlement transactions. Customer settlement transaction requests include the metered service, the start and end date for the requested time period, and the type of request. These requests are typically sent on an annual basis (such as at the beginning or end of the year), but customer settlement transactions are also created in the following specific situations:

• Final Bill: When a customer moves out or stops their service, a customer settlement transaction is created and applied to their final bill.

• Re-Bill: When a customer is re-billed, the customer settlement transaction is recalculated for inclusion on the new bill.

• Customer Unenrollment: When a customer unenrolls from a program, a customer settlement transaction is created and applied to their next bill.

Customer settlement transactions are created in the "Pending" state. Pending event settlement transactions are processed by the Process Customer Settlement (X1-PRCS) batch process which transitions them the "Calculate" state, in which all of the customer's event settlements for the requested time period are collated and totalized. These are then sent back to the customer information system for application on the customer's bill.

Customer settlement transactions contain the following data:

• Metered Service ID: The metered service (customer) for which the customer settlement transaction was run.

• Start and End Date: The start and end date for the customer settlement transaction period.

• Status: The current status of the customer settlement transaction.

• Used on Bill: A flag that indicates (Yes or No) if the customer settlement transaction has been calculated.

• Event   Settlement Request Type: The type of customer settlement request. Valid options include Periodic, Final, Rebill, and Unenrollment.

• Calculation Details: 

  • Program ID: The program associated with the customer settlement.

  • UOM/TOU/SQI:  The unit of measure, time of use period, and service quantity identifier combination used to define the interval usage values used in the event settlement transactions that comprise the customer settlement calculation

  • Total Consumption Saved: The  total "kwh avoided" consumption saved for the customer settlement, calculated by adding together the individual event settlement transaction "Consumption Saved" values 

  • Total Actual Consumption: The total actual consumption for the customer for the customer settlement, calculated by adding together the individual event settlement transaction "Actual Consumption" values 

  • Customer Settlement Amount: The monetary amount for the customer settlement, calculated by adding together the individual event settlement transaction "Event Settlement Amount" values

  • Issues: One or more messages related to the customer settlement transaction.

System Data

Customer settlement transactions are based on the following system data:

Batch Processing

Customer settlement transaction processing is supported by the following monitor batch processes:

• Process Customer Settlement (X1-PRCS): Used to transition customer settlement transactions in the "Pending" state to the "Calculate" state.

• Retry Customer Settlement (X1-RTCS): Used to retry customer settlement transactions in the "Error" state.

Use the Batch Control portal to learn more about the parameters used by these batch processes.