Epicor ARM 2025.2.2 Release Guide

Epicor ARM Release Guides

Disclaimer

This document is for informational purposes only and is subject to change without notice. This document and its contents, including the viewpoints, dates and functional content expressed herein are believed to be accurate as of its date of publication. However, Precise Business Solutions makes no guarantee, representations or warranties with regard to the enclosed information and specifically disclaims any applicable implied warranties, such as fitness for a particular purpose, merchantability, satisfactory quality or reasonable skill and care. As each user of Epicor software is likely to be unique in their requirements in the use of such software and their business processes, users of this document are always advised to discuss the content of this document with their Precise Business Solutions account manager. All information contained herein is subject to change without notice and changes to this document since printing and other important information about the software product are made or published in release notes, and you are urged to obtain the current release notes for the software product. Copyright © Precise Business Solutions 2025. All rights reserved. No part of this publication may be reproduced in any form without the prior written consent of Precise Business Solutions.

Introducing Epicor ARM 2025.2.2

Epicor Advanced Requisition Management (ARM) automates and streamlines the requisitioning process, utilizing a Web browser to integrate with and extend the Epicor Purchasing module.

Multiple approval methods provide a flexible framework that can be configured to meet the requirements of any organization.

Via a separately licensed module, ARM also facilitates inventory transfers between Epicor locations/warehouses/sites and importing bulk data for Requisitions or Receiving via .csv files.

About this Document

This Release Guide describes the features and enhancements included in Epicor ARM 2025.2.2.

The information in this document was accurate at the time of publication, January 22 2026, but it may change without notice.

Browser Guide

Browser	Version
Google Chrome Recommended	Last 3 Full Versions
Microsoft Edge Mozilla Firefox Safari	Last 3 Full Versions

Browser

Version

Google Chrome Recommended

Last 3 Full Versions

Microsoft Edge

Mozilla Firefox

Safari

Last 3 Full Versions

Certification relates to the ability to install and use Epicor ARM with a certified product version. It does not relate to specific functions or features that may or may not be implemented or available.

Upgrade Eligibility

To upgrade to version 2025.2.2 you need to meet the following eligibility criteria:

Minimum Version: Your current version must be at least 10.3.17.

If you have a lower version, you should first upgrade to 10.3.17 before proceeding further.
Intermediate Version: After reaching the minimum version you need to upgrade to the intermediate version 2023.1.1.1.69.

The intermediate version serves as a bridge between the minimum version and this version.
This Version: Finally, after successfully upgrading to 2023.1.1.69, you can proceed with the upgrade to version 2025.2.2.

Important Upgrade Eligibility Notes

BIL Version for Kinetic 2025.2

The BIL version for Kinetic 2025.2 is version 12_1_100.

AI Matching

A first-time Python installation is a requirement with installing or upgrading to ARM 2023.2.2 or higher. This software is used with the AI Matching functionality.

The relevant Python files (Dependencies) are included within the ARM package. These must be installed manually.

Python Update (ARM 2024.1.3+)

Epicor ARM has been enhanced, eliminating the need for Python installation in order to process PO receipts.

If Python is not installed, AI-Matching will not be invoked. Instead, a complete list of all available receipts for the current Vendor and Purchase Order is displayed in the matching sub-row list without confidence levels, allowing for manual selection.

Dot Net 9

Dot Net version 9 is a requirement for the installation or upgrade to ARM 2025.2.2.

Updating BPM, BAQ and UD Fields

An updated Precise CAB installation is required in order to obtain the latest BPMs, BAQs, and UD fields.

ARM Support for SLS Service Plans

Introduced in ARM 2025.2.2, the following list details the technical requirements required for access to the SLS Service Plans functionality.

A new CAB file is required for this release.
If the SLS service plan is enabled in ARM, new access scopes must be registered for the SLS CC module services.

The required access scope file is included with the ARM on-premises installer and can be found in the following directory: BPMs\AccessScopes.

Epicor ARM 2025.2.2

Release Date: January 22 2026

Editable GL Account Segments on User Maintenance

