---
title: "IDI Platform Version 22.12 Details"
slug: "idi-platform-version-22-12-details"
updated: 2026-05-09T18:18:28Z
published: 2026-05-19T16:21:08Z
canonical: "help.idibilling.com/idi-platform-version-22-12-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 Version 22.12 Details

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

#### Change Orders

| **Functional Area** | **AR/FR** | **Description** |
| --- | --- | --- |
| Orders | FR 3411 | **Web Sales milestone 2 – enhancements for tendered transactions** This milestone (in combination with AR 9106 below) provides an enhanced web transaction experience and new starting block functionality. You can initiate an order, sale, or direct invoice transaction that requires a *retail location* and *register*. You can do this by either: - Configuring the specific register and location on the starting block. In this case the selected starting block sets the register/location for the transaction without user involvement. - Applying the location and register from the user’s specified *My Location* as set via the Orders web module application tray. Applying a register and its location to a transaction lets you: - Add a retail product according to its defined location availability, unit price and cost. When added, you can also apply or modify: - A retail discount (either manually or by a retail promotion). - Sales and/or use taxes based on the location. - An installment plan based on configured profiles and rules, when applicable. - Accept tender types for the calculated amount due now based on the location’s register policy. The system will prompt for additional tendering details, when applicable. - Have receipt or direct invoice generated for the transaction. - Email the generated receipt or direct invoice to the customer as a message or notification using IDI’s Communication web module. Leveraging these enhancements, you can use a transaction in the Orders web module to either sell, order, or direct invoice any post-paid billing and/or retail catalog item for any service or account. For details regarding the overall goal, objectives, and planned future deliverables for web sales, refer to the IDI Knowledge Center > IDI Updates > Upcoming Features page. > [!NOTE] > **Note:** > > If the starting block and/or direct invoicing solutions are not currently enabled in your system, functionality described above will not be visible in your system. |
| Product Catalog – Starting Block Configuration | AR 9106 | **Starting block enhancements for web sales** Starting block configuration is facilitated by these enhancements: - Configuration parameters are presented on two tabs for cleaner presentation – *Main* and *Policy* - The Policy tab includes options for receipt (sales) and invoice (direct invoice) presentation Details are provided in *Web Sales Milestone 2 – Tendered Retail Transactions*. |
| Service Number History | 9075 | **Accessing billing order ID from service number history** The ID associated to a billing order (BillingOrderID in web APIs or SystemOrderID in IDI Desktop Client) can now be accessed from the Service Number History for use in reporting. When a service number history record is generated by an order, the ID is now recorded and can be accessed via: - IDI Desktop Client Service Number History when you choose to view *all* columns. The new column is labeled *SystemOrderID*. - *ServiceNumberHistory* OData in the Customer Web Service includes a *BillingOrderID* column for use in the web/APIs. |
| Payment Processing | FR 3453 | **Support for Paymentus payment portal – milestone 1** Integrating the IDI platform with Paymentus and its PCI 3.0 compliant solutions enhances IDI’s *full-web front office experience*. With this milestone, Customer Care and OnlineBill are updated to leverage the digital-payment experience provided by Paymentus solutions. On implementing this solution Paymentus will maintain e-pay accounts, tokens, and payment-related activity. In this release, existing electronic payment touchpoints in Customer Care and OnlineBill use a Single Sign-on solution that seamlessly navigate you from these IDI applications to a corresponding Paymentus solution: From an account in Customer Care, you navigate to the Paymentus *Agent Dashboard* to: - Make a payment for either the current account balance or an installment plan payoff. - Add and manage digital wallets, payment accounts, and payment scheduling. - Search and view payment history. - Refund an existing payment. From an account in OnlineBill, you navigate to the Paymentus *Customer Portal* to: - Make a payment for either the current account balance or an installment plan payoff. - Add and manage digital wallets, payment accounts, and payment scheduling. - Search and view payment history. Maintaining synchronicity of payment-related information between the IDI platform and Paymentus is performed by: - A new scheduled job to create the *Paymentus Customer Information File*. This file contains account and billing details and is exported from the IDI platform to Paymentus. - API integration to update account balances and receive payment notifications. The notifications include completed payments and updates to payment scheduling. > [!NOTE] > **Note:** > > This functionality is not immediately available upon upgrading to the 22.12 release or later. Customers will need to coordinate with IDI Support/Account Management and Paymentus to properly implement this functionality. |

