> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/whats-new/release-notes/previous-releases/2026/april-2026-release.md).
# April 2026 Release
{% hint style="warning" %}
This is a Custom Release. Feature availability depends on configuration and rollout status. Some features listed above may not be visible in your environment if they are part of a staged or custom deployment. Please contact your support representative to confirm enablement.
{% endhint %}
### **Added “Custom Description” Column to the Data Export Centre**
**Overview:**
The Data Export Centre enables users to extract data from various modules for reporting, analysis, and external processing. Within the **Purchase Order Detail** export, users can select specific columns to control the data included in the output.
With this enhancement, the **Custom Description** field is now available as a selectable column in the **Purchase Order Detail** export, improving data visibility and usability in exported reports. The field is automatically populated based on the item associated with each line and is sourced from **Item → Other Attributes → Custom Description**.
***
***
**Key Enhancements:**
* **Enhanced Data Visibility:** Provides direct access to item-level custom descriptions within Purchase Order exports without requiring additional lookups.
* **Improved Reporting Accuracy:** Ensures exported data reflects item-specific contextual information used in business operations.
* **Seamless Integration with Existing Export Options:** The field behaves like any standard column and is compatible with all export methods (**Export to Local, Export to FTP, Export to Email, and Scheduled Export**).
* **Reduced Manual Effort:** Eliminates the need to manually map or merge item attributes after export.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Admin → Item → Item Centre** and open an Item record.
**Step 2:** In the **Other Attributes** tab, enter the required value in the **Custom Description** field and save the Item record.
**Step 3:** Navigate to **Menu → Purchase → Purchase Order** and create a new Purchase Order using the same item.
**Step 4:** Navigate to **Menu → Utilities → Data Exports → Data Export Centre**. In the **Search By** dropdown, select **Purchase Order Detail**.
**Step 5:** View the required Purchase Order record in the grid. The **Custom Description** column displays the value automatically populated from **Item → Other Attributes → Custom Description** for the corresponding item.
***
### **Enhanced Profitability Calculation with Configurable Cost Type in Sales Orders**
**Overview:**
The **Show Profitability** option in **Sales Orders** and **Estimates** provides visibility into profit margins, total cost, and total profit, helping users evaluate the financial viability of transactions.
Previously, the profitability calculation relied on a fixed cost source **(Average Cost),** which could lead to inconsistencies when businesses needed to evaluate margins based on **Standard Unit Cost**—especially for forward-looking scenarios such as replenishment planning.
With this enhancement, the profitability calculation is now aligned with the configured **Item Profitability Cost Type**, ensuring consistent and accurate cost evaluation based on business preference.
***
**Configuration Details:**
* **App Config Name:** Item Profitability Cost Type
* **Type:** Single-select Dropdown
* **Configuration Location:** Menu → App Config → General → **Item Profitability Cost Type**
* **Available Options:**
* Average Cost
* Standard Unit Cost
***
**Functionality:**
This configuration determines the cost basis used in profitability calculations within the **Show Profitability** view.
* When **Average Cost** is selected, the system calculates profitability using the item’s average cost.
* When **Standard Unit Cost** is selected, the system calculates profitability using the item’s standard unit cost.
***
**Key Enhancements:**
* Introduced a new app configuration, Item Profitability Cost Type, allowing users to control the cost basis used in the Show Profitability view for Sales Orders and Estimates.
* Users can now choose between Average Cost and Standard Unit Cost for profitability calculations based on business requirements.
* The system now correctly fetches and applies the configured cost type value while calculating **Total Cost**, **Total Profit Margin**, and **Total Profit Value**.
{% hint style="info" %}
This configuration currently does **not** impact profitability calculations in the **Invoice module** or **Reports module**.
{% endhint %}
***
### **Tax Adjustment Handling Enabled in Linked Bills**
**Overview:**
This enhancement improves how **Tax Adjustments** are handled in linked (child) bills by allowing controlled updates while maintaining the integrity of the parent transaction.
Previously, any modification to a linked bill—including tax adjustments—was restricted, displaying the message: **“Bill details cannot be changed in the linked bill. Parent bill number: #...”**
With this update, users can now add or update **Tax Adjustment lines** in linked bills, while changes to core financial data remain restricted.
***
**Feature Added:**
Users can add or modify **Tax Adjustment lines** in the linked bills.
***
**How It Works:**
**Step 1:** Create a linked bill from a parent bill and open the linked (child) bill where you want to perform updates.
**Step 2:** Navigate to the **Tax Adjustments** tab in the **Bill Details** section. Select a tax adjustment item, enter the adjustment amount and memo, then click **Add**.
**Step 3:** The update is successfully saved, and the adjustment is reflected in the bill total.
***
**Key Enhancements:**
* **Controlled Edit Permissions:** Only tax-related changes are allowed; changes to item and expense lines remain restricted.
* **Tax Adjustment Flexibility:** Enables adding and updating Tax Adjustment lines in linked bills.
* **Data Integrity Maintenance:** Prevents discrepancies between parent and linked bills.
* **Textual Updates Allowed:** Users can update fields such as Memo without any restrictions.
***
### **Order Type Added to Purchase Order Header**
**Overview:**
This enhancement introduces the **Order Type** field at the Purchase Order header level, allowing users to directly view and assign an order classification while creating or reviewing a purchase order. This improves visibility and ensures consistency between manually created purchase orders and those uploaded via CSV.
***
**Key Enhancements:**
* Added **Order Type** field to the **Purchase Order Header**.
* The selected Order Type is now visible directly within the PO header view.
* Ensures alignment with existing upload functionality using the **PoSubTypeName** field.
* Enables consistent categorization of purchase orders across manual entry and upload processes.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Purchase → Purchase Order** and create a new purchase order or open an existing one.
**Step 2:** In the **header section**, locate the **Order Type** field.
**Step 3:** Select the appropriate order type (e.g., Supply, Wholesale, Retail, etc.) based on your classification setup.
**Step 4:** Save the purchase order. The selected Order Type will now be displayed in the PO header and used for categorization and reporting.
**Step 5:** If creating purchase orders via upload, populate the **PoSubTypeName** field in the template with a valid order type name.
The system will map this value to the **Order Type Name** and **Order Type Code** fields of the newly created purchase order, as reflected in the **Purchase Order Centre**.
***
### **App Config: Make Phone Number Optional for Customer**
**Overview:**
This enhancement introduces a new app configuration that allows users to control whether the **Main Phone** field is mandatory during customer creation and updates. It provides flexibility for scenarios where phone numbers may not always be available and is applied consistently across UI, upload (CSV), API, and B2B customer updates.
***
**Configuration Details:**
**App Config Name:** Make Phone Number Optional for Customer
**Configuration Location:** Menu → App Config → General → **Make Phone Number Optional for Customer**
***
**Functionality:**
**When App Config Is Enabled:**
* The **Main Phone** field becomes optional during customer creation and updates.
* Customer records can be saved even if the Main Phone field is left blank.
**When App Config Is Disabled:**
* The **Main Phone** field remains mandatory for all customer records.
* The system will not allow saving a customer without a phone number.
***
**How It Works:**
**Step 1:** Navigate to **Menu → App Config → General** and enable the app config **“Make Phone Number Optional for Customer.”**
**Step 2:** Go to **Menu → Sales → Customer Section → Customer Centre**, then open an existing customer or create a new one.
**Step 3:** In the **Contact Info** tab, leave the **Main Phone** field blank and update the record. The system will allow the customer record to be saved successfully without a phone number.
***
### **Addition of UOMCode Field in Item Customer Mapping Upload**
**Overview:**
This enhancement introduces support for UOM-based Item Customer Mapping uploads when the **Multi UOM** feature is enabled in App Module Access. A new mandatory field, **UOMCode**, is added to the upload template to ensure mappings are accurately created or updated based on the specified unit of measure.
This prevents ambiguity in cases where the same item is mapped differently for a customer across multiple UOMs.
***
**Key Enhancements:**
* When Multi UOM is enabled, the **UOMCode** field is available and mandatory in the **Item Customer Mapping** **upload template** to uniquely identify each mapping.
* The upload template dynamically changes based on configuration. If Multi UOM access is disabled, the **UOMCode** column is not included.
* The system validates mappings using a unique combination of Customer, Item, and UOM. During upload, if a matching combination already exists, the existing mapping is updated; if not, a new mapping is created.
* Uploaded UOM values are reflected across the system, including the Item Customer Mapping Centre, exported data, and Advanced Search filters.
***
**How It Works:**
**Step 1:** Enable the **Multi UOM feature** from **App Module Access**. Once enabled, download the Item **Customer Mapping upload template**, which will now include the **UOMCode column**.
**Step 2:** Populate the template with Customer, Item, Customer Item details, and the required UOMCode for each mapping. Ensure that the UOMCode corresponds to a valid unit of measure configured in the system.
**Step 3:** Upload the completed file through the **Batch Upload Item Customer Mapping** module.
**Step 4:** The system validates each row based on the Customer, Item, and UOM combination. Since no matching mapping existed, a new mapping was created in the **Item–Customer Mapping Centre**.
***
### **Item Description Column Added in Item Vendor Mapping Centre**
**Overview:**
This enhancement introduces a new **Item Description** column in the **Item Vendor Mapping Centre**, allowing users to view item descriptions directly alongside vendor mapping details. This eliminates the need to navigate to the Item module for additional context and improves visibility when managing item-vendor relationships.
***
**Key Enhancements:**
* A new **Item Description** column is added to the **Item Vendor Mapping Centre** grid.
* Displays the item’s description as defined in the Item master, reducing the need to navigate to the Item module to view item details.
* Provides better visibility and context while reviewing vendor mappings.
* Available within the grid view and supports standard listing behavior alongside existing fields.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Purchase → Item Vendor Mapping → Item Vendor Mapping Centre**.
**Step 2:** In the **Item Vendor Mapping grid**, the **Item Description** column is available alongside existing fields such as **Item Number**, **Vendor**, **Price**, and **Discount**.
**Step 3:** The Item Description displayed in the **Item Vendor Mapping Centre** is fetched from the **Description** field in the **Primary tab** while creating the item.
***
### **Addition of Project/Class Column in Inventory by Location**
**Overview:**
This enhancement introduces the **Project/Class Name** column in the Inventory by Location module, enabling users to view inventory distribution segmented by project or class directly within the grid. This eliminates the need to cross-reference project/class information from Sales Orders and Purchase Orders, improving visibility into inventory allocation across different business segments.
***
**Key Enhancements:**
* A new **Project/Class Name** column is added to the Inventory by Location grid, displaying the project or class associated with each inventory record.
* The column value is derived from the **Project/Class** assigned at the **header level of transactions** such as **Sales Orders**, **Purchase Orders**, and **Estimates**, and is reflected in the associated inventory records.
* Users can include or exclude the **Project/Class Name** column using the column visibility options.
* The **Project/Class Name** field is now available in **Advanced Search**, allowing users to filter inventory records based on specific projects or classes.
* Enhances traceability and reporting by providing project-level visibility of inventory across locations.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Inventory → Inventory by Location → Inventory by Location Centre**.
**Step 2:** In the inventory grid, view the **Project/Class Name** column alongside existing fields such as **Item Number**, **Location**, and **Available Quantity**.
**Step 3:** You can also use **Advanced Search** to filter inventory by selecting **Project/Class Name** and applying the desired condition to refine results.
***
### **Expiry Date Column Added in Wave Line Allocation**
**Overview:**
The Wave Line Allocation sub-form in the Wave Centre now displays the **Expiry Date** column whenever **LPN (License Plate Number)** is enabled, regardless of whether the **WMS module** is enabled or disabled.
This enhancement improves inventory visibility during wave allocation by allowing users to view expiry information directly from the allocation details screen without depending on WMS functionality.
***
**Key Enhancements:**
* Displays the **Expiry Date** column in the Wave Line Allocation sub-form when LPN is enabled.
* The Expiry Date column is now available even if the WMS module is disabled.
* Improves visibility of inventory expiry information during wave allocation and picking.
* Helps users identify and allocate inventory based on expiry details more efficiently.
* Supports better inventory tracking for LPN-managed inventory.
***
**How It Works:**
**Step 1:** Navigate to **Menu → App Config → Warehouse** and enable the app config **"Enable LPN Tracking".**
If **LPN Tracking** is enabled, only then will the **Expiry Date column** be available in the **Wave Line Allocation sub-form**.
**Step 2:** Go to: **Menu → Warehouse → Picking → Wave Centre**. Double-click on the required Wave record to open the **Wave** sub-form.
**Step 3:** In the Wave sub-form, click on the **Search** icon available under the **Action** column. This opens the **Wave Line Allocation** sub-form.
**Step 4:** The **Expiry Date** column will now be visible in the allocation grid.
***
### **Introduced Item Category Column in the Inventory Adjustment Centre**
**Overview:**
The **Inventory Adjustment Centre** now includes an **Item Category** column, allowing users to view the category associated with adjusted inventory items directly from the adjustment listing screen.
This enhancement improves inventory visibility and reporting by making it easier to identify and analyze inventory adjustments based on item categories without opening individual adjustment records.
***
**Key Enhancements:**
* Added a new **Item Category** column in the Inventory Adjustment Centre grid.
* Displays the category assigned to the item associated with the inventory adjustment.
* Helps users quickly identify adjustments related to specific item categories.
* Improves inventory analysis, filtering, and reporting at the category level.
***
**How It Works:**
**Step 1:** Go to **Menu → Inventory → Inventory Adjustment Centre**.
**Step 2:** The Inventory Adjustment Centre grid now displays the **Item Category** column. This column shows the category associated with the adjusted inventory item.
**Step 3:** Users can now filter adjustments based on the associated item categories directly from the Inventory Adjustment Centre using the **Advanced Search option**.
***
### **Enhanced Short Inventory Notifications to Exclude Inactive Items from Re-Order Alerts**
**Overview:**
The **Short Inventory Email Notification** process has been enhanced to exclude **inactive items** from notification emails. Previously, both active and inactive items were included in short inventory notification emails, which could result in unnecessary reorder recommendations for discontinued or inactive inventory items.
With this enhancement, the system now validates the item’s active status before including it in the Short Inventory Notification email.
This behavior applies across all available options of the **Short Inventory Notification Trigger** configuration.
***
**Configuration Details:**
* **App Config Name:** Short Inventory Notification Trigger
* **Location:** Menu → App Config → Inventory → Short Inventory Notification Trigger
* **Type:** Multi-select Dropdown
* **Available Options:**
* Re-Order and Short Qty
* Re-Order Point
* Re-Order Inc (On PO - Short Qty)
***
**Functionality:**
**When Re-Order & Short Qty Is Selected**
* Select **Re-Order Point** from the available options in the *Short Inventory Notification Trigger* app configuration.
* The notification email will be sent for items that have the “circle” icon added (i.e., items short by Re-Order Point), as well as items that are short even by 1 unit.
***
**When Re-Order Point Is Selected**
* Select **Re-Order Point** from the available options in the *Short Inventory Notification Trigger* app configuration.
* The notification email includes only items that are short by Re-Order Point, i.e., items that display the circular indicator icon in the Short Inventory Planner.
***
**When Re-Order Inc (On PO - Short Qty) Is Selected**
* Select **Re-Order Inc (On PO - Short Qty)** from the available options in the *Short Inventory Notification Trigger* app configuration.
* The notification email is triggered when the following condition is satisfied:\
**(On PO - Short Qty - ReOrder Qty) < 0**
Only **active items** are considered for notification emails. **Inactive items** are automatically excluded from the notification list regardless of the **selected option** above.
***
**How It Works:**
**Step 1:** Navigate to **Menu → App Config → Inventory** and select the **Re-Order Point** option in the **Short Inventory Notification Trigger** app configuration.
**Step 2:** Go to the **Short Inventory Planner** module and review the items marked with the circular indicator icon, which identifies items short by Re-Order Point.
**Step 3:** Trigger or wait for the Short Inventory Notification email process to run. The notification email includes only active items that are short by the Re-Order Point.
Inactive items are automatically excluded from the notification list, even if they satisfy the reorder point condition.
***
### **“Manufacturer” Field Added to Item Centre Batch Update**
**Overview:**
The Item Centre Batch Update functionality now supports the Manufacturer field, allowing users to assign or update the manufacturer for multiple items simultaneously directly from the Item Centre.
This enhancement improves operational efficiency by eliminating the need to manually open and update each item individually. It also ensures consistent manufacturer mapping across inventory items.
***
**Key Enhancements:**
* Allows users to update the Manufacturer field for multiple selected items in a single action.
* Updated manufacturer values are reflected in the Manufacturer column in the Item Centre.
* Manufacturer updates are automatically synced with the Manufacturer field under the Other Attributes tab in the Item module.
* Supports filtering items using the Manufacturer field through the Advanced Search option.
***
**How It Works:**
**Step 1:** Go to **Menu → Admin → Item → Item Centre** and select one or more items whose **Manufacturer value** you want to update.
**Step 2:** Click **Options → Batch Updates**.
In the **Batch Update subform**, select **Manufacturer** from the Column Name dropdown. Enter the required Manufacturer in the Value field and click **Update** to apply the selected Manufacturer to all chosen items.
**Step 3:** The updated Manufacturer value is displayed in the Manufacturer column in the **Item Centre**.
It is also reflected in the Manufacturer field under the **Other Attributes** tab of the **Create/Edit Item page.**
***
### **UPC Column Added in RMA Line and RMA Details**
**Overview:**
The RMA module now includes a UPC column in both the **RMA Centre (RMA Line view)** and the RMA Details section of the **Create/Edit RMA** page. This enhancement improves item identification and return tracking by allowing users to view and search RMAs using UPC values directly from the RMA screens.
Additionally, the UPC value entered or fetched in the RMA Details section is now retained after saving the RMA, ensuring consistent visibility of item identification data throughout the return process.
***
**Key Enhancements:**
* Added a UPC column in the RMA Centre when the Search By option is set to RMA Line.
* Added a UPC column in the RMA Details table of the Create/Edit RMA page.
* UPC values are now retained in the RMA Details section after saving the RMA.
* Users can search and filter RMAs using UPC through the Advanced Search option in the RMA Centre.
* Improves item traceability and simplifies return item identification during RMA processing.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Sales → Credit & Deposit → RMA** and open or create an RMA record. In the **RMA Details section**, the **UPC column** is now available for the added item lines.
**Step 2:** Go to **Menu → Sales → Credit & Deposit → RMA Centre** and select **RMA Line** from the **Search By** dropdown.
The UPC column is displayed for RMA line items. If the column is not visible, users can enable it using the grid column selection icon.
**Step 3:** Users can also use the **Advanced Search option** in the **RMA Centre** and select **UPC** as the search field to filter RMA records based on UPC values.
***
### **Enable Daily Invoice Emails alongside Ship Confirmation Emails**
**Overview:**
A new app configuration, **Enable Separate Invoice and Shipping Confirmation Emails**, has been introduced to allow Daily Invoice Emails and Ship Confirmation Emails to function independently.
Previously, when a Ship Confirmation Email was sent for an invoice, the system automatically marked the invoice as emailed. As a result, the invoice was excluded from the Daily Invoice Email process.
With this enhancement, users can now configure the system so that sending a Ship Confirmation Email does not prevent the invoice from being included in the Daily Invoice Email schedule. This ensures customers can receive both email types independently when required.
***
**Configuration Details:**
**App Config Name:** Enable Separate Invoice and Shipping Confirmation Emails
**Configuration Location:** Menu → App Config → Sales → **Enable Separate Invoice and Shipping Confirmation Emails**
***
**Functionality:**
**When the App Config is Enabled:**
* Ship Confirmation Emails and Daily Invoice Emails work independently.
* Invoices are still included in the Daily Invoice Email process even if a Ship Confirmation Email has already been sent.
* Sending a Ship Confirmation Email does not update the Emailed? flag for Daily Invoice Email tracking. The **Emailed?** flag is updated only after the Daily Invoice Email is successfully sent by enabling **“Enable Daily Invoice Email”.**
**When the App Config is Disabled:**
* The system follows the existing combined email behavior. When a Ship Confirmation Email is sent, the invoice is marked as emailed.
* Invoices that receive Ship Confirmation Emails are excluded from the Daily Invoice Email process.
***
**How It Works:**
**Step 1:** Navigate to **Menu → App Config → Sales** and enable the following app configs:
* **“Enable Daily Invoice Email”**
* **“Automatically Send Ship Confirmation Email When Invoice Is Marked As Shipped”**
* **“Enable Separate Invoice and Shipping Confirmation Emails.”**
**Step 2:** Go to **Menu → Sales → Invoice** and create an invoice.
**Step 3:** Click on **Options** and select **Mark As Shipped**. The system automatically sends the **Ship Confirmation Email** to the configured [**Shipment Notification email address**](broken://pages/Tv8fTQZy6afywWQUxVwq).
**Step 4:** In the **Invoice Centre**, the **Ship Confirmation Email Sent?** and **Ship Confirmation Email Sent At** fields track the Ship Confirmation Email activity, while the **Emailed?** column remains unmarked.
**Step 5:** Now, the **Daily Invoice Email** is sent at the time configured under the app config **“Daily Invoice Email Time.”**
**Step 6:** Once the email is successfully sent, the **Emailed?** flag in the **Invoice Centre** is updated to true.
***
### **ASN Custom Fields Visibility Added in Item Inventory Snapshot**
**Overview:**
The Item Inventory Snapshot module has been enhanced to display ASN (Advanced Shipping Notice) Custom Fields within the In Receiving Details view.
Previously, ASN Custom Field information configured through the Custom Field Definition module was not visible in the Item Inventory Snapshot → In the **Receiving Details** section. Users could only view ASN quantity and receiving-related information without access to the associated custom field values.
With this enhancement, all configured ASN Custom Fields are now displayed directly in the In Receiving Details grid for the corresponding ASN records. This provides users with better visibility into incoming inventory details and allows important ASN-specific information to be reviewed directly from the Item Inventory Snapshot module without navigating back to the ASN Centre.
***
**Key Enhancements:**
* Custom Fields configured for the ASN transaction type are automatically reflected in the In Receiving Details grid of the Item Inventory Snapshot module.
* Users can now review ASN Custom Field values directly while analyzing incoming inventory quantities.
* Any updates made to ASN Custom Fields are automatically reflected in the Item Inventory Snapshot receiving details.
* Improves visibility and traceability for incoming inventory associated with ASN records.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Admin → Custom Field Definition → Custom Field Definition Centre** and review the existing Custom Fields created for the **ASN transaction type**.
**Step 2:** If no Custom Fields are defined for the ASN transaction type, create the required Custom Fields from the **Custom Field Definition module**, such as **Text**, **Number**, **List**, **Date**, **Multi-line Text**, or **Multi-Select List**, and save the configuration.
**Step 3:** Go to **Menu → Warehouse → ASN Centre**. Right-click on an ASN record and select **Update Custom Fields**.
Enter values for the configured ASN Custom Fields and save the record.
Double-click on the ASN record and select the **Custom Fields** tab to view the updated details.
**Step 4:** Navigate to **Menu → Inventory → Item Inventory Snapshot** and search for the **item** and **store** associated with the ASN.
**Step 5:** Click on the **In Receiving** quantity for the item to open the **In Receiving Details** view.
**Step 6:** The system displays the ASN records associated with the item, along with all **configured ASN Custom Field columns** and values in the **In Receiving Details grid**.
***
### **Introduced Default Discount Account Configuration in Bill Payment Page Defaults**
**Overview:**
The Bill Payment module has been enhanced to support configuring a **default Discount Account** through the **Page Defaults** settings. Previously, users were required to manually select the Discount Account each time a discount was applied to a bill payment.
With this enhancement, users can now configure a default Discount Account directly from the Bill Payment Page Defaults configuration. Once configured, the selected Discount Account is automatically populated in the Add Discount pop-up while applying discounts to bills. This helps streamline the bill payment process, improves consistency, and reduces repetitive manual selection.
***
**Key Enhancements:**
* Added a new Discount Account field in the Bill Payment Page Defaults configuration.
* The configured Discount Account is automatically populated in the Add Discount pop-up during bill payment processing.
* Eliminates the need to manually select the Discount Account each time a discount is applied.
* Helps maintain consistency in discount accounting entries.
* Improves efficiency and reduces manual errors during bill payment processing.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Purchase → Payment → Bill Payment** and open the **Bill Payment** module.
**Step 2:** Click on the **vertical ellipsis (⋮)** in the top-right corner of the page and select **Page Defaults**.
**Step 3:** A **Default Configuration pop-up** opens. Select the required **Discount Account** in the Discount Account field and click Save.
**Step 4:** Click on the value under the **Discount column** for a bill record. The **Discount Account** field in the **Add Discount pop-up** is automatically populated with the configured value from the **Page Defaults**.
**Step 5:** Enter or update the **Discount Account** as required and click **Apply Discount** to apply the discount to the bill payment.
***
### **Efficient Bulk Removal of Item Customer Mappings**
**Overview:**
Users can now delete multiple item customer mappings simultaneously from the **Item Customer Mapping Centre** using the newly added **Batch Delete** functionality. Earlier, mappings could only be removed individually, which made cleanup and maintenance difficult when working with large datasets.
This enhancement streamlines the management of outdated, duplicate, or incorrect item customer mappings and improves overall database maintenance efficiency.
***
**Key Enhancements:**
* Added a **Batch Delete** option under the **Options** menu.
* Enabled multi-record selection using checkboxes in the Item Customer Mapping Centre.
* Reduced manual effort by allowing multiple mappings to be deleted in a single action.
* Improved the cleanup and maintenance of item customer mapping records.
***
**How It Works:**
**Step 1:** Navigate to **Menu → Admin → Item Customer Mapping → Item Customer Mapping Centre**.
**Step 2:** Select the required item customer mapping records using the checkboxes available against each record.
**Step 3:** Click on the **Options** button and select **Batch Delete**.
**Step 4:** Confirm the deletion action to remove the selected item's customer mapping records from the system.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.xorosoft.com/whats-new/release-notes/previous-releases/2026/april-2026-release.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
