IDI Platform Version 25.5 Details

This extends the functionality delivered in the IDI platform 24.10 release to support privacy of calls and texts to covered hotline numbers (FCC mandate 23-96). The 24.10 release provided the ability to bypass/omit calls and text messages to and from covered hotlines during core usage processing.

The 25.5 release provides the following enhancements:

• A new Covered Hotlines bulk data import for importing the covered hotline numbers in FCC file format into the Orig-Term Number table in Admin Console. Previously, this could only be done through manual entry.
• The ability to store bypassed covered hotline usage (CDR091 Bypasses) in Document Storage to support confidential retention of the records.

The full functionality provided in the 24.10 and 25.5 releases is covered in this article in the IDI knowledge center: Maintaining Privacy of Covered Hotline Numbers.

The new bulk import specification for automated download of covered numbers is available here.

An enhancement to the Address Validation platform will help developers better track and correlate address validation results. This update modifies the Address Validation Management API such that when an address validation is successful, the API response will now include the unique identifier (ID) of the validation log record. Refer to the Address Validation management API documentation in the IDI knowledge center for details.

This feature adds support for the Caslix SMx provisioning provider. Refer the Calix SMx provisioning specification in the IDI Knowledge Center for details.

Note: Some users may experience a blank page when opening for the first time due to browser caching. Press Ctrl Shift R to refresh the page.

Validation has been added to identify Non-Invoice Responsible (NIR) accounts that attempt to rollup their balance to an Invoice Responsible (IR) parent which is not found. This prevents NIR accounts that are left in a tree without an IR parent from incorrectly rolling up their balance, when manually correcting the misconfigured tree. This maintains data integrity downstream with account balances and general ledger entries.

When running an invoice preview with an account that has an installment plan where the installment plan has been billed at least once, the prebill process was adding an additional installment plan payment on the preview. This was due to the process that generates and invoice preview and how installment plans are marked as billed.

This has been fixed.

The Invoice summary page in Customer Care had tax amounts that did not match between the tax summary and detail views. This was due to tax credits being filtered out of the detail view. Note: The taxes charged on the Invoice were correct. This was only an issue with the view.

The filters have been updated to include the correct tax credits in both the tax summary and detail views.

Taxes on finance charges were not listed at the account level in the Group Services by Class of Service optional invoice report.

The report now includes account-level taxes on finance charges,

There was a small difference between what was reported under the Invoice Tax Details in Customer Care and what was reported in the Invoice Tax Details Audit Report. This was due to in-advance recurring charges that had charges broken out on an invoice between arrears and in-advance.

This has been resolved in most cases. The Invoice Tax Details Audit Report sums the tax due for each tax assessed per charge on the Invoice. Customer Care displays a combination of aggregated totals grouped per tax and service. Small differences can still occur based on how an environment rounds taxes.

The service contact count on the Account Contacts page would initially show as 0 when the Customer and Billing Contact IDs were the same. The count would only update after clicking on the Service tab.

Now the accurate service contact count is displayed immediately upon loading the page.

With this update, the first payment type group you create is designated and labeled as the default. Also, the New button is now disabled until the first (default) group is saved. This prevents unintended creation of multiple default payment type groups. This update impacts users configuring Paymentus for the first time, ensuring a smoother setup process.

Some protection plans were not created in the IDI system when an order was submitted with two or more protection plans.

The logic for creating and enrolling in protection plans has been updated to avoid this issue.

The Communications application stopped saving daily utilization records.

The application now saves daily utilization records correctly by adding a unique ID to the ID field of utilization records before it saves them.