ARM has introduced Editable GL Account Segments in the User Maintenance module. A list of controlled and dynamic segments will be displayed for each user.

If Access All GL Segments is unchecked, a User Administrator can specify which GL segments the user is authorized to edit. This allows for assigning specific segments that the user has permission to modify.

When the user raises a requisition, the current default GL logic will still apply as defined in the GL sequence.

By clicking the Edit button, a GL Account Edit window will appear, displaying each segment as an individual field. This enables users to edit controlled and dynamic segments separately. Users can either search for a GL account or modify only the segments they are authorized to access.

The interface supports two editing modes:

Inline Editing: Users can edit the full GL Account directly in a single field (as per the current functionality).
Segment Editing: Users can click the Edit icon to open the GL Account Edit window, where each segment is editable individually.

For users with limited access, the full GL Account field will be read-only. However, they are still able to click the Edit icon to open the new GL Account Edit screen, where only their permitted segments are available for editing.

For implementation, a complete synchronization of the GL Segment Value job must be performed.

Support SLS Service Plans

The Community Care Requisition menu has been created for direct use with the Kinetic SLS function.

Settings

Enable Community Care Purchasing: Added in Global Settings. When this is set to Yes and the backend is SLS, users can raise Community Care requisitions which will be integrated with SLS.
Default Void Visit Reason Code: Added in Company Settings. This defines the default reason for voiding a visit if it is rejected during the PFO stage.

Functionality

This enhancement allows users to purchase service plans through the following sub-menus:

Local Catalogue
Non-Catalogue
Community Care Visits

In addition, punchout purchasing is also supported. Users can complete a punchout order and then either link it to an existing visit record or create a new visit for it.

The header default has been enhanced to include Add Client, Service Plan, and Service Plan Detail in the requisition header, enabling automated visit creation during purchasing.

The approval workflow remains unchanged and follows the standard requisition approval process.

A new CAB file is required for this release.
If the SLS service plan is enabled in ARM, new access scopes must be registered for the SLS CC module services.
- The required access scope file is included with the ARM on-premises installer and can be found in the following directory: BPMs\AccessScopes.

Blanket Order Release Editable Dynamic GL Segments

The Blanket Order Release function allows users with the “Can specify dynamic GL Segments on Blanket Order Release” permission to modify dynamic GL segments.

When “Add Release Line Details” next to the Release Amount field is clicked, a dialog is displayed with the following elements:

Controlled GL Account Code: Displayed as read-only.
Dynamic GL Segments: Editable (if the user has access to the segment) and defaulted from the values on the original line.

Upon release, the selected dynamic GL segments will be applied to the corresponding Released, Received, or Closed PO lines.

System Enhancements

Workflow Diagram – Visual Enhancements

The workflow diagram in the updated user interface has been refined to improve visual clarity, status recognition, and overall usability.

Approval steps are now displayed as circular nodes, each color-coded to clearly indicate its current state within the workflow:

Orange: Nodes that have not yet been processed and are not currently active.
Blue: Nodes that are active and ready for the next action.
Green: Nodes that have been manually completed with approval.
Red: Nodes that have been manually completed with rejection.
Grey: Nodes that have been automatically completed, skipped, bypassed, or marked as not required.

These visual enhancements enable users to quickly assess workflow progress and identify required actions at a glance.

Purchase Order Number Consistency

A new setting has been added on the Integration Agent titled “Use consistent PO Numbers in both ARM and Kinetic.”

When enabled: PO numbers generated in Kinetic will be reflected identically in ARM and the ERP system. This ensures consistency across systems, enhancing traceability and reducing discrepancies.

ARM retrieves the PO number from Kinetic prior to creating the PO in ARM. As a result, PO number values are immediately available for EDI jobs without waiting for the full PO integration to complete.
When disabled: The system will continue to behave as it did previously. That is, PO numbers created in Kinetic may differ from those displayed in ARM.

For implementation, a new CAB file is required as the BPM on POHeader has been updated.

Alternate UOM Synchronization and Performance

The Alternate UOM job has been restructured into two separate jobs:

