Epicor ARM 2024.1.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 2024.1.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 2024.1.2.

The information in this document was accurate at the time of publication, June 17 2024, 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 2024.1.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 2024.1.2.

Important Upgrade Eligibility Notes

BIL Version for Kinetic 2024.1

The BIL version for Kinetic 2024.1 is version 11_3_100. The BIL version for SLS is version 11_2_200_08.

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.

Dot Net 8

Dot Net version 8 is a requirement for the installation or upgrade to ARM 2023.2.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 2024.1.2

Release Date: June 17 2024

AP Invoice Enhancements

New Permission “Revise GL Account on AP Invoice”

A new permission called “Revise GL Account on AP Invoice” has been introduced that allows the GL Account and any related GL Reference Codes on an existing GL Distribution record to be edited within a revised AP Invoice.

Users with the “Edit GL Distribution on AP Invoices” permission may add /edit/ delete the GL Account and any related GL Reference Codes without the need for the new “Revise GL Account on AP Invoice” permission.

New Permissions for Adding AP Charges, Invoice Batches and Invoice Editing

AP Charges

Add AP Header Charges: The user can add charges on the Invoice Header.
Add AP Line Charges: The user can add charges on the Invoice Lines.

Invoice Date and Batch Number

Edit AP Invoice Batch Number: The user can edit the AP Invoice Batch Number.
Edit AP Invoice’s Invoice Date: The user can edit the Invoice Date on AP Invoices.

Assigned Invoice Editing

Edit Assigned AP Invoices: The user can edit AP Invoices assigned to them.

Users with this permission can edit all fields not controlled by the field-specific permissions "Edit AP Invoices XYZ" (e.g., Edit AP Invoice Due Date, Edit AP Invoice Terms etc.).

“Document Change Rights” Setting for Document Types

A new setting has been added to the Document Types Configuration.

Allow Edits During Approval and Revision (default)

This is the current behavior.
Only Allow Edits During Revision

This option locks down all * fields on the document (Invoice) during approval. The document must be in a revised state in order to be altered and therefore re-submitted (triggering a new workflow approval assessment).

Support Advance Approval on AP Invoices Only

Advance approval ability has been split into REQ and AP.

Users can now assign the permission to just AP if desired.

ARM Dashboard Enhancements

Support both AP Invoice Status and Draft Invoice Status on Draft Invoice Dashboard: The current “Status” column in the Draft Invoice search results has been renamed to “Draft Invoice Status”.

A new “AP Invoice Status" column is now visible to the right of the “Invoice #” column. When the Draft Invoice Status is “Invoice Created”, the new AP Invoice Status column displays the status of the Invoice created.

If an AP Invoice that originated from a Draft Invoice is deleted, the status of the Draft Invoice is updated to “Saved” and put on Hold with reason “Linked AP Invoice has been deleted.”
AP Invoice “Paid” Status: The ARM Dashboard now displays the Paid status of AP Invoices.

This field is flagged when the invoice has been fully paid.
Support PO Number Search and Visibility on Draft Invoice Dashboard: The Draft Invoice search now allows a user to enter and search by PO Number.

Retain Approvals Prior to Revision

When an AP Invoice is revised all existing actioned (historical) workflow steps, including the current step under which the revision is being actioned, will be retained.

When the AP Invoice is re-submitted, the current workflow step will be recorded as “Revised and Submitted”, and the lines are then reassessed against the active approval trees to determine the new workflow steps. These new steps will be added to the workflow.

Send AP Invoice for Review prior to Submission

The “Send for Review” option has been added to the Workflow button on the AP Invoice document, making this functionality available prior to submitting the AP Invoice.

Un-Deny line functionality during AP Approval and Revision

The ability to un-deny an AP Invoice line operates around the following conditions:

