2025-13

Iteration: 2025-13

October 20th, 2025

Whats New?

Drop Request Queue →

Improvements

Change the delimiter used in the Drop Request template when submitting drop transactions to the ECI Billing System.

ETF amounts can now be customized within the Drops Management

Revamped Pricing Matrix login portal.

Added “Class” filter to Autoresponders.

Enhancements for customer data syncing between OpsAdmin and the ESG Billing System

Affiliates: Feature to set commissions per commodity

UX Improvement: Single list multiselect component for Available vs Associated areas of the system.

Added multiselect dropdown component to screens that were missing it.

Fixes

Fixed error message at the time of saving a dynamic template.

Adjusted Quick Enrollments as it was not loading correctly.

Solved error on Plans Manager when creating a commercial plan under a Utility with Autorenewable plans turned on.

Resolved issue that prevented PPUs and Renewals from being exported to the P2C Billing System.

UI Correction in the Change Plan functionality from Enrollment Details where users could not switch to the desired plan.

Adjustment for Affiliate TOU plans that did not inherit interval data from their parent plan.

Modified how the system validates if a notification has been previously sent for a given customer.

Minor corrections in System Logs. Added login option for existing customers in the web enrollment journey.

Fix for PPU UI where some profiles were not able to select a plan version from the dropdown.

Adjusted how billing address data is updated when syncing with the ECI Billing System.

Updated colors for Usage Chart when getting usage data from SMT.

Enrollments API: Fixed “Internal Server Error” when trying to retrieve plans through the plans/for-wizard endpoint.

Corrected how the Name Key is generated for customers whose last names are less than 4 digits to prevent issues in the Sales Importer.

Adjustment for System Setup RESTFUL API URL when connecting to the ESG Billing System.

Fixed bug in Web Enrollment Journey that forced customers to input non mandatory fields when accessing the site through certain browsers.

Corrected issue in MyAccount where an incorrect Past Due amount was displayed when retrieving data from the ESG Billing System using REST.

Resolved error on Renewal Importer that prevented users from renewing existing accounts.

Improved validations in the Renewal Importer to stop records with no contract dates on them.

Fix in Plans Manager for Autorenewable plan dropdown that did not populate with data.

Solved error in Enrollment Details that prevented users from doing changes to an enrollment.

Correction for issue at the time of generating PDF files.

Addressed a discrepancy between the MyAccount usage graphic and the one from Customer Details (Customer Support).

Adjusted validation verbiage when adding an invalid traunch in Usage Credits.

Adjustment for New Incoming Enrollment filter that did not work in the Sales Importer.

Fix for PPU UI where the dropdowns were not populating correctly.

Corrected how traunches were calculated on Autoresponders when working with plans that have usage credits.

Revamped presentation of iCheck iframe as it occupied the full width of the iframe.

Pricing Matrix: Adjusted import process so it does not fail when the file's rate class is not in upper case.

Enrollments API: Modified how TOU and usage credit plan data is returned.

Major correction in System Setup so sites as well as the API are refreshed after making changes in settings.

Corrected multiple bugs in the Renewal process.

Added missing columns to the Datamart Service Agreement Band Detail database table that caused issues at the time of importing/refreshing datamart.

Fixed steps indicator in the Web Enrollment Journey.

Features & Fixes Details

Drop Request Queue

Some utilities allow a slight delay to inform the drops requested by customers. To take advantage of this, the REPs can retain drop requests for a few days before submitting them to the billing system to try and recover the customer before even generating the drop. With this new feature, instead of sending drop transactions straight to the Billing System, OpsAdmin sends these transactions to a queue where users can work through these transactions in an attempt to retain customers. To make use of this feature, 3 new roles were added to User Manager: Drop Requests Queue: Access, Drop Requests Queue: Release Requests, Drop Requests Queue: Cancel Requests.

Utility Manager

This release revamps the Drop Configuration section in Utility Manager, removing old unused fields and adding 2 new ones:

• Drop Request Hold Hours: Number of hours a drop request will be retained before sending it to the billing system. If this field remains empty, drop transactions are sent straight to the Billing System and they appear with a status that reads Released Automatically.
• Allow Customers To Cancel Drop During Hold Window: By enabling this checkbox, customers can cancel an already requested drop transaction through MyAccount.

