---
title: "IDI Platform 24.9 Details"
slug: "idi-platform-24-9-details"
updated: 2026-05-09T18:17:57Z
published: 2026-05-19T16:07:16Z
canonical: "help.idibilling.com/idi-platform-24-9-details"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.idibilling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# IDI Platform 24.9 Details

#### [IDI Platform Version 24.9 Core Bulletin](https://cdn.us.document360.io/3f7f8ade-bcb1-4ec8-af25-0c0ad8601afb/Images/Documentation/IDI-Solution-24.9-Core-Release-Bulletin(1).pdf?sv=2026-02-06&spr=https&st=2026-11-14T10%3A50%3A00Z&se=2026-11-14T11%3A50%3A00Z&sr=c&sp=r&sig=FGXkTo7VD4mdBA4QIORdbPaL%2FspGgXi6LqRCUP4H8oo%3D)

#### Change Orders

| **Functional Area** | **AR/FR** | **Description** |
| --- | --- | --- |
| Customer Care | FR 3596 | **CPNI Authenticationenhancements** The following enhancements will support compliance with FCC title 47, CFR 64.2010: - **New configuration options for CPNI verification in CustomerCare** - Prompt for the CPNI Account Password (without displaying the password value) - Prompt for the answer to the CPNI Security Question (without displaying the answer) - **Hide Account Information**: During CPNI verification of an account, the account information will be shielded from the user. |
| Payment Processing Paymentus | FR 3606 | **Paymentus installment plan payoff date adjustment** Prior to this enhancement, installment plan payoffs posted immediately when the payoff was performed. As a result, the account would appear to have a large credit (negative balance) as the payment would hit the account immediately; however, installment plans would not be evaluated until billing ran. To remedy this, the posted date for installment plan payoffs is now set to one day before the next bill. The payment is initially created as an *unposted* transaction and not posted/applied to the account balance until the current date is the *posted date*. |
| Data Replication | AR 9344 | **Add Last Modified Date column to additional tables** This initiative was begun with AR 9155 in version 23.11 help data engineers analyze and troubleshoot issues where problems may occur during data transmission. This latest enhancement adds SQL triggers to populate a new *ct_LastModifiedDate* column in the tables listed below. The value will be set to the current date when the table is updated. - GCJFulfillmentReq - InventoryItemServiceNumber |

### Resolved Known Issues

| Functional Area | PR | Description |
| --- | --- | --- |
| Customer Care, Tickets & Communications | 84725 | **Select/deselect rows on grids not behaving correctly** These grids did not behave as expected when deselecting selected rows: - *Credit Usage Details* grid in Customer Care - *Tickets* grid in Tickets - *Bounced Emails* grid in Communications The following behavior would occur in this specific scenario: - Rows were selected on the current page. - You used the grid’s paging buttons to navigate away from and then back to the original page where rows were selected. - You unselected those rows, selected other rows and then invoked an action on those rows. In this case the system did not recognize the previously selected rows were unselected. Consequently, the action would be applied to the currently selected rows (as intended) *AND* the rows that were previously selected and now unselected (unintended). The only way to properly reset those rows was to refresh the page. These grids now handle grid selection changes correctly. |
| Orders | 84736 | **Orders using Bill Payment starting action unable to complete** When using a starting block with Start As action = *Bill Payment*, the system should first look at the register configured on the starting block, then if there isn’t one, look to the register assigned to the current user; however, it was only looking at the starting block register, and would throw the following error if there isn’t one: *Location does not support any Payment Applicable Tender Types*. Now the system uses the user’s current register if one isn’t configured on the starting block. |
| Bulk Data Import | 84737 | **Attributes not populating from the bulk data featureimport** When creating an order via the bulk data feature import, and using the StartingBlockID attribute to specify which starting block to use, order-level attributes were not being saved. This has been fixed. |
| Rating & Billing | 84732 | **Account Posting job failing with *StatusNotFound*error** The account posting scheduled job could error when the main job ran in under an hour and its cleanup job took longer. Account posting now properly tracks the completion state of both its jobs. |

#### Platform System Deployment Updates:

| **Module** | **Target Deployment Updates** |
| --- | --- |
| No deployments scheduled |  |