> 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/current-release/october-2026-release.md). # October 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 %} ### **Customer Name Search and Customer Group Support in Estimate Centre** **Overview** The Estimate Centre now supports searching estimates by Customer Name directly from the header-level search fields. Additionally, the Customer Group field is available in Advanced Search and the column selection, allowing users to filter estimates by customer group and display the corresponding information in the Estimate Centre. *** **Key Enhancements** * Customer Name Search: Added a Customer search field outside the filter options in the Estimate Centre, allowing users to search for estimates by customer name. * Customer Group in Advanced Search: Added Customer Group to the Column Name options in Advanced Search, enabling users to filter estimates based on customer group. *** **How It Works** Step 1: Navigate to **Sales → Customer Section → Customer Centre** and open the required customer record or create a new customer.
**Step 2:** Go to the **Other Info** tab and select the required customer group from the dropdown list in the **Customer Group** field.
**Step 3:** Click Update to save the changes.
**Step 4:** Create an estimate for the customer.
**Step 5:** Navigate to **Estimate Centre** and enter the customer name in the **Customer search field** to retrieve the estimates associated with that customer.
**Step 6:** Click **Advanced Search** and select **Customer Group** from the Column Name dropdown.
**Step 7:** Select the appropriate Operator, enter the customer group in the Value field, and click Find to retrieve estimates associated with customers assigned to that group.
*** ### **Added Download PDF Option in Print Modal** **Overview** A Download PDF option has been added to the modal that appears when users click Print. This allows users to download the selected document as a PDF directly from the modal. *** **Key Enhancements** * Added the Download PDF option to the Print modal across multiple centres and document workflows. * Supports downloading PDF reports for selected records, with single-select-only support in the ASN Centre. * Available across sales, purchasing, inventory, and financial modules, including batch download and batch report workflows where applicable. *** **How It Works** **Step 1:** Navigate to the **Sales Order Centre**, select the required record or records, and click **Print** from the **Options** menu to open the reporting modal.
**Step 2:** Select the required document template from the **Select Document Template** dropdown. **Step 3:** Click the dropdown arrow beside **Print Preview** to view the available options, and select **Download PDF** to download the selected document as a PDF.
*** ### **On SO (Draft) Quantity Details in Advance Variant Finder** **Overview** The **Advance Variant Finder** now displays an **On SO (Draft)** column next to **On SO Qty.** This enhancement allows users to view the quantity associated with draft Sales Orders for a product variant directly from the Advance Variant Finder, making it easier to review inventory commitments while creating or transferring orders. *** **Key Enhancements** * Added the **On SO (Draft)** column in the Advance Variant Finder. * Available in the following modules: * Create Sales Order * Create Purchase Order * Create Estimate * Transfer Sales Order * Transfer Purchase Order * Users can click the quantity displayed under **On SO (Draft)** to open the **On SO (Draft) Detail** pop-up. * The detail pop-up provides a breakdown of draft Sales Order quantities, including the customer, Sales Order number, quantity ordered, quantity shipped, ship-by date, and order date. *** **How It Works** **Step 1:** Navigate to **Sales Order Centre** and create a new Sales Order. **Step 2:** Click the **Advance Variant Finder** to open the **Product Variants Finder** pop-up.
**Step 3:** Locate the **On SO (Draft)** column displayed next to **On SO Qty.**
**Step 4:** Click the quantity displayed under **On SO (Draft)** to open the **On SO (Draft) Detail** pop-up.
Review the draft Sales Order details, including the customer, Sales Order number, quantity ordered, quantity shipped, ship-by date, and order date. *** ### **Wave Notes Update During Picking and Packing Slip Template Support** **Overview** The Notes functionality has been enhanced to allow users to update notes during picking without modifying the original **Sales Order Detail** Notes. When a Wave is created, the notes from the Sales Order Details are copied to the corresponding **Wave Details**. Any updates made to the Wave Detail Notes during picking are carried forward to the **Shipment** and **Invoice**, while the original Sales Order Detail Notes remain unchanged. Additionally, a **Packing Slip** template option has been added to the **Select Reporting Template** window when users select **Add to Email Queue** in the Create Invoice module. *** **Key Enhancements** * Notes entered while adding items to a Sales Order, which appear at the Sales Order Detail level, are copied to the corresponding Wave Details when the Wave is created. * Users can modify Wave Detail Notes during picking without changing the original Sales Order Detail Notes. * Added the **Packing Slip** template option under **Select Reporting Template** when using **Add to Email Queue** in the Create Invoice module. *** **How It Works** **Step 1:** Navigate to the **Sales Order** module and create a new Sales Order. Click **Add Item** to add the required items.
**Step 2:** The **Item Details** pop-up opens. Enter the required notes in the **Item Notes** field and save the item.
The notes appear at the **Sales Order Detail level** under the **Notes** column.
**Step 3:** Release the SO and create a Wave from the Sales Order.
**Step 4:** Navigate to the **Wave Centre** and verify that the Sales Order Detail Notes have been copied to the corresponding Wave Detail Notes under the **Item Notes** column.
**Step 5:** Click the Wave record and select **Pick Wave**.
**Step 6:** During the picking process, click the cart icon under the **Action** column in the **Wave Lines** section.
**Step 7:** Update the **Wave Item Line Notes** as required. The changes are saved at the Wave Detail level.
**Step 8:** Proceed with the shipping process. The updated Wave Detail Notes are carried forward to the Invoice and displayed in the **Notes** column under **Invoice Details**.
**Step 9:** Verify that the original Sales Order Detail Notes remain unchanged after updating the Wave Detail Notes from the **Sales Order Centre** (search by **Sales Order Detail**).
*** ### **Flexible Error Handling for Product Imports** **Overview** A new **Reject File on Error** toggle has been added to the **Upload Products** functionality, allowing users to control how product uploads are processed when errors are encountered. When enabled, the entire file is rejected if any errors are found. When disabled, only valid records are uploaded, and a list of items containing errors is provided for review and correction. *** **Key Enhancements** * When the toggle is enabled, the entire file is rejected if any errors are encountered during upload. * When the toggle is disabled, valid records are uploaded while records containing errors are excluded. * This functionality is also available when uploading products through the **Job Scheduler**. *** **How It Works** **Step 1:** Navigate to the **Upload Products** module. Click **Download Template** to download the product upload template.
**Step 2:** Enter the product details in the template. For this example, two product records are included, with the **BasePart** field left blank for the second record.
**Step 3:** Upload the completed template and enable the **Reject File on Error** toggle. Click **Upload**. Since the file contains an error, the entire file is rejected, and no records are uploaded.
**Step 4:** Disable the **Reject File on Error** toggle and upload the same file again. Click **Upload**. The valid record is uploaded successfully, while the record containing the error is excluded. Click **Download File** to review the error details, correct the errors, and upload the failed record again.
*** ### **Tracking Inventory and Accounting While Goods Are in Transit** **Overview** Inventory in Transit Accounting enables businesses to track the accounting impact of inventory while goods are in transit from a Vendor to the receiving location. The functionality allows users to configure transit accounting at the Vendor level, determine whether accounting should be posted for individual Purchase Orders, and record accounting transactions when quantities are confirmed in transit through an ASN. When the goods are subsequently received through an Item Receipt or processed through a Bill, the corresponding transit accounting entries are reversed. *** **Key Enhancements** * Added the **Use in Transit Accounting** toggle and the **Default In Transit Asset Account** and **Default Transit Accrual Account** fields under the **Payments** tab on the **Create Vendor** page. * Both accounts are mandatory when the toggle is enabled and are cleared and disabled when it is turned off. * Added the **Post Inventory in Transit** and **Do Not Post Inventory in Transit** options under the **Other Info** tab on the Purchase Order page to control transit accounting for individual Purchase Orders. * When **Post Inventory in Transit** is selected, the configured Vendor accounts are copied to the Purchase Order and carried forward to newly created ASN lines. * Added the **Confirm in Transit** action to the **Receive ASN** module, supporting full and partial quantity confirmations and generating the corresponding accounting transactions. * Transit accounting entries are reversed when an Item Receipt is created or a Bill is processed. Only previously confirmed quantities are reversed. * The functionality also supports partial confirmations, partial receipts, and multiple transactions while maintaining accurate outstanding balances and accounting references. * Prevents ineligible confirmations and quantity changes that could invalidate posted transit accounting. Closed and voided ASN lines cannot be processed again. *** **How It Works** **Step 1:** Navigate to the **Vendor** module and open the required Vendor record. Enable **Use in Transit Accounting** and configure the following accounts: * **Default In Transit Asset Account** * **Default Transit Accrual Account**
{% hint style="info" %} Both accounts are mandatory when the toggle is enabled. Ensure that the currency of the accounts matches the Vendor's currency. If the toggle is disabled, the account fields are cleared and disabled. {% endhint %} **Step 2:** Create or open a Purchase Order for the configured Vendor. Release the PO. Select one of the following options in the [**Inventory in Transit Accounting**](/xoroerp-1/purchase/vendor-section/vendor/inventory-in-transit-accounting.md) field available under the **Other Info** tab: * **Post Inventory in Transit:** Enables transit accounting for the Purchase Order. The configured Vendor accounts are copied to the Purchase Order. * **Do Not Post Inventory in Transit:** Disables transit accounting for the Purchase Order.
**Step 3:** Create an ASN from the Purchase Order.
If **Post Inventory in Transit** is selected on the Purchase Order, the transit accounting setting and configured accounts are copied to the newly created ASN lines. **Step 4:** Now, in the **Receive ASN** module, select the required ASN lines and use **Confirm in Transit** to confirm the quantities entering the in-transit stage. Enter the full or partial quantity and click **"Confirm”**.
Once the confirmation is completed, Xoro creates the corresponding accounting transaction: | Account | Debit | Credit | | -------------------------- | ----------- | ----------- | | Inventory in Transit Asset | ✓ |