Customer Support

When generating a drop transaction from Customer Support, the “Drop Request” UI now includes a “Flag for Review” checkbox as well as an area to insert notes:

The transaction is now visible on the Drop Request Queue with a Pending status. The request can only be sent to the billing system when the specified hours have passed by and the status is *Pending *OR when the drop status is Released, in spite of the configured delay.

Records are shown from older to newer and users can:

• Release Request: Submits the transaction to the billing system. It appears disabled if the record has already been exported to the billing system or the release date has been reached.
• Cancel Request: Changes the status to Cancelled. It appears disabled if the record has already been exported to the billing system or the release date has been reached.
• Massively release or cancel selected transactions.

Background Job Logic

The existing Import drop job that brings all the drop transactions from the Billing System to OpsAdmin now includes a validation so that if there is an incoming drop transaction from the Billing system for a record that already has a drop request, this drop request is Canceled.

The automated job that exports all the drop requests has been upgraded to handle multiple scenarios such as delayed drops, drops that have exceeded their release date, drops that should be submitted immediately, etc.

MyAccount

If a customer has requested to drop through MyAccount, now they have the option to cancel that request by clicking on the "Cancel Drop Request" button. This is only for those utilities with a Delay configured and when the transaction has not been submitted to the Billing System yet or previously cancelled.

Overwrite calculated ETF Amount in Drops Manager

Some contracts require early termination fees (ETFs) to be determined after the customer drops, based on factors outside the system. To support this, Ops Admin now provides a Custom ETF Type where the value is not predefined but entered manually at the time of drop by authorized users. This ensures accurate handling, clear communication to agents and customers, and maintains compliance with notice obligations.

To enter a custom ETF amount, users should have the role: Drop Management -> ETF Invoice Queue: Edit custom ETFs.

There is a new ETF Type in Plans Manager: “Custom”. When this Cancellation Fee Type is selected, the field “Cancellation Fee” is grayed out and no value can be input.

No ETF data is submitted to the Billing System when “Custom” is selected.

When displaying the ETF popup, if the customer is enrolled under a plan with Custom ETF, the calculation is shown as follows:

Users can click on the pencil icon to enter the actual fee **as long as the customer has a drop transaction associated. **The “Pending” label indicates that the ETF amount still hasn’t been entered by the user.

Note: Users that do not have the specific role to overwrite ETFs won’t be able to see the pencil icon.

Plans that have this type of ETF show “Customer” across the whole system, including Account Details (Customer Support), Web Enrollment Journey, Quick Enrollments, ETF Invoice Queue.

Replacement values that pertain to ETF data show “Custom” as well, for example: ARP_ETF, PLAN_ETF and any other dynamic field related to the ETF.

Drop Process

When an account tied to a Custom ETF is dropped, the following rules apply:

• If the drop transaction happens inside the ETF Window period, Rescission period or Plan Risk Free Period, the drop is sent directly to the Drop Archive.
• If the drop happens outside those periods and the ETF hasn't been set:
• The automation configured in System Setup regarding queues and ETF generation is ignored.
• Waiving and manually sending the transaction to the drop archive is allowed.
• In a scenario where the user chooses to massively send ETF Invoices and the drop isn't waived, it is skipped.
• The option to Send ETF Invoice is disabled.
• If the drop transaction happens outside those periods and the etf is already configured, all the logic works just like any other drops, including the utility threshold for 0/small ETFs.

Enhancements for customer data syncing between OpsAdmin and the ESG Billing System

The following enhancements apply to the integration with the ESG Billing System:

• When deleting a customer’s phone number in OpsAdmin, this phone number is deleted in P2C as well.
• The customer’s email address is updated in P2C’s Billing group as well. This only works when connecting via REST API. Integration via SOAP has an issue in this endpoint which ESG was not able to address.
• Billing Address fields are also updated when connecting via REST.

Affiliates: Feature to set commissions per commodity

Users can now define affiliate commissions for electricity or gas. The existing Commissions tab now shows two sets of data for the commodities. The values will be retrieved based on the affiliate plan commodity.