Invoices in Revised State: Users can un-deny an AP Invoice line if the Invoice is in a revised state.
Subsequent Workflow Steps: Users can un-deny an AP Invoice line if they are on workflow steps that follow the step where the line was initially denied, provided they are within the same workflow path.
Exclusion of Parallel Approvers: Parallel approvers who are notin the same approval path are not permitted to un-deny the line.
Post-Approval Restriction: Once an Invoice has been fully approved (i.e., all lines are either rejected or fully approved and the status is changed to “Approved”), denied lines cannot be undenied.

Tax Liability Editing on AP Invoice Header

Epicor ARM now supports the ability to edit the Tax Liability on the invoice header.

Apply Date from Kinetic Time Zone

The apply date defaulting logic will be updated to use the time zone defined in the Kinetic Company Maintenance. If no value is defined, the local regional time zone shall be used, consistent with the current logic.

In the ARM company detail view additional information about the time zone from Kinetic Company Maintenance has been displayed, together with the ARM application server and the client time zones.

In AP Invoice entry, company time zone is only applicable for default values. The default logic only applies to the Invoice Apply Date when “use current date” is ticked. Once a date is selected from the calendar picker, the zone is set to the current user’s time zone.

Support Storage Types in Kinetic

Epicor ARM now supports the Kinetic storage types “SharePoint” and “ECM”.

Column Switching Learning

Smart Invoice Capture has improved the experience of the column switching learning.

For example, when the PO column is not initially detected, the user can manually switch the column. The next time the same template is scanned, the learning process will initiate and the PO column will be populated correctly.

Enhance Draft Invoice Terms Code Defaulting

The Draft Invoice logic for defaulting the Terms Code now follows the hierarchy below until a valid Terms Code is found:

Use the valid Epicor Terms Code from OCR (if above the “low” threshold); or
Look up the OCR value (if above the “low” threshold) to match a Terms Code Mapping; or
Default from Purchase Order (if the draft invoice contains receipt lines and all receipt lines are from the same PO); or
Default from Supplier; or
Default from Company settings; or
<Blank> (An error will be raised due to required field forcing the user to select a value).

Validations added to the Draft Invoice:

If the Terms Code on the Draft Invoice is different than the Terms Code on the Supplier, raise a warning.
If a Receipt Line references a PO with a different Terms Code than the Draft Invoice, raise a warning.

By setting the “low” threshold on the Terms Code field to a high value like 100, implies that the system should never use the OCR value, but always use the Terms Code from the PO or Supplier.

Enhance Draft Invoice Due Date Defaulting

The Draft Invoice logic for defaulting the Due Date now follows the hierarchy below until a valid Due Date is determined:

Use OCR Due Date (if above the “low” threshold).
Default from Terms Code
<blank> - The user must enter or select a value.

By setting the “low” threshold on the Due Date field to a high value like 100, implies that the system should never use the OCR value, but always calculate the due date from the terms code.

Validations added to the Draft Invoice:

If the Due Date is different than what the terms would otherwise generate, raise a warning.

MATCHES Operator for Project Criteria and all Text-based Criteria

The “MATCHES” operator has been added to the Project Approval criterium and all other text-based criteria.

This criterium assesses the text value against the Project Code on the line. Text values entered against a “MATCHES” operator will be assessed using the same logic as an SQL “LIKE”, allowing wild card operators “%” and “_” anywhere in the string to be assessed.

Kinetic Memo Captures Approval Audit Detail for PO

Epicor ARM now tracks approval audit information and integrates this into the Kinetic memo. A new company setting called “PO Workflow Memo Category” has been added to define the Memo Category Code configured in Kinetic for the integration flow of this information.

Additional XML tags support for Ancora

There are three XML tags that have been added into the header section of Ancora files. These tags appear as follows:

Explicit Document Type Tag:

<FIELD name="HDR_DOCUMENT_TYPE"></FIELD>

Specific values that translate to a Debit memo are:

“Credit Note”
“Debit Memo”
"CreditNote"
"DebitMemo"

BPAY fields:

<FIELD name="HDR_BILLER_CODE"></FIELD>

<FIELD name="HDR_BILL_REFERENCE"> </FIELD>