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 2026.2.0

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 2026.2.0.

The information in this document was accurate at the time of publication, August 27 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

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 2026.1.1 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 2026.1.1.

Important Upgrade Eligibility Notes

BIL Version for Kinetic 2026.100

The BIL version for Kinetic 2026.100 is version V12_2_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 10

Dot Net version 10 is a requirement for the installation or upgrade to ARM 2026.2.0.

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 2026.2.0

Release Date: August 27 2026

Kinetic 2026.100 Compatibility

ARM is now compatible with Kinetic 2026.100.

Release Summary

This release focuses on improving the reliability of key workflows while strengthening the platform for future product capabilities.

  • Approval workflows are more reliable and transparent, with improvements to skipped and delegated approvals, active approver visibility, and approval routing.

  • The underlying platform has been modernised and optimised, including upgrades to .NET 10 and the Python runtime used for AI matching, performance improvements, and foundational work for future analytics capabilities. Together, these changes improve the day-to-day experience for users while preparing the product for continued expansion.

New Version Numbering

ARM releases now follow a new version numbering convention: ARM <Kinetic version>.<ARM version>.<patch>.<build>

For example: ARM 2026.2.1.5

Where:

2026 = Kinetic version

2 = ARM version

1 = Patch version

5 = Build number

Pre-Requisites

The latest CAB/ZIP file must be deployed to Kinetic as part of this release. This CAB/ZIP file contains resolutions for ARM-4927 and ARM-5440, see below. If not using the embedded Access Scope in the CAB/ZIP file a new one will need be imported into your existing Kinetic Access Scope.

Key Highlights

Area

Delivered in 2026.2.0

Representative items

Reporting and analytics

Foundation for analytics API and report-ready data processing.

Analytics API security, infrastructure and OData support.

Architecture

Modernized runtime stack for supportability and future development.

.NET 10 upgrade, Python 3.14 upgrade.

Document handling

Improved draft invoice and AP behaviours.

Line reordering, template-based AP creation, improved matching and validation handling.

Improvements

AP invoices and Draft Invoices

  • Improved manual tax edit error messaging on AP invoices.

  • Resolved non-ASCII PDF display issues after prior upgrade changes.

  • Added API support to view PDF files with non-ASCII or control characters.

  • Corrected duplicate invoice filtering behavior, including invoices on hold for duplication detection.

  • Fixed tax, vendor, and duplicate-related draft invoice filters.

  • Corrected quantity, UOM, unit cost, and extended cost conversion issues in draft-to-AP processing.

  • Ensured advanced billing is received correctly.

  • Fixed access issues after converting draft invoices to AP invoices.

  • Resolved inconsistencies where tax liability updates could incorrectly zero cost values.

  • Improved draft invoice performance while OCR retry jobs are running.

  • PO matching with multiple manual Invoicing of Receipts.

Approvals

  • Fixed skip-node behavior where the document owner is also an approver.

  • Ensured advanced approvals honor skip-node configuration from sequence 2 onward.

  • Resolved issues where approval workflows failed to progress correctly after skipping ineligible approvers.

  • Fixed initial approver node skipping behavior.

  • Corrected advanced approval criteria behavior for vendor code.

  • Improved approval delegate caching to prevent missing approval links and delayed loading.

  • Expand Rejection to cater for a value list of Reason Codes plus a text-based denial reason.

Requisitions and Purchasing

  • Ensured job and material descriptions display for the correct job/company only.

  • Validated purchase point existence when copying requisitions to prevent PO integration failures.

  • Displayed all associated purchase points in requisition entry.

  • Corrected requisition email approval decimal-place handling for transfer lines.

  • Improved dynamic segment support for single mandatory-segment COAs.

  • Updated due-date-required validation and related messaging.

  • Fixed blanket order and standing order behaviors affected by due date settings.

  • Corrected fast copy due date handling.

  • Ensured vendor currency defaults correctly for catalogue requisition lines.

  • Fixed issues with invalid part revisions, release line sequencing, whitespace in blanket order descriptions, and failed catalogue line submissions where revisions are not configured.

  • Added support for warehouse name and update delivery defaulting logic.

