About Event Settlement Transactions

Event settlement transactions represent credits that will be applied to a customer's bill based on participation in an individual event. Note that event settlement transactions aren't applied directly to a customer's bill. A customer's event settlement transactions are totalized into Customer Settlement Transactions (see About Customer Settlements Transactions) which are applied to the customer's bill.

Event settlement transactions are created from "kWh avoided" data received from Oracle Utilities Analytics Insights.  Oracle Utilities Analytics Insights sends "kWh avoided" files containing the actual energy reduction achieved for the duration of an event for each customer. A batch process imports these files and creates business flags that capture the data for each metered service point. These business flags in turn create event settlement transactions. See KWH Avoided Business Flags for more information about how event settlement transactions are created from business flags.

Event settlement transactions are created in the "Pending" state. Pending event settlement transactions are processed by the Process Event Settlement (X1-PREVS) batch process which transitions the transaction to the "Calculate" state where the Event Settlement Calculation Rules defined for the program related to the event settlement transactions (See Understanding Event Settlement Calculation Rules for more information) are executed. Once the event settlement transaction calculations are complete, it's transitioned to the "Calculated" state.

The amount of an event settlement transaction is calculated by applying the Event Settlement Calculation Rules defined on the metered service's program to the "kWh avoided" values captured on the business flag. These rules apply interval prices to the "kWh avoided" interval values and total the results for the event. 

Event settlement transactions contain the following data:

• Program Subscription: The program subscription associated with the event for which the event settlement transaction was created

• Start Date/Time: The start date and time of the event

• End Date/Time: The end date and time of the event

• Parent Customer Settlement Transaction: The customer settlement transaction that is considered the "parent" of the event settlement transaction. (Note: Only populated after after customer settlement transaction request is received). 

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

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

• Calculation Details:

  • Metered Service Point: The metered service point for which the event settlement transaction was run.

  • Program Event: The program event for which the event settlement transaction was created.

  • Event Settlement Calculation Group: The event settlement calculation group containing the event settlement calculation rules executed as part of the event settlement transaction.

  • Line Description: A single line description of the event settlement transaction, used when 

  • 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 calculation. These are derived from the UOM/TOU/SQI defined on the business flag type of the business flag that created the event settlement transaction.

  • Interval Size: The size of the interval usage values, represented as hours:minutes:seconds (HH:MI:SS). This is derived from the Interval Size defined on the business flag type of the business flag that created the event settlement transaction. This should match the interval size used for interval price sets.  

  • Consumption Saved: The "kwh avoided" consumption saved for the event period, calculated by adding together the individual "kWh avoided" values for the event period

  • Actual Consumption: The actual consumption for the customer for the event period

  • Event Settlement Amount: The event settlement transaction's monetary amount, calculated by multiplying the individual "kWh avoided" interval values (from the "kWh avoided" business flags received from Oracle Utilities Analytics Insights) times the interval prices during the event. 

  • Intervals: Details of the interval values and prices used in the event settlement transaction calculation, including: 

    • Service Quantity Data Date/Time: The date and time of the interval "kWh avoided" value and price

    • Quantity: The "kWh avoided" value for the interval date and time

    • Service Quantity Interval Condition: The condition code of the "kWh avoided" value for the interval date and time

    • Price: The interval price for the interval date and time

    • Event Settlement Amount: The monetary amount for the date and time, calculated by multiplying the "kWh avoided" interval value times the interval price at the interval date and time 

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

Example

An event scheduled for 12:00 PM to 6:00 PM on February 11, 2023 results in the following "kWh avoided" values for a particular customer:

This represents a total "Consumption Saved" of 29.00. 

Later, the system receives the following price data for this event period:

When an event settlement transaction is calculated for this event, the details of the event settlement transaction would be as follows:

• UOM/TOU/SQI:  kWh

• Interval Size: 01:00:00

• Consumption Saved: 29.00

• Actual Consumption: 430

• Event Settlement Amount: 12.15

• Intervals:  

System Data

Event settlement transactions are based on the following system data:

Batch Processing

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

• Process Event Settlement (X1-PREVS): Used to transition event settlement transactions in the "Pending" state to the "Calculate" state.

• Retry Event Settlement (X1-RTEVS): Used to retry event settlement transactions in the "Issue Detected" state.

• Recalculate Event Settlement (X1-RCEVS): Used to recalculate event settlement transactions in the "Calculated" state. This is used in the case of a rebill or when updated "kWh avoided" data is received from Oracle Utilities Analytics Insights.

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