#### Resolved Known Issues

| Functional Area | PR | Description |
| --- | --- | --- |
| Customer Care | 84200 | **Lag time displaying *Account* menu options** On opening an account, options for the Account, Billing, Services, and Orders menus were slow to display. These menus now load more efficiently. |
| Customer Care | 84250 | **Balancestab error related to invoice category functionality** This issue is related to FR 3452 that provides support of invoice categories in Customer Care. This feature was originally introduced in CostGuard version 22.10 with enhancements provided in CostGuard version 22.11. An issue was found where the Customer Care balances page would error when there were less than five (5) configured aging buckets. Consequently, this functionality has been disabled by default The issue is fixed in the CostGuard 22.12 release; however, you’ll need to contact IDI Customer Support if you need the new invoice category functionality enabled in your system. |
| Orders – CostGuard Client | 84223 | **Timeout error on attempting to move a service (SQL Server 2014)** Users still on SQL Server 2014 experienced timeouts when attempting to move services on very large accounts. The performance of the *move service* function in the CostGuard Client has been improved to help avoid time outs. |
| Orders – CostGuard Client | 84224 | **Voided order not reverting back to original plan** In the CostGuard Client, if an order disconnected a product, and that order is voided, it should reconnect the product. This process was encountering an error since the deployment of AR 8763 in CostGuard version 22.06. AR 8763 introduced enhancements to reverse service fees originally introduced in CostGuard version 22.3. Specifically it provided two options to process reconnects based on your business requirements. - Restart Billing Charges updates the start date on recurring billing charges to the reconnection date, giving you an option to bill for a partial month of service and recoup additional revenue. - Exclude reconnecting previously invoiced one-time charges. The process has been corrected so that products disconnected via client-based orders will be reconnected upon voiding the disconnect order. |
| Orders – Web | 84261 | **Issue reconnecting services on accounts with multiple previous disconnect orders** There was an issue with reconnecting services where the account had more than one web-initiated disconnect order in its history. The logic would look at the oldest order and fail to reconnect services on the most recent disconnect order. The reconnect logic was updated to reconnect based on the most recent disconnect order on the account. |
| Orders Web | 84220 | **Unable to reconnect service without an EID** When reconnecting a service via the web, the Order web module did not allow the reconnection if the service did not have an EID. CostGuard Client allows services to reconnect with a null EID, which is the expected functionality. Reconnection of services in the web is now allowed when the EID is null. |
| CostGuard Client Journal/Follow-up Search | 84271 | **Unexpected search results and errors** - **On journal searches**, targeting specific *Entered By* or *Last Modified By* users was causing an error. This issue was addressed to no longer display an error. - **On follow-up searches**, targeting specific *Assigned To*, *Entered By*, or *Closed By* users, would return results for users within the groups for the selected users even when *Include Group Members* was not selected. This issue was addressed to only show follow-ups associated to the selected user(s) and not group members when *Include Group Members* is not selected. |
| RateBill | 84199 | **Billing operation runs longer than expected** The billing operation was inefficiently processing usage per service causing the operation to run long for the bill period. This affected accounts with high amounts of usage records for their services. The billing operation was updated to more efficiently calculate total usage for accounts and services when there is a high number of usage records. |
| RateBill | 84254 | **Error on prorated product charge dynamic charges** Prorated Product Charge dynamic charges would error the billing operation when processing contributing products that start before the bill period and end during the bill period. The billing operation has been updated to handle this scenario. |
| Inventory | 84264 | **Inventory Automatic Updates scheduled job times out** The performance of the Inventory Automatic Updates scheduled job has been enhanced when updating the status of MINs and Service Numbers to either *Assigned* or *Aging*. |

#### Platform System Deployment Updates:

| Module | Target Deployment Updates |
| --- | --- |
| N/A |  |