Integrations and Master Data

  • Corrected preferred vendor integration updates into ARM.

  • Ensured vendor integration changes propagate correctly to TRAILD.

  • Fixed shipment and drop shipment update behavior from Kinetic.

  • Corrected vendor group assignment handling so inactive vendor status is not overridden in ARM.

  • Resolved endless looping on BIL multi-page loading via Kinetic OData.

  • Added extra BIL access scope items for Kinetic application version checks.

  • Company Setting: Add "FOB required".

Platform, Performance, and Administration

  • Upgraded ARM/BIL to .NET 10.

  • Upgraded Python runtime for AI matching to 3.14.

  • Added database indexes to improve query performance.

  • Added customer-specific supplemental indexes across several entities to support performance improvements.

  • Included Splink installation guidance with the installation bundles.

Resolved Issues

This release contains the following fixes across AP, Draft Invoice, OCR, approvals, requisitions, purchasing, integrations, platform behaviour, and refreshed UI workflows.

Accounts Payable and Draft Invoice

  • [ARM-2836] — Improved the AP error message shown when editing Tax manually on the header.

  • [ARM-5233] — Corrected the Draft Invoice duplicate filter so it only shows duplicates.

  • [ARM-5272] — Resolved PDF display failures for Draft/AP invoices containing non-ASCII characters after system upgrade.

  • [ARM-5297] — Invoices on hold for duplication now appear in the Duplicate Invoice filter.

  • [ARM-5304] — Fixed incorrect quantity and unit cost UOM conversions during Draft Invoice to AP Invoice processing.

  • [ARM-5307] — Corrected the Vendor error filter to include invoices where vendor number is blank.

  • [ARM-5311] — Corrected the Tax error filter to include tax liability mismatch cases.

  • [ARM-5347] — Ensured Advanced Billing is properly received in AP processing.

  • [ARM-5361] — Delivered multiple refreshed UI fixes for Draft Invoice behaviour.

  • [ARM-5414] — Fixed incorrect pagination range display on the Draft Invoice page.

  • [ARM-5440] — Restored the View button on the AP Invoice screen for draft invoices.

  • [ARM-5441] — Fixed reviewer data loading on Draft Invoice.

  • [ARM-5514] — Corrected invalid Terms Code updates on Draft Invoice.

  • [ARM-5571] — Fixed access issues to AP Invoice after conversion from Draft Invoice.

  • [ARM-5708] - Fixed Invoice line items from disappearing from the display after a line is denied and a new one is added.

Approvals and Workflow

  • [ARM-1496] — Approval nodes are now skipped correctly when the document owner is an approver on the node.

  • [ARM-1609] — Reviewed and corrected approval workflow behaviour where the document owner is an approver.

  • [ARM-5226] — Advanced Approvals now honor “Skip Approval Nodes” on sequence 2 and beyond.

  • [ARM-5327] — Requisition email approval for transfer lines now honors decimal places.

  • [ARM-5473] — Corrected advanced approval criteria where Vendor Code was not working.

  • [ARM-5474] — Fixed workflow progression when an approver is skipped because they cannot approve their own document.

  • [ARM-5484] — Resolved incorrect skipping of the initial approver node.

  • [ARM-5538] — Fixed approval delegate caching issues that caused missing approval links and slow approval list loading.

