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.1.3
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.1.3.
| The information in this document was accurate at the time of publication, August 1 2025, 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 |
| 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.1.3 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.1.3.
Important Upgrade Eligibility Notes
BIL Version for Kinetic 2025.1
The BIL version for Kinetic 2025.1 is version 12_0_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.1.3.
Updating BPM, BAQ and UD Fields
An updated Precise CAB installation is required in order to obtain the latest BPMs, BAQs, and UD fields.
Epicor ARM 2025.1.3
Release Date: August 1 2025
Linux Compatibility
ARM is now compatible with Kinetic 2025.1 running on Linux.
Dot Net 9 Requirement
Dot Net 9 is a requirement for ARM 2025.1.3.
New Cab File
A new cab file Precise_BAQ_BPM_UD_2025_1_3_4 is available.
Use the .cab file or the .zip file, depending on which is compatible with your current version of Epicor.
System Enhancements
Transfers Module Improvements
ARM’s Transfers module has several improvements in terms of stabilization and performance.
Support for Lead Time
ARM now integrates the “Lead Time” field from Kinetic Supplier Price Lists and Inventory Items.
The Lead Time value is displayed in the Location and Price section of the Catalogue Maintenance form in ARM and is used by the system’s Due Date defaulting logic.
Additionally, you can define the Lead Time directly on the catalogue item itself.
GL Sequences Information Panel for GL Account Code on a Requisition Line
For a requisition line, ARM supplies a default GL Account Code which is derived according to the GL Account Mask Sequence (defined in Global Settings) and the current selections for the requisition line (for example, the Category, Location, Vendor, etc.).
There is a new GL Sequences information panel which displays a list of GL sequences with the following information:
- Attribute
-
The attribute name from the GL Account Mask Sequence, with the first in the sequence at the top of the list (for example, CATEGORY).
- Value
-
The value of that attribute on the requisition line (for example, HDW). GL Mask The GL mask associated with the value of the attribute. e.g., "__-00-20".
- Result
-
The resultant GL Account code when this attribute value’s mask is applied to the cumulative GL Account. The result is color-coded as follows:
- Amber
-
The GL Account mask is incomplete, but valid.
- Red
-
The GL Account mask is complete, but invalid.
- Green
-
The GL Account mask is complete and valid. (This is the value that ARM defaults into the GL Account field.)
Based on the information shown, it is possible to see how the default GL Account Code is derived, and where GL Account segments, relevant to the attribute values, are missing from the chart of accounts
To open the information panel, click on the new information button above the GL Account Code search box on a requisition line item.
Intercompany GL Expense Account Defaulting
You can now define Intercompany GL Account Masks for Locations, as well as for Categories and Requestors, to enable Intercompany GL Expense Account defaulting.
Due Date Enhancements for Requisition Lines
Requisition lines now have an option to add a default due date, with new logic to calculate this.
New ‘Use Default’ Checkbox on Requisition Lines
A new checkbox titled ‘Use Default’ has been added next to the Due Date field on each Requisition Line. The default state is checked.
When checked:
-
the Due Date field switches to read-only and
-
the Due Date is dynamically calculated using the new Default Due Date Logic.
Default Due Date Logic
When ‘Use Default’ is checked, the system will calculate the Due Date value as follows (in order of precedence):
-
Current Date + Supplier Price List ‘Lead’ Time (days) OR, if unavailable,
-
Current Date + Catalogue Item Location Lead Time (days) OR, if unavailable,
-
Current Date + Global Setting: ‘Due Date Days from Today’
New Permissions for Due Date
Two new permissions have been added:
-
Edit Requisition Due Date
-
Edit Proforma Order Release Line Due Date
UOM Defaulting when Job Material Selected
When a line is added from Job Material, the UOM defaults from the Job Material UOM, overriding the Part UOM.
Copy Date Values for Requisition/Template
A new setting titled ‘Include Dates’ has been added to Global Settings.
When this setting is enabled, any date check boxes are automatically selected in the requisition copy options, and template copy options, and also in template-to-requisition copy options.
Support for Line Type on Draft Invoices
The available line type options are determined by the Manual Matching Requirement setting and the user’s Override Manual Invoice Requirements permission, which governs access to Miscellaneous Invoice Lines.
You can select a default line type from the available options, in the Defaults for New Added Line section of the Draft Invoice page.
Enhanced Draft Invoice Functionality
Draft invoice behavior has changed to work as described below:
Draft Invoices have two modes: auto-mode and manual-mode.
Manual-mode is indicated by a blue banner with a notice. When a draft invoice is in manual-mode, a user must submit it after finishing all edits. After it is submitted, it goes to auto-mode.
Any notifications, emails, or OCR retries only happen when the draft invoice is in auto-mode. OCR retries submit the draft invoice automatically.
Note: OCR documents start in auto-mode. Manually entered draft invoices start in manual-mode.
Improved Behavior for Line-level PO on Draft Invoices
Line-level PO fields are now left blank, unless a line-level PO OCR value is explicitly provided. When the matching algorithm runs, the header-level PO value is implied in the logic if the line-level PO value is blank.
This behavior prevents incorrect header-level PO numbers from being copied to the lines.
Additionally, for Vendors with “Never Use a PO” as their Automation Matching Requirements setting, the PO number is not displayed on the header, and the line-level PO fields are blank and read-only on line-level, regardless of what is provided by OCR.
Support for Negative Miscellaneous Charges on AP Invoices
ARM now supports negative miscellaneous charge amounts at both the header and line levels on AP Invoices.
Enable or Disable Automatic Search Functionality
A new setting called ‘Auto-execute Search for Catalogue Items’ controls how the catalogue items are searched.
If the setting is enabled, catalogue items are preloaded automatically. If the setting is disabled, the user must search manually for catalogue items, by first clicking on the search button.
Invoice Payment Information Display
ARM now displays invoice payment details directly on the AP Entry screen.
Users can click on the 'Posted' or 'Paid' status to view the corresponding payment information.
Category, Due Date and Term Code ‘Use Default’ Functionality
A new check box titled ‘Use Default’ has been introduced for the line-level Category, Term Code, and Due Date fields.
The default state is checked.
- When checked
-
The corresponding field becomes read-only and will be automatically updated based on defaulting logic when the Item, Vendor, or Company fields are changed.
- When unchecked
-
The user can manually edit the field, and the system will no longer apply automatic updates.
Re-process PO Integration Stuck in 'Running' Status
Users now have the ability to re-process the integration of any Purchase Orders that may fall stuck in a long-running process.
This is done by loading the Pending Records Review screen and clicking 'Retry' on any PO with a ‘Running’ status.
Support Vendor Level OCR Settings
ARM now supports 'OCR Settings' at the Vendor level.
Integration Speed Improvement - InventoryItem Full Sync
Previously, any change to an inventory item’s related data required reloading the entire item along with all its associated information.
Now, only the modified parts are reloaded and updated, resulting in faster and more efficient integration.
Improved Suspension Feedback for Failed Line Identification
ARM now displays suspension reasons with the corresponding line numbers. This feature is limited to show a maximum of 5 errors.
Email Notification and Attachment Permissions
ARM now includes attachment links for both header and line-level attachments in the Requisition for Approval email notifications.
Additionally, two new user permissions have been introduced to manage attachment deletion:
-
Can Delete Own Attachment
-
Can Delete Any Attachment
These enhancements aim to improve attachment visibility and provide better control over attachment management.
Consolidated Email Notifications
Email notifications for approvals have been enhanced such that an approver now receives a single notification email, listing their approval requirements for all related lines.
Extra Information in Approval Notification Email
The approval notification email now also includes payment terms and external notes.
New Company Setting: AP Invoice Header’s Custom Data
A new company-level setting titled ‘AP Invoice Header’s Custom Data’ has been introduced to replace the APInvoice Header UD Field Label and APInvoice Header UD Field Name.
This allows users to define custom data fields for the header of AP Invoices.
Each field is specified as a “FieldName: DisplayLabel” pair, with multiple pairs separated by semicolons.
Data Handling
Once defined and saved, the custom field data is stored locally in ARM in a new UserDefinedData field added to the APInvoice table.
If the Kinetic system’s APInvHed table contains corresponding UDFs (e.g. CustomField1_c, CustomField2_c), the values will also be synchronized and stored there.
Draft Invoice Header’s Custom Data
Custom fields will display on the Draft Invoice page, provided the company setting AP Invoice Header’s Custom Data is enabled.
Tracker on AP Invoice
The AP Invoice page has a new Tracker button on the menu.
Click on this to open the AP Invoices > [invoice number] > Tracker. The tracker shows the path of the AP Invoice from draft to purchase order, as well as the requisition(s) and pro-forma invoice relating to the PO.
Support for Downloading Attachments
Attachments stored in the database (which is how they were previously stored) can now be opened, as well as any documents stored in the new Attachment Storage Provider.
User Guide and Release Documents Available on the ARM User Interface
You can access the latest Release Guide document and the online User Guide from the ARM user interface. Click on the help button on the top right of the main menu, then select from the drop-down menu.
The online User Guide is an updated version of ARM’s online help, for the current major version of ARM. You can also access the legacy help files from within the new help.
ARM BIL Configuration Update
UD Tables Extended
Previously limited to UD37 and UD38, ARM now supports UD01 to UD40. You can now configure any of the UD01 to UD40 tables in the ARM BIL configuration.