| | Transit Accrual |


| ✓ | **Step 5:** The system tracks the confirmed quantity and its associated accounting references. You can view the related accounting transactions from the **ASN Centre** by navigating to **Options → Show Transactions**.
**Step 6:** Close the ASN. The goods are subsequently received through an **Item Receipt** or processed through a **Bill,** where the corresponding transit accounting entries are reversed.
The reversal transaction is: | Account | Debit | Credit | | -------------------------- | ----------- | ----------- | | Transit Accrual | ✓ |


| | Inventory in Transit Asset |


| ✓ | **Step 7:** You can view the related accounting transactions from the **Item Receipt Centre** by navigating to **Options → Show Transactions**.
*** ### **Table Column Interceptor Support for Item Inventory Snapshot** **Overview** Table Column Interceptor support has been added to the Item Inventory Snapshot module, allowing administrators to control the visibility of specific columns for individual users. This enhancement helps restrict access to customer and vendor information by hiding the relevant columns from selected users without affecting what other users can see. *** **Key Enhancements** * Added Table Column Interceptor support for the Item Inventory Snapshot – Summary, On SO Details, and On PO Details tables. * Enabled administrators to hide any selected column from the Summary table for specific users using the Table Column Interceptor. * Enabled administrators to hide any selected column from the On SO Details subform for specific users using the Table Column Interceptor. * Enabled administrators to hide any selected column from the On PO Details subform for specific users using the Table Column Interceptor. * Other users can continue to see the columns unless their own interceptor configuration hides them. *** **How It Works** **Step 1:** Navigate to the **Table Column Interceptor Centre** and create or configure an interceptor for the required Item Inventory Snapshot table. Select the appropriate entity: * **Item Inventory Snapshot – Summary** to control columns in the main Summary table. * **Item Inventory Snapshot – On SO Details** to control columns in the On SO Details subform. * **Item Inventory Snapshot – On PO Details** to control columns in the On PO Details subform.
**Step 2:** Add a custom script to identify the logged-in user and hide the required column by setting `DisplayColumnFlag` and `switchable` to `false`. Use the appropriate column name for each interceptor: * Summary: `DefaultVendorName` — hides the default vendor column.
* On SO Details: `CUSTOMER_NAME` — hides the customer column.
* On PO Details: `VENDOR_NAME` — hides the vendor column. Save the Table Column Interceptor after configuring the script for the required entity and user. **Step 3:** Open the **Item Inventory Snapshot** module and click the quantity in the **On SO** or **On PO** column to open the corresponding details subform.
For the user configured in the interceptor, the **Vendor** column will be hidden in the summary table.
Other users without the restriction will continue to see the **Vendor** column in the summary table.
**Step 4:** Now, click an **On SO** quantity in the Item Inventory Snapshot table to open the On SO Details subform. For the configured user, the **Customer** column will be hidden in the **On SO Details** table.
Other users without the restriction will continue to see the **Customer** column in the **On SO Details** table.
**Step 5:** Similarly, click an **On PO** quantity to open the On PO Details subform. For the configured user, the Vendor column will be hidden in the **On PO Details** table. *** ### **Improved Wave Allocation Using Location Class Priority and Configured Criteria** **Overview** Wave allocation has been enhanced with the **Ignore Pick Sequence & Location Name** option in the **Location Pick Sort** dropdown of the Wave Template. When selected, the system prioritizes inventory according to the order configured in **Location Class Allocation**, then applies the criteria and sorting order defined in **Add Criteria** within each location class. This ensures that inventory allocation follows the configured location class priority and criteria rather than Pick Sequence and Location Name. *** **Key Enhancements** * Added the **Ignore Pick Sequence & Location Name** option to the **Location Pick Sort** dropdown in the Wave Template. * Prioritizes inventory according to the order configured in **Location Class Allocation**. * Applies the criteria and sorting order defined in **Add Criteria** within each location class. * Ensures inventory allocation follows the configured location class priority and criteria when **Ignore Pick Sequence & Location Name** is selected. *** **How It Works** **Step 1:** Navigate to the **Wave Template** module and create a new Wave Template. **Step 2:** Configure the required allocation priority using the **Location Class Allocation** dropdown. **Step 3:** Select **Ignore Pick Sequence & Location Name** from the **Location Pick Sort** dropdown. **Step 4:** Use **Add Criteria** to define the required allocation criteria by specifying the **Type**, **Operator**, **Value**, and **Sort Type**, as applicable. **Step 5:** Save the Wave Template and select it when creating a wave for a Sales Order. **Step 6:** Ensure that the required item has available inventory in the location classes selected in the **Location Class Allocation** dropdown. **Step 7:** Create a wave and verify that inventory is allocated according to the configured **Location Class Allocation** priority, followed by the criteria and sorting order defined in **Add Criteria**. *** ### **Addition of Country of Origin Field to VAS Item Rules** **Overview** Enhanced VAS Item Rule Matching introduces a Country of Origin field in the VAS Item Rules section, allowing rules to be configured using an item's origin alongside other matching criteria. When multiple VAS item rules match a sales order line, XoroERP applies the rule with the maximum number of matching fields. If multiple rules have the same number of matching fields, the system uses a predefined field priority to determine which rule to apply. *** **Key Enhancements** * Added a new dropdown **Country of Origin** field to **VAS Item Rules** to support more specific rule matching. * When multiple rules match, the rule with the greatest number of matching fields is applied. * If multiple rules have the same number of matching fields, the system uses the following priority: * Country → State/Province → Item Number → Item Tags → Customer Tags → HS Code → Country of Origin *** **How It Works** **Step 1:** Navigate to the **VAS Item** module and create a new VAS Item. Enter the required details, including the VAS Item Name, Income Account, Expense Account, and VAS Cost Type. **Step 2:** Under **VAS Item Rules**, configure the following fields: * **Country:** Canada * **State/Province:** Alberta * **Item Number:** Crimson * **VAS Cost Type:** Fixed * **VAS Item Cost Amount:** 10 Click **Add VAS Item Rule**, then save the VAS Item.
**Step 3:** Open **Customer Centre** and open the relevant customer record. Go to **Contact Info → Address Info**. Ensure that the **Ship To Address** is configured with the required address details, then save the changes.
**Step 4:** Create a Sales Order and add the **Crimson** item. Verify that the configured VAS Item Rule is applied to the Sales Order line and that the **VAS Item Unit Cost** is **10**.
{% hint style="info" %} The screenshots show **Alberta** in the customer’s Ship To Address field, which is displayed as **AB** in the Sales Order’s **Ship To** address. {% endhint %} **Step 5:** Reopen the **Custom VAS Flat** VAS Item. Under **VAS Item Rules**, configure a second rule with the following criteria: * **Country:** Canada * **State/Province:** Alberta * **Item Number:** Crimson * **Customer Tags:** B2C * **Country of Origin:** Albania * **VAS Cost Type:** Fixed * **VAS Item Cost Amount:** 200 Click **Add VAS Item Rule**, then save the VAS Item.
**Step 6:** Navigate to **Customer Centre** and open the relevant customer record. In the **Other Info** tab, enter **B2C** in the **Customer Tags** field. Save the customer record.
**Step 7:** Open the **Crimson** item and navigate to the **Other Attributes** tab. Set **Country of Origin** to **Albania**, then save the item record.
**Step 8:** Create another Sales Order for the same customer and add the **Crimson** item. Verify that the newly configured VAS Item Rule is applied and that the **VAS Item Unit Cost** is **200**.
{% hint style="info" %} The following App Configs, available under **App Config → General**, control how VAS costs are displayed and included in the subtotal: * **Show VAS Item Total Amount In Separate Summary Line**: Displays the total VAS item amount as a separate summary line. * **Exclude VAS Cost from Subtotal**: Excludes VAS costs from the subtotal when enabled. This setting works only when Show VAS Item Total Amount In Separate Summary Line is also enabled. {% endhint %} --- # 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/current-release/october-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.