Requisitions, Purchasing, and Receiving

  • [ARM-5147] — Requisition line job and material descriptions now show data from the correct job and company.

  • [ARM-5184] — Inactive local locations now appear in the PFO list and PFO lines can be accessed without error.

  • [ARM-5232] — ARM now validates that a Vendor Purchase Point still exists when copying a requisition, preventing PO IM failures.

  • [ARM-5240] — Requisition Entry now displays all associated Purchase Points.

  • [ARM-5331] — Catalogue requisition lines now default to Vendor Currency rather than Company Currency.

  • [ARM-5342] — Improved error messaging when requisitions are submitted without a due date while Due Date Required is enabled.

  • [ARM-5352] — Purchase order and packing slip suggestions are no longer always included when no modifications were made.

  • [ARM-5355] — Fixed Due Date Required logic so Blanket Order Lines can be added correctly.

  • [ARM-5372] — Fixed Due Date Required logic so Standing Orders can be added correctly.

  • [ARM-5373] — Fixed import file and header settings population when Due Date is required during requisition creation.

  • [ARM-5374] — Fast Copy now copies the due date from the line item.

  • [ARM-5418] — Ship Via is now populated from system default during requisition line import for miscellaneous items.

  • [ARM-5449] — Subcontract Operation comments are visible again on requisitions and purchase orders.

  • [ARM-5457] — UOM conversion is no longer required for matching option 2.

  • [ARM-5528] — GL Reference is now optional.

  • [ARM-5535] — Fixed PO creation failure where “POHeader is not available” in certain OTV and new job scenarios.

  • [ARM-5556] — Fixed application of requisition header defaults when lines do not have Vendors or Category.

  • [ARM-5563] — Fixed Blanket Order release to allow whitespace in descriptions.

  • [ARM-5572] — Corrected incorrect Part Revision being applied to Change Order and Receipt lines.

  • [ARM-5576] — Prevented invalid part revisions being imported into requisition lines.

  • [ARM-5583] — Fixed requisition submission failure for catalogue lines without a configured revision.

  • [ARM-5620] - The PO Receipt docket is downloaded automatically after each receipt.

  • [ARM-5713] - Added a “Part Revision Behaviour” global setting.

  • [ARM-5689] - Added VendorContactPhone value to the PO Report dataset.

Integrations, Vendor Data, and Platform

  • [ARM-4927] — Fixed line sequencing of Blanket Orders when an order is integrated (CAB File Update).

  • [ARM-5312] — Added support for the ARM API to view specific PDF files with non-ASCII or control characters.

  • [ARM-5322] — Removed duplicate threshold settings appearing in Company Settings.

  • [ARM-5330] — Corrected Preferred Vendor integration so updates flow to ARM accurately (CAB file update).

  • [ARM-5340] — Enabled Dynamic Segments when using a COA with only one mandatory segment.

  • [ARM-5371] — Fixed GL handling for COA entries with variable length.

  • [ARM-5381] — Resolved endless loop behaviour in BIL when loading multiple pages via a Kinetic OData endpoint.

  • [ARM-5391] — Fixed vendor integration logic so new or updated vendors are propagated to TRAILD.

  • [ARM-5393] — Corrected behaviour for mixed variable-length Chart of Account configurations.

  • [ARM-5412] — Corrected shipment status updates from Kinetic for ARM transfer orders.

  • [ARM-5435] — Fixed /api/user/statistics endpoint failure in fresh ARM installations upgraded to .NET 10.

  • [ARM-5469] — Fixed drop shipment updates from Kinetic into ARM.

  • [ARM-5541] — Ensured Vendor Group assignments in Kinetic do not override Vendor inactive status in ARM.

  • [ARM-5573] — Corrected default Tax ID behaviour when no Tax ID is provided.

  • [ARM-5604] — ARM now updates associated GL values when Part Class changes.

  • [ARM-4644] - User/SSO: Flush User token on deactivated user accounts

  • Validate approval trees involving self-approval restrictions, skip nodes, delegates, and multi-sequence approvals.

  • Validate requisition due date rules, purchase point behavior, vendor defaults, and part revision handling.

  • Validate integrations for vendors, shipments, drop shipments, and preferred vendor updates.