Alternate UOM - Standard

and
Alternate UOM - Part-specific.

This enhancement enables ARM to correctly handle part-specific UOMs and improves the synchronization of related part UOMs, without requiring costly full synchronization of inventory items.

As a result, significant performance improvements have been achieved. The Part-specific UOM IM job now runs at least three times faster, and in SaaS environments can be more than 10 times faster when compared to the inventory item IM job.

A one-time full synchronization for Alternate UOM jobs is required.

AP Invoice

Alternate Group Submission for AP Invoice Approval

It is now possible to submit an invoice from a different group (other than ARMUNAPP) into ARM’s approval workflow. After the invoice is fully approved, it will be transferred to the target group defined by the batch number.

AP Search Screen Sort Controls

The following options have been removed from the AP Search screen: sort by Last Update, Latest Due Date, and Earliest Due Date.

These have been replaced with up and down arrow sort controls on Invoice Date, Create Date, and Due Date.

Paid Status, Date and Workflow Filters

Users are now able to search and filter invoices by Paid Status and by Payment Date Range, making it easier to track and review paid invoices.

The Status criteria also includes a new search status, "Any (Workflow)”. This option returns invoices with any of the following statuses: Pending Revision, Review In Progress, Suspended, Rejected, Unsubmitted, Submitted, or Approval In Progress when searching via ARM.

For implementation, a new BAQ is required.

Hide Legacy Approval Tree Types

ARM has introduced a new hidden global setting titled “Disabled Legacy Approval Trees.”

This setting is not visible in the UI, but its setting ID can be accessed manually through the site URL.

New installations: The value should default to Yes.
Upgrades: If the setting already exists, retain the existing value.

If the setting does not exist, default the value to No.

When this setting is set to Yes:

Creating or maintaining any Legacy Approval Trees will be fully hidden and unavailable in the user interface.
Any existing Legacy Approval Trees will be disabled and excluded from all search results.

Advanced Approval Additional Criteria

The following additional criteria have been introduced for the advanced approval functionality:

Inventory - yes/no
Linked Sales Order
Project
Phase
Cost Code
Document Type
Order Adjustment Type
AP Line Type
Project Manager

No additional field has been added to the purchase line.

The Project Manager on a requisition purchase line is automatically populated based on the selected Project.

A one-time full synchronization on the Project Job is required.

Import and Export by Requester Group

The Requester Group now has import and export functionality.

The ARM Catalogue Item Locations import file now allows users to update the preferred vendor for all locations using the keyword ##ALL-LOCATIONS##, or for specific locations individually.

Integration Change Detection Interval

Change Detection Interval (seconds) has been added to the Integration functionality and can now be configured in the UI under Agent Properties.

The default value is 3 seconds, which is also the minimum value that can be configured.

The maximum value is 86,400 seconds (1 day).

EDI: Punchout Line-Level Note Transmission

ARM has been enhanced to support Line Note import logic (Response Parser) and Replacement Variables (Request EDI Content).

This enhancement introduces the ability to transmit and receive line-level notes on Requisitions and Purchase Orders (POs) through Punchout integration.

Resend Feature for OCR Notifications

A new global setting has been added titled “Number of day(s) after which Draft Invoice validation notifications will be reset”.

This setting determines the number of days after which Draft Invoice validation notifications will be resent to users.

A new job titled “Reset Draft Invoice Notification Tracking” has also been introduced to support this functionality. This job moves tracking data from the main table to the history table and is disabled by default.

Users can download the JSON file by clicking the “envelope” icon displayed on the Draft Invoice.

Draft Invoice Attachment Function

Adding attachments to draft invoices is now supported. Users can manually upload attachments, and when the invoice is created, the attachments will be carried forward to the AP Invoice.

Support for Kinetic Part Purchasing Comments

ARM now pulls the purchasing comment into the REQ line for catalogue items, allowing users to view the comment throughout all stages: REQ → PFO → PO → Reports.

A new setting titled “Environment Login Banner Image” has been added to Global Settings.

This allows users to upload a banner image which will be displayed on the ARM login screen.