Acumatica Cloud ERP: 2025 R1
Release Notes 2025 R1
Contents
Copyright 5
Introduction 6
Installation and Upgrade Notes 7
Actions Before the Upgrade 10
Post-Upgrade Changes and Actions 11
CRM: Implementation of the ISO 20022 Address Format 13
CRM: Improvements to the Calculation of Case Commitments 15
DeviceHub: Polling Frequency Settings for DeviceHub Scales 19
Documentation: Improvements in User Guides 20
Field Services: Support of Stock Items With Lot or Serial Numbers Assigned in Appointments 22
Field Services: Improvements in Managing Project-Specific Inventory 26
Finance: Increasing of the Authorized Payment Amount 30
Finance: Payment Receipts for Released Transactions 35
Finance: Prepayments from Sales Order Payment Links 43
Finance: Recording of Finance Charges for Refunds 44
Finance: Support of the BAI2 Format by Bank Feeds 46
Finance: Other Improvements 49
Integrations: Ability to Deactivate Ship-Via Codes and External Carriers 53
Integrations: Filtering in the Shop for Rates Dialog Box 55
Integrations: Multiple Access Tokens for Each External Application 56
Integrations: Removal of Obsolete FedEx and UPS Plug-Ins 59
Inventory and Order Management: Capturing Weights of Packages from DeviceHub 60
Inventory and Order Management: Changes to Access Rights in Predefined User Roles 62
Inventory and Order Management: Correction of Purchase Receipts for Drop-Ship Purchase Orders 65
Inventory and Order Management: Correction of Purchase Receipts for Purchase Orders with the Normal Type 72
Inventory and Order Management: Lot and Serial Attributes for Stock Items 82
Inventory and Order Management: Receive Transfer Mode of the Receive and Put Away Form 91
Inventory and Order Management: Other Improvements 101
Inventory Planning: Forecast Consumption Visibility 102
Inventory Planning: Improved Traceability of Demand and Supply 104
Localization (Canada): RBC ACH094 Plug-In for International Payments 105
Localization (Canada): Support of T4A Reporting 107
Manufacturing: Due Date Handling in Production Orders 112
Manufacturing: Enhanced Material Availability and Production Readiness Tracking 114
Manufacturing: Enhanced Production Scheduling Views 115
Manufacturing: Enhancements in Finite Production Scheduling 116
Manufacturing: Other Improvements 117
Payroll: Accruing Time Off by Earning Type for PTO Banks 118
Payroll: Calculating a Deduction Based on a Percentage of Eligible Earnings 120
Payroll: Detailed Pay Stub Reports 121
Payroll: Exporting Batch Payments to ZIP 125
Payroll: Summary Report 127
Payroll: Taxes by Code Report 129
Platform: Improved Licensing for Anomaly Detection in Generic Inquiries 130
Platform: Improvements to the XML Import and Export Functionality 132
Platform: Extended Support for Date-Relative Parameters 135
Platform: Support for the Numeric Attribute Type 137
Platform: Other Improvements 138
Projects and Construction: AIA Report with Time and Material Lines 140
Projects and Construction: AP Document Recognition for Projects 143
Projects and Construction: Enhanced Usability for AP Documents with Multiple Projects 145
Projects and Construction: Enhancements to the Correction of Pro Forma Invoices 147
Projects and Construction: Enhancements to the Cost Projection Functionality 150
Projects and Construction: Improvements to AR and AP Reports 155
Projects and Construction: Improvements in Tracking Project Inventory 161
Projects and Construction: Improvements to the Creation of Final Lien Waivers 164
Projects and Construction: Improvements to the Construction Bonding Report 166
Projects and Construction: Improvements to the Subcontract Audit Report 170
Projects and Construction: Project Quotes in the Mobile App 173
Projects and Construction: Usage of Free Stock for Projects with Project-Specific Inventory 175
Retail Commerce: Depreciation of Authorize.Net 178
Retail Commerce: Import of Shopify Orders Without Importing Customers 179
Retail Commerce: Import of Shopify Documents in the Default Store Currency 180
Retail Commerce: Improvements to the Mapping of Taxes for Shopify 182
Retail Commerce: Improvements to Synchronization of Price Lists with Shopify 184
Retail Commerce: Inventory Replenishment for Amazon-Fulfilled Orders 185
Retail Commerce: Replacement of REST API with GraphQL API for Shopify 188
System Administration: Email Scheduling for Reports 195
Customization: Access Rights for Custom Forms 200
Developer Documentation: New Topics 202
Mobile Development: Dialog Result for the Close Button 203
Mobile Development: Displaying the Progress and Results of Processing 205
Platform API: Improved Logging in Connectors for External Systems 207
Platform API: Processing of API Rate Limits in a Connector for an External System 208
Platform API: Changes to the Image Processor Modules of the Shopify and BigCommerce Connectors 210
Platform API: Changes to the Methods of the ARPaymentEntry Graph 211
Web Services: New PATCH Method in the REST API 212
Web Services: Tracking of Deleted Records Through OData 214
Web Services: New Manufacturing Endpoint 216
Workflow UI: Viewing of Workflow Changes 217
Fixes and Enhancements 219
© 2025 Acumatica, Inc. ALL RIGHTS RESERVED.
No part of this document may be reproduced, copied, or transmitted without the express prior consent of Acumatica, Inc.
3075 112th Avenue NE, Suite 200, Bellevue, WA 98004, USA
Restricted Rights
The product is provided with restricted rights. Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in the applicable License and Services Agreement and in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Soware clause at DFARS 252.227-7013 or subparagraphs (c)(1) and (c)(2) of the Commercial Computer Soware-Restricted Rights at 48 CFR 52.227-19, as applicable.
Disclaimer
Acumatica, Inc. makes no representations or warranties with respect to the contents or use of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Acumatica, Inc. reserves the right to revise this document and make changes in its content at any time, without obligation to notify any person or entity of such revisions or changes.
Trademarks
Acumatica is a registered trademark of Acumatica, Inc. HubSpot is a registered trademark of HubSpot, Inc. Microso Exchange and Microso Exchange Server are registered trademarks of Microso Corporation. All other product names and services herein are trademarks or service marks of their respective companies.
Soware Version: 2025 R1 Last Updated: 04/15/2025
This document provides important information about fixes, enhancements, and key features that are available in Acumatica ERP 2025 R1. The document is designed particularly for those who install Acumatica ERP. All users can benefit from reviewing this content to determine how they may benefit from the changes in this release.
Information about fixes, enhancements, and key features for those who customize Acumatica ERP or develop applications for it can be found in the separate Release Notes for Developers document.
Installation and Upgrade Notes
We strongly recommend that before administrators upgrade Acumatica ERP to a newer product version, they back up all configuration files and databases used by the application instances. For a detailed description of the general procedure of updating Acumatica ERP, see Upgrading of Acumatica ERP: General Information.
Multiple changes have been made between Acumatica ERP 2024 R2 and Version 2025 R1 that may affect customizations and integrations. For details, see Release Notes for Developers.
If the Acumatica ERP instance was integrated with soware provided by an independent soware vendor (ISV) partner, we recommend that the administrator consult with this partner about the compatibility of its products with Acumatica ERP 2025 R1.
Supported Web Browsers for Acumatica ERP Workstations
Supported web browsers that can be used to work with Acumatica ERP 2025 R1 workstations are listed in the following table.
Web browsers on mobile devices are not supported. We recommend that the Acumatica mobile app be used. Microso Internet Explorer is not supported.
Table: Supported Web Browsers
Web Browser Version
Microsoft Edge 120 or later
Mozilla Firefox 130 or later
Apple Safari 17 or later
Google Chrome 120 or later
For details on system requirements, see System Requirements for the Acumatica ERP Installation.
Deprecated Support for the Authorize.Net Payment Plug-In
Starting in Acumatica ERP 2025 R1, the Authorize.Net plug-in will no longer be supported or available in the system. We encourage companies to take advantage of the Acumatica Payments plug-in, which provides greater functionality, better support, and competitive rates.
The client should contact its partner to create a presales support case to learn more about making the transition.
If the company have customer credit cards saved in the Authorized.Net gateway, aer an upgrade to Acumatica ERP 2025 R1, this data will be lost. The company should contact its partner for help with token migration.
If the company uses Acumatica ERP 2023 R2 or a later version, a system administrator can configure the Acumatica Payments plug-in without making any soware changes. For more information about Acumatica Payments, see Configuring and Using Acumatica Payments and To Configure Acumatica Payments.
Deprecated Third-Party Soware
Starting in Acumatica ERP 2025 R1, the system no longer supports the versions of third-party soware listed in the following table.
Software Version
Windows Server 2016 64-bit edition
Microsoft SQL Server • 2016 Service Pack 1
• 2017
MySQL Community Server 5.7
For details on system requirements, see System Requirements for the Acumatica ERP Installation.
Changes to the Report Scheduling
Starting in Acumatica ERP 2025 R1, the report scheduling has been reworked, as described in System Administration: Email Scheduling for Reports. The changes to this functionality will be implemented in the stages listed in the following table.
Version Stage
2025 R1 The Schedule Template button has been removed from the report toolbar of all report forms.
The report migration functionality has been added.
2025 R2 The Send Reports (SM205060) form has been removed.
2026 R2 The report migration functionality has been deprecated. This includes the removal of the Mi- grate command from the Automation Schedules (SM205020) form.
Aer the upgrade to Acumatica ERP 2025 R1, the system administrator will need to migrate automation schedules that have been configured by using the Send Reports (SM205060) form. For details, see After an upgrade to Acumatica ERP 2025 R2 and later, the functionality for sending reports using the Send Reports form will no longer be available.
Upgrade Policy
On the Apply Updates (SM203510) form, only minor updates are available for the currently installed version of Acumatica ERP. The administrator should upgrade the Acumatica ERP instance from previous major versions of the system to Version 2025 R1 manually on the server. (An upgrade through the web interface is not supported because the customization of the Acumatica ERP instance may be incompatible with Version 2025 R1 due to changes in Version 2025 R1.)
Prerequisite Steps
Before administrators install Acumatica ERP 2025 R1 or upgrade to it locally, they need to do the following:
1. Switch the Internet Information Services application pool where the Acumatica ERP 2025 R1 instance will be installed to Integrated mode. (Classic mode is not supported.)
2. Install Microso .NET Framework 4.8 on the server where the Acumatica ERP 2025 R1 instance will be installed.
Upgrade Path
The upgrade to Acumatica ERP 2025 R1 must be performed as described in the following table. The upgrade process depends on the version before the upgrade.
Table: Upgrade Paths for Acumatica ERP
From Version Upgrade Path
2024 R2 A direct upgrade to Acumatica ERP 2025 R1 is supported.
2024 R1 A direct upgrade to Acumatica ERP 2025 R1 is supported.
2023 R2 A direct upgrade to Acumatica ERP 2025 R1 is supported.
2023 R1 An incremental upgrade is required. The following steps must be performed in the listed order:
1. Upgrade to the latest Version 2023 R2 build available.
2. Upgrade to Version 2025 R1.
2022 R2 An incremental upgrade is required. The following steps must be performed in the listed order:
1. Upgrade to the latest Version 2023 R2 build available.
2. Upgrade to Version 2025 R1.
Acumatica ERP 2025 R1 can be upgraded from the following particular versions:
• 2024 R2 Update 8 (Build 24.208.0020) and earlier
• 2024 R1 Update 16 (Build 24.116.0026) and earlier
• 2023 R2 Update 19 (Build 23.219.0006) and earlier
Later versions are compatible with only the 2025 R1 Service Pack. It is not possible to upgrade them to Version 2025 R1.
For the list of upgradable versions for later 2025 R1 updates, see the release notes for the particular 2025 R1 update.
Actions Before the Upgrade
Before performing the upgrade to Acumatica ERP 2025 R1, an administrator should perform the actions described in the following sections.
Inventory and Order Management
If the Acumatica-LotSerialNbrAttribute customization project was used in the system before the upgrade, the administrator should contact their Acumatica support provider and request a migration script. For existing stock item records, a user can import lot and serial attributes by creating and using an import scenario on the Import Scenarios (SM206025) form.
• In Version 2025 R1, lot and serial attributes are not supported in manufacturing, field services, and retail commerce. If a company has published this customization project to deliver the functionality to these areas before the upgrade, it must continue using the customization project.
• Stock items that have been used in the customization project will not be added to Acumatica ERP if their lot or serial class had the When Used assignment method on the Lot/Serial Classes (IN207000) form before the upgrade.
Post-Upgrade Changes and Actions
An administrator should be aware of the changes that have been made in the system aer the upgrade to Acumatica ERP 2025 R1 has been performed. The following sections describe these changes, as well as any actions that the administrator needs to take aer the upgrade.
Finance
Aer an upgrade to Acumatica ERP 2025 R1, the following changes will be made in the system:
• On the Payment Methods (CA204000) form, the Send Payment Receipts Automatically check box will be cleared for all existing payment methods.
• On the Payments and Applications (AR302000) and Cash Sales (AR304000) forms, the Don't Print and Don't Email check boxes will be selected for existing documents. As a result, these documents will not appear for processing on the Print/Email AR Documents (AR508000) form.
• The upgrade script will perform the following changes on the Credit Terms (CS206500) form for all existing credit terms with the Custom due date type:
• The Date From 1 box for the first due day will be set to 1 and made read-only.
• The Date To 2 box for the second due day will be set to 31 and made read-only.
Inventory and Order Management
Aer an upgrade to Acumatica ERP 2025 R1, on the Purchase Orders Preferences (PO101000) form, the state of the
Display the Receive Transfer Tab check box will be the following:
• Selected if the Display the Receive Tab check box was selected before the upgrade
• Cleared if the Display the Receive Tab check box was cleared before the upgrade
Projects and Construction
Aer an upgrade to Acumatica ERP Construction Edition 2025 R1, an administrator should run the recalculation of project balances on the Recalculate Project Balances (PM504000) form by clicking Process All on the form toolbar. The recalculation of project balances is required before the new date-sensitive cost projections can be used. For more information, see Projects and Construction: Enhancements to the Cost Projection Functionality.
CRM
Aer an upgrade to Acumatica ERP 2025 R1, the Email activity type will be selected in the Activity Type box of the
Email Templates (SM204003) form for all email templates except the following:
• CRCasesPendingClosureNotification
• CRNewCaseNotification
• New Case Comment from Portal
For these email templates, the System Email option will be selected in the Activity Type box.
System Administration
Aer the upgrade to Acumatica ERP 2025 R1, a system administrator will need to migrate automation schedules that have been configured by using the Send Reports (SM205060) form. To locate these schedules, the administrator can filter schedules that have SM.20.50.60 in the Screen ID column on the Automation Schedule
Statuses (SM205030) form. The system also displays a warning for these records. The administrator can click a link in the Schedule ID column to open the Automation Schedules (SM205020) form for the schedule.
On the Automation Schedules form, for a schedule that requires migration, the Migrate button has been added to the form toolbar. Also, the system displays a warning about the deprecation of the Send Reports form and migration instructions.
The migration process creates an email template for each report template in the schedule and links it to a new schedule. It also deactivates the original schedule and marks as migrated to avoid duplication.
For details, see System Administration: Email Scheduling for Reports.
CRM: Implementation of the ISO 20022 Address Format
Acumatica ERP 2025 R1 introduces the extension of postal address data settings system-wide to adhere to the ISO 20022 standard. Adherence to the ISO 20022 standard provides the following advantages:
• Enhanced consistency and accuracy of address data
• Improved interoperability with global systems
• Better data exchange
• More efficient processing of international transactions.
The following section describes the changes in address data settings.
Extended Address Settings
Starting in Acumatica ERP 2025 R1, the following address settings have been added to the system:
• Department: The identifier of a large division within an organization or building
• Subdepartment: The identifier of a smaller division within a large division in an organization or building
• Street Name: The name of the street
• Building Number: The numerical or alphanumerical identifier assigned to the building
• Building Name: The name of the building
• Floor: The number indicating the level within the building
• Unit Number: The number identifying the particular unit or apartment if this is a multiunit building
• Post Box: The unique identifier for the private mailbox in a post office where mail is delivered
• Room: The specific room identifier within the building
• Town Location Name: The name of the town location
• District Name: The name identifying the subdivision within the city or town
By default, the extended address settings are not displayed on forms containing address data. Users can define which address settings should be displayed on specific forms as follows:
• On inquiry forms: By using the Column Configuration dialog box (see the following screenshot)
• On data entry forms: By using a customization project
Figure: The extended address settings in the Column Configuration dialog box
CRM: Improvements to the Calculation of Case Commitments
In previous versions of Acumatica ERP, the calculation of case commitment statistics was affected by outgoing emails that the system created based on email templates. The system treated these emails as response activities
—that is, activities of the Email type with the Outgoing check box selected on the Activity Types (CR102000) form. Thus, the system recognized the system email date and time as the response date and time, stopped tracking the time for fulfilling case commitments, and cleared the Initial Response Due and Response Due boxes for the case on the Cases (CR306000) form.
Starting in Acumatica ERP 2025 R1, the changes described in the sections below have been made to exclude system emails from the calculation time of fulfilling case commitments.
Enhancements to Email Activity Types
To distinguish emails created by the system from other outgoing emails, the System Email activity type with the ASE type ID has been added to the Activity Types (CR102000) form. (The following screenshot shows this type.) Users cannot change the settings of this type or remove the type from the Activity Types form.
Figure: The System Email activity type
On the Email Templates (SM204003) form, the Activity Type box has been added (see the following screenshot). In this box, users can select the type of email activity for which the selected email template is created.
Figure: The Activity Type box on the Email Templates form
The Activity Type box has the following options:
• Email (default): The email template is intended for emails created by users.
• System Email: The email template is intended for emails created by the system.
The System Email activity type is selected by default in the following predefined email templates on the Email Templates form:
• CRCasesPendingClosureNotification
• CRNewCaseNotification
• New Case Comment from Portal
If an email template has the System Email activity type, it cannot be selected in the Select Template dialog box on the Email Activity (CR306015) and Mass Emails (CR308000) forms.
The read-only Type box has been added to the Email Activity form (see the following screenshot). This box displays the activity type of an email.
Figure: The Type box on the Email Activity form
By default, the Email option is selected.
Enhanced Case Commitment Calculations
The Include System Activities in Response Time Calculation check box has been added to the Commitments tab of the Case Classes (CR206000) form, as shown in the following screenshot. This check box gives users greater flexibility in calculating response time for the fulfillment of case commitments.
Figure: The Include System Activities in Response Time Calculation check box
If the check box is selected, the system includes emails with the System Email activity type in the response time calculations in cases of the case class. This means that the system considers these emails to be responses, records their date and time for statistical purposes, and stops counting time for fulfilling case commitments. (This is
the way the system worked prior to Acumatica ERP 2025 R1, which may cause unintended inaccuracies in case fulfillment statistics.)
By default, the Include System Activities in Response Time Calculation check box is cleared, meaning that system emails are excluded from the calculation of response time for fulfilling case commitments.
Upgrade Notes
Aer an upgrade to Acumatica ERP 2025 R1, the Email activity type will be selected in the Activity Type box of the
Email Templates (SM204003) form for all email templates except the following:
• CRCasesPendingClosureNotification
• CRNewCaseNotification
• New Case Comment from Portal
For these email templates, the System Email option will be selected in the Activity Type box.
Additional Information
For more information about setting up the calculation of the case commitment statistics, see Case Classes: Case Commitments.
DeviceHub: Polling Frequency Settings for DeviceHub Scales
In Acumatica ERP 2025 R1, users can now specify the frequency of polling for scales in DeviceHub.
Specifying the Polling Frequency
A user can now change the frequency of polling for DeviceHub scales in the new Polling delays for weight retrieval section, as shown in the following screenshot.
Figure: The Polling delays for weight retrieval section
The section contains the following boxes:
• Delay between devices: This setting defines the minimum delay in milliseconds before DeviceHub can poll another scale and send the result to Acumatica ERP.
• Delay between polling cycles: The application polls all scales added to DeviceHub one by one. A single polling request to all of the scales constitutes a cycle. Once every scale has been polled, the application starts a new cycle. This setting defines the minimum delay in milliseconds before DeviceHub can start another cycle of polling.
Documentation: Improvements in User Guides
In Acumatica ERP 2025 R1, significant improvements have been made to the content and structure of the guides that make up the documentation, as described in the following sections.
Accounts Payable
In the Accounts Payable Guide, the following changes have been made:
• The former Configuring Predefined Mailings for Customers and Vendors chapter has been reworked into the Configuring Predefined Mailings for Vendors chapter. This chapter describes how to configure predefined mailings for vendors and how to use these mailings for sending and printing documents.
• The former Configuring the Reclassification of Expenses chapter has been reworked into the Configuring Reclassification of Expenses chapter. This chapter describes how to create a document with the default expense account and reclassify this expense.
• The former Managing Vendor Relations chapter has been reworked into the Managing Vendor Relations chapter. This chapter describes how to set up the vendor relations functionality and process a purchase from one vendor and the payment for the purchase to a different vendor.
• The former Rounding of Document Amounts chapter has been reworked into the Rounding of AP Document Amounts chapter. This chapter describes how to set up document amount rounding and process an AP document with a rounded amount.
• The former Configuring Schedules for Recurring Documents chapter has been reworked into the Creating Recurring AP Documents chapter. This chapter describes how to configure a schedule for document generation, run this schedule, and process the generated documents.
• The former Applying Payments to Particular Lines of AP Documents chapter has been reworked into the Applying Payments to Particular Lines of AP Documents chapter. This chapter describes how to create an AP bill that can be paid by line and pay one of its lines.
• The former Performing Period-End Procedures in AP chapter has been reworked into the Performing Period- End Procedures chapter. This chapter describes how to perform account reconciliation and how to close a financial period in accounts payable.
All the added chapters include activities that users can perform by using the U100 dataset.
Accounts Receivable
In the Accounts Receivable Guide, the following changes have been made:
• The Configuring Predefined Mailings for Customers chapter has been added. This chapter describes how to configure predefined mailings for customers and how to use these mailings for sending and printing documents.
• The former Types of AR Documents chapter has been replaced with the Processing Cash Sales and Cash Returns chapter. This chapter explains how to process a cash sale and a cash return.
• The former Rounding of Document Amounts chapter has been reworked into the Rounding of AR Document Amounts chapter. This chapter describes how to set up document amount rounding and process an AR document with a rounded amount.
• The former Configuring Schedules for Recurring Documents chapter has been reworked into the Creating Recurring AR Documents chapter. This chapter describes how to configure a schedule for document generation, to run this schedule, and process the generated documents.
• The former Applying Payments to Particular Lines of AR Documents chapter has been reworked into the Applying Payments to Particular Lines of AR Documents chapter. This chapter describes how to create an AR invoice that can be paid by line and pay one of its lines.
• The former Performing Period-End Procedures in AR chapter has been reworked into the Performing Period- End Procedures chapter. This chapter describes how to close a financial period in accounts receivable.
• The former Managing Commissions chapter has been reworked into the Managing Commissions chapter. This chapter describes how to set up salesperson commissions in the system, create a commissionable document, and calculate a commission for a salesperson.
• The former Managing Parent-Child Relationships chapter has been reworked into the Managing Parent- Child Relationships. This chapter describes how to set up parent and child relationships between existing customer accounts, process the documents of child accounts and parent accounts, and run a consolidated report to review the balances.
All the added chapters include activities that users can perform by using the predefined U100 dataset.
Service Management
The new Integrating Field Services with Projects chapter has been added. This chapter explains how to integrate the service management functionality with the project management functionality to enhance users' ability to effectively manage project tasks and resources. The chapter describes in detail the setup and use of the service management functionality in projects.
Route Management
The following chapters have been added to the guide:
• Route Executions with Service Delivery
• Route Executions with Item Delivery
In these chapters, users will learn how to do the following:
• Create a route execution that involves service delivery or the movement of inventory items
• Add appointments to a route
• View a route on the map
• Modify the route execution document
• Edit the order of appointments in the route execution
• Start, complete, and close the route execution
• Run route appointment billing
Data Migration
The new Finance Data Migration guide has been added. The chapters of this guide describe how to prepare the system for migrating data from a legacy ERP system to Acumatica ERP, as well as how to migrate financial data by using import scenarios. Additionally, users will learn how to verify the results of migration by reconciling the accounts' balances and cross-checking the imported records.
Field Services: Support of Stock Items With Lot or Serial Numbers Assigned in Appointments
Appointments oen include stock items. In some cases, lot or serial numbers need to be assigned to these stock items at the time they are used during an appointment, rather than when they are received in the warehouse. This is oen necessary when, for example, the specific item to be installed at the customer location is unknown beforehand, and the technician needs to enter the relevant number during installation.
In previous versions of Acumatica ERP, appointments that included stock items tracked by lot or serial numbers could not be processed if stock items had the When Used assignment method. This method is specified in the stock item's lot or serial class on the Lot/Serial Classes (IN207000) form. This was because a lot or serial number had to be specified for a stock item in the appointment's detail line. However, stock items with the When Used lot or serial number assignment method were not supported in appointments and therefore, a lot or serial number could not be specified for them.
Starting in Acumatica ERP 2025 R1, the Appointments (FS300200) form has been enhanced. Users can do the following for stock items whose lot or serial class has the When Used lot or serial number assignment method specified on the Lot/Serial Classes (IN20700) form:
• Manually generate lot or serial numbers for stock items, if the Auto-Generate Next Number check box is cleared in the stock item's lot or serial class on the Lot/Serial Classes form.
• View the auto-generated lot or serial numbers for stock items, if the Auto-Generate Next Number check box is selected in the stock item's lot or serial class on the Lot/Serial Classes form.
The functionality is available only if the Lot and Serial Tracking feature is enabled on the Enable/ Disable Features (CS100000) form.
Changes to the Appointments Form
On the Appointments (FS300200) form, a lot or serial number can now be assigned to a stock item with the following settings specified in the stock item's lot or serial class on the Lot/Serial Classes (IN207000) form:
• The Track Serial Numbers or Track Lot Numbers tracking method (Item 1 in the following screenshot)
• The When Used assignment method (Item 2)
(The following screenshot is provided to illustrate the settings closely related to the new functionality. However, no new elements have been added to the Lot/Serial Classes form.)
Figure: The stock item's lot or serial class settings
This functionality applies only to customers with a billing cycle set up to process billing for appointments.
The way a lot or serial number can be assigned to a stock item depends on the state of the Auto-Generate Next Number check box (Item 3 in the screenshot above) in the settings of the stock item's lot or serial class. The number is assigned as follows:
• If the Auto-Generate Next Number check box is selected, the system generates a lot or serial number for the stock item automatically and inserts it in the Lot/Serial Nbr. column in the item's line on the Details tab of the Appointments form.
• If the Auto-Generate Next Number check box is cleared, a user can initiate the generation of the lot or serial number on the Appointments form. To do this, the user first selects the detail line with the stock item and clicks Lot/Serial Nbrs. on the table toolbar of the Details tab. The user then clicks Generate in the Selection area of the Line Details dialog box.
In the Line Details dialog box, the following elements have been added to the Selection area (see the following screenshot):
Figure: The new UI elements in the Line Details dialog box
• Unassigned Qty.: The quantity of stock items that have no lot or serial numbers assigned.
• Quantity to Generate: The quantity of stock items for which lot or serial numbers will be generated. The system automatically inserts the value copied from the Actual Quantity column in the stock item's detail line on the Details tab. The user can edit this value. If the user specifies a smaller number than the actual quantity, the system generates the specified number of lot or serial numbers. When the user opens the dialog box again to generate lot or serial numbers for the remaining stock items, the system displays the actual quantity minus the number of items for which lot or serial numbers have already been generated.
For stock items whose lot or serial class settings require auto-generation of the lot or serial number, the Unassigned Qty. and Quantity to Generate boxes contain 0 by default. This is because the lot or serial numbers are automatically generated by the system when the appointment is saved.
• Start Lot/Serial Number: The alphanumeric value to be used as a start number for the lot or serial numbers. The system uses the value specified in the stock item's settings.
Figure: The generated serial numbers
For stock items with the When Used assignment method, lot or serial numbers cannot be generated and assigned in service orders on the Service Orders (FS300100) form. Additionally, the serial or lot numbers for stock items with the When Used assignment method generated in appointments on the Appointments form are not copied to related service orders.
The described functionality is not available in the Acumatica mobile app.
Field Services: Improvements in Managing Project- Specific Inventory
In previous versions of Acumatica ERP, the project-specific inventory functionality was not fully integrated with the service management functionality.
When an appointment or a service order was linked to a project with Track by Project Quantity and Cost selected in the Inventory Tracking box on the Summary tab of the Projects (PM301000) form, the system had the following limitations:
• For project stock items (those with the Project cost layer) whose lot or serial class had the Track Serial Numbers or Track Lot Numbers specified as the Tracking Method on the Lot/Serial Classes (IN207000) form, serial or lot numbers were not available on the Details tab of the Service Orders (FS300100) and Appointments (FS300200) forms.
• For project stock items whose lot or serial class had Not Tracked selected as the Tracking Method on the Lot/Serial Classes form, inventory allocations for the item plans FS Booked and FS Allocated were created in the system with the Normal cost layer. As a result, the available quantities for a specific project displayed in the table footer of the Service Orders and Appointments forms for a selected item could be inaccurate before the appointment or service order was billed.
Starting in Acumatica ERP 2025 R1, the Service Orders and Appointments forms have been enhanced to support projects where Track by Project Quantity and Cost is specified in the Inventory Tracking box on the Projects form. These enhancements include the following:
• Serial and lot numbers for project stock items are now available for selection on the Service Orders
(FS300100) and Appointments (FS300200) forms.
• For lines with stock items and a specified project task, the system now displays project-specific quantities in the table footer at the bottom of the Details tab of the Service Orders and Appointments forms.
• The Project cost layer is now assigned to inventory allocations created for service documents.
To make it possible to manage project stock items, the Project-Specific Inventory feature must be enabled on the Enable/Disable Features (CS100000) form.
These enhancements are described in detail in the next section of this topic.
Improvements to Managing Project Stock Items in Service Documents
For service orders and appointments linked to projects with Track by Project Quantity and Cost specified in the
Inventory Tracking box on the Projects (PM301000) form, the following changes have been implemented:
• In the Line Details dialog box of the Service Orders (FS300100) form, serial or lot numbers are now available in the Lot/Serial Nbr. column for a project stock item tracked by serial or lot number. The Line Details dialog box opens when a user selects a detail line and click the Line Details button on the table toolbar of the Details tab (see the following screenshot).
Figure: The lot or serial numbers for a project-reserved stock item
For stock items whose lot or serial class has the When Used assignment method specified on the Lot/Serial Classes form, a serial or lot number can be assigned only on the Appointments (FS300200) form.
• On the Appointments form, in the lookup table of the Lot/Serial Nbr. column on the Details tab, only the serial or lot numbers for the selected project stock item are displayed (see the following screenshot.) A user can select the serial or lot number in this lookup table.
Figure: The list of serial numbers available for the selected project-specific stock item
• On the Appointments form, in the Line Details dialog box, only serial or lot numbers of the selected project stock item are displayed. (This dialog box opens when a user selects a detail line and clicks Lot/Serial Nbrs on the table toolbar.) A user can view the serial or lot number in this box.
• On the Service Orders and Appointments forms, at the bottom of the Details tab, the table footer displays the project stock quantities and free stock quantities of the selected item (see the following screenshot) as follows:
• The first value (before the slash) shows the available quantity of stock items in the Project cost layer related to the selected project and project task.
• The second value (aer the slash) shows the quantity of free stock items (that is, of the Normal cost layer) and project stock items stored in the warehouse location that is specified in the line.
Figure: Project-specific and free stock quantities displayed in the table footer
• The system can now manage the allocation of stock items with a Project cost layer type. It automatically determines and assigns the appropriate allocation type (for example, FS Prepared, FS Booked, and FS Allocated) along with the Project cost layer when creating allocations for service documents that include project stock items tracked by serial or lot number. Users can view these allocations on the Inventory Allocation Details (IN402000) form.
Figure: An allocation type specified according to the Project cost layer
Finance: Increasing of the Authorized Payment Amount
In previous versions of Acumatica ERP, for a payment whose payment method has the Credit Card means of payment, a user could capture an amount that was less than or the same as the authorized payment amount. However, there was no way to increase the captured amount so that it exceeded the authorized amount. To work around this limitation, the user could void the authorization and create a new one; however, the system required some time to complete the voiding process. This sometimes resulted in reserving excess funds being reserved on the customer's account.
Starting in Acumatica ERP 2025 R1, for payments by credit card, users can increase the authorized amount. The system will change only the authorized amount in the original transaction. The other transaction settings, such as the expiration date, will not change.
The following sections describe the changes to the UI and document processing to support this functionality.
Changes to the Processing Centers Form
On the Processing Centers (CA205000) form, the following sections have been added to the Summary area:
• Payment Profile (see Item 1 in the screenshot below). The following check boxes have been moved to this section: Allow Saving Payment Profiles, Synchronize Deletion, and Accept Payments from New Cards.
• Payment Processing (Item 2). The following check boxes have been moved to this section: Accept Payments from POS Terminals, Allow Unlinked Refunds, and Allow Payment Links. Also, the new Allow Increasing Authorized Amounts check box has been added to the section (Item 3). When this check box
is selected, users can increase the authorization amounts for documents on data entry forms. The check box is available only if the selected processing center plug-in supports the functionality of incrementing authorization amounts.
Figure: UI changes on the Processing Centers form
Changes to the Sales Orders Form
On the Payments tab of the Sales Orders (SO301000) form, the Increase Authorized Amount button has been added to the table toolbar (see the screenshot below). This button appears on the form only if the selected order type has one of the following behaviors:
• Blanket Order
• RMA Order
• Sales Order
• Invoice
Figure: The Increase Authorized Amount button on the Sales Orders form
• The sales order has an unapplied amount.
• The payment method of the payment selected on the Payments tab has the Credit Card means of payment specified on the Payment Methods (CA204000) form.
• The processing center used for the selected payment has the Allow Increasing Authorized Amounts check box selected on the Processing Centers (CA205000) form.
• The processing status of the payment on the Payments tab of the Sales Orders form is Pre-authorized.
When the user selects a row with a payment and clicks the Increase Authorized Amount button, the Increase Authorized Amount dialog box is opened (see the following screenshot).
Figure: The Increase Authorized Amount dialog box
Changes to the Invoices Form
On the Applications tab of the Invoices (SO303000) form, the Increase Authorized Amount button has been added to the table toolbar (see Item 1 in the screenshot below).
• The sales invoice has an unapplied amount.
• The payment method of the payment selected on the Applications tab of the form has the Credit Card
means of payment specified on the Payment Methods (CA204000) form.
• The processing center used for the selected payment method has the Allow Increasing Authorized Amounts check box selected on the Processing Centers (CA205000) form.
• The processing status of the payment on the Applications tab of the Invoices form is Pre-authorized.
When the user selects a row with a payment and clicks the Increase Authorized Amount button, the Increase Authorized Amount dialog box is opened (see Item 2).
Figure: UI changes on the Invoices form
If a user clicks this button, the system checks whether the payment is applied to multiple sales invoices or to a sales invoice and a sales order that is not related to the invoice. If this condition is met, the system displays a warning message.
Changes to the Credit Card Processing for Sales Form
On the Credit Card Processing for Sales (SO507000) form, the following UI changes have been made:
• In the Action box, the Increase Authorized Amount option has been added to the drop-down list (see Item 1 in the following screenshot).
• If the Increase Authorized Amount option is selected, the Increased Authorized Amount and Increased Applied Amount columns appear in the table (Item 2).
Figure: The UI changes on the Credit Card Processing for Sales form
When a user selects a payment and clicks Process or Process All on the form toolbar, the system performs the following actions for each selected row:
1. Checks if the payment in each selected row has an available balance. If a payment's balance is greater than 0.00, the system displays an error message.
2. Sends an API request for the rest of the selected payments and updates the payments and their application details upon successful authorization. If the API request has returned an error, the authorized amounts remain the same and the payment amount and applied amount are not updated.
When this check box is selected, the Increased Authorized Amount and Increased Applied Amount columns appear in the table. If these columns contain values, the authorized payment amount can be increased for the row. If these columns are empty, the capture process will be applied to the payment amount in the row when Process is clicked.
Figure: The Increase Authorized Amount Before Capture check box
With this check box selected, when a user selects a payment and clicks Process or Process All on the form toolbar, the system performs the following actions for each processed payment:
1. Checks whether the authorized amount can be increased for the payment. If the amount cannot be increased, the system captures the existing amount.
a. Checks whether the payment has an available balance and displays an error message if the balance is greater than 0.00.
b. Checks whether the payment applied to the sales invoice still has an amount applied to the related sales order. If it does, the system displays an error message.
c. Sends an API request increasing the authorized amount for the payment and updates the payments and their application details upon successful authorization.
d. Sends an API request for capturing the payment.
If the API request for increasing the amount returns an error, the system does not capture the amount. It creates a record for each problem payment and displays the error message received from the processing
center. The user can then try to capture the payment with the Increase Authorized Amount Before Capture check box selected again or clear this check box to capture the current amount.
Changes to the Payments and Applications Form
On the Payments and Applications (AR302000) form, if a user clicks Validate Card Payment on the More menu, the system does the following:
1. Verifies the transaction amount by comparing the credit card transaction amount and the payment amount in Acumatica ERP
2. If the transaction amount was increased, updates the payment amount and the payment application amount, if possible, in Acumatica ERP
The increased payment amount remains unapplied if either of the following conditions is met:
• The system cannot determine from which application the amount was increased.
• This sales order or sales invoice does not have an unpaid balance.
Additional Information
For more details about increasing the authorized amount in sales orders, see Sales with Payments and Prepayments: Increasing of the Authorized Amount.
Finance: Payment Receipts for Released Transactions
In previous versions of Acumatica ERP, aer a payment was processed in the system, merchants could not issue the proof of purchase to their customers.
Starting in Acumatica ERP 2025 R1, merchants can generate payment receipts for released transactions. On the Payments and Applications (AR302000) and Cash Sales (AR304000) forms, a user can send an email with a payment receipt or print the payment receipt. This functionality can be used if the following conditions are met:
• The payment is created with the Credit Card, POS, or EFT payment method, and is captured and released
• The payment is created with the Cash, Check, or Direct Deposit payment method, and is released
The PDF attachment in the generated email includes the payment details and cash sale details. This PDF report can also be printed.
The following sections describe the changes to the UI and document processing to support this functionality.
Changes to the Payment Methods Form
On the Payment Methods (CA204000) form, the Send Payment Receipts Automatically check box has been added to the Settings for Use in AR tab, as shown in the following screenshot.
Figure: The Send Payment Receipts Automatically check box
By default, this check box is cleared. If this check box is selected, payment receipts for the specified payment method will be sent automatically from the Payments and Applications (AR302000) and Cash Sales (AR304000) forms. Regardless of the state of this check box, users will also be able to manually send payment receipts from these forms.
Changes to the Accounts Receivable Preferences Form
On the Accounts Receivable Preferences (AR101000) form, the new Pay Receipt mailing ID has been added to the table on the Mailing and Printing tab, as shown in the following screenshot.
Figure: The Pay Receipt mailing on the Mailing and Printing tab
This row in the table defines the mapping between the mailing and the email template that will be used to send payment receipts from the Payments and Applications (AR302000) form. The mailing is active by default. If the organization needs to change or update this mapping, a system administrator can do it on the Customer Classes (AR201000) or Customers (AR303000) form.
Changes to the Payments and Applications Form
• Print Payment Receipt (see Item 1 in the screenshot below). When a user clicks this command, the system opens the payment receipt on the Payment Receipt (AR643000) form where the user can print it.
• Email Payment Receipt (Item 2). When a user clicks this command, the system generates an email message to the customer's email address. This address is specified in the Account Email box on the General tab of the Customers (AR303000) form. The user can review the generated email by clicking Activities on the title bar of the form.
Figure: New commands on the More menu of the Payments and Applications form
Payment receipts can be printed and emailed for all of the following document types: Payment, Prepayment, Refund, Voided Payment, and Voided Refund.
These commands become available in either of the following cases:
• On the Payment Methods (CA204000) form, the Integrated Processing check box on the Settings for Use in AR tab is selected, the Means of Payment is set to Credit Card, POS Terminal, or EFT, and the payment has been successfully captured and released
• On the Payment Methods form, the Integrated Processing check box is cleared, the Means of Payment is set to Check, Cash, or Direct Deposit, and the payment has been successfully released
On the Financial tab of the Payments and Applications form, the Print and Email Options section has been added, as shown in the following screenshot.
Figure: The Print and Email Options section on the Financial tab
This section contains the following check boxes:
• Printed: Read-only. This check box indicates, if selected, that the payment receipt has been printed. By default, this check box is cleared.
• Emailed: Read-only. This check box indicates, if selected, that the payment receipt has been emailed. By default, this check box is cleared.
• Don't Print: Read-only. This check box is selected by default.
• Don't Email: This check box is selected by default. The default state of this check box depends on the state of the Send Payment Receipts Automatically check box (Settings for Use in AR tab) on the Payment Methods (CA204000) form. If the Send Payment Receipts Automatically is selected, this check box is cleared. A user can change the state of this check box before the payment opened on the Payments and Applications form is captured.
On the Card Processing tab of the Payments and Applications form, the Card Number column has been added to the table, as shown in the following screenshot.
Figure: The Card Number column on the Card Processing tab
In this column, the system displays the last four digits of a masked credit card number, which was used to make a payment if the customer payment method was not saved. These last four digits are stored in the system and are displayed on the Payments and Applications (AR302000) and Cash Sales (AR304000) form, if the payment is captured with the Credit Card or POS Terminal payment method.
Changes to the Invoice/Memo Form
On the document printed on the Invoice/Memo (AR641000) form, the Payment Details section has been added to the bottom of the form, as shown in the following screenshot.
Figure: The updated Invoice/Memo form
This updated form is opened by the system when a user clicks Print on the More menu of the Cash Sales
(AR304000) form.
Changes to the Print Invoices and Memos Form
The Print Invoices and Memos (AR508000) form has been modified to support mass-processing of payment receipts and to schedule automation of payment receipts. The following UI changes have been added to the form:
• The form title has been changed from Print Invoices and Memos to Print/Email AR Documents (Item 1 in the screenshot below).
• In the drop-down list in the Action box, the following modifications have been made (Item 2):
• The title of the Print option has been changed to Print Invoices. The behavior of this option to print invoices and cash sales remains unchanged.
• The title of the Email option has been changed to Email Invoices. The behavior of this option to email invoices and cash sales remains unchanged.
• The Email Payment Receipts option to process payment receipts has been added.
• The Payment Method column (Item 3) has been added to the table. This column displays the payment method used for creating the payment. (For invoices, this column is empty.)
Figure: The UI changes on the Print/Email AR Documents form
The table on the form now displays documents of the following types: Invoice, Debit Memo, Credit Memo, Overdue Charge, Credit WO, Cash Sale, Cash Return, Payment, Prepayment, Voided Payment, Refund, and Voided Refund.
The functionality of the Show All check box has been changed as follows:
• If this check box is cleared, the system displays the documents that match the selection criteria and have the Don't Email and Emailed check boxes cleared on the Financial tab of the Payments and Applications (AR302000), Invoices and Memos (AR301000), or Cash Sales (AR304000) form.
• If this check box is selected, all the documents are available for processing regardless of the specified selection criteria.
Scheduling of Automatic Receipts
To schedule the automation of payment receipts, an administrative user should perform the following instructions:
1. On the Payment Methods (CA204000) form, select the Send Payment Receipts Automatically check box for the needed payment methods.
2. On the Print/Email AR Documents (AR508000) form, create a schedule. Once the schedule is created, payment receipts will be automatically sent to customers.
The Payment Receipt Report
The new Payment Receipt (AR643000) report has been added to the system. The system uses this form to print payment receipts from the Payments and Applications (AR302000) form. The printed form of the report is shown in the following screenshot.
Figure: The new Payment Receipt report
The users with the following roles assigned to them will have access to this report: Administrator, AcumaticaSupport, AR Admin, AR Clerk, SO Admin, AR Viewer, and Sales Manager.
Upgrade Notes
Aer an upgrade to Acumatica ERP 2025 R1, the following changes will be made in the system:
• On the Payment Methods (AR204000) form, the Send Payment Receipts Automatically check box will be cleared for all existing payment methods.
• On the Payments and Applications (AR302000) and Cash Sales (AR304000) forms, the Don't Print and Don't Email check boxes for existing documents will be selected. As a result, these documents will not appear for processing on the Print/Email AR Documents (AR508000) form.
Additional Information
For more information about payment receipts for cash sales and cash returns, see Cash Sales and Cash Returns: Payment Receipts.
For more information about payment receipts for invoice payments, see Invoice Payments: Payment Receipts. For more information about receipts for prepayments, see Invoice Prepayments: Payment Receipts.
For more information about payment receipts for refunds, see Refunds: Payment Receipts.
Finance: Prepayments from Sales Order Payment Links
In previous versions of Acumatica ERP, a payment received from a payment link for a sales order and sales invoice was created as a document with the Payment type. However, it is preferable to create a document for a sales order as a prepayment. (Prepayments are usually posted to a different AR account—Prepayment AR account.)
Starting in Acumatica ERP 2025 R1, a user can specify whether the system must create a document with the
Prepayment type for payments received from payment links created for sales orders.
On the Payment Links tab of the Processing Centers (CA205000) form, the Create from SO Payment Link box has been added as shown in the following screenshot.
Figure: The Create from SO Payment Link box on the Processing Centers form
This box contains the following options:
• Payment (default): The system will create payments from payment links created for sales orders.
• Prepayment: The system will create prepayments from payment links created for sales orders. This change affects payments that are created in the system when a user does one of the following:
• Clicks the Sync Payment Link button on the Payment Links tab of the Sales Orders (SO301000) form
• Selects the Sync Payment Link option in the Action box on the Process Payment Links (AR513500) form, selects the needed row in the table and clicks Process on the form toolbar
• Syncs a payment link by using a webhook
Finance: Recording of Finance Charges for Refunds
In previous versions of Acumatica ERP, if a user was entering a refund on the Payments and Applications (AR302000) form, they could not add finance charges to the refund on the Charges tab.
Starting in Acumatica ERP 2025 R1, users can add charges to refunds and voided refunds on the Payments and Applications form. The charge amount can be either a positive value or a negative value.
Entry of Charges for a Refund
On the Charges tab of the Payments and Applications (AR302000) form, a user can add finance charges to a refund, as shown in the following screenshot.
Figure: Finance charges added to a refund
When the refund is released, the positive amount of the charge will credit the cash account, and the negative amount of the charge will debit the cash account. The posted GL transaction is shown in the following screenshot.
Figure: The GL transaction posted for the refund with charges
Entry of Charges for a Voided Refund
When a user voids a refund on the Payments and Applications (AR302000) form, the system creates a document with the Voided Refund type. On the Charges tab of the form, the system automatically adds charges with the opposite sign of the values in the original refund. A voided refund with charges is shown in the following screenshot.
Figure: A voided refund with finance charges
Finance: Support of the BAI2 Format by Bank Feeds
In previous versions, Acumatica ERP did not support the Bank Administration Institute Version 2 (BAI2) format of bank statements. The Balance and Transaction Reporting Standard (BTRS) improves upon the BAI2 format. The BAI2 and BTRS formats are banking industry standards for communicating bank statements electronically.
Starting in Acumatica ERP 2025 R1, the BAI2 and BTRS file formats are supported by bank feeds. When a user retrieves bank feed transactions, the system detects a new file with transactions exported to it by a bank and creates bank transactions for the specified cash account. If a corporate card and employee are specified in the bank feed settings, the system creates expense receipts for them.
This functionality is available in the system if the Bank Feed Integration feature is enabled on the Enable/Disable Features (CS100000) form.
The following sections describe the changes to the UI and document processing to support this file format.
Changes to the Bank Feeds Form
On the Bank Feeds (CA205500) form, the following UI changes have been made:
• In the File Format box, the BAI2 (Bank Administration Institute) option has been added (Item 1 in the screenshot below). If this option is selected, the system checks for files with .bai, .bai2, or .btrs extension in the specified SFTP folder.
If the user selects this option, the boxes in the Source File section are not shown on the form, except for
Data Provider (Item 2).
• In the Source File section, the system inserts the Bank Feed BAI2 data provider (Item 3), which it created when the user clicks Set Up Data Provider. This type of data provider has been added on the Data Providers (SM206015) form and can parse files with BAI, BAI2, and BTRS formats.
• With the Bank Feed BAI2 data provider specified, the system automatically fills in the table in the Mapping Rules section (Item 4) with the mapping rules for required fields, which cannot be edited. However, users can set up mapping for optional fields.
Figure: UI changes on the Bank Feeds form
The Bank Reference Number source field is optional in the BAI2 format, but is required in Acumatica ERP because it is mapped to the transaction ID. The transaction ID is used by the system to identify transactions and avoid duplicate records.
Setup of BAI2 Transaction Retrieval
To set up the functionality of retrieving BAI2 transactions from a bank feed, an administrative user does the following:
1. On the Bank Feeds (CA205500) form, creates a bank feed, selecting BAI2 (Bank Administration Institute) as the File Format and entering credentials to the SFTP folder where the bank stores BAI2 files.
2. Clicks Set Up Data Provider. The system creates a new data provider for BAI2 files and inserts it in the Data Provider box.
3. Reviews the mapping rules populated by the system and changes the mapping for optional fields, if needed.
4. On the Cash Accounts tab of the Bank Feeds form, specifies the needed bank accounts and their corresponding cash accounts.
5. Activates the bank feed by clicking Activate on the form toolbar. This changes the bank feed’s status to Active. Now a user can start retrieving bank transactions on the Retrieve Bank Feed Transactions (CA507500) form.
Additional Information
For more details about support of the BAI2 format, see Loading of Bank Feeds from BAI2 Files.
For details on setting up bank feeds that support the BAI2 format, see To Set Up Bank Feeds Loaded from the BAI2 Format.
Finance: Other Improvements
In Acumatica ERP 2025 R1, multiple improvements to financial management processes and the UI have been introduced, as described below.
Refined Validations for a Custom Due Date Type
In previous versions of Acumatica ERP, credit terms with the Custom due date type could be created without the dates covering all the dates of a month. As a result, issues occurred when the system tried to insert the default due date in transactions.
In Acumatica ERP 2025 R1, on the Credit Terms (CS206500) form, the following refinements have been made to the validations that the system performs if Custom is selected in the Due Date Type box:
• The system now inserts 1 in the Day From 1 box for Due Day 1 (see Item 1 in the screenshot below) to ensure that the beginning of the month is covered. This setting is read-only.
• The value in the Day To 1 box for Due Day 1 must (Item 2) be less than 31; otherwise, the system displays an error message. Also, the day in the Day To 1 box must be later than or the same as the day specified in the Day From 1 box. If this condition is not met, the system displays an error message.
• The Day From 2 setting for Due Day 2 (Item 3) is now read-only. Its value is one day later than the day in the
Day To 1 box.
• The system inserts 31 in the Day To 2 box for Due Day 2 (Item 4) to ensure that the end of the month is covered. This setting is read-only. The day in the Day To 2 box must be later than or the same as the day specified in the Day From 2 box. If this condition is not met, the system displays an error message.
Figure: The boxes with refined validations
Upgrade Notes
Aer an upgrade to Acumatica ERP 2025 R1, the upgrade script will perform the following changes on the Credit Terms form for all existing credit terms with the Custom due date type:
• The Date From 1 box for the first due day will be set to 1 and made read-only.
• The Date To 2 box for the second due day will be set to 31 and made read-only.
Validation of Acumatica Payments Imported from Shopify
In previous versions of Acumatica ERP, the processing of payments initiated in the Acumatica Payments processing center from Shopify was not supported on the Acumatica ERP side due to missing processing center IDs. (Acumatica ERP uses these IDs for interactions with the processing center when the system performs actions, such as capture, void, or refund.) These IDs were missing because the Acumatica Payments plug-in in Shopify could not save the Acumatica Payments IDs to the Shopify database.
Starting in 2025 R1 RC, Acumatica ERP will support the Acumatica Payments processing center in ecommerce systems that use their internal IDs in interactions with a processing center and do not keep the IDs assigned by the processing center. Users will be able to import payments and refunds from these ecommerce systems into Acumatica ERP.
These payments and refunds must be validated aer import. Users can initiate the validation for a particular document on the Payments and Applications (AR302000) form or for multiple documents on the Validate Card Payments (AR513000) form. The validation process can be scheduled.
Improvements on the Manage Credit Holds Form
In previous versions of Acumatica ERP, if Credit Hold was selected in the Action box on the Manage Credit Holds (AR523000) form and a user selected the Show All check box, nothing changed from what was previously shown in the table. If the Remove Credit Hold action was selected and the user selected the Show All check box, all available records with all statuses were added to the table. This behavior was confusing because with this check box selected, the system should ignore all selection criteria on the form. Also, if one of the dates was not specified in the Start Date or the End Date box, no records were listed in the table.
To fix these issues, the following changes have been introduced on the Manage Credit Holds form:
• The Show All check box has been removed from the Selection area.
• If the Remove Credit Hold option is selected in the Action box, the form’s UI changes as follows:
• The Start Date and End Date boxes in the Selection area become hidden.
• The system displays only customers with the Credit Hold status.
The following screenshot illustrates the form with the Remove Credit Hold option selected.
Figure: The form with Remove Credit Hold selected
• If the Credit Hold option is selected in the Action box, the form’s UI changes as follows:
• The Start Date and End Date boxes are empty by default.
• If the start date is specified, the table shows only customers with the Active and One-Time statuses whose final dunning letter date is later than or the same as the start date.
• If the end date is specified, the table shows only customers with the Active and One-Time statuses whose final dunning letter date is earlier than or the same as the end date.
The following screenshot illustrates the form with the Credit Hold option selected.
Figure: The form with Credit Hold selected
Prevention of Auto-Reopening a Payment Link
In previous versions of Acumatica ERP, if a payment made by using a payment link was voided, the payment link became open again on the processing center's side and no notification was sent to the system. Consequently, the user could create a new payment link for this document, which could result in a duplicated payment.
To prevent the automatic reopening of a payment link, a new API parameter (auto-reopen) has been introduced for API requests for payment link creation and sync. This parameter will be set to false by the system for all created payment links. As a result, a payment link will remain closed on the processing center's side if the related transaction is voided, refunded, or unlinked.
Deprecated Support for the Authorize.Net Payment Plug-In
Starting in Acumatica ERP 2025 R1, the Authorize and Authorize and Capture commands on the More menu of accounts receivable forms will no longer be supported for credit card payments created through the Authorize.Net plug-in. As a result, users will no longer be able to create new transactions with Authorize.Net. The Capture, Void, Refund, and Validate Card Payment commands will remain available for existing payments with preliminarily authorized transactions. The Record Card Payment,Record and Capture Preauthorization, and Import Settlement Batches commands will also be available. Users will not be able to create new customer payment methods for Authorize.Net.
We encourage companies to take advantage of the Acumatica Payments plug-in, which provides greater functionality, better support, and competitive rates.
The client should contact its partner to learn more about making the transition to Acumatica Payments. If the company uses Acumatica ERP 2023 R2 or a later version, a system administrator can configure the Acumatica Payments plug-in without making any soware changes. For more information about Acumatica Payments, see Configuring and Using Acumatica Payments and To Configure Acumatica Payments.
Cancellation or Correction of an Invoice with Externally Calculated Taxes
In previous versions of Acumatica ERP, an issue arose with canceling or correcting invoices whose taxes were calculated by external tax providers. When a user canceled or corrected such an invoice, the taxes in the created
credit memo could differ from those applied to the original invoice. This caused the credit memo to fail when being applied to the invoice and prevented the release of the correction invoice.
For example, the inconsistency between the original invoice and the credit memo could occur when an exemption certificate was added for a customer in the external tax provider account (such as Avalara or Vertex) aer the invoice was created and released for this customer in Acumatica ERP. The user’s attempt to correct the invoice failed due to the discrepancy in totals between the original taxed invoice and the tax-free credit memo. This prevented the correction invoice from being released, and an error was displayed.
In Acumatica ERP 2025 R1, the process for canceling or correcting invoices with taxes calculated by external providers has been optimized. When a user cancels or corrects an invoice, the system creates a credit memo with the same taxes and document totals as the original invoice. Thus, the credit memo can be applied to the invoice, and the correction invoice can be released.
Integrations: Ability to Deactivate Ship-Via Codes and External Carriers
In previous versions of Acumatica ERP, users could not deactivate ship-via codes that had been created for discontinued external carriers. When a user shopped for rates for a shipment, these ship-via codes generated additional API calls to carrier services and returned non-functional rates.
Acumatica ERP 2025 R1 delivers the ability to deactivate unused ship-via codes and carriers. The inactive ship-via codes are unavailable for selection and do not generate any API calls to carrier services.
Deactivation of a Ship-Via Code or Carrier
To deactivate an unused ship-via code, the user needs to clear the Active check box for this code on the Ship via Codes (CS207500) form, as shown in the screenshot below, and save the record.
Figure: The Active check box on the Ship via Codes form
To deactivate an unused external carrier, the user needs to clear the Active check box for this carrier on the Carriers
(CS207700) form, as shown in the screenshot below, and save the record.
Figure: The Active check box on the Carriers form
If the user deactivates an external carrier that is used in an existing ship-via code, the system will also deactivate this code. That is, on the Ship via Codes form, the system will automatically clear the Active check box for this code and make it unavailable for editing. If this ship-via code has been selected in an unprocessed sales order or shipment, the system will show an error when the user attempts to complete the document's processing. To proceed with the processing, the user needs to select an active ship-via code.
The Active check box is cleared for a new ship-via code or external carrier by default
Upgrade Notes
Aer the upgrade to Acumatica ERP 2025 R1, for all existing ship-via codes and carriers, the Active check box will be selected by default.
Integrations: Filtering in the Shop for Rates Dialog Box
In previous versions of Acumatica ERP, if a user updated the rates in the Shop for Rates dialog box on the Sales Orders (SO301000), Shipments (SO302000), or Pick, Pack, and Ship (SO302020) form, the list of carrier rates started with the rates that returned errors or had an amount of 0.
Starting in Acumatica ERP 2025 R1, the Quick Filter and Filter Settings buttons have been added to the filtering area of the Shop for Rates dialog box. By default, the Available Rates quick filter (Item 1 in the following screenshot) is applied to the Carrier Rates table. With this quick filter applied, a user can have all the available rates at hand (Item 2). To see all the rates, the user can click the Quick Filter button and select All Records.
Also, the Filter Settings button has been added to the filtering area dialog box (Item 3). By clicking this button, a user can open the Filter Settings dialog box and specify additional filtering conditions for the following properties: Selected, Code, Description, Amount, Days in Transit, and Delivery Date.
Figure: Filtering in the Shop for Rates dialog box
Integrations: Multiple Access Tokens for Each External Application
When integrating Acumatica ERP with third-party services, administrators create external applications that connect Acumatica ERP and these services. To verify users, these services oen employ the OAuth authorization protocol, allowing these users to sign in on behalf of a specific account and receive an access token. This token is then used to request data that is available to the particular user. For certain services, such as Microso Exchange or Gmail, a separate access token must be specified for each user, to ensure that they can access only their own data.
In earlier versions of Acumatica ERP, each external application could use only a single access token. As a result, administrators had to create a separate external application for every third-party user, which created a significant burden for both users and administrators.
However, in Acumatica ERP 2025 R1, administrators can now create multi-token external applications—that is, applications having a single set of application parameters and multiple tokens associated with different users.
For example, administrators can now integrate the Gmail and Microso 365 email services as external applications that share a common set of application parameters, while allowing different users to specify their personal access tokens.
Changes to the External Applications Form
On the External Applications (SM301000) form, the following changes have been made to support multiple-token OAuth 2.0 applications:
• The new OAuth 2.0 option is available in the Type box (Item 1 in the following screenshot).
• The Authentication Token section was replaced with the Tokens tab, which lists the access tokens obtained for the application.
• The Return URL box has been removed and replaced with the View Redirect URI toolbar button.
• The Sign In command on the More menu becomes disabled for multi-token applications. To sign into the third-party services, users now need to use the Sign In commands on the User Profile (SM203010) or Email Accounts (SM204002) form.
Figure: Multi-token external application
Changes to the Email Accounts Form
On the Email Accounts (SM204002) form, the following changes have been made to support multiple-token external applications for the Gmail and Microso 365 email services:
• The new OAuth 2.0 for Gmail and OAuth 2.0 for Microso 365 options are available in the Authentication Method box (Item 1 in the following screenshot).
Accounts that use these authentication methods can share external application parameters and have their own personal access tokens. When an administrator selects one of these options, the administrator should then select an application of the new OAuth 2.0 type in the External Application box.
• The OAuth2 Scopes and OAuth2 Parameters boxes have been added (Item 2). These boxes contain predefined values of scopes and parameters that the system will use when issuing access tokens, but administrators have the flexibility to modify these values if necessary. These boxes appear only when OAuth
2.0 for Gmail or OAuth 2.0 for Microso 365 is selected in the Authentication Method box.
Figure: Email account settings for personal token OAuth authorization
Integrations: Removal of Obsolete FedEx and UPS Plug-Ins
In Acumatica ERP 2025 R1, obsolete plug-ins for the FedEx and UPS carrier services have been removed.
Removal of the Obsolete FedEx Plug-In
On August 31, 2024, FedEx stopped supporting its SOAP API.
Starting in Acumatica ERP 2025 R1, the FedEx SOAP API is no longer supported, and the obsolete FedEx plug-in with the PX.FedExCarrier.FedExCarrier type has been removed. The system administrator should select the FedEx Rest plug-in with the PX.FedExRestCarrier.FedExRestCarrier type in the Plug-In box on the Carriers (CS207700) form instead.
Removal of the Obsolete UPS Plug-In
On June 3, 2024, UPS stopped using its SOAP API.
Starting in Acumatica ERP 2025 R1, the UPS SOAP API is no longer supported, and the obsolete UPS plug-in with the PX.UpsCarrier.UpsCarrier type has been removed. The system administrator should select the UPS Rest plug-in with the PX.UpsRestCarrier.UpsRestCarrier type in the Plug-In box on the Carriers (CS207700) form instead.
Inventory and Order Management: Capturing Weights of Packages from DeviceHub
In previous versions of Acumatica ERP, the use of a scale connected to DeviceHub for weighing packages was limited to the scenario of packing shipments on the Pick, Pack, and Ship (SO302020) form. The users who added packages to shipments on the Shipments (SO302000) form could only type the weight of a package manually.
Starting in Acumatica ERP 2025 R1, users can capture the weighing result from DeviceHub on the Packages tab and in the Shop for Rates dialog box on the Shipments form.
This functionality is available only if the DeviceHub feature is enabled on the Enable/Disable Features
(CS100000) form.
Capture of the Weight of a Package on the Packages Tab
A user may need to specify the weight of a package on the Packages tab of the Shipments (SO302000) form while preparing a shipment for sending it to an external carrier service. To perform this operation, the user selects the package and clicks the new Capture Weight button on the table toolbar of the upper table on this tab (Item 1
in the following screenshot). If a default scale is specified for the user account, the system automatically inserts this scale's value from the Last Weight column on the Scales (SM206530) form into the Weight column on the Packages tab of the Shipments form (Item 2).
Figure: Capturing the weight of a package on the Packages tab
Capture of the Weight of a Package in the Shop for Rates Dialog Box
A user may want to specify the weight of a package directly in the Shop for Rates dialog box on the Shipments (SO302000) form before they get the carrier rates. To perform this operation, the user adds the packages to the Packages table in the dialog box, selects a package, and clicks the Capture Weight button on the table toolbar (Item 1 in the following screenshot). If a default scale is specified for the user account, the system automatically
inserts this scale's value from the Last Weight column on the Scales (SM206530) form into the Weight column on the Packages tab of the Shipments form (Item 2).
Figure: Capturing the weight of a package in the Shop for Rates dialog box
Specification of the Default Scale for a User Account
A user can specify the default digital scale device to be used for their own user account on the User Profile (SM203010) form. In the Personal Settings section of the General Info tab, they specify a configured device in the Default Scale box.
Other Changes
The use of a scale connected to DeviceHub prior to Acumatica ERP 2025 R1 required the DeviceHub and Warehouse Management features to be enabled on the Enable/Disable Features (CS1000000) form. Now it requires only the DeviceHub feature to be enabled.
Inventory and Order Management: Changes to Access Rights in Predefined User Roles
User roles provide access to the forms needed in employees' everyday work. Implementation managers can use predefined user roles in Acumatica ERP to determine access for individual users instead of creating and setting up roles from scratch.
In Acumatica ERP 2025 R1, certain predefined user roles related to inventory and order management have been updated to include access rights to the inventory planning forms.
Updated Access Rights to Inventory Planning Forms
The following table shows the updated access rights to inventory planning forms in the predefined user roles. Full access indicates the Delete restriction level; no access indicates the Revoked restriction level.
The inventory planning forms are available in the system only when the Distribution Requirements Planning or Material Requirements Planning feature is enabled on the Enable/Disable Features (CS100000) form.
Role Role Description Updated Access Rights
SO Admin A person who performs the setup of the sales order functionality and configures the sales processes. • Full access to the following forms:
• Forecast (AM202000)
• Forecast Listing (AM000005)
• Generate Forecasts (AM502000)
• Inventory Planning Preferences (AM100000)
• Inventory Planning Buckets (AM201200)
• Inventory Planning Requirements by Item
(AM401200)
• Inventory Planning Results by Item (AM404000)
• No access to any other inventory planning forms
SO Manager A person who creates sales orders, manages customer contracts (such as blanket sales orders), and views accounts receivable invoices and payments. This manager also nego- tiates customer terms, manages ap- provals, and oversees the sales op- eration staff and their activities. • Full access to the following forms:
• Forecast
• Forecast Listing
• Generate Forecasts
• Inventory Planning Buckets
• Inventory Planning Requirements by Item
• Inventory Planning Results by Item
• View-only access to the Inventory Planning Prefer- ences form
• No access to any other inventory planning forms
Role Role Description Updated Access Rights
SO Clerk A person who enters sales order da- ta, creates customer returns, prints and sends order confirmations, and manages customer inquiries. • Full access to the following forms:
• Forecast Listing
• Inventory Planning Requirements by Item
• Inventory Planning Results by Item
• No access to any other inventory planning forms
SO Viewer A person who can view the progress of the sales orders being processed but cannot change them. • Full access to the following forms:
• Forecast Listing
• Inventory Planning Requirements by Item
• Inventory Planning Results by Item
• No access to any other inventory planning forms
PO Admin A person who performs the setup of the purchase orders functional- ity and configures the purchasing processes. Full access to all inventory planning forms
PO Manager A person who creates purchase or- ders and requisitions and views ac- counts payable bills and payments. This manager also negotiates ven- dors’ credit terms, manages vendor returns, manages approvals, and oversees the purchasing staff and their activities. • View-only access to the Inventory Planning Prefer- ences form
• Full access to all other inventory planning forms
PO Buyer A person who procures inventory to replenish the warehouse stock lev- els or to fulfill orders (planning of purchases, creation of purchase or- ders, and linking of purchase orders to fulfill sales orders). This employ- ee also reviews seasonality and re- plenishment settings for optimiza- tion and procurement. • View-only access to the Inventory Planning Prefer- ences form
• Full access to all other inventory planning forms
PO Clerk A person who enters purchase order data, creates vendor returns, and views inquiries and reports. • Full access to the following forms:
• Inventory Planning Results by Item
• Forecast Listing
• Inventory Planning Display (AM400000)
• Inventory Planning Exceptions (AM403000)
• Inventory Planning Requirements by Item
• Full access to the Inventory Planning Display
(AM632000) report
• No access to any other inventory planning forms
PO Viewer A person who can view the progress of the purchase orders being processed but cannot change them. No access to any inventory planning forms
Role Role Description Updated Access Rights
IN Admin A person who performs the setup of the inventory functionality and con- figures the inventory processes. Full access to all inventory planning forms
IN Manager A person who analyzes and man- ages warehouse activities and per- formance, takes responsibility for the physical movement of goods to and from the warehouse as well as inventory optimization and efficien- cy within the warehouse, and over- sees the warehouse staff and their activities. • View-only access to the Inventory Planning Prefer- ences form
• Full access to all other inventory planning forms
IN Receiver A person who receives purchases, inbound transfers, and customer re- turns, puts away received goods in- to designated warehouse locations. No access to any inventory planning forms
IN Shipper A person who picks, packs, and ships customer sales orders, out- bound transfers, and vendor re- turns, and confirms shipments. No access to any inventory planning forms
IN Clerk A person who performs cycle counts and inventory adjustments and restocks the inventory within the same warehouse according to the warehouse manager's plan. No access to any inventory planning forms
IN Viewer A person who can view the docu- ments related to the warehouse processes and inventory settings but cannot change orders and set- tings. No access to any inventory planning forms
Additional Information
Access rights for the user roles can be modified on the following forms:
• Access Rights by Screen (SM201020)
• Access Rights by Role (SM201025)
The following reports show details about access to forms that has been granted to user roles:
• Access Rights by Role (SM651500)
• Access Rights by Screen (SM651700)
For more information about user roles in the system, see User Roles: General Information. For details about distribution requirements planning (DRP), see Inventory Planning with DRP: General Information
Inventory and Order Management: Correction of Purchase Receipts for Drop-Ship Purchase Orders
In previous versions of Acumatica ERP, a user could not correct or cancel a purchase receipt that had been created for a purchase order with the Drop-Ship type if the receipt had already been released. That is, if any errors had been made in the lines of this receipt or the company did not accept the receipt for some reason and it had to be canceled, there was no way to fix the issue properly.
Acumatica ERP 2025 R1 now provides users with the ability to correct or cancel a released purchase receipt for a drop-ship purchase order. For this purpose, the Correct Receipt and Cancel Receipt commands have been added to the More menu on the Purchase Receipts (PO302000) form, as shown in the following screenshot.
Figure: The Correct Receipt and Cancel Receipt commands
The functionality of receipt correction and cancellation for purchase orders with the Drop-Ship type is unavailable if the Manufacturing or Service Management feature is enabled on the Enable/ Disable Features (CS100000) form. (The Correct Receipt and Cancel Receipt commands are not displayed on the More menu in this case.) We highly recommend that a company verify that there are no unreleased correction receipts in the system before it enables the Manufacturing or Service Management feature.
Starting to Correct a Purchase Receipt for a Drop-Ship Purchase Order
The Purchase Receipts (PO302000) form is the starting point for correcting a released purchase receipt related to a purchase order with the Drop-Ship type. When the user clicks Correct Receipt on the More menu, the system checks whether all of the following conditions are met for the purchase receipt:
• The receipt includes at least one line of the Goods for Drop-Ship or Non-Stock for Drop-Ship type.
• The receipt does not include any lines of the Goods for IN or Non-Stock type.
• The receipt does not have related AP bills, except for AP bills that have been fully reversed.
• No landed cost documents have been applied to the purchase receipt.
• The receipt does not have related purchase returns that have not been released yet.
• No sales invoices include the lines of this purchase receipt, except for canceled invoices.
If all of these conditions are met, the system creates a new purchase receipt with the next sequential number, which is a correction purchase receipt.
For simplicity, the correction purchase receipt will be referred to as the correction receipt, and the original purchase receipt will be referred to as the original receipt.
In the original receipt, the system inserts the number of the correction receipt into the new Correction Doc. Ref. Nbr. box on the Other tab of the Purchase Receipts form, as shown below. This number is also a link that a user can click. In the correction receipt, the system inserts the number of the original receipt (which is also a link) into the new Original Doc. Ref. Nbr. box on the same tab.
Figure: The link to the correction receipt in the original receipt
Making Changes to the Correction Receipt
The system copies all the data of the original receipt to the correction receipt on the Purchase Receipts (PO302000) form, and the user can make the needed updates to the correction receipt. When the user saves the correction receipt for the first time, the system assigns the new Under Correction status to the original receipt. Also, the system updates the value in the Qty. On Receipts column for the lines of the related purchase order on the Purchase Orders (PO301000) form based on any updated quantities in the linked lines of the correction receipt.
Although the user can print the original receipt with the Under Correction status, the user cannot do the following in the system for this receipt:
• Prepare an associated AP bill on the Purchase Receipts form
• Add this receipt to an AP bill on the Bills and Adjustments (AP301000) form
• Recognize the purchase receipt on the Incoming Documents (AP301100) form
• Apply this receipt to a landed cost document on the Purchase Receipts or Landed Costs (PO303000) form
Also, the user cannot include the lines of an original receipt with the Under Correction status in the following documents:
• An AP bill for a related purchase order
• A sales invoice for a related sales order
In a correction receipt, the user cannot add new lines or delete lines that were copied from the original receipt. If a line in the original receipt had been added erroneously, the user can specify 0 in the Receipt Qty. column for the corresponding line in the correction receipt. This line will not be included in any of the following related documents during the processing of the correction receipt:
• AP bills
• Sales invoices
• Landed cost documents
In a correction receipt, the user can update the following elements in the Summary area of the Purchase Receipts
form:
• The Date box
• The Create AP Bill check box
• The Vendor Ref. box
• The Workgroup box
• The Owner box
Also, the user can update the value in the Exchange Rate box if both of following conditions are met:
• The Enable Rate Override check box is selected on the Financial tab of the Vendors (AP303000) form for the vendor in the correction receipt.
• The Allow Changing Currency Rate on Receipt check box is selected on the Purchase Orders Preferences
(PO101000) form.
In the lines of the correction receipt on the Purchase Receipts form, the user can edit the values in the following columns of the Details tab can:
• Warehouse
• Transaction Descr.
• UOM
• Receipt Qty.
• Expiration Date
• Lot/Serial Nbr.
• Unit Cost
• Ext. Cost
If the user changes a value in a purchase receipt line, the system automatically selects the check box in the new Corrected column for this line, as shown in the following screenshot. If the user changes the date or currency rate in the Summary area, the system automatically selects the check boxes in the Corrected column for all lines of the purchase receipt. The Corrected column is hidden by default.
Figure: The Corrected column
If the user made changes to a line on the Details tab by mistake, they can click Cancel for this line on the table toolbar. The system will discard all changes, and the line will be reverted to its original state at the time of document creation. Also, the system will clear the Corrected check box in the line unless it was selected due to the Date or Exchange Rate in the Summary area being changed
Completing the Correction of a Receipt
To complete the correction process, the user clicks Release on the More menu for the correction receipt. This causes the system to assign the Released status to the correction receipt and the Canceled status to the original receipt. For all lines of the correction receipt that have changes in the Receipt Qty. column on the Purchase Receipts (PO302000) form, the system does the following:
• Updates the quantities in the Qty. On Receipts column on the Purchase Orders (PO301000) form for the related purchase order
• Updates the quantities in the Qty. On Shipments and Open Qty. columns on the Sales Orders (SO301000) form for the related sales order
On the Purchase Orders and Sales Orders forms, the system performs the following actions, depending on whether the value in the Receipt Qty. column on the Details tab of the Purchase Receipts form has increased or decreased in lines of the correction receipt:
• If the quantity has decreased, the system does the following:
• Reopens the corresponding lines of the related sales and purchase orders if they have already been completed. That is, the Completed check box is cleared for these lines on the Details tab.
• If at least one line is reopened for the related purchase order that had the Completed status, assigns the
Open status to the purchase order.
• If at least one line is reopened for the related sales order that had the Completed status, assigns another status according to the order's workflow to it.
• If the quantity has increased, the system does the following:
• Selects the Completed check box in the lines of the related sales order and purchase order if the full quantity of the item has been received.
• If all lines of the related sales or purchase order become completed, assigns the Completed status to this order.
Canceling a Purchase Receipt
The Purchase Receipts (PO302000) form is the starting point for canceling a released purchase receipt related to a purchase order with the Drop-Ship type.
When the user clicks Cancel Receipt on the More menu, the system checks whether all of the following conditions are met for the purchase receipt:
• The receipt includes at least one line of the Goods for Drop-Ship or Non-Stock for Drop-Ship type.
• The receipt does not include any lines of the Goods for IN or Non-Stock types.
• The receipt does not have related AP bills, except for AP bills that have been fully reversed.
• No landed cost documents have been applied to the purchase receipt.
• The receipt does not have related purchase returns.
• No sales invoices include the lines of this purchase receipt, except for canceled invoices.
If all of these conditions are met, the system displays a confirmation dialog box, as shown in the following screenshot. If the user clicks OK, the system assigns the Canceled status to the purchase receipt.
Figure: The Cancel Receipt dialog box
As soon as the purchase receipt is canceled, the system updates the related documents as follows:
• It reopens the linked lines of the related purchase and sales order if these lines have already been completed.
• In each linked line of the related purchase order, the system updates the value in the Qty. On Receipts
column on the Details tab of the Purchase Orders form.
• In each linked line of the related sales order, the system updates the values in the Qty. On Shipments and
Open Qty. columns on the Details tab of the Sales Orders form.
Correcting or Canceling a Purchase Receipt with a Canceled Invoice
If a purchase receipt for a drop-ship purchase order has a released sales invoice, this receipt also has a related inventory issue, which is the original inventory issue. If the user cancels the sales invoice and then cancels the purchase receipt, the system also automatically generates and releases a reversal inventory issue with a reversal batch of transactions that fully revert the transactions that were generated on the release of the original inventory issue. The reversal inventory issue is released automatically, regardless of the state of the Release IN Documents Automatically check box on the Purchase Orders Preferences (PO101000) form.
The link to the reversal inventory issue appears in the new Reversal IN Ref. Nbr. box on the Other tab of the
Purchase Receipts (PO302000) form, as shown in the following screenshot.
Figure: The link to the reversal inventory issue
Viewing Purchase Receipts with the Canceled or Under Correction Status
The following Acumatica ERP reports and inquiry forms have updates related to purchase receipts with the
Canceled or Under Correction status for purchase orders with the Drop-Ship type.
On the Purchase Receipt Summary (PO620500) and Purchase Order Receipt and Billing History (PO643000) report form, the new Include Canceled and Under-Correction Receipts check box has been added to the Report Parameters tab, as shown in the following screenshot. By default, these reports do not include the purchase receipts with the Canceled or Under Correction status. If the user selects the check box, the reports include these receipts. In the Purchase Receipt Summary report, the quantity and extended cost of these purchase receipts are not included in the calculation of the total receipt quantity and total receipt extended cost.
Figure: The Include Canceled and Under-Correction Receipts check box
The following reports include the purchase receipts with the Under Correction status but exclude the purchase receipts with the Canceled status:
• Purchase Accrual Summary (PO630500) report
• Purchase Accrual Details (PO631000) report
These purchase receipts with the Under Correction or Canceled status are not listed in the following reports:
• Purchase Receipt Billing Summary (PO631500)
• Purchase Receipt Billing Details (PO632000)
• Purchase Receipt Details by Vendor (PO621000)
• Purchase Receipt Allocated and Backordered (PO622000)
On the Purchase Accrual Balance by Period (PO402000) inquiry form, the purchase receipts with the Under Correction or Canceled status are shown according to the following rules:
• The inquiry form does not show the purchase receipts with the Canceled or Under Correction status that do not have a canceled sales invoice and a related inventory issue because there are no transactions posted to the PO Accrual account at this moment.
• The inquiry form shows the purchase receipts with the Under Correction status that have a canceled sales invoice and a released inventory issue because transactions to the PO Accrual account in the original inventory issue are not reversed and still affect the PO Accrual account.
• The inquiry form does not show the purchase receipts with the Canceled status that have a canceled sales invoice and a released inventory issue because the original inventory transactions are already reversed in the reversal inventory issue if the purchase receipt is canceled.
Inventory and Order Management: Correction of Purchase Receipts for Purchase Orders with the Normal Type
In previous versions of Acumatica ERP, a user could not correct or cancel a purchase receipt that had been created for a purchase order with the Normal type if the receipt had already been released. That is, if any errors had been made in the lines of this receipt or the company did not accept the goods for some reason and the receipt had to be canceled, there was no way to fix the issue properly.
Acumatica ERP 2025 R1 now provides users with the ability to correct or cancel a released purchase receipt for a purchase order with the Normal type. For this purpose, the Correct Receipt and Cancel Receipt commands have been added to the More menu on the Purchase Receipts (PO302000) form, as shown in the following screenshot.
Figure: The Correct Receipt and Cancel Receipt commands
The functionality of receipt correction and cancellation for purchase orders with the Normal type is unavailable if the Manufacturing or Service Management feature is enabled on the Enable/ Disable Features (CS100000) form. (The Correct Receipt and Cancel Receipt commands are not
displayed on the More menu in this case.) We highly recommend that a company verify that there are no unreleased correction receipts in the system before it enables the Manufacturing or Service Management feature.
Starting to Correct a Purchase Receipt
The Purchase Receipts (PO302000) form is the starting point for correcting a released purchase receipt related to a purchase order with the Normal type.
When the user clicks Correct Receipt on the More menu, the system checks whether all of the following conditions are met for the purchase receipt:
• The receipt includes at least one line of the Goods for IN, Non-Stock for IN, Service, or Freight type.
• The receipt does not have related AP bills, except for AP bills that have been fully reversed.
• The receipt does not include any lines of the Goods for RP, Goods for Project, or Non Stock for Project type.
• No landed cost documents have been applied to the purchase receipt.
• No putaway transfers have been prepared for the purchase receipt.
• The receipt does not have related purchase returns that have not been released yet.
• The stock is not locked due to a physical inventory count.
If all of these conditions are met, the system creates a new purchase receipt with the next sequential number.
For simplicity, the newly created purchase receipt will be referred to as the correction receipt, and the purchase receipt in which the user clicked Correct Receipt as the original receipt.
In the original receipt, the system inserts the number of the correction receipt into the new Correction Doc. Ref. Nbr. box on the Other tab of the Purchase Receipts form, as shown below. This number is also a link that a user can click. In the correction receipt, the system inserts the number of the original receipt (which is also a link) into the new Original Doc. Ref. Nbr. box on the same tab.
Figure: The link to the correction receipt in the original receipt
Making Changes to the Correction Receipt
The system copies all the data of the original receipt to the correction receipt on the Purchase Receipts (PO302000) form, and the user can make the needed updates to the correction receipt. When the user saves the correction receipt for the first time, the system assigns the new Under Correction status to the original receipt. Also, the system updates the value in the Qty. On Receipts column for the lines of the related purchase order on the Purchase Orders (PO301000) form based on any updated quantities in the linked lines of the correction receipt.
Although the user can print the original receipt with the Under Correction status, the user cannot do the following in the system for this receipt:
• Prepare an associated AP bill on the Purchase Receipts form
• Add the original receipt to an AP bill on the Bills and Adjustments (AP301000) form
• Recognize the original receipt on the Incoming Documents (AP301100) form
• Apply the original receipt to a landed cost document on the Purchase Receipts or Landed Costs (PO303000) form
• Process putaway transfers for the original receipt on the Receive and Put Away (PO302020) form
Also, the user cannot include the lines of an original receipt with the Under Correction status in an AP bill for a related purchase order.
In a correction receipt, the user cannot add new lines or delete lines that were copied from the original receipt. If a line in the original receipt had been added erroneously, the user can specify 0 in the Receipt Qty. column for the corresponding line in the correction receipt. This line will not be included in any of the following related documents during the processing of the correction receipt:
• AP bills
• Landed cost documents
In a correction receipt, the user can update the following elements in the Summary area of the Purchase Receipts
form:
• The Date box
• The Create Bill check box
• The Vendor Ref. box
• The Workgroup box
• The Owner box
Also, the user can update the value in the Exchange Rate box if both of the following conditions are met:
• The Enable Rate Override check box is selected on the Financial tab of the Vendors (AP303000) form for the vendor in the correction receipt.
• The Allow Changing Currency Rate on Receipt check box is selected on the Purchase Orders Preferences
(PO101000) form.
In the lines of the correction receipt on the Purchase Receipts form, the user can edit the values in the following columns of the Details tab:
• Warehouse
• Location
• Transaction Descr.
• UOM
• Receipt Qty.
• Expiration Date
• Lot/Serial Nbr.
• Unit Cost
• Ext. Cost
• Account (for non-stock items only)
• Subaccount (for non-stock items only)
• Accrual Account
• Accrual Sub.
The lines with non-stock kits cannot be corrected.
If the user changes a value in a purchase receipt line, the system automatically selects the check box in the new Corrected column for this line, as shown in the following screenshot. Also, if the user changes the date or currency rate in the Summary area, the system automatically selects the check boxes in the Corrected column for all lines of the purchase receipt. The Corrected column is hidden by default.
Figure: The Corrected column
If the user made changes to a line on the Details tab by mistake, they can click Cancel for this line on the table toolbar. The system will discard all changes, and the line will be reverted to its original state at the time of document creation. Also, the system will clear the Corrected check box in the line unless it was selected due to the Date or Exchange Rate in the Summary area being changed
Completing the Correction of a Receipt
To complete the correction process, the user clicks Release on the More menu of the Purchase Receipts (PO302000) form for the correction receipt. On release of the correction receipt, the system validates the state of inventory. That is, it verifies whether the corrected items can be issued with the original quantity and cost.
If the validation fails, the system shows an error message, and the user can make additional changes if they want to proceed with the correction. The user can also delete the correction receipt if the correction cannot be performed.
If the validation is successful, the system generates and releases a correction inventory issue for the correction receipt. The user can find the link to this issue in the IN Ref. Nbr. box on the Purchase Receipts (PO302000) form. This issue will be released automatically, regardless of the state of the Release IN Documents Automatically check box on the Purchase Orders Preferences (PO101000) form. For details on this validation and the correction inventory issue, see Inventory Validation and Issue.
Aer the correction inventory issue is released, the system assigns the Released status to the correction receipt and the Canceled status to the original receipt.
Also, for each line of the correction receipt that has changes in the Receipt Qty. column on the Purchase Receipts form, the system updates the quantity in the Qty. On Receipts column of the Purchase Orders (PO301000) form for the related purchase order. The system changes the purchase order as follows, depending on whether the line’s corrected receipt quantity has increased or decreased:
• If the line quantity has decreased, the system reopens the corresponding line of the related purchase order if it has already been completed. That is, it clears the Completed check box for these lines on the Details tab. If at least one line is now reopened for the related purchase order and it had the Completed status, the system assigns the Open status to the purchase order.
• If the line quantity has increased, the system selects the Completed check box in the line of the related purchase order if the full quantity of the item has been received. If all lines of the related purchase order are now completed, the system assigns the Completed status to the purchase order.
Also, if the purchase order of the original receipt has a related sales order with lines that are marked for purchase on the Sales Orders (SO301000) form, in this sales order, the allocated quantities will be updated in the Line Details dialog box of that form.
Canceling a Purchase Receipt
The Purchase Receipts (PO302000) form is the starting point for canceling a released purchase receipt related to a purchase order with the Normal type.
When the user clicks Cancel Receipt on the More menu, the system checks whether all of the following conditions are met for the purchase receipt:
• The receipt includes at least one line of the Goods for IN , Non-Stock for IN, Service, or Freight type.
• The receipt does not have related AP bills, except for AP bills that have been fully reversed.
• The receipt does not include any lines of the Goods for RP , Goods for Project, or Non Stock for Project type.
• The receipt does not include any lines with non-stock kits.
• No landed cost documents have been applied to the purchase receipt.
• No putaway transfers have been prepared for the purchase receipt.
• The receipt does not have related purchase returns.
• The stock is not locked due to a physical inventory count.
If all of these conditions are met, the system displays a confirmation dialog box, as shown in the following screenshot. If the user clicks OK, the system validates the state of inventory. That is, it verifies whether it is possible to issue the items with the original quantity and cost. For details on the validation, see Inventory Validation and Issue.
If the validation fails, the system shows an error message. If the validation is successful, the system generates and releases a reversal inventory issue with the Issue type of transactions. This issue will be released automatically, regardless of the state of the Release IN Documents Automatically check box on the Purchase Orders Preferences (PO101000) form. The user can find the link to this issue in the Reversal IN Ref. Nbr. box on the Other tab of Purchase Receipts form. Then the system assigns the Canceled status to the purchase receipt.
If a purchase receipt is canceled, the system does not recalculate the cost statistics on the Price/ Cost tab of the Stock Items (IN202500) or Item Warehouse Details (IN204500) form for items that were included in this receipt.
Figure: The Cancel Receipt dialog box
As soon as the purchase receipt is canceled, the system updates the related documents as follows:
• It reopens the linked lines of the related purchase order if these lines have already been completed.
Open status to it.
• In each linked line of the related purchase order, the system updates the value in the Qty. On Receipts
column on the Details tab of the Purchase Orders form.
Inventory Validation and Issue
The correction of a purchase receipt for a purchase order with the Normal type can be one of the following types:
• A correction that does not update the state of the inventory or the information in the original inventory receipt, such as the correction of the vendor reference number or the transaction description.
• A correction that updates the state of the inventory or the information in the original inventory receipt, such as the correction of the receipt quantity or unit cost.
For the first type of correction, the system does not perform inventory validation. For the second type, the system verifies whether stock items can be issued in the quantity of the original receipt and at the original cost based on the current inventory state. This validation is required because some quantities could have already been sold, shipped, or transferred by the moment of the correction.
The system validates only stock items from the original inventory receipt. For items with the FIFO and Specific valuation methods, the validation is performed for the cost layers that have been updated on the release of the original inventory receipt. That is, for items with the FIFO valuation method, the system verifies if these items can be issued from a cost layer with the reference number of the original inventory receipt. For items with the Specific valuation method, the system verifies the cost layers of the lot or serial numbers included in the original inventory receipt.
To verify if the original quantity of stock items can be issued, the system validates their available-for-issue quantity. For items with the FIFO, Average, and Standard valuation methods, if this quantity is not sufficient in the cost layer of an item, the system also checks whether negative quantities are allowed for the item. That is, it checks the state of the Allow Negative Quantity check box on the Item Classes (IN201000) form for the item class. Depending on the state of the check box, the system does either of the following:
• If the check box is cleared for the item class, the system prohibits the issue of the items of the class. The validation fails, and the system shows an error message.
• If the check box is selected for the item class, the system allows the original quantity of the item of the class to be issued if the original quantity is greater than the available-for-issue quantity and is not greater than the quantity on hand.
For a stock item, the system does not allow the release of a correction or cancellation purchase receipt if the resulting on-hand quantity in the inventory will remain or become negative for this stock item due to the correction or cancellation. This is true regardless of the state of the Allow Negative Quantity check box for the class of the item.
Note that inventory validation applies a specific rule if the original receipt was prepared for a purchase order linked to a sales order that is marked for purchase. If this sales order has a prepared shipment for an item, the quantity of this item in the correction receipt cannot be less than the quantity in the shipment.
If the validation fails, the system shows an error message. If the validation completes successfully and the items can be issued in the quantity and at the cost of the original receipt, the system generates and releases the correction inventory issue. The inventory issue includes transactions of the Issue and Receipt type for each corrected line of the purchase receipt on the Purchase Receipts (PO302000) form, excluding the following lines:
• The lines whose correction does not update the state of the inventory.
• The lines whose quantity was changed to 0. For these lines, only the transactions with the Issue type are included.
• The lines with the Service or Freight type. These lines are not included either in the inventory receipt for the original receipt, or in the inventory issue for the correction receipt.
If the cost is edited in the correction receipt, the correction inventory issue may also include transactions with the
Adjustment type. For details, see Using a New Correction Reason Code.
On the release of the correction inventory issue, the system first processes the transaction with the Receipt type and then processes the transaction with the Issue type.
An item can be issued at a cost that differs from the cost in the original receipt if the resulting on-hand quantity is 0 in the cost layer from which the item is issued.
The system does not validate the quantity and cost of lines with non-stock items. A non-stock item is included in a correction inventory issue if at least one of the following values has been changed for it:
• Warehouse
• Location
• UOM
• Receipt Qty.
• Unit Cost
• Ext. Cost
• Account
• Sub.
• Accrual Account
• Accrual Sub.
Reviewing an Example of a Correction Inventory Issue
The following example illustrates the process of correction and the correction inventory issue for stock items with different valuation methods. Suppose that the company has the following items in stock:
• An item with the FIFO valuation method whose on-hand quantity is 100.
• A serial-tracked item with the Specific valuation method. The serial numbers from LRF00001 to LRF000015
are on hand.
• An item with the Average valuation method whose on-hand quantity is 100.
On the Purchase Receipts (PO302000), a user releases the 002325 purchase receipt for a purchase order with the
Normal type. The purchase receipt includes lines with the following items and their settings:
• An item with the FIFO valuation method:
• Receipt Qty.: 100
• Unit Cost: 100
• Two serial-tracked items with the following numbers: LRF000016 and LRF000017. Both items have a unit cost of 100.
• An item with the Average valuation method:
• Receipt Qty.: 100
• Unit Cost: 100
On the Purchase Receipts form, the user clicks Correct Receipt on the More menu. The system creates a correction receipt. In the correction receipt, the user makes the following changes:
• The unit cost of the item with the FIFO valuation method is changed from 100 to 95.
• The LRF000016 serial number is changed to LRFC00016.
The system releases a correction receipt and generates a correction inventory issue with the following transactions:
• A transaction with the Issue type for the item with the FIFO valuation method:
• Quantity: 100
• Unit Cost: 100
The item is issued from the cost layer of the 002325 purchase receipt.
• A transaction with the Issue type for the serial-tracked items:
• Lot/Serial Nbr.: LRF000016 and LRF000017
• Quantity: 2
• Unit Cost: 100
• A transaction with the Receipt type for the item with the FIFO valuation method:
• Quantity: 100
• Unit Cost: 95
• A transaction with the Receipt type for the serial-tracked items:
• Lot/Serial Nbr.: LRFC00016 and LRF000017
• Quantity: 2
• Unit Cost: 100
Using a New Correction Reason Code
On the General tab of the Posting Classes (IN206000) form, the Purchase Receipt Correction Reason Code box has been added, as shown in the following screenshot. The system posts transactions to the account of this reason code if both of the following conditions are met for the correction receipt:
• The unit cost or extended cost of an item with this posting class has been changed in a line of a correction receipt.
• A part of the received quantity has already been issued, sold, or transferred from the receiving warehouse.
Figure: The Purchase Receipt Correction Reason Code box
Suppose that on the Purchase Receipts (PO302000) form, a purchase manager has processed a purchase receipt with a line that contains 10 items with the Average valuation method and a unit cost of 10. Once the purchase receipt is released, the on-hand quantity of the item is 10, and its total cost is 100.
On the same day, a sales manager has sold five units of the item with a unit cost of 10. The remaining on-hand quantity of the item is 5, and the total cost is 50.
The purchase manager finds out that the unit cost of the received item should be 7, not 10. The manager clicks Correct Receipt on the Purchase Receipts form and specifies 7 as the unit cost in the line of the correction receipt. On the release of the correction receipt, the system generates and releases a correction inventory issue. On the release of the issue, the system posts the following transactions to the general ledger.
Account Debit Credit
Inventory account 70 (the receipt of the corrected val- ues) 0
PO accrual account 0 70
Inventory account 15 (the difference in cost for the sold units) 0
The account of the correction rea- son code 0 15 (the difference in cost for the off- set units)
Inventory account 0 100 (the issue of the original amount)
PO accrual account 100 0
Viewing Purchase Receipts with the Canceled or Under Correction Status
The following Acumatica ERP reports and inquiry forms have updates related to purchase receipts with the
Canceled or Under Correction status for purchase orders with the Normal type.
• In the reports and inquiry forms that are related to purchase orders:
• Purchase receipts with the Canceled status are not listed in the following reports and on the following inquiry forms:
• Purchase Receipt Details by Vendor (PO621000)
• Purchase Receipt Allocated and Backordered (PO622000)
• Purchase Accrual Summary (PO630500)
• Purchase Accrual Details (PO631000)
• Purchase Receipt Billing Summary (PO631500)
• Purchase Receipt Billing Details (PO632000)
• Purchase Accrual Balance by Period (PO402000)
• Purchase receipts with the Under Correction status are not listed in the following reports:
• Purchase Receipt Details by Vendor
• Purchase Receipt Allocated and Backordered
• Purchase Receipt Billing Summary
• Purchase Receipt Billing Details
• Purchase receipts with the Canceled or Under Correction status can be listed in the Purchase Receipt Summary (PO620500) and Purchase Order Receipt and Billing History (PO643000) reports. These receipts are included if the new Include Canceled and Under-Correction Receipts check box is selected on the Report Parameters tab of the report form. In the Purchase Receipt Summary report, the Total value for the Receipt Qty. column does not include quantities from these receipts, regardless of the state of the check box.
• Purchase receipts with the Under Correction status are listed in the following reports and on the following inquiry form:
• Purchase Accrual Summary
• Purchase Accrual Details
• Purchase Accrual Balance by Period
• In the reports and inquiry forms that are related to inventory:
• The transactions with the Issue, Receipt, and Adjustment types from the correction and reversal inventory issues are listed on the following inquiry forms:
• Inventory Transaction History (IN405000)
• Inventory Transaction Details (IN404500)
• Inventory Transactions by Account (IN403000)
• Inventory Lot/Serial History (IN407000)
• On the Inventory Turnover (IN407010) inquiry form, if the Include Issues and Adjustments check box is selected on the Inventory Preferences (IN101000) form, the amounts and quantities of correction and reversal issues type are not included as sold amounts and quantities in the turnover formula.
In the summarized format of the Historical Inventory Balance (IN616000) and Historical Inventory Valuation (IN617000) reports, the quantities from canceled purchase receipts are not included in the Receipt column. Also, the quantities from the correction and reversal inventory issues are not included in the Issue column. The detailed format of these reports lists all transactions, including the transactions for correction and reversal inventory issues.
The Inventory Transaction History and Inventory Transaction Details inquiry forms list all inventory transactions, including the corrected transactions. If the Summary by Day check box is selected on either form, the following columns contain summarized values for all transactions, including the transactions for correction and reversal inventory issues: Qty. In, Qty. Out, Cost In, and Cost Out.
If inventory reports look inaccurate aer a receipt correction or cancellation was performed in the system, the user should recalculate the inventory on the Recalculate Inventory (IN505000) form.
Inventory and Order Management: Lot and Serial Attributes for Stock Items
In previous versions, users could not assign attribute values to a unit of a stock item with a particular serial number or to units of a stock item with a particular lot number. As a result, inventory management and sales processes required manual efforts to track additional information about stock items, which was inefficient and could lead to errors.
Acumatica ERP 2025 R1 provides users with the ability to define attributes for a lot or serial class and manage the set of the attributes for a unit of a stock item with a lot or serial number. Users can assign attributes to units in stock, correct lot or serial attribute values that were incorrectly entered, and review and update information on lot- or serial-tracked items. Also, they can search for the necessary items by these attributes to add them to a sales
document. This functionality becomes available if the company has the Lot/Serial Attributes feature enabled on the
Enable/Disable Features (CS100000) form.
In 2025 R1, the functionality is not supported in manufacturing, field services, and retail commerce.
The following sections describe the changes related to this functionality in Acumatica ERP 2025 R1.
Changes to the Enable/Disable Features Form
The Lot/Serial Attributes check box has been added under Experimental Features on the Enable/Disable Features (CS100000) form. This check box becomes available for selection if the Lot and Serial Tracking check box is selected under Inventory and Order Management.
Changes to the Lot/Serial Classes Form
The Lot/Serial Classes (IN207000) form now has two tabs. The table that lists the segments of the lot or serial numbers to be used for items of the class is now shown on the Numbering Settings tab. The Attributes tab lists the lot or serial attributes for items of the class (see Item 1 in the following screenshot). A user first defines these attributes on the Attributes (CS205000) form, and then they can add the attributes to the table on the Lot/Serial Classes form. By default, the system will use these attributes for each newly created stock item. The following screenshot shows the updated layout of the form.
A user can add attributes for an item of a lot or serial class only if the tracking method of the class is either Track Serial Numbers or Track Lot Numbers and the assignment method is When Received. If the item has a different tracking method or assignment method (or both), the Add and Delete buttons are unavailable on the tab.
Also, the Specify Lot/Serial Price and Description check box has been added to the Attributes tab (Item 2). With this check box selected, a user can define the sales price, manufacturer’s suggested retail price (MSRP), and description for a unit of a stock item with a serial number or units with a lot number. For details, see the Specification of a Sales Price and Description for a Unit of a Stock Item section below.
Figure: The Lot/Serial Classes form
Changes to the Stock Items Form
On the Attributes tab of the Stock Items (IN202500) form, the Lot/Serial Attributes table has been added (see the following screenshot). The table shows attributes for a particular lot- or serial-tracked item. By default, the table has the lot or serial attributes specified for the lot or serial class assigned to the item.
Figure: The Lot/Serial Attributes table on the Stock Items form
Changes to the Purchase Receipts and Receipts Forms
On the Purchase Receipts (PO302000) and Receipts (IN301000) forms, the Lot/Serial Attributes table has been added to the Line Details dialog box (see the following screenshot). The table contains the attributes and attribute values that are specified for the unit of the stock item selected in the line.
A user must enter the lot or serial number first; then they can specify attributes for the lot or serial numbers in the Lot/Serial Attributes table.
Figure: The Lot/Serial Attributes table in the Line Details dialog box
For each lot or serial number, a user can specify different attribute values. The user can copy all the attribute values in the first line to all the lines in the table by clicking Use Attributes from First Line on the table toolbar (Item 1 in the following screenshot).
Also, for each lot or serial number, the user can specify the manufacturer's lot or serial number in the Manufacturer Lot/Serial Nbr. column (Item 2).
Viewing and Modification of Lot or Serial Details for a Stock Item
The Lot/Serial Details (IN209600) form has been added (see the following screenshot). On this form, the user can do the following:
• In the Summary area, view the information related to a particular unit of a stock item with a lot or serial number (such as the expiration date, the manufacturer's lot or serial number, or the short description of the item)
• On the Attributes tab, view and modify the attribute values and upload an image of the unit
• On the Description tab, add or update an extended description of the unit
• On the History tab, review the history of related inventory documents
Figure: The Lot/Serial Details form
The user can open the Lot/Serial Details (IN209600) form by using the Lot/Serial Details (IN2096PL) list of records (see the following screenshot). Its link is available in the Inventory workspace under the Profiles category. The list of records shows all the lot- or serial-tracked units that are in stock or have been issued from the warehouse and have the following settings specified on the Lot/Serial Classes (IN207000) form:
• Tracking Method: Track Lot Numbers or Track Serial Numbers
• Assignment Method: When Received
By clicking a link in the Lot/Serial Nbr. column, a user can open the record with that number on the Lot/Serial Details form.
Figure: The Lot/Serial Details list of records
Deletion, Addition, and Updating of Lot and Serial Attributes
If a user adds or deletes attributes for a particular lot or serial class on the Lot/Serial Classes (IN207000) form, the system adds or deletes them for each existing item of this class on the Stock Items (IN202500) form. Also, if the user changes the state of the Active or Required check box for an attribute in the lot or serial class, the system changes the state of the respective check box for all the items of this class.
A user cannot delete a lot or serial attribute from the Stock Items or Lot/Serial Classes form if at least one unit with a lot or serial number has been added to an unprocessed sales order.
Selection of a Lot- or Serial-Tracked Item in Documents
On the Sales Orders (SO301000), Issues (IN302000), Adjustments (IN303000), and Transfers (IN304000) forms, the Add Lot/Serial Nbr. button has been added to the table toolbar of the Details tab (see below). The button is available for a sales order with the On Hold status or Open status (if approvals are not configured for the order type).
Figure: The Add Lot/Serial Nbr. button on the Sales Orders form
A user clicks the button to open the Add Lot/Serial Nbr. dialog box (see the following screenshot). In the dialog box, the user can view item availability and select units with particular lot or serial numbers.
Figure: The Add Lot/Serial Nbr. dialog box
The table in the dialog box displays columns with attribute values specific for a unit with a particular lot or serial number (see the following screenshot). In the Search box, the user can search for units with lot or serial numbers by attribute values. The user can filter data in the table by the values in attribute columns.
When the user adds a unit with a lot or serial number to the sales order, the system allocates the unit with this lot or serial number for this order. The system will insert each unit with a serial number in a separate document line. For units with lot numbers, the system will add a line for all units with a particular lot number.
Figure: The unit-specific serial attributes
Specification of a Sales Price and Description for a Unit of a Stock Item
A user can specify the description, sales price, and MSRP for a particular unit of a stock item in the Summary area of the Lot/Serial Details (IN209600) form (see Items 1, 2, and 3 in the following screenshot). This functionality is available if the Specify Lot/Serial Price and Description check box is selected for the lot or serial class of the item on the Lot/Serial Classes (IN207000) form.
Figure: Editable description, sales price, and MSRP for a unit
When the unit with a particular lot or serial number is created, the system inserts the sales price and MSRP from the Default Price and MSRP boxes of the Stock Items (IN202500) form on the Lot/Serial Details form. In the Description box, the system inserts the description from one of the following forms:
• Purchase Receipts (PO302000)
• Receipts (IN301000) if the unit was added directly on this form to be received to stock
If the Specify Lot/Serial Price and Description check box is cleared, the Description, Sales Price, and MSRP
boxes are cleared and unavailable for editing on the Lot/Serial Details form.
When the user adds the unit to a line on the Details tab of the Sales Orders (SO301000) form, the system inserts the unit’s sales price in the Unit Price column and its description in the Line Description column.
This capability is available as long as the order type of the sales order does not have Blanket Order or
Quote specified as its automation behavior on the Template tab of the Order Types (SO201000) form.
Limitations
If the Specify Lot/Serial Price and Description check box is selected for the lot or serial class on the Lot/Serial Classes (IN207000) form, the following limitations apply to each item of the class:
• The item cannot be added to a sales price list on the Sales Prices (AR202000) form or a sales price worksheet on the Sales Price Worksheets (AR202010) form.
• The item must have a lot or serial number specified in a sales order line. The Mark for PO check box cannot be selected for this line.
• Each unit of a stock item with a lot or serial number must be added to a separate sales order line on the
Sales Orders (SO301000) form because each unit may have a unique description and price.
Upgrade Notes
Before an upgrade to Acumatica ERP 2025 R1, if the Acumatica-LotSerialNbrAttribute customization project was used in the system before the upgrade, the administrator should contact their Acumatica support provider and request a migration script. For existing stock item records, a user can import lot and serial attributes by creating and using an import scenario on the Import Scenarios (SM206025) form.
• In Version 2025 R1, lot and serial attributes are not supported in manufacturing, field services, and retail commerce. If a company has published this customization project to deliver the functionality to these areas before the upgrade, it must continue using the customization project.
• Stock items that have been used in the customization project will not be added to Acumatica ERP if their lot or serial class had the When Used assignment method on the Lot/Serial Classes (IN207000) form before the upgrade.
Additional Information
For more information about lot and serial attributes for stock items, see Items with Lot and Serial Numbers: Lot and Serial Attributes.
Inventory and Order Management: Receive Transfer Mode of the Receive and Put Away Form
When items are transferred between warehouses, warehouse personnel may work with the following documents:
• A transfer order, which is an order with the Transfer Order automation behavior created on the Sales Orders
(SO301000) form
• A transfer shipment—that is, a shipment of the Transfer type created on the Shipments (SO302000) form
• A transfer receipt—a purchase receipt of the Transfer Receipt type created on the Purchase Receipts
(PO302000) form
In previous versions of Acumatica ERP, a warehouse worker could not create a transfer receipt when they were receiving and putting away items by using the mobile app. Instead, the warehouse manager had to create the transfer receipt in the system and provide it to the worker. Also, for the worker to put away the items, the manager had to create a separate inventory transfer. These restrictions in operations resulted in extra work, increased the risk of document errors, and caused processing delays.
Starting in Acumatica ERP 2025 R1, a warehouse worker can transfer items from the source warehouse to the destination warehouse by using the mobile app. They can create a transfer receipt based on a delivery document, such as a transfer shipment or transfer order. Multiple warehouse workers can now receive one transfer shipment if it includes different items. Aer a receiver releases the transfer receipt, they can put away the received items.
Warehouse workers can receive and put away inventory items by using a barcode scanner or mobile device for scanning if the Receiving feature is enabled on the Enable/Disable Features (CS100000) form.
The following sections describe the changes related to this functionality in Acumatica ERP 2025 R1.
Changes to the Purchase Orders Preferences Form
On the Warehouse Management tab of the Purchase Orders Preferences (PO101000) form, the Display the Receive Transfer Tab check box (shown below) has been added. If this check box is selected, users can process transfer receipts by using the Receive and Put Away screen of the mobile app or the Receive and Put Away (PO302020) form.
Figure: The new check box
Changes to the User Profile Form
On the User Profile (SM203010) form, the Receive Transfer option (shown below) has been added to the Receive and Put Away box on the General Info tab. If a user selects this option, the default mode on the Receive and Put Away (PO302020) form for this user will be Receive Transfer. The system will apply this change the next time the user signs in.
Figure: The new option in the Receive and Put Away box
A user can open the User Profile form by doing the following:
1. Clicking the User menu button in the top pane of the Acumatica ERP screen
2. Clicking My Profile on the User menu
Changes to the Receive and Put Away Form
On the Receive and Put Away (PO302020) form, the Receive Transfer tab has been added (see the following screenshot). This tab lists the lines of a purchase receipt with the Transfer Receipt type.
Figure: The Receive Transfer tab
The tab is shown if the Display the Receive Transfer Tab check box is selected on the Purchase Orders Preferences
(PO101000) form and a user has switched to Receive Transfer mode by scanning any of the following:
• The @potransfer command
• The transfer receipt number (if the transfer receipt has already been created)
On the Receive and Put Away form, in Receive Transfer mode, a user can create a transfer receipt by scanning the number of a transfer shipment or transfer order. By default, the system creates the new transfer receipt with the On Hold status. The Receive Transfer tab has no lines from the newly created transfer receipt. Each line is added automatically by the system aer a user has scanned the barcode of the item to be received.
Also, the system now automatically switches between Receive, Return, and Receive Transfer modes on the Receive and Put Away form based on the type of the scanned purchase receipt. For example, if Receive mode is in use and a user is scanning the number of a transfer receipt, the system automatically recognizes the type of the document and switches the mode to Receive Transfer so the user can process the transfer receipt.
Changes to the Purchase Receipts Form
On the Purchase Receipts (PO302000) form, the Put Away tab now appears for a receipt of the Transfer Receipt type. It lists single-step inventory transfers created in Put Away mode on the Receive and Put Away (PO302020) form for this purchase receipt (see the following screenshot).
Figure: The Put Away tab
Changes to the Shipments Form
On the Shipments (SO302000) form, the Receipts tab has been added (see the following screenshot). The tab appears only for shipments of the Transfer type and lists all purchase receipts of the Transfer Receipt type created for the shipment. On this tab, a user can click links to the related transfer receipts and check which items in these receipts have been received at the destination warehouse.
Figure: The Receipts tab
A user can click the link in the Receipt Nbr. column to open a transfer receipt on the Purchase Receipts (PO302000) form only if the user has access to the destination warehouse.
Changes to the Shipment Confirmation Report
In the Shipment Confirmation (SO642000) report, the barcode of the corresponding shipment number has been added (see the following screenshot). By scanning the shipment barcode, a warehouse worker can start processing the corresponding transfer receipt on the Receive and Put Away (PO302020) form.
Figure: The barcode of the shipment
Processing of a Transfer Receipt on the Receive and Put Away Form
Starting in Acumatica ERP 2025 R1, warehouse workers can receive multiple transfer receipts for one transfer shipment simultaneously and put away items from these transfer receipts.
Suppose that goods (computers and monitors) should be transferred from a source warehouse to a destination warehouse. A user creates a transfer order on the Sales Orders (SO301000) form and processes the related transfer shipment on the Shipments (SO302000) form. The system generates and releases the inventory transfer that issues the items from the source warehouse to the destination warehouse. The transfer shipment has the Completed status on the Shipments form. Now the goods can be received at the destination warehouse.
Further suppose that the shipment confirmation report has 10 computers and 10 monitors to be transferred to the destination warehouse. One warehouse worker is responsible for receiving the computers at the warehouse location for computers, and another warehouse worker is responsible for receiving the monitors at the warehouse location for monitors. The warehouse personnel can transfer items from the source warehouse to the destination warehouse by performing the following steps:
1. Warehouse worker 1 scans the shipment barcode in the Shipment Confirmation (SO642000) report. The system switches to Receive Transfer mode, creates the transfer receipt, and displays the Receive Transfer tab with no lines on the Receive and Put Away (PO302020) form.
2. Warehouse worker 1 performs the following operations to process the transfer receipt:
a. Scans the barcode of the location for computers at the destination warehouse
b. Scans the barcode of each computer that has been received
c. Releases the transfer receipt
When the transfer receipt has been released, warehouse worker 1 can put away the items.
3. Warehouse worker 2 scans the barcode in the Shipment Confirmation report. The system switches to Receive Transfer mode, creates the transfer receipt, and displays the Receive Transfer tab with no lines on the Receive and Put Away form.
4. Warehouse worker 2 performs the following operations to process the transfer receipt:
a. Scans the barcode of the location for monitors at the destination warehouse
b. Scans the barcode of each monitor that has been received
c. Releases the transfer receipt
When the transfer receipt has been released, warehouse worker 2 can put away the items.
Duplicate Identifiers in Document Processing
In Receive Transfer mode on the Receive and Put Away (PO302020) form, a user can scan the identifiers (that is, reference numbers) of such documents as transfer shipments, transfer receipts, or transfer orders. Although documents of a particular type (such as transfer receipts) have unique identifiers, documents of different types
(such as a transfer receipt and a transfer order) can share the same identifier. When an identifier is scanned, the system searches in the following order until it finds a document with the identifier:
1. Transfer receipts on the Purchase Receipts (PO302000) form
2. Transfer shipments on the Shipments (SO302000) form
3. Transfer orders on the Sales Orders (SO301000) form
Suppose that the system has two documents with identical identifiers: a transfer receipt and a transfer shipment. If a user enters an identifier matching a released transfer receipt on the Receive and Put Away form, the system displays an error message indicating that the transfer receipt has already been released. This prevents further processing of the shipment with the same identifier.
To ensure that identifiers are unique and avoid issues with duplicates, we strongly recommend creating a separate numbering sequence with a unique prefix on the Numbering Sequences (CS201010) form for each type of document. This will cause identifiers to be unique across documents of different types.
Mobile App
In the Acumatica mobile app, on the Receive and Put Away screen, the Receive Transfer button has been added under the Change Mode category (see the following screenshot). The button is available if the Display the Receive Transfer Tab check box is selected on the Warehouse Management tab of the Purchase Orders Preferences (PO101000) form.
Figure: The Receive Transfer button
Figure: The Release Receipt command
On the Receive and Put Away screen, if a user taps Review and then taps the item, the system displays the information about the received item, including the transfer order number and the transfer shipment number (see the following screenshot).
Figure: The numbers of the transfer order and transfer shipment
Limitations
In Acumatica ERP 2025 R1, multiple users cannot simultaneously process unreleased transfer receipts with partial item quantities on the Receive and Put Away (PO302020) form. However, if a user has created and released a transfer receipt with a partial item quantity, the remaining quantity can be received in another transfer receipt.
Upgrade Notes
Aer an upgrade to Acumatica ERP 2025 R1, on the Purchase Orders Preferences (PO101000) form, the state of the
Display the Receive Transfer Tab check box will be either of the following:
• Selected if the Display the Receive Tab check box was selected before the upgrade
• Cleared if the Display the Receive Tab check box was cleared before the upgrade
Additional Information
For more information about Receive Transfer mode, see Receiving and Putting Away Operations: Transfer Receipt Processing.
Inventory and Order Management: Other Improvements
Acumatica ERP 2025 R1 introduces improvements to inventory and order management processes and the UI, as described below.
Removal of the Advanced Availability Validation Check Box
In Acumatica ERP 2025 R1, the Advanced Availability Validation check box has been removed from the Sales Orders Preferences (SO101000) form because the system does not use it to calculate on-hand item quantities. If a user wants to allow the on-hand quantity of an item to become negative in documents, they need to select the
Allow Negative Quantity check box on the Item Classes (IN201000) form for the item’s class. Otherwise, they will not be able to do either of the following if the action would cause the actual quantity of an item of the class to become negative:
• Confirm a shipment that contains the item
• Save a sales order that contains the item if the order has the Invoice automation behavior
Inventory Planning: Forecast Consumption Visibility
In Acumatica ERP, the forecasted demand is included in inventory planning workflows. Forecasts can be set up based on historical sales data, seasonality, or other business-specific patterns and can be adjusted for various factors, such as promotions or anticipated demand spikes. These forecasts provide insight that managers can use to determine replenishment strategies so that inventory levels are optimized to avoid stockouts or overstock. As such, the forecasts help companies to maintain balance in inventory-carrying costs and to meet customer demand efficiently.
When a forecast is marked as dependent, Acumatica ERP automatically reduces the forecasted quantity by the quantity of items in sales orders and excludes the consumed forecasted quantity from inventory planning. By using dependent forecasts, companies can reduce the risk of over-ordering and producing excess inventory that may not be needed.
Previous versions of Acumatica ERP did not provide the ability to easily compare the forecasted demand with the actual demand for dependent forecasts, so planning managers had to create custom reports or generic inquiries.
In Acumatica ERP 2025 R1, a side panel has been introduced on the Forecast (AM202000) and Forecast Listing (AM000005) forms to improve the visibility of the actual demand during particular forecast intervals. The tabs of the new side panel of this form are described in the following section.
The forecasting functionality is available only when the Distribution Requirements Planning or
Material Requirements Planning feature is enabled on the Enable/Disable Features (CS100000) form.
Side Panel on the Forecast and Forecast Listing Forms
A side panel has been added to the Forecast (AM202000) and Forecast Listing (AM000005) forms with the Forecast vs. Sales and Forecast vs. Sales Details tabs. The following screenshot shows these tabs on the side panel of the Forecast form. On these tabs, the system displays data from the Forecast vs. Sales (AM404100) and Forecast vs.
Sales Details (AM404200) inquiry forms, respectively. These inquiry forms have been added to the site map and are available in the Inventory Planning workspace.
Figure: The tabs of the new side panel on the Forecast form
For each forecast selected on the Forecast or Forecast Listing form, a planning manager can open and expand the Forecast vs. Sales tab to see the forecasted quantity, the ordered quantity, and the quantity variance for each forecast interval. (See the following screenshot.)
Figure: The Forecast vs. Sales tab on the side panel
To explore which sales orders consumed the forecasted demand, the planning manager can use the Forecast vs. Sales Details tab, which is shown in the following screenshot. The table on this tab lists all sales orders that have been created for the item during the forecast interval selected in the Selection area, along with the ordered quantities and additional details from the corresponding sales order lines.
Figure: The Forecast vs. Sales Details tab on the side panel
For ease of comparison, the ordered quantities displayed on the Forecast vs. Sales and Forecast vs. Sales Details tabs are converted to the forecast's unit of measure.
Inventory Planning: Improved Traceability of Demand and Supply
The Inventory Planning Results by Item (AM404000) form is a key tool for schedulers and planners to review and interpret inventory planning suggestions before taking action.
In previous versions of Acumatica ERP, labeling inconsistencies across the Inventory Planning forms made it difficult to identify document IDs responsible for quantity changes. Additionally, the lack of clear references to demand or supply documents and the absence of details on consolidated demand records further complicated the interpretation of inventory planning data.
In Acumatica ERP 2025 R1, the following updates have been made to improve demand and supply traceability and enhance consistency between related inventory planning forms:
• The following new columns have been added to the table on the Inventory Planning Results by Item form:
• Consolidation ID: Displays the identifier of the consolidation record either for a demand record included in a consolidation or for a generated supply record created to meet the demand of a consolidated record, allowing users to trace which demand records were consolidated into a single supply record. This column is available only if the Use Days of Supply to Consolidate Orders check box is selected on the Inventory Planning Preferences (AM100000) form.
• The Generated Supply Document column has been added to the Inventory Planning Display (AM400000) form. This column displays the system-assigned ID of the supply document generated by the inventory planning regeneration process, enabling users to easily relate the supply row on the Inventory Planning Display form to the corresponding row on the Inventory Planning Results by Item (AM404000) form.
• A new numbering sequence that uses the PLPO prefix has been introduced for inventory planning-generated purchase orders, ensuring consistency with other generated plans, such as planned production orders, consolidation suggestions, planned transfer orders, and planned kit assemblies, all of which are created and stored with unique IDs.
Localization (Canada): RBC ACH094 Plug-In for International Payments
In previous versions of Acumatica ERP, users could export batches of AP payments via the Automated Clearing House (ACH) plug-in, which works for domestic payments in the United States. Acumatica ERP also supports the CPA005 plug-in for domestic payments in Canada. These plug-ins do not support the International ACH Transactions format and cannot be used for cross-border payments between Canada and the US.
In Acumatica ERP 2025 R1, the Royal Bank of Canada (RBC) ACH094 plug-in has been added to export AP payments in the National Automated Clearing House Association (NACHA) ACH094 format for cross-border payments from a USD account residing in Canada to a USD account residing in the United States. The plug-in appears in the system if the Canadian Localization feature is enabled on the Enable/Disable Features (CS100000) form.
The following sections describe the UI changes and changes in document processing to support this functionality.
Changes to the Payment Methods Form
On the Payment Methods (CA204000) form, the following changes have been made:
• In the Direct Deposit File Format box, the RBC ACH094 option has been added (Item 1 in the screenshot below).
• In the Export Method box, the RBC ACH094 Plug-In option has been added (Item 2). The system automatically inserts this option when RBC ACH094 is selected as Direct Deposit File Format. On the Remittance Settings tab, the settings for the specified export method are filled in automatically.
Figure: UI changes on the Payment Methods form
On the Plug-In Settings tab, the system automatically inserts the default settings for this plug-in (shown below), which the user can override.
Figure: The settings of the RBC ACH094 plug-in
Setup of the RBC ACH094 Plug-In
To set up the RBC ACH094 plug-in in the system, an administrative user performs the following actions:
1. On the Payment Methods (CA204000) form, creates a payment method, selecting Direct Deposit in the Means of Payment box.
2. In the Direct Deposit File Format box for the payment method, selects RBC ACH094.
The system automatically inserts RBC ACH094 Plug-In in the Export Method box on the Settings for Use in AP tab.
3. On the Remittance Settings tab, specifies the remittance settings for the cash account. These settings are filled in for the cash account on the Remittance Settings tab of the Cash Accounts (CA202000) form.
4. On the Settings for Use in AP tab, specifies or adjusts the payment details with the vendor's settings. These settings are filled in for the vendor on the Payment tab of the Vendors (AP303000) form.
5. On the Plug-In Settings tab of the Payment Methods form, reviews and adjusts the plug-in settings.
Localization (Canada): Support of T4A Reporting
Previous versions of Acumatica ERP did not support the generation of the T4A report (also known as a Statement of Pension, Retirement, Annuity, and Other Income) and its electronic submission to the Canada Revenue Agency (CRA).
Acumatica ERP 2025 R1 introduces support for the generation of the T4A XML file and its electronic submission to the CRA. This functionality is available in the system if the Canadian Localization feature is enabled on the Enable/ Disable Features (CS100000) form.
The following sections describe the UI changes made to multiple forms and changes in document processing to support this functionality.
Changes to the Vendors Form
On the Vendors (AP303000) form, the following changes have been made:
Enable T5018 Reporting and Disable T5018 Reporting.
• On the General tab, the T5018 Vendor check box has been removed from the Vendor Properties section.
• The CRA Reporting Type box (Item 1 in the screenshot below) has been added to the Vendor Properties
section. This box contains one of the following options:
• None (default): This value is specified when the Canadian Localization feature is enabled.
• T5018: If a user selects this option, users will be able to mark lines of bills or prepayments as T5018. The lines of these bill payments and prepayment will be included in the vendor's T5018 amount.
• T4A: If a user selects this option, all the released payments are included in the vendor's T4A amount.
• If T4A is selected in the CRA Reporting Type box, the following boxes appear on the form:
• T4A Box (Item 2): The type of payment, which can be one of the following: Box 20 - Self Employed Commissions, Box 28 - Other Income, or Box 48 - Fees for Services (default).
• CRA Vendor Type (Item 3): The type of subcontractor (the former T5018 Box).
• CRA Payroll Account Number (Item 4): A 15-character payroll account number for dealing with CRA. This box appears on the form if the CRA Vendor Type box is set to Corporation or Partnership.
• The SIN box now appears on the form if the CRA Vendor Type box contains Individual.
Figure: Boxes related to T4A reporting
Changes to the Companies Form
On the Companies (CS101500) form, the following changes have been made:
• The T5018 Settings section has been removed and the CRA section (Item 1 in the screenshot below) has been added instead.
• The CRA Payroll Account Number box has been renamed to Payroll Account Number (Item 2).
• The Program Number box has been renamed to Information Returns Account Number (Item 3).
• The Year Type box has been renamed to T5018 Year Type (Item 4).
Figure: UI changes on the Companies form
The Canadian Tax Reporting tab appears on the form is one of the following conditions is met:
• On the Enable/Disable Features (CS100000) form, the Canadian Payroll feature is enabled and the Canadian Localization feature is disabled; also, the File Taxes by Branch check box is cleared on the Companies form.
• The Canadian Localization feature is enabled and the Canadian Payroll feature is disabled on the Enable/ Disable Features form. In this case, the system doesn't check the state of the File Taxes by Branch check box on the Companies form.
• The Canadian Payroll and Canadian Localization features are both enabled on the Enable/Disable Features form. In this case, the system doesn't check the state of the File Taxes by Branch check box on the Companies form.
Changes to the Branches Form
On the Branches (CS102000) form, the following changes have been made:
• The T5018 Settings section has been removed.
• The CRA Payroll Account Number box has been renamed to Payroll Account Number, as shown in the following screenshot.
Figure: UI change on the Branches form
Changes to the Accounts Payable Preferences Form
On the Canadian Tax Reporting tab of the Accounts Payable Preferences (AP101000) form, the following changes have been made:
• The T4A Settings section (Item 1 in the screenshot below) has been added.
• The Threshold Amount box (Item 2) has been added to this section. If the total of all released payments to a particular vendor is the same as or more than the threshold amount, these payments will be included in the vendor's T4A report.
Figure: UI changes on the Accounts Payable Preferences form
Changes to the Create T5018 E-File Form
On the Create CRA E-File (AP507600) form, the following changes have been made:
• The Create T5018 E-File form has been renamed to Create CRA E-File.
• The Tax Form box (Item 1 in the screenshot below) has been added to the Selection area of the form. In this box, the user can select T5018 or T4A.
• The Transmitter box has been renamed to Payer (Item 2) to be more in line with CRA documentation and business processes. If T4A is selected in the Tax Form box, a branch can be selected in this box if this branch belongs to a company with the Canada localization and the File Taxes by Branch check box selected.
• The T5018 Tax Year box has been renamed to Year (Item 3) so that it can be used for both T5018 and T4A reports. For a T4A report, the calendar year is always used.
Figure: UI changes on the Create CRA E-File form
Users can generate the original, amended, or canceled T4A e-file in XML format. The following document types are included in the T4A report:
• Payment: A document created on the Checks and Payments (AP302000) form. The document amount is added to the T4A amount.
• Prepayment: A document created on the Checks and Payments form. The document amount is added to the T4A amount.
Prepayments without applications are included in the T4A report without any adjustments for the possible taxes. Aer prepayment applications are released, there will be enough data for the system to adjust the amounts. This means that the user will have to generate a new revision of the T4A report to get correct report amounts.
• Refund: A document created on the Checks and Payments form. The document amount is subtracted from the T4A amount.
• Cash Purchase: A document created on the Cash Purchases (AP304000) form. The document amount is added to the T4A amount.
• Cash Return: A document created on the Cash Purchases form. The document amount is subtracted from the T4A amount.
The New T4A Report Details Form
The T4A Report Details (AP407700) inquiry form has been added to the system. This form shows a list of documents whose amounts are included in the selected revision of the T4A report, as shown in the following screenshot.
Figure: The T4A Report Details form
Other UI Changes
The following UI changes have also been made:
• On the Checks and Payments (AP302000) form for the Prepayment document type, the T5018 Report
section on the Financial tab has been renamed to T5018 Reporting.
• The new CRA Reporting section has been added to the Payables workspace. This section includes all the forms and reports related to CRA reporting.
Additional Information
For details on configuration of the T4A reporting, see Configuring CRA Reporting and Filing the T4A Form Electronically.
For details on how to generate the original T4A file, see To Generate the Original CRA Reporting Forms.
For details on how to generate an amendment to a T4A file, see To Generate an Amendment to CRA Reporting Forms.
Manufacturing: Due Date Handling in Production Orders
In previous versions of Acumatica ERP, production orders whose start and end dates were updated during the finite scheduling in advanced planning and scheduling (APS) did not retain the due dates of their linked or pegged demands. This could affect the production manager's confidence in the production schedule because tracking of potentially late production orders oen involved manual effort, which could lead to errors.
In Acumatica ERP 2025 R1, a new box, Due Date, has been added in the Scheduling Details section on the General
tab of the Production Order Maintenance (AM201500) form, as shown in the following screenshot. This box holds the date by which the production order is expected to be completed to ensure on-time delivery for the pegged demand.
Figure: The new Due Date box
The Due Date box is useful in various production scenarios, including the following:
• Rescheduling production orders to prioritize rush sales orders
When production orders are canceled or rescheduled, the scheduler can now see the original Ship On date on the production order to adjust priorities accordingly.
• Fulfilling sales orders with updated ship-on dates
If the customer's required delivery date changes, production and scheduling teams can see the updated
Ship On date and adjust production schedules as needed.
• Managing parent production order demand
The scheduler can now track the parent production order’s needed date for components and identify delays in child production orders when adjusting the schedule.
• Handling MRP-generated make-to-stock production orders
The production manager can preserve the original demand date by ensuring the Promised Date from the
Inventory Planning Display (AM400000) form is reflected on the production order, helping prevent stockouts.
• Manually creating production orders
The production manager can define and retain the completion date of manually created orders, ensuring visibility for schedulers when making scheduling adjustments.
• Identifying delayed production orders on the Production Schedule Board
The scheduler can quickly spot late production orders that must fulfill linked demand, using the Ship On date as a reference. Delayed orders are also visually highlighted in the grid view on the Production Schedule Board (AM215555) form.
• Tracking lead time gaps between production completion and supply date
The system now calculates lead time gaps between production completion and supply dates, providing visibility into the Ship On date of the related sales order line.
The Due Date box is editable if there's no linked demand and the order is on hold.
If the production order is linked to a sales order line or a parent production order, the due date is determined as follows:
• If a sales order line is specified in the SO References section on the References tab of the Production Order Maintenance form, the Ship On date of the linked sales order line is automatically used as the due date of the production order. Any changes to the ship-on date update the due date accordingly. If the sales order is unlinked, the due date remains unchanged, but the Due Date box becomes editable.
• If a production order with the Parent relationship type is specified on the Related Production tab of the Production Order Maintenance form, the system uses the earliest allocation date of the inventory item if it is used as a material in an operation in the related production order. If the allocation date changes, the due date updates accordingly. If the related production order is deleted, the due date remains unchanged, but the Due Date box becomes editable.
If the production order has no linked demand, the system sets its due date to the date specified in the Promise Date column on the Inventory Planning Display form when the production order is created through that form.
The system will log an event on the Events tab of the Production Order Maintenance form when the production order's due date has been assigned or updated. This allows users to track who and when assigned or modified the due date, providing information for investigating changes that led to delayed or expedited production orders.
To improve visibility of the required supply dates for planning, scheduling, and tracking, the system also displays the due dates on the following forms:
• Production Schedule Board (AM215555)
• Production Summary (AM000006)
• Release Production Orders (AM500000)
• Rough Cut Planning (AM501000)
• Work Center Schedule (AM000001)
Manufacturing: Enhanced Material Availability and Production Readiness Tracking
In Acumatica ERP 2025 R1, a new inquiry form, Production Orders by Build Capability (AM409000), has been introduced. This inquiry form (shown in the following screenshot) provides advanced tools for improving production planning efficiency by providing real-time insights into material availability. This enhancement supports production managers and planners in making more informed decisions and streamlining their workflows.
Figure: The new inquiry form
Each production order displayed on this form is assigned a readiness status, enabling users to quickly assess whether orders can be initiated based on material availability. Color coding is applied to highlight the readiness of production orders, particularly those with insufficient materials for production. The following readiness statuses are available:
• Ready to Produce (dark green): All materials are available to produce the remaining quantity.
• Partially Ready to Produce (light green): Materials are sufficient to produce a portion of the remaining quantity.
• Ready to Start (yellow): Materials are available to complete the first operation.
• Not Ready (red): Materials are insufficient to complete the first operation.
Calculations are based on the Qty. Hard Available for all materials.
The inquiry form has a side panel with the following tabs for streamlined planning:
• Production Order Maintenance: Provides quick access to additional production information for detailed review.
• Critical Materials: Enables planners to create supply records for addressing material shortages.
• Production Tickets: Allows production managers to print necessary documents for production orders being released into production.
In the out-of-the-box system, a user can find the link to this inquiry form in the Production Orders workspace under the Inquiries category.
These changes simplify the process of evaluating material readiness, improve transparency in production planning, and enhance the ability to address material shortages proactively. Production managers and planners can now rely on more precise insights and efficient tools to ensure production schedules are met and supply chain disruptions are minimized.
Manufacturing: Enhanced Production Scheduling Views | 115
Manufacturing: Enhanced Production Scheduling Views
In Acumatica ERP 2025 R1, production scheduling views have been significantly enhanced. The improvements address the diverse needs of different manufacturing environments, providing manufacturing schedulers and planners with advanced tools to visualize and manage production schedules more effectively.
Work Center Planned Utilization Dashboard
A new dashboard, Work Center Planned Utilization (AM0044DB), has been introduced. This dashboard offers a graphical view of the planned load for a work center, displayed as a bar graph representing utilization over time. Users can select specific work centers to analyze and define time ranges for the data displayed on the graph. The planned load is shown as a percentage of capacity. The graph uses the following color coding to represent planned load:
• Green: Planned load is between 0% and 100%.
• Yellow: Planned load is greater than or equal to 100% and less than 101%.
• Orange: Planned load is greater than or equal to 101% and less than 120%.
• Red: Planned load is greater than or equal to 120%.
The Work Center Schedule table below the graph displays information about the production schedule and load details for the date selected in the Schedule Date box.
The dashboard is shown in the following screenshot.
Figure: Work Center Planned Utilization dashboard
In the out-of-the-box system, a user can find the link to this dashboard in the Dashboards workspace under the
Dashboard: Manufacturing category.
The dashboard is available only if the Advanced Planning and Scheduling feature is enabled on the Enable/Disable Features (CS100000) form.
Manufacturing: Enhancements in Finite Production Scheduling | 116
Manufacturing: Enhancements in Finite Production Scheduling
The changes described below are applicable to companies that have enabled the Advanced Planning and Scheduling feature on the Enable/Disable Features (CS100000) form and are using this functionality.
In Acumatica ERP Manufacturing Edition, the constraint date acts as a limiting factor in planning, influencing when production activities should start or finish. The production scheduling algorithm attempts to schedule a production order as close to its constraint date as possible, factoring in available capacity and material availability (if it is configured).
When a production order cannot be scheduled to meet the constraint date, a production planning manager reviews the scheduling outcomes to determine which production orders can be rescheduled, which orders can be delayed, and when overtime is required to increase capacity.
In previous versions of Acumatica ERP, users could encounter unexpected results when the system could not backward-schedule a production order based on its constraint date (that is, when the Finish On scheduling method was used and the start date calculated based on the constraint date was in the past). In this case, the system switched from backward scheduling to forward scheduling (that is, the scheduling method was changed to Start On) and changed the constraint date to the current date (or to a future date, if other production orders were competing for the same work center resources). The information about the original constraint date and scheduling direction was lost, which made it challenging for the production planning manager to compare the calculated production start and end dates with the desired constraint date.
In Acumatica ERP 2025 R1, if a user is attempting to schedule a production order on the Rough Cut Planning (AM501000), Production Order Maintenance (AM201500), or Production Schedule Board (AM215555) form and the production order cannot be scheduled backward to meet the constraint date, the system does the following:
• Attempts to schedule the production order forward by assigning the start date to the current date or a future date based on the load of the work centers involved. The constraint date and the Finish On scheduling method are preserved, which helps the production planning manager to compare the calculated earliest end date with the original constraint date.
• Displays a message indicating that the production order has been scheduled forward instead of backward. A similar message is also displayed on the Events tab of the Production Order Maintenance form.
Additionally, the system now displays a warning message if a production order cannot be scheduled because its constraint date is outside the scheduling window of 120 days. Previously, the scheduling algorithm ignored such production orders, but no notification was shown to the user.
Manufacturing: Other Improvements
Improvements to the Processing of Inventory Transactions
Starting in Acumatica ERP 2025 R1, all manufacturing journal transactions, which were previously recorded in the general ledger, will now be handled within the Inventory functional area. This change simplifies the manufacturing transaction release process and reduces the likelihood of data issues.
Inventory transactions generated in manufacturing will now respect the state of the Update GL check box on the Inventory Preferences (IN101000) form. If the check box is selected, the transactions are posted to the general ledger. If the check box is cleared, the general ledger is not updated by these transactions.
Payroll: Accruing Time Off by Earning Type for PTO Banks
In Acumatica ERP 2024 R2 and previous versions, users could define a particular earning type to accrue time off for paid time off (PTO) banks. If a PTO bank had the Percentage or Front-Loading and Percentage accrual method, it accrued time off based on all the earning types that had the Accrue Time Off check box selected in the Summary area of the Earning Type Codes (PR102000) form.
Starting in Acumatica ERP 2025 R1, the applicable earning types for accruing time off are defined on the PTO bank level instead of earning type level so that users can more flexibly configure PTO banks.
Configuration of the Applicable Earning Types for PTO Banks
To define the earning types to be used for accruing time off for a PTO bank, a payroll administrative user should perform the following steps on the PTO Banks (PR204000) form:
1. Selecting the Percentage or Front-Loading and Percentage accrual method in the Accrual Method box on the
General tab.
The Applicable Earning Types tab appears on the form. In the Accrue Time Off Based On box in the upper area of this tab, the Selected Earning Types option is selected by default.
2. Specifying the earning types to accrue time off on the Applicable Earning Types tab in one of the following ways:
• Leaving Selected Earning Types selected in the Accrue Time Off Based On box in the upper area of the tab, and adding to the table the earning types to accrue time off, as the screenshot below shows. The system will use only the earning types added to the table to accrue time off for the PTO bank.
• Selecting All Earning Types Except Selected in the Accrue Time Off Based On box, and adding to the table the earning types that will not accrue time off. The system will use all the earning types configured in the system on the Earning Type Codes (PR102000) form except the ones listed in the table to accrue time off for the PTO bank.
Figure: Earning types that accrue time off for a PTO bank
Upgrade Process
During the upgrade of Acumatica ERP to 2025 R1, the system updates the PTO banks that have the Percentage or Front-Loading and Percentage accrual method specified in the Accrual Method box on the General tab of the PTO Banks (PR204000) form. The system does the following for these PTO banks on the Applicable Earning Types tab:
• Inserts the Selected Earning Types option in the Accrue Time Off Based On box in the upper area of the tab.
• Adds to the table all the earning types with the Accrue Time Off check box selected in the Summary area of the Earning Type Codes (PR102000) form.
Other Changes
In the Summary area of the Earning Type Codes (PR102000) form, the Accrue Time Off check box has been removed.
Payroll: Calculating a Deduction Based on a Percentage of Eligible Earnings
In Acumatica ERP 2025 R1, users can now specify which earnings and benefits should be included in the calculation of deductions or benefits, such as like the 401(k) plan, based on the percentage of some eligible earnings but not all the gross wages.
On the Deduction and Benefit Codes (PR101060) form, it is now possible to select the Percent of Custom calculation method on the Employer Deduction and Employer Contribution tabs when the Affect Tax Calculation check box is selected in the Summary area (see the screenshot below). With this calculation method selected, the deduction or contribution is calculated as a percentage of the applicable wage specified on the Applicable Wage tab.
Figure: The new calculation method available for deductions
When the Affect Tax Calculation and Payable Benefit check boxes are selected in the Summary area, the Percent of Custom calculation method can also be selected for the benefit on the Employer Contribution tab.
Payroll: Detailed Pay Stub Reports
The following reports, which can be used for printing pay stubs, have been added to the system:
• Detailed Pay Stub (PR642010)
• Detailed Pay Stubs (PR642015)
The usage of these reports is configured at the payment method level.
Configuration of Payment Methods
The configuration of the payroll functionality for the Cash/Check and Direct Deposit payment methods has been improved. An administrative user can now specify whether users can print payroll documents by using simplified or detailed paycheck and pay stub reports.
On the Settings for Use in PR tab of the Payment Methods (CA204000) form, while configuring a Cash/Check payment method (Item 1 in the screenshot below) with the Print Checks option button selected (Item 2), the administrative user can select the Use Detailed Pay Stub Report check box (Item 3). This makes the system use the detailed pay stub reports for printing payroll documents processed with that payment method. Also, if the check box is selected, the system automatically selects the Detailed Paychecks (PR642000) report in the Report box (Item 4).
If any other report except Detailed Paychecks is selected in the Report box, the system clears the Use Detailed Pay Stub Report check box. When the user clears the Use Detailed Pay Stub Report check box, the system automatically selects the simplified Paychecks (PR641010) report in the Report box. Thus, the detailed pay stub report is always used along with the detailed paycheck report for a Cash/Check payment method.
Figure: Payroll settings for a Cash/Check payment method
On the same tab, while configuring a Direct Deposit payment method (Item 1 in the screenshot below) with the Create Batch Payments option button selected (Item 2), the administrative user can select the Use Detailed Pay Stub Report check box (Item 3). This makes the system use the detailed pay stub reports for printing payroll documents processed with this payment method.
Figure: Payroll settings for a Direct Deposit payment method
Printing of Payroll Documents
On the Paychecks and Adjustments (PR302000) form, when a user clicks Print Pay Stub on the More menu, the system opens one of the following:
• The Detailed Pay Stub (PR642010) report (see the following screenshots) if the Use Detailed Pay Stub Report check box is selected for the payment method of the document
• The simplified Pay Stub (PR641000) report if the Use Detailed Pay Stub Report check box is cleared
Figure: Page 1 of the Detailed Pay Stub report
Figure: Page 2 of the Detailed Pay Stub report
Similarly, on the Payment Batches (PR305000) form, when a user clicks Display Pay Stubs on the More menu, the system opens one of the following:
• The Detailed Pay Stubs (PR642015) report if the Use Detailed Pay Stub Report check box is selected for the payment method of the document
• The simplified Pay Stubs (PR641015) report if the Use Detailed Pay Stub Report check box is cleared
On the My Payroll Documents (PR405000) form, when a user clicks a link in the Reference Nbr. column (see the following screenshot), the system opens one of the following:
• The Detailed Pay Stub report if the Use Detailed Pay Stub Report check box is selected for the payment method of the document
• The simplified Pay Stub report if the Use Detailed Pay Stub Report check box is cleared
Figure: Link to open the pay stub reports from the My Payroll Documents form
The same reports are also available on the Pay Stubs screen in the Acumatica mobile app.
Other Enhancements
The Detailed Pay Stubs (PR642000) report that already existed in Acumatica ERP 2024 R2 and previous versions has been renamed to Detailed Paychecks.
Payroll: Exporting Batch Payments to ZIP
In Acumatica ERP, users can export payroll batch payments to an EFT file by using a Canadian EFT plug-in on the Batch Payments (AP305000) form. An electronic funds transfer (EFT) is a file format accepted by major Canadian banks. In Acumatica ERP 2025 R1, users can also compress these exported files to ZIP.
This functionality becomes available if the Canadian Payroll and Canadian Localization features are enabled on the Enable/Disable Features (CS100000) form.
Configuring the Export of Payroll Batch Payments
The way the export of payroll batch payments proceeds on the Batch Payments (AP305000) form depends on the settings of the payment method and cash account used for the batch payments.
To configure the export of payroll batch payments to ZIP files, a payroll administrative user first configures a Direct Deposit payment method on the Payment Methods (CA204000) form. In the Summary area, they specify the following settings:
• Use in PR: Selected
• Require Remittance Information for Cash Account : Selected
• Direct Deposit File Format: CPA005
Then on the Settings for Use in PR tab, the payroll administrative user specifies the following settings:
• Create Batch Payments: Selected
• Export Scenario: Export PR Payments to EFT
On the Remittance Settings tab, the payroll administrative user specifies the remittance settings listed in the following table. These remittance settings will be required for the cash accounts linked to the payment method on the Allowed Cash Accounts tab.
ID Description Entry Mask Validation Reg. Exp.
1 Name AAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ^([\w]|\s){1,30}$
2 Short Name AAAAAAAAAAAAAAA ^([\w]|\s){1,15}$
3 Bank 0000 ^\d{3,3}$
4 Branch 00000 ^\d{5,5}$
5 Account AAAAAAAAAAAA ^([\w]|\s){1,12}$
6 Originator ID AAAAAAAAAA ^([\w]|\s){1,10}$
7 Data Center ^\d{5,5}$
8 Compress to ZIP format 1 ^(1|0)$
The Compress to ZIP format setting determines whether the system should compress the exported file. The administrative user sets the entry mask of this setting to 1 to make the system perform the compression (see the following screenshot).
Figure: Remittance settings of a payment method
For the cash accounts linked to the payment method, on the Remittance Settings tab of the Cash Accounts (CA202000) form, the administrative user specifies the remittance information required by the payment method in the Remittance Details table.
If the payment method and one of its linked cash accounts are specified for a payroll batch payment on the Batch Payments form, when a user clicks Export on the form toolbar, the system exports the batch payment to an ETF file and compresses the file to ZIP.
Payroll: Summary Report
The Payroll Summary (PR641012) report has been added to the Reports category of the Payroll workspace. The report provides an easy way to review the results of one or multiple pay runs before or aer release. The results include payroll funding, check counts, advice counts, wages, employer taxes, employee taxes, hours, earnings, deductions, and benefits. The following screenshot shows the first three pages of this report.
Figure: Pages 1, 2, and 3 of the Payroll Summary report
The last section of the report, Grand Total, provides the following summary information on the remaining pages of the report, as the screenshot below shows:
• Total gross payroll
• Total earnings
• Total payable benefits
• Total employer tax
• Total deductions
• Total employee withholding
• Total net pay
• Total cost of payroll
Figure: Pages 4 and 5 of the Payroll Summary report
Payroll: Taxes by Code Report
The Taxes by Code (PR641068) report has been added to the Annual Reports category of the Payroll workspace. The report shows annual statistics of paid taxes grouped by tax codes. The following screenshot shows the report generated with the default Tax Code option selected as the Level of Detail report parameter.
Figure: The Taxes by Code report with the tax code level of detail
The report additionally shows employee breakdowns for each tax code if it is generated with the Employee option selected as the Level of Detail report parameter. If a user clicks an employee name in the report (see the following screenshot), the system opens the Taxes by Employee (PR641067) report for that employee.
Figure: The Taxes by Code report with the employee level of detail
Platform: Improved Licensing for Anomaly Detection in Generic Inquiries
Acumatica ERP 2025 R1 introduces improved license management for the Detection of Numeric Anomalies in Generic Inquiries feature. (The topics of the Detecting Anomalies in Generic Inquiries chapter provide detailed information about this feature.)
Licensing Updates
In Acumatica ERP 2024 R2, the license limited the number of generic inquiry rows processed per day to 1000. Also, the following limitations were imposed:
• Number of generic inquiries processed per day: 10
• Total number of records sent for processing per day: 1 million
In Acumatica ERP 2025 R1, the license includes parameters that track the number of processed generic inquiries and generic inquiry rows. Also, these parameters have been removed from the web.config file.
Viewing of the Consumption Statistics
An administrative user can now view the consumption statistics for the feature on the License Monitoring Console (SM604000) form. The License tab of the form (System Constraints section) shows the limits specified in the applicable license for system resources based on the license tier. The new license limitations are shown in the following screenshot.
Figure: License limitations on the License Monitoring Console form
On the Constraint History tab of this form, the user can see how much data has been processed. On this tab, the Generic Inquiry Rows Checked for Anomalies in Day (% of Limit) and Generic Inquiries Checked for Anomalies in Day (% of Limit) columns have been added (see the following screenshot). The columns display the total number of processed generic inquiries and their rows for the selected day, as well the percent of the daily limit.
Figure: The updated Constraint History tab
Each number in the columns is a link that a user can click to open the new Anomaly Detection Usage Statistics dialog box. This dialog box contains the list of processed generic inquiries and the number of processed rows for each inquiry (see the following screenshot).
Figure: The Anomaly Detection Usage Statistics dialog box
The statistics are calculated according to the time zone of the server with the Acumatica ERP instance.
The user can view the statistics for the instance and for each of the tenants. Note that license limitations are applied to the instance, not to each tenant separately. If any of the license limits are exceeded, the system now displays the appropriate message on the Detect Anomalies in Generic Inquiries (ML502000) form.
Platform: Improvements to the XML Import and Export Functionality
Acumatica ERP 2025 R1 introduces the improved import of records by using the XML import and export functionality.
Changes to the Export Template
For certain records in Acumatica ERP, the primary keys on the database level differ from the primary keys on the application level. For example, a Dashboard record has the Name primary key in the data access class (DAC) and the DashboardID primary key in the database table. In previous versions, if a customizer used the XML import and export functionality to import records that had the same key fields as the existing records, the system added the records without checking for duplicates. If the customizer then tried to view, modify, or delete any of these duplicate records, an error occurred. To resolve this issue, the customizer had to remove the records from the database.
In Acumatica ERP 2025 R1, the export template has been modified to prevent the duplication of records during import. Version 4 (the format-version="4" attribute; see Item 1 in the following screenshot) of the XML schema provided with Acumatica ERP now supports the new unique-key attribute (Item 2). The system uses this attribute to check for duplicate records. The attribute can be specified for parent and child tables.
Figure: The updated elements of the XML definition
A unique key can contain multiple fields if it is a composite key.
Updates to the Import of Records
The changes described in this section have been made to all forms that support the XML import and export functionality.
When a customizer imports an XML file, the system now verifies whether this file contains any of the unique keys of the database tables from the export template. If the file does not contain a unique key, the system adds this key. The system then checks whether a record with the same unique key exists in the system. The system searches for these records by using the primary key and the unique index from the database (as in the previous versions), as well as by the unique key from the export template.
If only one record is found in a parent table, the system displays a warning that this record will be overwritten (see the following screenshot). If the customizer confirms the operation, the system replaces the unique key of the existing record with the unique key of the imported record.
Figure: The overwriting of an existing record during import
If multiple duplicate records are found, the system displays a warning about these records (see the following screenshot). If the customizer clicks Yes in the Import dialog box, the system then processes the duplicate records depending on the link type and attributes specified for the parent and child tables in the XML schema.
Figure: Detection of duplicate records
Changes to the Publication of a Customization Project
The system also checks for duplicate records during the publication of customization projects.
Suppose that an item in a customization project has the same key (the primary key, the unique index, or the unique key) as the records that exist in the system. When the customizer publishes such a project, the system displays a warning and overwrites the existing records with the item from the project (see the following screenshot).
Figure: Warning during the publication of the customization project
Additional Information
For more information about XML import and export functionality, see XML Import and Export.
Platform: Extended Support for Date-Relative Parameters
Acumatica ERP 2025 R1 introduces support for relative date selection in import and export scenarios and automation schedules.
Support of Relative Dates in Integration Scenarios
In previous versions of Acumatica ERP, if a customizer wanted to specify a relative date in an import or export scenario, they needed to select the Is Relative check box and then select a date in the Value column. The Is Relative check box was available in the following locations:
• On the Target Restrictions tab of the Import Scenarios (SM206025) form
• On the Source Restrictions tab of the Import Scenarios (SM206025) form
• On the Source Restrictions tab of the Export Scenarios (SM207025) form
In Acumatica ERP 2025 R1, this check box has been removed. To select a relative date, the customizer can now select one of the following standard options in the Value column of any of the above-listed tabs:
• @Today: The business day.
• @WeekStart and @WeekEnd: The start and end, respectively, of the current week. The start and end of the week are determined according to the default system locale or the locale the user has selected when signing in to Acumatica ERP.
• @MonthStart and @MonthEnd: The start and end, respectively, of the current month.
• @QuarterStart and @QuarterEnd: The start and end, respectively, of the current quarter.
• @PeriodStart and @PeriodEnd: The start and end, respectively, of the current financial period.
• @YearStart and @YearEnd: The start and end, respectively, of the current calendar year.
The customizer can also specify one of the options listed above followed by + or - and the number of days to be added or subtracted from that date. For example, the customizer could do the following:
• Indicate the previous day by selecting @Today in the Calendar dialog box (see Item 1 in the following screenshot) and then type -1 in the Value column (Item 2).
The customizer opens this dialog box by clicking the Calendar button in a date box (Item 3).
• Specify a relative date in the past or in the future by specifying values such as @Today-2 or @Today+4.
Figure: Selection of a relative date on the Import Scenarios form
On the Source Restrictions tab of the Import Scenarios form, the Calendar dialog box is available for a field only if this field has DateTime selected in the Data Type column on the Data Providers (SM206015) form.
Support of Relative Dates in Automation Schedules
In previous versions of Acumatica ERP, the customizer needed to perform similar actions to those described in the previous section to select relative dates in automation schedules on the Conditions and Filter Values tabs of the Automation Schedules (SM205020) form.
In Acumatica ERP 2025 R1, the Relative check box has been removed from these tabs, and standard date-relative options have been added. The customizer can now specify a relative date in the same way as the previous section described.
Migration Notes
If the customizer has import scenarios, export scenarios, or automation schedules that used date-relative parameters with the Relative check box selected, they do not need to make any changes to these entities. When the customizer updates the instance by using the Acumatica ERP Configuration wizard, the system transforms the parameters to the new format automatically.
Platform: Support for the Numeric Attribute Type
Acumatica ERP 2025 R1 introduces the support of numeric values for attributes.
Support for the New Attribute Type
In previous versions of Acumatica ERP, a user could not specify attributes that contained numbers.
In Acumatica ERP 2025 R1, the new Number control type is supported. The user can use this type to create attributes with numeric values.
Users can select attributes of the Number type on the Attributes tab of all forms that have this tab, such as Vendor Classes (AP201000). Also, these attributes can be selected in the User-Defined Field Parameters dialog box on all forms that support user-defined fields, such as Shipments (SO302000) and Leads (CR301000).
Changes to the Attributes Form
On the Attributes (CS205000) form, the Number option has been added to the Control Type box (see Item 1 in the following screenshot). If the user selects this option, the new Decimal Places box becomes available (Item 2). In this box, the user can specify the number of decimal places (0 through 8) that an attribute of this type can contain.
Figure: The updated Attributes form
If the user specifies a number that is greater than 8, the system replaces the entered value with 8. If the user specifies 0, the system will use an integer value for the attribute. By default, the value in this box is 0.
Platform: Other Improvements
Acumatica ERP 2025 R1 introduces the improvements to the platform functionality that are described below.
Maintenance Mode During Snapshot and Tenant Operations
Starting in Acumatica ERP 2025 R1, administrative users must switch on maintenance mode before copying tenants and creating or restoring snapshots. (For more information about these tasks, see Tenants: General Information and Snapshots: General Information.) The activation of this mode is crucial because these operations temporarily disable database constraints, which can endanger data consistency.
In the new version, if a user attempts to copy a tenant or create or restore a snapshot on the Tenants (SM203520) form, the system prompts them to activate maintenance mode, as illustrated in the screenshot below.
Figure: A prompt to activate maintenance mode
When the user clicks Open, the system opens the Apply Updates (SM203510) form, where they can switch on maintenance mode by clicking Schedule Lockout on the form toolbar. The user must then specify the date, time, and reason for the lockout in the Schedule Lockout dialog.
Aer the tenant has been copied or the snapshot created or restored, the user should switch off maintenance mode by clicking Stop Lockout on the form toolbar of the Apply Updates form.
Profile Entities in Search Results
Beginning in Acumatica ERP 2025 R1, search results displayed on the Transactions and Profiles tab of the Search workspace prioritizes records of the following entity types:
Entity Data access class
Business account PX.Objects.CR.BAccount
Customer PX.Objects.AR.Customer
Payroll employee PX.Objects.PR.PREmployee
Entity Data access class
Contact PX.Objects.CR.Contact
Vendor PX.Objects.AP.Vendor
Employee PX.Objects.EP.EPEmployee
Lead PX.Objects.CR.CRLead
Inventory item (stock or non-stock) PX.Objects.IN.InventoryItem
Projects and Construction: AIA Report with Time and Material Lines
The American Institute of Architects (AIA) report is a standardized report form that is used for billing purposes in the construction industry. In previous versions of Acumatica ERP Construction Edition, users could include only progress billing lines of pro forma invoices in the prepared AIA reports.
In Acumatica ERP Construction Edition 2025 R1, the AIA report functionality has been enhanced. Now users can include time and material lines of pro forma invoices in the AIA reports in addition to progress billing lines. The following sections describe the process of including time and material lines in AIA reports and list the UI changes that have been introduced with this functionality.
AIA Reports with Time and Material Amounts
To include time and material lines in an AIA report and prepare the report, a user performs the following general steps:
1. The user runs project billing for a project on the Projects (PM301000) form or Run Project Billing (PM503000) form to prepare a pro forma invoice.
2. The user opens the prepared pro forma invoice on the Pro Forma Invoices (PM307000) form. On the Time and Material tab, cleared check boxes in the Include in Progress Billing column (shown below) for the time and material lines indicate that the lines have not been added to the progress billing yet. The Revenue Task column on the Time and Material tab indicates the progress billing line to which the time and material line corresponds. The system automatically inserts a revenue task in each time and material line that has been created automatically during project billing or added manually by a user.
Figure: Pro forma invoice with time and material lines
If the project task in a time and material line has the Cost Task type and the corresponding cost budget line has no revenue task specified on the Cost Budget tab of the Projects (PM301000) form, the Revenue Task column remains empty by default. A user should specify the corresponding revenue task in this line manually.
3. On the Progress Billing tab, the user loads progress billing lines by clicking Load Lines (if the lines were not added automatically during the billing procedure).
4. The user transfers the time and material amounts to the respective progress billing lines by doing either of the following on the Time and Material tab:
• Selecting the Include in Progress Billing check box for the particular lines to be included in progress billing and, thus, in the AIA report
• Clicking the Include in Progress Billing button on the table toolbar to include all lines in progress billing and in the AIA report
In each line, the Progress Billing Line Nbr. column indicates the line on the Progress Billing tab this time and material line corresponds to (see the following screenshot). The Amount Included in Progress Billing column shows the amount that was included in progress billing.
Figure: Time and material lines to be included in the AIA report
On the Progress Billing tab, the Time and Material Amount column indicates the total amount of the time and material line that corresponds to a progress billing line, as shown in the following screenshot.
Figure: Amounts transferred from time and material lines to progress billing lines
5. Finally, the user clicks Print AIA Report on the form toolbar to prepare the AIA report for the pro forma invoice. The resulting report includes the amounts of the time and material lines, as the following screenshot shows.
Figure: Time and material amounts included in the AIA report
To remove previously added time and material lines from the AIA report, the user either clears the Include in Progress Billing check box for particular lines or clicks the Remove from Progress Billing button on the table toolbar of the Time and Material tab of the Pro Forma Invoices (PM307000) form to remove all lines.
New Tab on the Side Panel of the Pro Forma Invoices Form
On the side panel of the Pro Forma Invoices (PM307000) form, the Time and Material Lines in Progress Billing tab has been added. On this tab, a user can view the time and material lines that are related to the currently selected progress billing line, as shown in the following screenshot.
Figure: The new tab of the side panel
Other Enhancements
The following changes have also been made to support the described functionality:
• If a time and material line is linked to a revenue budget line and the Use T&M Revenue Budget Limits check box is selected for a project on the Summary tab of the Projects (PM301000) form, the system calculates the maximum amount that is currently available for billing the customer based on the billing limit amount of the corresponding revenue budget line that is related to the selected revenue task. For the time and material lines with no revenue task specified, the system calculates the maximum billable amount based on the project task in these lines.
• On the Projects form, the system now automatically populates the Revenue Task column in the newly added cost budget lines.
• The following UI elements, which previously were available only if the Construction feature was enabled on the Enable/Disable Features (CS100000) form, now appear unconditionally:
• The Type column on the Tasks tab of the Projects and Project Templates (PM208000) forms
• The Type box in the Summary area of the Project Tasks (PM302000), Project Template Tasks (PM208010), and Common Tasks (PM208030) forms
Projects and Construction: AP Document Recognition for Projects
In previous versions of Acumatica ERP Construction Edition, the AP document recognition functionality did not support the project-related AP documents. Thus, if project accountants received emails with attached invoices related to projects, they had to manually enter project-related AP bills and AP bills for subcontracts in the system. These were a time-consuming and error-prone operation.
In Acumatica ERP Construction Edition 2025 R1, the recognition of an AP documents has been further improved to provide the automatic defaulting of project-related information and recognition of the subcontract numbers in the document lines. This enhancement simplifies and automates the management of AP bills for construction projects and increases efficiency and accuracy in tracking project-related expenses.
New Recognition Feature
A new feature, Recognition of Project-Related Documents, has been added to the Experimental Features group of features on the Enable/Disable Features (CS100000) form.
This feature requires the AP Document Recognition Service feature to be also enabled on the form.
If the feature is enabled, users can now do the following on the Incoming Documents (AP301100) form:
• Select project-related data for project-related bills that are not linked to commitments.
Users can manually populate the project budget key in the lines of the recognized AP document, if needed.
• Include project-related data in the bills linked to purchase orders with receipts or without receipts.
The system now recognizes purchase order numbers in the AP bill lines, links these lines to AP document lines, and automatically populates the project budget key in the lines of the recognized AP document based on the corresponding purchase order. Users can also link AP document lines to purchase orders manually if no exact matching document was found.
• Recognize the subcontract number and include project-related data in the bill lines linked to subcontracts.
The system recognizes subcontract numbers in the AP bill lines, links these lines to AP document lines, and automatically populates the project budget key based on the corresponding subcontract. Users can also link AP document lines to subcontracts manually if no exact matching document was found.
The following screenshot shows a recognized AP bill that is related to a purchase order. The system has linked the purchase order and purchase receipt to these lines and inserted the project budget key (project, project task, and cost code) in both lines.
Figure: A recognized project-related bill
If the system did not link the line automatically to a subcontract line (for example, if multiple options for linking are available), a user can link the line by clicking the line and then clicking the Link Subcontract button on the table toolbar of the Incoming Documents form. When the user clicks this button, the Link Subcontract dialog box opens with a list of subcontracts. When the user selects the corresponding subcontract line and links it to the AP document line, the system automatically populates the project budget key based on the subcontract.
When the user clicks Save and Continue for the recognized bill, the system creates an AP bill and opens the Bills and Adjustments (AP301000) form with it (see the screenshot below). The bill lines are added to the Details tab. For the direct AP bills, the system copies the project budget key along with other line information. For the project- related lines linked to purchase orders, the system also copies the purchase order and receipt numbers to the
PO Number and PO Receipt Nbr. columns, respectively. For the project-related lines linked to subcontracts, the system copies the subcontract number to the Subcontract Nbr. box.
Figure: AP bill created from the recognized document
For more information on AP document recognition, see AP Documents from PDFs: General Information.
Projects and Construction: Enhanced Usability for AP Documents with Multiple Projects
In Acumatica ERP 2025 R1, the accounts payable, purchase orders, and subcontracts functionality related to working with multiple projects has been reworked and enhanced. The user experience of working with the single- project and multi-project documents has been streamlined. The introduced changes simplify data entry for single- project documents, provide flexibility for multi-project documents, and enhance the reporting capabilities.
UI Changes
On the Accounts Payable Preferences (AP101000) form, the Require Single Project per Document check box has been removed. Now users can specify one project, multiple projects, or a combination of any number of projects and the non-project code in the lines of a single AP document, purchase order, or subcontract.
Documents with Multiple Projects
Now if a document relates to multiple projects or to at least one project and non-project code, the system shows
<Multiple projects> in the Project box in the Summary area of the following forms:
• Bills and Adjustments (AP301000)
• Purchase Orders (PO301000)
• Subcontracts (SC301000)
The following screenshot shows a bill that has two different projects specified in its lines on the Bills and Adjustments form. The Project box in the Summary area indicates that the document is related to multiple projects.
Figure: A bill with multiple projects in its lines
Improvements to AP Documents with Retainage
The lines of retainage AP documents now contain all project-related information (project, project task, and cost code) from the original bill lines, as the following screenshot shows. This change helps users to ensure consistency and facilitates detailed subcontract audit reporting.
Figure: A retainage bill with project information in its line
Other Improvements
The users can now select or clear the Pay by Line check box in AP documents, regardless of whether they have document lines specified on the Details tab of the Bills and Adjustments (AP301000) form.
Projects and Construction: Enhancements to the Correction of Pro Forma Invoices
In previous versions of Acumatica ERP, users were able to make corrections to released pro forma invoices that include only progress billing lines. On a user's attempt to correct a pro forma invoice that has at least one time and material line, the system shown an error message. Also, this functionality was available only if the Construction feature was in use.
In Acumatica ERP 2025 R1, the restrictions on correcting the pro forma invoices with time and material lines have been eliminated. The following sections describe the improvements to the ability to correct pro forma invoices.
Workflow of the Correction of Pro Forma Invoices
Suppose that a user needs to correct a pro forma invoice with time and material lines and the invoice has already been released; the corresponding AR invoice has also been released and has the Open status. To create a new revision of the pro forma invoice, the user clicks Correct on the More menu of the Pro Forma Invoices (PM307000) form, as shown in the following screenshot.
Figure: Pro forma invoice to be corrected
The system creates a correction pro forma invoice: that is, a new revision of the pro forma invoice with the On Hold status and a line with the previous revision of the pro forma invoice in the Previous Revisions table on the
Financial tab of the form, as shown in the following screenshot. The time and material lines need to be corrected; the Time and Material Total of the pro forma invoice has not been changed yet.
Figure: The correction pro forma invoice that has been created
Aer the user has made all needed corrections to the time and material lines and the Time and Material Total is now correct, the user releases the new revision of the pro forma invoice. On release of this new revision, the system creates a reversing document, which is listed in the Previous Revisions table of the Financial tab, as shown in
the following screenshot. The system also creates an accounts receivable document; the type, reference number, and current status of this document are shown in the AR Invoice Info section of the tab. The correction pro forma invoice is assigned the Closed status.
Figure: The correction pro forma invoice that has been released
On release of the correction pro forma invoice, the system automatically releases and applies the reversing AR document to the original AR document to completely reverse the previous revision and update project actual values. For more information about pro forma invoice correction, see the Correcting Pro Forma Invoices chapter.
Other Enhancements
The following changes have also been made on the Pro Forma Invoices (PM307000) form:
• The Correct command on the More menu is now available for closed pro forma invoices regardless of whether the Construction feature is enabled on the Enable/Disable Features (CS100000) form.
• The AR Doc. Status box has been added to the Financial tab. This box shows the current status of the AR document that has been prepared for a pro forma invoice.
Projects and Construction: Enhancements to the Cost Projection Functionality
In Acumatica ERP 2025 R1, the cost projection functionality has been enhanced, as described in the following sections.
Time-Sensitive Cost Projections
Now users can create cost projections, calculate project margins, and analyze over- and underbilling for projects for a specific date. The new Cost Projection by Date (PM305500) form and the corresponding Cost Projection by Date (PM3055PL) list of records have been added.
When a user creates a cost projection on the Cost Projection by Date form, they select the project for which the cost projection is prepared and the date on which the cost projection will be calculated (shown below). The system automatically selects or clears the check boxes in the Budget Level section in the Summary area (see the following screenshot) based on the cost budget level specified on the Projects (PM301000) form. The user can clear any of the selected check boxes in the Budget Level section to prepare the cost projection with a less detailed structure.
Figure: New cost projection by date
On the form toolbar, the user clicks Load Lines to populate the budget lines to be analyzed on the Details tab (see the following screenshot).
Figure: Cost projection with added budget lines
Then the user changes the value in the Projected Cost at Completion, Projected Cost to Complete, or % Completed column in the budget lines that should be analyzed. The system recalculates the Overbilling or Underbilling value in the Summary area of the form accordingly.
Creation of a Copy of a Cost Projection
On the Cost Projection by Date (PM305500) form, a user can create a new cost projection based on an existing one. This updates the cost projection with the latest actual values from the project while preserving the manual changes that have been made to the Projected Cost at Completion values on the previous projection date. To do this, on the Cost Projection by Date form, the user creates a new cost projection by date for the same project with the same budget level, loads the budget lines, and clicks Copy Projection on the form toolbar (shown below).
The system opens the dialog box with the list of released cost projections with the same project and project budget structure (also shown in the screenshot below). Then the user clicks the line with the needed cost projection and clicks OK. The system copies the Projected Cost at Completion value to each line in which the Anticipated Cost value does not exceed the Projected Cost at Completion value being copied.
Figure: Creation of a cost projection copy
Enhanced Project Analytics
To get more detailed information and analytics, the user clicks View Finance Chart on the table toolbar of the Cost Projection by Date (PM305500) form. The system opens the new Project Financial Vision (PM405000) form (shown below) with the information for the line that had been selected in the table of the Cost Projection by Date form.
Figure: The Project Financial Vision form
On this form, a user has the following capabilities for analysis of the project costs and revenues and investigating anomalies in actual costs (see the screenshot below):
• Changing the selection criteria to change the scope of the information being analyzed.
• Changing the period for which the data is collected by clicking Zoom In and Zoom Out on the form toolbar, or by changing the option in the Period box and specifying dates in the Start Date and End Date boxes. The system filters the scope of project transactions being included in the analysis based on these dates.
• Grouping information by project task, account group, inventory ID, and cost code by selecting the respective check boxes in the Selection area (see the screenshot below).
Figure: UI elements on the Project Financial Vision form
The user can also view a project dynamics chart by clicking Show Chart on the form toolbar (see the following screenshot).
Figure: Chart prepared for the selected cost projection
Release of Cost Projections by Date
A user can release a cost projection by date on the Cost Projection by Date (PM305500) form regardless of its budget structure. If the cost projection structure matches the structure of the cost budget of the project, the user can
also select the Update Project Budget check box prior to release; on release of such cost projection the system will update the Projected Cost at Completion values in the project cost budget for the corresponding project on the Projects (PM301000) form. For each projection date, only one cost projection by date can be released for each project.
The project budget can be updated on release of the cost projection if there is no released cost projection whose projection date is later than the projection date of the cost projection being released.
The user can then prepare Project WIP (PM651500) and Project WIP Detail (PM652500) reports with the Planned Cost Estimation parameter set to By Cost Projection to use the amounts from the last released cost projection for calculations.
Other Enhancements
On the Cost Projections by Date Report (PMGI3055) inquiry form, users can review the list of released cost projections for all projects. For each project, the table shows a cost projection by date with the latest projection date until the date that is specified in the Actual to Date box, as shown in the following screenshot.
Figure: The Cost Projections by Date Report inquiry form
Upgrade Notes
Aer an upgrade to Acumatica ERP Construction Edition 2025 R1, the system will notify users that the recalculation of project balances is required for the existing projects. For more information, see Post-Upgrade Changes and Actions.
Projects and Construction: Improvements to AR and AP Reports
In Acumatica ERP 2025 R1, improvements have been made to multiple AR and AP reports and inquiry forms to improve their usability for construction companies. The following sections describe the changes to the UI of the report forms used to run reports and to the generated reports.
Changes to the Reports on AR Documents
The following changes have been made to the AR Documents by Customer (AR634000) and AR Documents by Project
(AR634100) reports:
• The reports previously named AR Open Documents by Customer and AR Open Documents by Project have been renamed to AR Documents by Customer (AR634000) and AR Documents by Project (AR634100), respectively. These names reflect the reports' content more precisely. The following changes have been made to both report forms:
• On the Report Parameters tab, the Open and Closed Documents option (Item 1 in the screenshots below) has been added to the Format box to show both open and closed documents.
• In the Format box, the Detailed option has been renamed to Open Documents.
• On the Report Parameters tab, the Project Manager box (Item 2) and the Show Active Projects Only check box (Item 3) have been added. By using these UI elements, users can review data for only active projects and for a specific project manager, which will help them focus on relevant results.
Figure: The AR Documents by Customer report form
Figure: The AR Documents by Project report form
In both generated reports, the following changes have been made:
• Totals have been added to the following columns: Total Amount, Original Retainage, and Paid/Adjusted.
• Projects are now sorted alphabetically.
The following screenshot illustrates the AR Documents by Customer report run for Maxwell Baker’s open and closed documents and including only active projects.
Figure: The AR Documents by Customer report
The following screenshot illustrates the AR Documents by Project report run for open and closed documents and including active projects only.
Figure: The AR Documents by Project report
Changes to the Reports on AP Documents
The following changes have been introduced in the AP Documents by Vendor (AP634000) and AP Documents by Project (AP634100) reports and report forms:
• The reports previously named AP Open Documents by Vendor and AP Open Documents by Project have been renamed to AP Documents by Vendor (AP634000) and AP Documents by Project (AP634100), respectively. These names reflect the reports' content more precisely. The following changes have been made to both report forms:
• On the Report Parameters tab, the Open and Closed Documents option (see Item 1 in the screenshots below) has been added to the Format box to show both open and closed documents.
• In the Format box, the Detailed option has been renamed to Open Documents.
• On the Report Parameters tab, the Project Manager box (Item 2) and the Show Active Projects Only check box (Item 3) have been added. By using these UI elements, users can review data for only active projects and for a specific project manager, which will help them focus on relevant results.
Figure: The AP Documents by Vendor report form
Figure: The AP Documents by Project report form
In both of the generated reports, the following changes have been made:
• Totals have been added to the following columns: Total Amount, Original Retainage, and Paid/Adjusted.
• Projects are now sorted alphabetically.
The following screenshot illustrates the AP Documents by Vendor report run for Maxwell Baker’s open and closed documents and including only active projects.
Figure: The AP Documents by Vendor report
The following screenshot illustrates the AP Documents by Project report run for open and closed documents and including active projects only.
Figure: The AP Documents by Project report
Changes to the Retainage Register Reports
The following changes have been introduced in the AR Retainage Register (AR634500) and AP Retainage Register
(AP634500) reports:
• The new Non-Retain. Paid column has been added to the generated reports. This column shows the amount paid for the non-retainage part of the original document.
• Projects are now sorted alphabetically.
The following screenshot illustrates the AR Retainage Register report.
Figure: The AR Retainage Register report
The following screenshot illustrates the AP Retainage Register report.
Figure: The AP Retainage Register report
Change to the Customer Details Form
On the Customer Details (AR402000) inquiry form, the Project column has been added, as shown in the following screenshot.
Figure: The Customer Details form
Changes to the Invoices and Memos List of Records
On the Invoices and Memos (AR3010PL) list of records, the Project column has been added, as shown in the following screenshot.
Figure: The Invoices and Memos list of records
Projects and Construction: Improvements in Tracking Project Inventory
Acumatica ERP tracks the project-specific inventory information for each project that has the Track by Project Quantity or Track by Project Quantity and Cost inventory tracking method selected on the Summary tab of the Projects (PM301000) form. This tracking is available if the Project-Specific Inventory feature is enabled on the Enable/ Disable Features (CS100000) form.
Side Panels for Tracking Project Inventory
In Acumatica ERP 2025 R1, the following side panel tabs has been added on the Projects form:
• Current Project Inventory: This tab of the side panel (shown below) displays the project inventory information for the project that is currently selected on the Projects form.
Figure: The Current Project Inventory tab of the side panel
• All Project Inventory: This tab of the side panel (shown below) displays the project inventory information for all projects that are configured for project-specific inventory tracking.
Figure: The All Project Inventory tab of the side panel
Both tabs are available if the Project-Specific Inventory feature is enabled on the Enable/Disable Features form. By using these tabs, users can easily get information about the inventory items that are available for a particular project or reserved for all projects so they can plan the usage of materials for projects and the needed project purchases.
By default, the tables on both tabs show only lines with nonzero quantities. To also see the inventory that has already been consumed for the project, a user selects the Show Lines with Zero On Hand Quantity check box in the Selection area of the tab. The system will show lines with zero quantities in the table on a tab as well.
Transfer of the Project Stock to Free Stock
When a project is finished, some project inventory may still be le unused in the project-specific cost layer. In Acumatica ERP 2025 R1, users now have the ability to quickly transfer all the leover material back to the free stock.
On the Projects (PM301000) form, the Transfer Inventory to Free Stock command has been added to the More menu. The command is available for the projects that have the Track by Project Quantity or Track by Project Quantity and Cost inventory tracking mode.
When a user clicks the command, the system opens the new Transfer Project Inventory to Free Stock (PM508000) mass-processing form, shown in the screenshot below. On this form, the user selects the unlabeled check boxes in the lines with the project-related stock items that have a nonzero quantity on hand. The user then clicks Process to run mass-processing. The system creates and releases inventory transfer transactions on the Transfers (IN304000) form that will move the stock from the project cost layer to the normal cost layer of the same warehouse and warehouse location.
Figure: The new mass-processing form
Projects and Construction: Improvements to the Creation of Final Lien Waivers
A final lien waiver is a legal document used in the construction industry when the entire construction job or delivery is finished and final payment has been made. Once an accountant considers the received payment to be final for the scope of the lien waiver, the corresponding lien waiver should be marked as the final one.
In Acumatica ERP Construction Edition 2025 R1, the lien waiver functionality has been extended. Now users can mass-mark lien waivers as final; this capability is available on two forms so that each user can decide which way they find more convenient.
Changes to the Compliance Management Form
A user responsible for lien waiver processing can now finalize lien waivers directly on the Compliance Management (CL401000) form. For this purpose, the Set as Final button has been added on the form toolbar (see the following screenshot).
Figure: The Set as Final button
To mark a particular lien waiver or multiple line waivers as the final ones, the user selects the unlabeled check box in the needed rows and clicks this button. The system verifies that the selected lien waivers can be marked as final; that is, it ensures that no other final lien waiver exists for the group of lien waivers.
The system groups the payment amounts to each conditional or unconditional lien waiver and generates lien waivers based on the option selected in the Calculate Amount By boxes on the Lien Waiver Settings tab of the Compliance Preferences (CL301000) form. For more information, see Lien Waivers: General Information.
Then the system changes the lien waiver type in the Document Category column as follows:
• Conditional Partial to Conditional Final
• Unconditional Partial to Unconditional Final
Mass-Processing of Final Lien Waivers
On the Print/Email Lien Waivers (CL502000) form, the Set as Final option has been added to the Action box, as shown in the screenshot below. Now a user can mass-mark lien waivers as the final ones. On the form, the user selects the Set as Final action and selects the unlabeled check boxes in the rows of the lien waivers to be marked as final. Then the user clicks Process on the form toolbar.
Figure: Mass-marking of the final lien waivers
Also, on the Print/Email Lien Waivers form, the Subcontract Total, PO Total, and PO Number columns have been added. Users can configure filters based on these columns to quickly select lien waivers that are ready to be set as the final ones.
Projects and Construction: Improvements to the Construction Bonding Report
In the construction industry, management uses construction bonding reports to determine the financial health of projects. Acumatica ERP Construction Edition includes the Construction Bonding Report (PM650500) report, which is specifically designed to give a wide-angle snapshot of all the projects in the system and helps users to analyze how much has actually been billed for the project compared to the percentage of the project completion.
In Acumatica ERP 2025 R1, the construction bonding report has been revised and enhanced, as described in the sections below.
Changes to Report Parameters
On the Construction Bonding Report (PM650500) report form, the report parameters (see the screenshot below) have been changed as follows:
• The Use Cost Projection check box has been removed.
• The Planned Cost Estimation box has been added. This parameter specifies the source of the costs that the system will use to calculate the report values. The following options are available:
• By Cost Budget (default): The system will use the revised budgeted amounts of the cost budget lines for calculations.
• By Cost Projection: The system will use the amounts from the last released cost projection for calculations.
Figure: The new report parameter
Changes to the Report Layout
The following columns have been renamed in the printed report:
• Revenue Recognized to Earned Revenue
• Billed to Date to Billings to Period
• Cost to Date to Costs to Period
The following screenshot shows the layout of the prepared report.
Figure: The updated report layout
Changes to Report Calculations
The following table summarizes the changes that have been made to the calculation of some values in the report.
Column Formula Comments
Contract Amount The system now uses the following formula: Contract Amount = SUM of Original Budgeted Amount values + SUM of CO Revenue Budget Change Total values. In the formula, SUM is the sum of the respective amounts in the revenue budget. The values in the Contract Amount column now include the amounts of the change orders that have been released prior to and within the period specified in the As of Pe- riod report parameter.
Cost to Complete The system calculates the value by using the following formula: Cost to Complete = Cost at Completion - Costs to Period.
Projected Cost to Complete The system calculates the value by using the following formulas:
• If there is no released cost pro- jection for the period: Pro- jected Cost to Com- plete = Cost to Com- plete
• If there is a released cost projec- tion for the period: Projected Cost to Complete = SUM of Projected Cost to Complete, where SUM is the sum of the respective amounts in the cost budget
Column Formula Comments
Cost at Completion The system calculates the value by using the following formula: Cost at Completion = SUM of Original Budgeted Amount values + SUM of CO Cost Budget Change Total val- ues. In the formula, SUM is the sum of the respective amounts in the cost budget.
Projected Cost at Completion The system calculates the value by using the following formulas:
• If there is no released cost pro- jection for the period: Pro- jected Cost at Comple- tion = Cost at Comple- tion
• If there is a released cost pro- jection for the period: Pro- jected Cost at Comple- tion = SUM of Project- ed Cost at Completion, where SUM is the sum of the re- spective amounts in the cost budget
Complete % The system calculates the value by using the following formulas:
• If the report is prepared with By Cost Budget selected in the Planned Cost Estimation box: Complete % = Cost to Period / Cost at Com- pletion * 100%
• If the report is prepared with By Cost Projection selected in the Planned Cost Estimation box: Complete % = Cost to Period / Projected Cost at Completion * 100% In both cases, if the calculated val- ue exceeds 100%, % Complete is set to 100.
Column Formula Comments
Period Billings The turnover revenue amount for the specified period, which the sys- tem calculates by using the follow- ing formula: Period Billings
= SUM (Amount)
In this formula, SUM (Amount) is the total amount of project trans- actions of this project with the AR type on the Project Transactions (PM304000) form that have been re- leased within the period specified in the As of Period report parame- ter. The project transactions that orig- inate from AR invoices and deb-
it memos increase the calculated amount; the project transactions that originate from AR credit mem- os decrease the calculated amount.
Billings to Period The billed amount of the project, which the system calculates by using the following formula: Billings to Period = SUM of Amount values.
In this formula, SUM of Amount values is the sum of the relevant project transactions with the AR type on the Project Transactions (PM304000) form that have been re- leased prior to and within the peri- od specified in the As of Period re- port parameter. The project transactions that orig- inate from AR invoices and deb-
it memos increase the calculated amount; the project transactions that originate from AR credit mem- os decrease the calculated amount.
Projects and Construction: Improvements to the Subcontract Audit Report
In the construction industry, management uses subcontract audit reports to ensure accuracy in subcontract billing and verify that the performed work aligns with contract terms. These reports help managers to identify potential risks, track costs, and maintain accountability throughout the construction project lifecycle. For this
purpose, Acumatica ERP Construction Edition includes the Subcontract Audit (SC644000) report. The printed report lists subcontract balances and related documents that have affected these balances (change orders, bills, and payments).
In Acumatica ERP 2025 R1, the layout of the report has been revised, and the report has been enhanced with new parameters, as described in the sections below.
Changes to Report Parameters
On the Subcontract Audit (SC644000) report form, the following report parameters (see the screenshot below) have been added:
• The Project Status box: This parameter filters the projects whose subcontracts will be listed in the report by the statuses of the projects. The default value is All, which means that projects with all statuses are included. A user can select any other parameter option (Active, Completed, Canceled, or Suspended) to include only the projects with the selected status.
• The Subcontract Status box: This parameter filters the subcontracts that will be included in the report. The default value is Open, which means that subcontracts with open statuses are included. A user can select any other parameter option (All, Closed, Open and Closed, or Pending Approval) to include only the subcontracts with the selected status in the report.
• The Report Date box: By default, this box is empty, which means that the report is prepared for the current business date. The user can select a date to prepare the report for this date.
• The Include Pending CO in Revised Subcontract Amounts check box: The user can select whether to include the change orders that have the Open, On Hold, and Pending Approval statuses in the revised subcontract amounts (if the check box is selected) or exclude them (if the check box is cleared).
Figure: The new report parameters
Changes to the Report Layout
The following changes have been made in the printed report (shown in the following screenshot):
• The report header has been reworked to provide detailed information about the report parameters that have been used for preparing the report.
• The Invoices table has been renamed to Bills. In this table, two new columns, Original Retainage and Released Retainage, have been added. The Unreleased Retainage column has been removed from the table.
• The Payments table has been renamed to Applied Payments. In this table, the Original Invoice column has been added to simplify reconciliation.
• The Unapplied Payments table has been added to the report. A user can review this table to make sure that all unapplied payments for subcontracts have been recorded.
Figure: The updated layout of the report
Projects and Construction: Project Quotes in the Mobile App
A project quote in Acumatica ERP is a document that is used to estimate the revenue and costs of a potential project; it can also be used to create this project if the customer agrees to the terms of the quote. Previously, the project quote functionality was not supported in the Acumatica mobile app connected to an instance of prior versions of Acumatica ERP. In the mobile app, the users were not able to create project quotes or review the complete details of existing project quotes that were submitted for approval.
Starting in Acumatica ERP 2025 R1, the Acumatica mobile app includes the Project Quotes screen, which fully supports all the capabilities of the Project Quotes (PM304500) form in the web version.
New Project Quotes Screen
A user can now perform the following operations with project quotes and related documents in mobile app:
• Create a project quote from scratch
• Create a project quote based on an opportunity
• Select a project template in a project quote
• Edit project quotes
• Convert project quotes to projects
• Approve project quotes on the Approvals screen (if the Approval Workflow feature is in use and an approval map is configured for project quotes)
The following screenshot shows a project quote that has been created in the Acumatica mobile app based on an opportunity and is ready to be converted to a project.
Figure: Project quote in the mobile app
For more information about the project quote workflow, see the Processing Project Quotes chapter.
Known Limitations
In the Acumatica mobile app, a user cannot create a project quote based on an opportunity if this opportunity includes user-defined fields that are required. To create a project quote from this opportunity, the user should use the web version.
Projects and Construction: Usage of Free Stock for Projects with Project-Specific Inventory
A project uses the project-specific inventory if it has the Track by Project Quantity or Track by Project Quantity and Cost inventory tracking mode selected on the Summary tab of the Projects (PM301000) form. In previous versions of Acumatica ERP, users were able to directly issue materials for a project that uses the project-specific inventory only if the items were on hand for the project cost layer of the exact project and project task. If the materials
were on hand but not allocated for the project (that is, the materials were in free stock), a user had to process an inventory transfer from the free stock to the project stock first.
Projects that use the project-specific inventory are available if the Project-Specific Inventory feature is enabled on the Enable/Disable Features (CS100000) form.
In Acumatica ERP 2025 R1, the functionality related to project-specific stock has been enhanced. Now users can issue free stock for projects with the project-specific inventory without processing manual inventory transactions. The system automatically performs the needed transfer operations and generates the corresponding inventory transactions.
Changes to the Project-Related Forms
For the projects that have the Track by Project Quantity or Track by Project Quantity and Cost inventory tracking mode selected on the Summary tab of the Projects (PM301000) form, a user now can specify whether free stock items can be issued for these projects. On the same tab, the Allow Issue from Free Stock check box is now available (see the following screenshot).
Figure: The new check box in the project settings
The user selects this check box for a particular project to allow the issuing of the stock that is not allocated to any project in the project-related documents that are created on the Issues (IN302000), Sales Orders (SO301000), Materials (AM300000), and Vendor Shipments (AM310000) forms.
Also, to provide users the capability to quickly create projects that allow the issuing of free stock, the Allow Issue from Free Stock check box has been added on the Summary tab of the Project Templates (PM208000) form.
Changes to Inventory and Order Management Forms
For stock items, a user can now specify the default source that the system will insert in the document lines that are associated with the projects that use the Track by Project Quantity or Track by Project Quantity and Cost inventory tracking mode.
For this purpose, on the Inventory Planning tab of the Stock Items (IN202500) form, the Default Inventory Source for Projects box has been added (see the screenshot below). For each stock item, a user can define the default source from which the system will issue the items on the Sales Orders (SO301000), Materials (AM300000), and Vendor Shipments (AM310000) forms.
The following options are available in the box:
• Project Stock: The system will issue the items from the project-specific layer by default.
• Free Stock: The system will issue the items that are not allocated to any projects by default.
Figure: Stock item settings
The Inventory Source column has been added on the Details tab of the following forms:
• Sales Orders (SO301000)
• Receipts (IN301000)
• Issues (IN302000)
• Adjustments (IN303000)
The option selected in this column (Project Stock or Free Stock) specifies from which source the items will be issued. The items can be issued from the free stock in sales orders and inventory issues only if the Allow Issue from Free Stock check box is selected for the project specified in the document line.
The Cost Layer Type column has been preserved for backward compatibility; now the column is hidden by default on the Details tab of the listed forms and cannot be edited. The value in this
column is specified based on the combination of the inventory source selected in the line and the inventory tracking mode selected in the corresponding project.
On the Transfers (IN304000) form, the From Inventory Source and To Inventory Source columns have been added on the Details tab. In these columns, the user specifies the original source and the destination source for the inventory transfer transactions.
The Cost Layer Type and To Cost Layer Type columns have been preserved for backward compatibility; now the columns are hidden by default on the Details tab of the form and cannot be edited. The values in these columns are specified based on the combination of the inventory source selected in the line and the inventory tracking mode selected in the corresponding project.
On the Sales Orders form, a user can allocate the items for the sales order lines in which Free Stock is specified in the Inventory Source column. To do this, the user clicks Line Details on the table toolbar, selects the Allocated check box in a line, and specifies the quantity of items to be allocated.
Changes to Manufacturing Forms
For the manufacturing documents that are related to projects, the changes listed below have been made to the
Details tab of the Materials (AM300000) and Vendor Shipments (AM310000) forms:
• The Inventory Source column has been added. The option specified in this column (Project Stock or Free Stock) indicates from which source the items will be issued. The items can be issued from the free stock only if the Allow Issue from Free Stock check box is selected for a project specified in the document line.
Changes to the Calculation of Item Quantities in Manufacturing
The rules of calculating item quantities have been revised for the stock items that are issued from free stock for production orders integrated with projects that use project-specific inventory. These are the production orders that have the Update Project check box selected in the Project section of the References tab of the Production Order Maintenance (AM201500) form.
On the Material Wizard 2 (AM300020) form, the Available Qty. for Project values are now calculated as follows:
• If a location is specified for a material in the production order details: The Available Qty. for Project is calculated as the total quantity of item hard available in this warehouse location.
• If no location is specified for a material in the production order details: The Available Qty. for Project
is calculated as the total quantity of item hard available in all locations in the warehouse in which the
Production Allowed and Sales Allowed check boxes are selected on the Warehouses (IN204000) form.
On the Critical Materials (AM401000) form, the Qty. On Hand for Project is calculated as the total quantity of the item that is on hand on the normal cost layer of the applicable warehouse locations. The applicable locations are those in which the Production Allowed and Sales Allowed check boxes are selected on the Warehouses form.
Retail Commerce: Depreciation of Authorize.Net
Starting in Acumatica ERP 2025 R1, the support of the Authorize.Net plug-in has been deprecated. As a result, users can no longer create new transactions with Authorize.Net. For details, see Deprecated Support for the Authorize.Net Payment Plug-In. We recommend that companies switch to other payment methods in the Shopify and BigCommerce stores.
If a BigCommerce store continues using Authorize.Net, an administrative user should perform the following steps to be able to import Authorize.Net payments to Acumatica ERP:
• On the Payments tab of the BigCommerce Stores (BC201000) form, map the Authorize.Net payment method to a Cash/Check payment method of Acumatica ERP and clear the value in the Proc. Center ID column (see the following screenshot).
Figure: Store settings in Acumatica ERP
• Optional: In the BigCommerce store, go to the Settings > Payments page. On the Authorize.Net Settings
Figure: Settings of the Authorize.Net payment method in a BigCommerce store
This setting prevents the Open status from being assigned to a non-captured payment imported to Acumatica ERP, which is an incorrect status for a payment with unfinished processing.
With these settings, credit card payments processed with Authorize.Net in the BigCommerce store will be imported to Acumatica ERP as non-card payments. These payments can be captured, voided, or refunded only in the BigCommerce store. For more details on processing non-card payments for BigCommerce, see Order Synchronization: Non-Card Payments.
Refunds created for these payments will be imported as non-card refunds. For more details on processing non-card refunds for BigCommerce, see Importing Non-Card Refunds.
Retail Commerce: Import of Shopify Orders Without Importing Customers
In Acumatica ERP 2024 R2 and previous versions, when the Sales Order entity was activated for a Shopify or BigCommerce store, the activation of the Customer entity was required. When a new customer registered in a store and placed an order, the order was imported to Acumatica ERP along with the customer.
In Acumatica ERP 2025 R1, if users do not need to process the customer data in Acumatica ERP, they can import orders from Shopify and BigCommerce stores without importing customers using a generic guest customer instead.
Configuring the Import of Orders Without Customers
The following topics describe the configuration of the order synchronization with customers between Acumatica ERP and each of the external stores:
• Shopify: The Minimal Configuration of Order Synchronization section of the Order Synchronization: General Information topic
• BigCommerce: The Minimal Configuration of Order Synchronization section of the Order Synchronization: General Information topic
To configure the synchronization of orders without customers for the Shopify or BigCommerce store, an administrative user should perform the steps described in the topics listed above with the following differences on the Shopify Stores (BC201010) or BigCommerce Stores (BC201000) form:
• Selecting Import in the Sync Direction column for the Sales Order entity on the Entities tab.
• Skipping the activation of the Customer entity on the Entities tab. That is, the Active check box remains cleared for the Customer entity, and no steps are performed to activate the entity.
• Specifying a guest customer in the Generic Guest Customer box on the Customers tab, as the following screenshot shows for a Shopify store.
Figure: The guest customer specified for a Shopify store
When the system imports orders from the Shopify or BigCommerce store, the guest customer specified for the store is assigned as the customer for each created sales order. The system does not import customers from the store and does not create new customer records. On the Addresses tab of the Sales Orders (SO301000), the system selects the Override Contact and Override Address check boxes and fills in the ship-to and bill-to information with the corresponding customer's data from the external store.
Retail Commerce: Import of Shopify Documents in the Default Store Currency
A Shopify store can support multiple currencies, one of which is the default store currency. Users can pay their orders in a currency that is different than the default one.
In Acumatica ERP 2024 R2 and previous versions, the system imported an order and the related documents, such as payments and refunds, from a Shopify store in the currency in which the order was paid in the store.
To support the scenarios when users do not need multicurrency accounting, Acumatica ERP 2025 R1 allows administrative users to import orders and the related payments and refunds from Shopify using only the default store currency.
Importing Documents in the Default Store Currency
To make the system import documents from the Shopify store in only the default store currency, an administrative user selects the Import in External Default Currency check box on the Orders tab of the Shopify Stores (BC201010) form. (See the following screenshot.)
Figure: The new currency setting on the Shopify Stores form
With the check box selected, the system imports orders from the Shopify store in the default store currency even if they were paid in another currency. The system can import all the documents related to these orders as payments and refunds in the default store currency as well. To set this up, the administrative user also configures proper mappings that have the default store currency on the Payments tab of the Shopify Stores form.
The following limitations apply to the import of documents in the default store currency:
• If a Shopify order has already been imported to Acumatica ERP in a currency that is different than the default store currency before the Import in External Default Currency check box is selected on the Orders
tab of the Shopify Stores form, all the documents related to that order will be imported in the same order currency even with the Import in External Default Currency check box selected for the store.
• If a credit card payment is imported to Acumatica ERP in a currency other than the one in which the customer paid in the Shopify store, the payment can be captured, voided, or refunded only in the Shopify store.
Retail Commerce: Improvements to the Mapping of Taxes for Shopify
Taxes in Shopify can have the same name but different rates, as the following screenshot shows.
Figure: Taxes with the same name but different rates in Shopify
In Acumatica ERP 2024 R2 and previous versions, the mapping of taxes from Shopify with taxes configured in Acumatica ERP was performed by the tax name. In Acumatica ERP 2025 R1, the mapping of taxes has been improved to support the import of taxes with the same name but different rates from Shopify.
Configuring the Mapping of Taxes
To map taxes from Shopify with taxes from Acumatica ERP, an administrative user creates a substitution list on the Substitution Lists (SM206026) form. In the substitution list, the administrative user specifies a tax from the Shopify store in the Original Value column in either of the following ways (see the screenshot below):
• <Tax Name>: The tax name if the name is unique (for example, Arkansas State Tax).
• <Tax Name> <Tax Rate>: The tax name followed by the space character and the tax rate if there are multiple taxes with the same name but different rates (for example, Arkansas State Tax 6.5%).
The administrative user specifies the tax rate as a decimal followed by the % character, as it is represented in the Shopify store. For example, the tax rate of 6.5% is specified as 6.5% and the tax rate of 0.125% is specified as 0.125%.
If a user specifies the tax name along with the tax rate for a tax with a unique name, the system still correctly processes this mapping.
Figure: A substitution list for taxes
To use the created substitution list for the Shopify store, the administrative user specifies the substitution list in the
Taxes box on the Orders tab of the Shopify Stores (BC201010) form. (See the following screenshot.)
Figure: The substitution list for taxes specified for a Shopify store
Retail Commerce: Improvements to Synchronization of Price Lists with Shopify
In Acumatica ERP 2024 R2 and previous versions, during the synchronization of the Price List entity for a Shopify store, the system created or updated the product catalogs that corresponded to the exported price classes. The system added to each catalog all the products, including those that had no prices defined within the corresponding price class. For more information about the synchronization of price lists, see Sales Price Lists: General Information.
In Acumatica ERP 2025 R1, the export of price lists has been improved so that the product catalogs include only products whose prices (of the corresponding price class) were effective on the synchronization date.
Export of Sales Prices
During the synchronization of the Price List entity for a Shopify store, the system creates or updates the catalog that corresponds to the exporting customer price class of the Customer Price Class type specified on the Sales Prices (AR202000) form.
In the Included section of the catalog (see the following screenshot), the system adds all the inventory items of the price class that have sales prices effective on the date of the synchronization on the Sales Prices form. The rest of the products, which have been already synchronized with the Shopify store but have no effective prices within the price class, are added to the Excluded section. The excluded items are hidden from customers assigned to the catalog.
Figure: The Included and Excluded sections of a product catalog at a Shopify store
Retail Commerce: Inventory Replenishment for Amazon- Fulfilled Orders
Acumatica ERP supports the import of marketplace-fulfilled orders from Amazon stores. To fulfill these orders, merchants send inbound shipments with items to Amazon fulfillment centers, and Amazon uses the stock sent to handle the order fulfillment. However, items sent to Amazon fulfillment centers may be lost or damaged during shipping and receiving. As a result, the stock data in Acumatica ERP may be inaccurate and thus may not match the quantity of items received by Amazon.
To streamline inventory management and improve the accuracy of inventory stock, Acumatica ERP 2025 R1 allows the synchronization of inbound shipments sent from merchants to Amazon fulfillment centers.
Configuration of the Store
To configure the system to import inbound shipments sent to Amazon fulfillment centers, an administrative user should perform the following steps on the Amazon Stores (BC201020) form:
1. Activating the Marketplace Transfer Order and Marketplace Transfer Receipt entities on the Entities tab.
2. Specifying an order type in the Order Type for Import box on the Inventory tab (Item 1 in the screenshot below). The system will use the specified order type to create transfer orders during the import of inbound shipments. The selected order type must have the TR - Transfer order template specified on the Order Types (SO201000) form.
3. Specifying a date in the Earliest Shipment Date box on the Inventory tab (Item 2). The system will import inbound shipments from Amazon created on or aer the specified date.
4. Specifying the merchant warehouse in the Source Warehouse box on the Inventory tab (Item 3). This is the warehouse from which stock items are shipped to the Amazon fulfillment center. The source warehouse must differ from the marketplace warehouse specified on the Orders tab for the store.
5. Specifying the warehouse that represents the Amazon fulfillment center in the Marketplace Warehouse box on the Orders tab. The merchant sends stock items to that warehouse, and Amazon fulfills the merchant's orders from the warehouse. The marketplace warehouse must differ from the source warehouse specified on the Inventory tab for the store.
6. Optional: Specifying a substitution list configured on the Substitution Lists (SM206026) form in the Ship- Via Codes to Carriers box on the Inventory tab (Item 4). The system will use this substitution list to match carrier names from the Amazon store with ship-via codes from Acumatica ERP.
Figure: New inventory settings on the Amazon Stores form
In addition to specifying store settings, the administrative user has the ability to configure filtering and mapping rules for the Marketplace Transfer Order entity on the Entities (BC201020) form, if needed.
Import of Inbound Shipments from Amazon
While the administrative user prepares and processes the data for the Marketplace Transfer Order entity on the Prepare Data (BC501000) and Process Data (BC501500) forms, the system imports from Amazon inbound shipments sent from the merchant warehouse to the Amazon fulfillment center. The system imports only the inbound shipments created on or aer the date specified in the Earliest Shipment Date box on the Inventory tab of the Amazon Stores (BC201020) form.
For each imported inbound shipment, the system creates a transfer order on the Sales Orders (SO301000) form with the type specified in the Order Type for Import box on the Inventory tab of the Amazon Stores form. In each line of the created transfer order, the system inserts the source warehouse specified for the Amazon store in the Warehouse column on the Details tab of the Sales Orders form. In the Destination Warehouse box of the Summary area, the system inserts the marketplace warehouse specified for the Amazon store.
During the preparation and processing of the data for the Marketplace Transfer Receipt entity on the Prepare Data and Process Data forms, the system creates a purchase receipt of the Transfer Receipt type on the Purchase Receipts (PO302000) form for the imported transfer order if the following conditions are met:
• The corresponding inbound shipment in Amazon is being received (has the Receiving status) or has been received (has the Closed status).
• The transfer order has been processed and has a released transfer of the 2-Step type created on the
Transfers (IN304000) form.
Limitations of Importing Inbound Shipments
The following limitations apply to the import of inbound shipments:
• The connector can import inbound shipments created only within the last 18 months. To avoid data inconsistencies, we recommend specifying a date within the past 18 months in the Earliest Shipment Date box on the Inventory tab of the Amazon Stores (BC201020).
• When users process the data for the Marketplace Transfer Order entity on the Prepare Data (BC501000) form, the connector creates sync records with the Invalid status for inbound shipments that have not been imported yet but have already been closed in Amazon. These records are excluded from further processing. If users need to import these inbound shipments, they need to force-synchronize the corresponding sync records on the Sync History (BC301000) form.
• The synchronization of inbound shipments with lot- or serial-tracked inventory items is partially supported because Amazon does not provide any information about the lot or serial numbers of the received items.
During the processing of the Marketplace Transfer Order entity, the connector creates a transfer order for an inbound shipment with lot- or serial-tracked items without information about lot or serial numbers. Users need to manually process the transfer order to add lot or serial numbers for the shipping items. Aer the processing of the transfer order is finished and a transfer of the 2-Step type has been created and released on the Transfers (IN304000) form, users skip the processing of the Marketplace Transfer Receipt entity.
Instead, they manually create a purchase receipt of the Transfer Receipt type on the Purchase Receipts
(PO302000) form for the transfer.
• The synchronization of inbound shipments with non-stock kits is partially supported.
When a 2-step transfer is created for a transfer order with a non-stock kit on the Transfers form, Acumatica ERP automatically adds the components of the non-stock kit to the transfer based on the kit specification from the Kit Specifications (IN209500) form. A user needs to process this transfer manually.
• During the processing of the Marketplace Transfer Receipt entity, if the quantity of an item received in Amazon is either less than the quantity received in Acumatica ERP or greater than the initially shipped quantity, the connector does not add the item to the created purchase receipt. Users need to manually process these items.
Users need to create a purchase receipt of the Transfer Receipt type for the initially shipped quantity of the item on the Purchase Receipts form. For the discrepancy between the shipped and received quantities, users need to create an inventory adjustment on the Adjustments (IN303000) form with a positive value for the exceeded quantity or with a negative value for the insufficient quantity.
• The connector may experience delays with the processing of already-imported inbound shipments because Amazon does not provide the date of the shipment modification. Consider an inbound shipment that has been imported to Acumatica ERP, and then some changes have been made to the shipment in Amazon. If users need to receive these changes in Acumatica ERP as soon as possible, they should force-synchronize the sync record of the inbound shipment on the Sync History form.
• To comply with the limitations of the Amazon API and to optimize the system load, we recommended preparing and processing of the data for the Marketplace Transfer Order and Marketplace Transfer Receipt entities once a day at nighttime.
Retail Commerce: Replacement of REST API with GraphQL API for Shopify
Shopify is deprecating the REST API for apps and integrations aer February 1, 2025, and switching to GraphQL instead. In Acumatica ERP 2025 R1, the corresponding changes have been implemented in the ecommerce connector. The connector synchronizes the following entities by using GraphQL:
• Stock Item
• Non-Stock Item
• Template Item
• Product Availability
Stock Item and Non-Stock Item Entities
The following table shows how the ecommerce connector maps Acumatica ERP fields to Shopify fields when it synchronizes stock items and non-stock items with Shopify by using the GraphQL API.
For details about the mapping for the Shopify user interface, see Stock Item Entity and Non-Stock Item Entity.
Table: Stock Item and Non-Stock Item Import/Export Mapping
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
The Stock Items (IN202500) form if the exported item is a stock item or the Non-Stock Items (IN202000) form if the exported item is a non- stock item
Description Summary area title ProductCreateInput / ProductUpdateIn- put String
Item Class General tab, Item Defaults section productType ProductCreateInput / ProductUpdateIn- put String
Description Description tab descriptionHtml ProductCreateInput / ProductUpdateIn- put HTML
Vendor ID Vendors tab vendor ProductCreateInput / ProductUpdateIn- put String
Search Key- words eCommerce tab tags ProductCreateInput / ProductUpdateIn- put String
Category ID Attributes tab, Sales Cate- gories table tags ProductCreateInput / ProductUpdateIn- put String
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
Visibility: Visi- ble eCommerce tab status: ACTIVE ProductCreateInput / ProductUpdateIn- put String
Visibility: Fea- tured eCommerce tab status: ARCHIVED ProductCreateInput / ProductUpdateIn- put String
Visibility: Invisi- ble eCommerce tab status: DRAFT ProductCreateInput / ProductUpdateIn- put String
Inventory ID Summary area sku ProductVariantsBulkInput / ProductVari- antsBulkUpdate String
Weight Packaging tab, Dimensions section inventoryItem.mea- surement.weight.val- ue ProductVariantsBulkInput.inventoryItem
> InventoryItemInput.measurement > In- ventoryItemMeasurementInput.weight Deci- mal
Weight UOM Packaging tab, Dimensions section inventoryItem.mea- surement.weight.unit ProductVariantsBulkInput.inventoryItem
> InventoryItemInput.measurement > In- ventoryItemMeasurementInput.weight String
Default Price Price/Cost tab, Price Manage- ment section price ProductVariantsBulkInput / ProductVari- antsBulkUpdate Money
Tax Category General tab, Item Defaults section taxable ProductVariantsBulkInput / ProductVari- antsBulkUpdate Boolean
MSRP Price/Cost tab, Price Manage- ment section compareAtPrice ProductVariantsBulkInput / ProductVari- antsBulkUpdate Money
Alternate Type:
GTIN/EAN/UPC/
ISBN or Barcode Cross-Refer- ence tab barcode ProductVariantsBulkInput / ProductVari- antsBulkUpdate String
A stock item requiresShipping ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
A non-stock item, Require Shipment: Selected General tab, Item Defaults section
Page Title eCommerce tab Product.seo.title ProductCreateInput.seo / ProductUp- dateInput.seo String
Meta Descrip- tion eCommerce tab Product.seo.descrip- tion ProductCreateInput.seo / ProductUp- dateInput.seo String
Template Item Entity
The following table shows how the ecommerce connector maps Acumatica ERP fields to Shopify fields when it synchronizes template items with Shopify by using the GraphQL API.
For details about the mapping for the Shopify user interface, see Template Item Entity.
Table: Template Item Import/Export Mapping
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
The Template Items (IN203000) form
Description Summary area title ProductCreateInput / ProductUpdateIn- put String
Item Class General tab, Item Defaults section productType ProductCreateInput / ProductUpdateIn- put String
Description Description tab descriptionHtml ProductCreateInput / ProductUpdateIn- put HTML
Vendor ID Vendors tab vendor ProductCreateInput / ProductUpdateIn- put String
Search Key- words eCommerce tab tags ProductCreateInput / ProductUpdateIn- put String
Category ID Attributes tab, Sales Cate- gories table tags ProductCreateInput / ProductUpdateIn- put String
Visibility: Visi- ble eCommerce tab status: ACTIVE ProductCreateInput / ProductUpdateIn- put String
Visibility: Fea- tured eCommerce tab status: ARCHIVED ProductCreateInput / ProductUpdateIn- put String
Visibility: Invisi- ble eCommerce tab status: DRAFT ProductCreateInput / ProductUpdateIn- put String
As part of the synchronization of the Template Item entity, .matrix items are exported to Shopify. The following table shows how the ecommerce connector maps Acumatica ERP fields to Shopify fields when it synchronizes matrix items with Shopify by using the GraphQL API.
Table: Matrix Item Import/Export Mapping
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
The Template Items form
Attribute Configuration tab, Attributes section options ProductCreateBulkInput / ProductUp- dateBulkInput Array
Attribute Value Item Creation
tab options values ProductCreateBulkInput / ProductUp- dateBulkInput Array
Default Price Price/Cost tab, Price Manage- ment section price ProductCreateBulkInput / ProductUp- dateBulkInput Money
Tax Category General tab, Item Defaults section taxable ProductCreateBulkInput / ProductUp- dateBulkInput Boolean
MSRP Price/Cost tab, Price Manage- ment section compareAtPrice ProductCreateBulkInput / ProductUp- dateBulkInput Money
Page Title eCommerce tab Product.seo.title ProductCreateInput.seo / ProductUp- dateInput.seo String
Meta Descrip- tion eCommerce tab Product.seo.descrip- tion ProductCreateInput.seo / ProductUp- dateInput.seo String
Availability: Set as Available (Track Qty.) eCommerce tab invento- ryItem.tracked: true ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Set as Available (Don't Track Qty.) eCommerce tab invento- ryItem.tracked: false ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Set as Pre-Order eCommerce tab invento- ryItem.tracked: false ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Do Not Update eCommerce tab invento- ryItem.tracked: No changes ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Set as Unavailable eCommerce tab invento- ryItem.tracked: false ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
When Qty. Un- available: Do Nothing eCommerce tab inventoryPolicy: No changes ProductVariantsBulkInput.inventoryPoli- cy / ProductVariantsBulkUpdate.invento- ryPolicy String
When Qty. Un- available: Set as Unavailable eCommerce tab inventoryPolicy: DE- NY ProductVariantsBulkInput.inventoryPoli- cy / ProductVariantsBulkUpdate.invento- ryPolicy String
The Stock Items (IN202500) form if the matrix item is a stock item or the Non-Stock Items (IN202000) form if the matrix item is a non- stock item
Inventory ID Summary area sku ProductVariantsBulkInput / ProductVari- antsBulkUpdate String
Weight Packaging tab, Dimensions section inventoryItem.mea- surement.weight.val- ue ProductVariantsBulkInput.inventoryItem
> InventoryItemInput.measurement > In- ventoryItemMeasurementInput.weight Deci- mal
Weight UOM Packaging tab, Dimensions section inventoryItem.mea- surement.weight.unit ProductVariantsBulkInput.inventoryItem
> InventoryItemInput.measurement > In- ventoryItemMeasurementInput.weight String
Alternate Type:
GTIN/EAN/UPC/
ISBN or Barcode Cross-Refer- ence tab barcode ProductVariantsBulkInput / ProductVari- antsBulkUpdate String
Product Availability Entity
The following table shows how the ecommerce connector maps Acumatica ERP fields to Shopify fields when it exports the availability of stock items to Shopify by using the GraphQL API.
For details about the mapping for the Shopify user interface, see Product Availability Entity.
Table: Product Availability Export Mapping
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
The Stock Items (IN202500) form
Fields in Acumatica ERP Fields in Shopify
Field Name Form Object Field Name for Query Object Type
Availability: Set as Available (Track Qty.) eCommerce tab invento- ryItem.tracked: true ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Set as Available (Don't Track Qty.) eCommerce tab invento- ryItem.tracked: false ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Set as Pre-Order eCommerce tab invento- ryItem.tracked: false ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Do Not Update eCommerce tab invento- ryItem.tracked: No changes ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
Availability: Set as Unavailable eCommerce tab invento- ryItem.tracked: false ProductVariantsBulkInput.inventoryItem
/ ProductVariantsBulkUpdate.invento- ryItem Boolean
The Shopify Stores (BC201010) form when When Qty. Unavailable is set to Store Default on the eCommerce tab of the Stock Items form
When Qty. Un- available: Do Nothing eCommerce tab inventoryPolicy: No changes ProductVariantsBulkInput.inventoryPoli- cy / ProductVariantsBulkUpdate.invento- ryPolicy String
When Qty. Un- available: Set as Unavailable eCommerce tab inventoryPolicy: DE- NY ProductVariantsBulkInput.inventoryPoli- cy / ProductVariantsBulkUpdate.invento- ryPolicy String
The following table shows the Shopify fields that were available during the synchronization of the Stock Item, Non- Stock Item, and Template Item entities through the REST API but are unavailable with GraphQL.
Table: External Fields Unavailable Through GraphQL: Stock Item, Non-Stock Item, and Template Item
Tabs of the Entities
(BC202000) form External Object External Field REST API Object REST API Field
Import Mapping, Import Filtering Product Published Published
Import Mapping, Import Filtering, Export Mapping Product PublishedScope PublishedScope
Import Mapping, Export Mapping Product -> Product Variants FulfillmentService Product > Product Variants fulfillmen- t_service
PresentmentPrices Product > Product Variants presentmen- t_prices
The following table shows the Shopify fields that were available during the synchronization of the Product Availability entity through the REST API but are unavailable with GraphQL.
Table: External Fields Unavailable Through GraphQL: Product Availability
External Field REST API Object REST API Field
RelocateIfNecessary InventoryLevel relocate_if_necessary
DisconnectIfNecessary InventoryLevel disconnect_if_necessary
System Administration: Email Scheduling for Reports
In previous versions of Acumatica ERP, a user could schedule the regular sending of reports in the system in either of the following ways, but both approaches had limitations:
• The user could schedule the sending of a report by using the Send Reports (SM205060) form, which is now obsolete and due for deprecation.
• On the Business Events (SM302050) form, the user could configure a business event with an email template as a subscriber to send the report as an attachment. However, configuring a business event requires specifying a data source, such as a generic inquiry or data entry form, which is not always suitable for the scheduling of reports.
Improvements in Acumatica ERP 2025 R1 address these limitations by enhancing email templates and report management, replacing outdated functionality, and providing comprehensive support for all report-scheduling scenarios.
Scheduling of the Sending of a Report
On the report toolbar of all report forms, the Schedule Template button has been removed. To replace this outdated functionality, the new Email Notification tab has been added to these report forms. On this tab, a user can view the list of email templates used to send the report. Also, the user can start scheduling the sending of the report by clicking the Schedule Report button on the table toolbar of the tab (see the following screenshot).
The Schedule Report button is available only to users with at least the Insert level of access rights to the Email Templates (SM204003) form.
Figure: New Schedule Report button
When the user clicks Schedule Report, the system opens the Email Templates (SM204003) form in a new tab. By default, the system fills in the settings for the new email template as follows:
• In the Summary area, To, CC, BCC, and Subject are filled in with the values specified for the report in the Email Settings section of the Print and Email Settings tab of the report form. The Activity Type is set to Email.
• On the Attached Reports tab, Report ID is filled in with the report identifier, and Report Format is set to the format specified on the Print and Email Settings tab of the report form. Also, the report parameters are copied from the Report Parameters tab of the report form. If at the moment of report creation, a shared report template was selected in the Template box of the report form, its name will be inserted to the Report Template box.
When the user saves the email template, the Send by Schedules tab becomes available for the email template.
The following screenshot shows an email template that was created based on the shared report template of the
Daily Sales Profitability (AR676000) report.
Figure: An email template created for a report
On the Send by Schedules tab of the form, the user can create and remove linked schedules or link the existing schedules to the email template. Also, they can review the history of a selected schedule. To schedule the email template, the user clicks Create Schedule on the table toolbar of the tab. The system opens the Automation Schedules (SM205020) form in a pop-up window, as shown in the following screenshot.
Figure: Automation Schedules form opened for an email template
The user specifies the settings of the schedule, saves their changes, and closes the pop-up window. The system displays the configured schedule in the table of the Send by Schedules tab of the Email Templates form. For details on configuring automation schedules, see Scheduling Automated Processing.
To view the history of the schedule execution, a user clicks View Schedule History on the tab. The system displays the details in the pop-up window, as shown in the following screenshot.
Figure: The history of schedule executions
Other Changes to the Email Templates Form
The implementation of this new functionality involved other changes to the Email Templates (SM204003) form. The most significant change is that the Screen box is now optional. Depending on whether the Screen box is filled in and the objects are linked to the template, the system hides certain UI elements or displays a warning for an element.
If Screen is empty and there are no linked business events, the system hides the following UI elements:
• The Attach Activity, Link-To Entity, Link-To Contact, and Link-To Account boxes in the Summary area
• The Attach Report Opened by Action box and the Use Event as Data Source check box on the Attached Reports tab
• The Send by Events tab
If Screen is empty and there is at least one linked business event, the system does the following:
• Hides the Attach Activity, Link-To Entity, Link-To Contact, and Link-To Account boxes in the Summary area
• Hides the Attach Report Opened by Action box and the Use Event as Data Source check box on the
Attached Reports tab
• Displays a warning about the empty Screen box on the Send by Events tab and the linked business event If Screen is specified and there are no linked schedules, the system does the following:
• Displays the Attach Activity box only if a data entry form is specified in the Screen box
• Displays the Link-To Entity box only if a generic inquiry is specified in the Screen box
• Hides the Send by Schedules tab
If Screen is specified and there is at least one linked schedule, the system does the following:
• Displays the Attach Activity box only if a data entry form is specified in the Screen box
• Displays the Link-To Entity box only if a generic inquiry is specified in the Screen box
• Displays a warning on the Send by Schedules tab and the linked schedule about the inability to retrieve values for screen data fields if they are used as placeholders
The absence of a value in the Screen box also affects the availability of data for placeholders used in an email template. If Screen is empty, only the General Info node is available in the lookup box's Screen Fields tab for the To box in the Summary area. Similarly, only the General Info node is available in the lookup box for adding data fields in the text editor on the Message tab.
Changes to the Automation Schedules Form
On the Automation Schedules (SM205020) form, the new Action drop-down box has been added with the following options:
• Mass-Process: This new option is selected by default when a user creates a schedule from a processing form or directly on the Automation Schedules form.
• Raise Business Event: This option has been moved from the Action Name drop-down box and is inserted by default when a user initiates schedule creation on the Business Events (SM302050) form.
• Send Email Notification: This new option is inserted by default when a user initiates schedule creation on the
Email Templates (SM204003) form.
The Action Name control has been changed from a drop-down box to a lookup box and made optional. It is available only if the Mass-Process option is selected in the Action drop-down box. The corresponding mass operation is inserted automatically based on the processing form specified in the Screen ID box.
The availability of the Screen ID box and the list of forms available for selection depend on the option selected in the Action drop-down box. The following table summarizes the limitations.
Option Availability Forms Available for Selection
Mass-Process Available and required Mass-processing forms only
Raise Business Event Available and required Inquiry forms only
Send Email Notification Hidden and optional Not applicable
Also, the new Email Notifications tab has been added to the Automation Schedules form. The tab is displayed if the
Send Email Notification option is selected in the Action drop-down box.
Changes to the Automation Schedule Statuses Form
The following changes have been made to the table that displays the list of schedules on the Automation Schedule Statuses (SM205030) form:
• The Screen ID column is now optional, and its values are no longer links that users can click to navigate to the specified forms.
• When a record with an empty value in the Screen ID column is selected, the system hides the View Screen
• The Description column has been removed.
• The Schedule ID column has been added; its values are clickable links. When a user clicks a link, the system opens the Automation Schedules form with the selected schedule.
Changes to the Automation Schedule History Form
In the Selection area of the Automation Schedule History (SM205035) form, the Screen box has been removed. The following changes have been made to the table that displays the list of schedules on the form:
• The values in the Screen ID column are no longer links that users can click to navigate to the specified forms.
• The Schedule column has been renamed to Schedule ID.
Upgrade Notes
Aer an upgrade to Acumatica ERP 2025 R1, the following change will be applied in the system: For each automation schedule, the upgrade script will insert a value in the new Action box. If the option in the Action Name box was Raise Business Event, it will be le as it is. Otherwise, Mass-Process will be inserted in the Action box.
Aer the upgrade, a system administrator will need to migrate automation schedules that have been configured by using the Send Reports (SM205060) form. To locate the required schedules, the administrator can use the Automation Schedule Statuses (SM205030) form to filter schedules with SM.20.50.60 in the Screen ID column. The system will also display a warning for these records. The administrator may click a link in the Schedule ID column to open the Automation Schedules (SM205020) form for the schedule.
On the Automation Schedules form, for these schedules, the Migrate button has been added to the form toolbar to assist with the migration. Also, the system will display a warning about the deprecation of the Send Reports form and migration instructions; see the following screenshot.
Figure: The Migrate button and warning with migration instructions
The migration process will create an email template for each report template in the schedule and link it to a new schedule. The original schedule will be deactivated and marked as migrated to avoid duplication.
Customization: Access Rights for Custom Forms
Acumatica ERP 2025 R1 introduces improved management of access rights for custom forms.
In the Customization Project Editor, screen is used in UI labels to describe the Acumatica ERP form being developed.
Addition of Access Rights
In Acumatica ERP 2024 R1, if a developer created a form and did not add access rights for this form to the customization project, the system assigned the Revoked access rights to the form for all user roles. As a result, the developer could not open the form aer the customization project was published.
In Acumatica ERP 2025 R1, the system adds to the customization project the Delete access rights for the Customizer role for each new form. The developer can now test new forms without specifying access rights explicitly. Aer the developer has tested the changes, a system administrator can add the needed access rights to the customization project.
Changes to the Customization Project Editor
When a developer creates a new form, the system displays a message that access rights will be added to the customization project. The the following screenshot shows the Create Screen dialog box with this message. (This dialog box opens when the developer clicks Create Screen on the page toolbar of the Customized Screens page.)
Figure: Message about the addition of access rights
Aer the developer clicks Create in the dialog box, the system adds the needed elements to the respective pages, as it did in previous versions. The following screenshot shows the Access Rights page with the added access rights (see Item 1). Notice that the Apply and Keep merge rule has been selected for these access rights (Item 2). This option indicates that the system will apply the access rights from the customization project to the form and keep them unchanged for the roles that are not included in the customization project.
Figure: The Access Rights page with the added access rights
Developer Documentation: New Topics
In the documentation for Acumatica ERP 2025 R1, a developer can find a number of new and reworked topics, as described in the following sections.
Modern UI Components
The UI Component Guide has been extended with chapters about each of the following Modern UI components:
• Currency
• Icon
• Mask Editor
• Upload Dialog Box
• Upload Files Button
• Wizard
Universal Search
An application developer can find detailed information about the customization of Acumatica ERP’s universal search for data access classes in the following new chapter: Customizing the Acumatica ERP Search.
New REST API Examples
An integration developer can find the following new REST API examples:
• Create a Return for Credit for Items with Lot or Serial Numbers
• Update Allocations in a Return for Credit
Mobile Development: Dialog Result for the Close Button
In Acumatica ERP 2025 R1, a developer can specify a dialog result for the Close action (which corresponds to the X button on a screen toolbar) of a dialog box mapped to the mobile app in one of the following ways:
• Specify the dialog result in the CloseButtonDialogResult property of the dialog object
• Define the Close action in detail by using the CloseButtonDialogAction property of the dialog
object
A developer can use only one of the approaches for each action.
Specifying the Dialog Result for the Close Action
To specify the dialog result for the Close action, a developer needs to specify it in the CloseButtonDialogResult property of the dialog object. The possible values of the property correspond to the elements of the WebDialogResult enumeration. The following code shows an example of the dialog result value being specified for the Close action.
Defining the Close Action
A developer can define the Close action by doing the following:
1. In the dialog object, define an action by adding the dialogAction object.
2. In the dialogAction object, specify the dialog result in the dialogResult property. For more details, see dialogAction.
In the dialogAction object, there is no need to specify the CloseDialog property because the button closes the screen by default.
3. In the dialog object, specify the name of the action in the CloseButtonDialogAction property. The following code shows an example of the Close action being defined in a dialog box.
• dialog
• dialogAction
• Enum WebDialogResult
• Mapping a Smart Panel
Mobile Development: Displaying the Progress and Results of Processing
The Acumatica mobile app connected to an instance of Acumatica ERP 2025 R1 can display the progress and the results of a processing operation.
When the processing is being performed, the app shows a dialog box with the progress of the operation. For processing screens, the dialog box may contain progress numbers, such as the elapsed time, the estimated remaining time, and the percent of completion. The following screenshots show examples of the dialog boxes that show the progress of the operation.
Figure: Processing dialog boxes
Aer the processing is completed, the app shows the results of the processing for each record included in the processing. The results of the processing are displayed on the Processing screen and are grouped by the following tabs: Failed, Remaining, Total. An example of the Processing screen is shown in the following screenshot.
Figure: Results of the processing
This functionality is available out of the box, and no changes need to be made to the mapping of the screen.
Changes to the Mobile API
The SyncLongOperation property has been deprecated for the following objects:
• recordAction
• containerAction
• listAction
• selectionAction
The SyncLongOperation property will be removed in the next major release.
Platform API: Improved Logging in Connectors for External Systems
Acumatica ERP 2025 R1 introduces improved logging of events for the connectors for external systems. Now the system logs requests and events related to the connector on the Request Profiler (SM205070) form if a user specifies the following settings on this form:
• Log Requests (Apply Filter): Selected
• Log Events (Apply Filter): Selected
• Log Level: Verbose
• Category: Commerce
For the implementation of this improvement, multiple API changes have been made. A developer needs to update their implementation of the connector as described in the following sections. For more information about the implementation of a custom connector, see Implementing a Connector for an External System.
Changes to the BCConnectorBase Class
The PX.Commerce.Core.BCConnectorBase<TGraph> abstract class now implements the PX.Commerce.Core.IConnector interface. Therefore, the BCConnectorBase<TGraph> abstract class now includes the following abstract methods:
• Process(ConnectorOperation operation, int?[] syncIDs = null, CancellationToken cancellationToken = default)
• GetSyncTime(ConnectorOperation operation)
• ProcessHook(IEnumerable<BCExternQueueMessage> messages, CancellationToken cancellationToken = default)
A developer must override these methods in their implementation of a connector for an external system. Also, there is no need to derive the connector class from the IConnector interface.
Changes to the IProcessor and IConnector Interfaces
All logging methods of the PX.Commerce.Core.IProcessor and PX.Commerce.Core.IConnector
interfaces have been removed.
A developer must remove their previous implementation of these methods. Instead, the developer can use the methods that are provided in the PX.Commerce.Core.Logging.CommerceLoggerExtensions class. These methods extend the functionality of the Serilog.ILogger interface.
The following code shows an example of writing a log message. The example uses the PX.Commerce.Core.BCProcessorBase<TGraph, TEntityBucket, TPrimaryMapped>.Logger class, which uses the ILogger methods.
Platform API: Processing of API Rate Limits in a Connector for an External System
In Acumatica ERP 2025 R1, the built-in connectors for external systems (such as the BigCommerce, Amazon, and Shopify connectors) process responses with the 429 Too Many Requests response code differently. Previously, if the API rate limit of the external system was reached—that is, the 429 Too Many Requests response code was received— the built-in connector ignored this error and retried the request without a delay. This request failed in most cases. Now if the 429 Too Many Requests response code is received, the connector checks the headers of the response to find the recommended delay for the request, and retries the request aer this delay.
If a developer implemented a custom connector by using the Acumatica Commerce Framework, the developer can update this connector to use the same approach for handling the 429 Too Many Requests response
code. To use this approach, the developer needs to derive the REST API client implementation from the PX.Commerce.Core.REST.RetryCapableRESTClientBase abstract class and override its methods. The RetryCapableRESTClientBase class uses the Polly.Core.dll library.
The following code shows a sample fragment of the REST API client implementation for the BigCommerce connector.
For more information about the implementation of a custom connector, see Implementing a Connector for an External System.
Platform API: Changes to the Image Processor Modules of the Shopify and BigCommerce Connectors
In previous versions of Acumatica ERP, the image processor modules of the Shopify and BigCommerce connectors retrieved the image details for the Product Image entity by using the BC-ItemImages generic inquiry. In some cases, this implementation led to a timeout error on the Sync History (BC301000) and Prepare Data (BC501000) forms.
In Acumatica ERP 2025 R1, this behavior has been modified. Now the image processor modules of the Shopify and BigCommerce connectors retrieve the image details for the Product Image entity by using a BQL query. As a result, the BC-ItemImages generic inquiry has been removed from the code base.
Updating Customizations That Depend on the BC-ItemImages Generic Inquiry
Because the BC-ItemImages generic inquiry has been removed from the code base, developers must update their customization projects if they previously customized the BC-ItemImages generic inquiry. To customize the BQL query that now replaces the BC-ItemImages generic inquiry, a developer must implement the PX.Commerce.Objects.IImageDataProvider interface and all of its methods.
The IImageDataProvider interface consists of the following methods:
• FetchCommand PrepareCommand(List<BCSyncStatus> ids, TGraph processorGraph): This method specifies a base BQL query to fetch the image details for the Product Image entity. Developers can specify additional conditions for this BQL query in the following SelectByIds and Select methods.
• IEnuemrable<ItemImageDetails> SelectByIds(List<BCSyncStatus> ids, TGraph processorGraph): This method, which specifies a list of sync IDs, is called during the syncing process on the Sync History (BC301000) and Process Data (BC501500) forms. This method fetches the image details for the Product Image entity by calling the PrepareCommand method.
• IEnuemrable<ItemImageDetails> Select(TGraph processorGraph): This method does not specify any sync IDs and is called from the Prepare Data (BC501000) form. The method fetches the image details for the Product Image entity by calling the PrepareCommand method.
A developer can specify a custom BQL query that fetches the image details for the Product Image entity in their implementation of the FetchCommand PrepareCommand(List<BCSyncStatus> ids, TGraph processorGraph) method. The following code shows an example.
Platform API: Changes to the Methods of the ARPaymentEntry Graph
In previous versions of Acumatica ERP, when a developer wanted to customize the PX.Objects.AR.ARPaymentEntry graph by modifying the behavior of its methods, the developer had to copy a large amount of code from the original graph. This process was necessary even for implementing simple customizations, such as implementing a filter to include only the documents that have a particular status. The following methods belong to the ARPaymentEntry graph, whose behavior was difficult to modify:
• public static int GetCustDocsCount(LoadOptions opts, ARPayment currentARPayment, ARSetup currentARSetup,PXGraph currentGraph)
• public static PXResultset<ARInvoice> GetCustDocs(LoadOptions opts, ARPayment currentARPayment, ARSetup currentARSetup, PXGraph currentGraph)
Since these methods were declared as public static, it was not possible to override them. In Acumatica ERP 2025 R1, these methods have been moved to the new PX.Objects.AR.CustomerDocsExtensionBase abstract graph extension and their method signatures have been modified as follows:
• public virtual int GetCustDocsCount(LoadOptions opts, ARPayment currentARPayment, ARSetup currentARSetup)
• public virtual PXResultset<ARInvoice> GetCustDocs(LoadOptions opts, ARPayment currentARPayment, ARSetup currentARSetup)
Because the methods above are now declared as public virtual and have been moved to an abstract graph extension, a developer can simply override these methods to modify their behavior. For details about the code changes in this release, see the Reference List of Changes.
Overriding the GetCustDocsCount and GetCustDocs Methods
To override the GetCustDocsCount and GetCustDocs methods, the developer must declare a second-level graph extension that is derived from the ARPaymentEntryCustomerDocsExtension graph extension, as shown in the following code example.
The ARPaymentEntryCustomerDocsExtension graph extension in the code example above is derived from the new CustomerDocsExtensionBase abstract graph extension, which was mentioned in the preceding section.
Web Services: New PATCH Method in the REST API
In previous versions of Acumatica ERP, to update a record by using the REST API, a developer had to use the PUT HTTP method. In Acumatica ERP 2025 R1, the developer can use the new PATCH method to update only particular fields of an existing record.
Behavior of the PUT and PATCH Methods
The PUT method updates the fields as follows:
1. To find the fields to update, the system compares the values specified in the request body with the field values for the record in the system.
2. The system skips the values in the request body that are equal to the field values in the system.
3. The system updates only the fields for which the value specified in the request body differs from the value stored in the system.
However, during this update, other fields of the record may be changed because of the logic implemented in the respective graph. Meanwhile, the request body may include values specified for the fields that have been updated because of the graph logic. In this case, the system does not save the values specified in the request body.
The PATCH method updates exactly the fields specified in the request body, regardless of the values for these fields that are stored in the system. However, the PATCH method does not override the graph logic. For example, if because of the graph logic, the value cannot be changed as the request body specifies, this value will not be changed.
Use of the PATCH Method
A developer may consider using the PATCH method during the synchronization of records from an external system when the developer knows exactly which fields have been changed in the external system. The developer may also use this method in situations when particular fields of a record cannot be updated with a PUT request (as described in the previous section).
In a request with the PATCH method, the developer needs to identify the record and specify only the fields that should be updated. The developer can identify the record by key fields, by ID, or by filtering conditions. For details about the PATCH method, see Update Particular Fields of a Record.
Example
Suppose that the developer needs to update the order quantity and discount amount in a detail line of the 000029
sales order. The developer can use the following request.
Web Services: Tracking of Deleted Records Through OData
The optimal way to synchronize data between Acumatica ERP and an external system is to synchronize only the data that was modified since the previous synchronization. To track the modification date, a developer can use the values in the LastModifiedDateTime field of a record. However, this type of synchronization does not take into account records that were deleted since the last synchronization. Therefore, to synchronize deleted records, the developer should do one of the following:
• Perform the synchronization of all records (which may cause performance issues)
• Use push notifications (which requires additional development)
Acumatica ERP 2025 R1 introduces a new mechanism that can be used to retrieve the list of records of a particular type that were deleted since the last synchronization. The developer can retrieve this list through DAC-based OData.
Configuring the Tracking of Deleted Records
On the new Tables to Track Deleted Records (SM207010) form, a developer adds the data access classes (DACs) for which the system should track deleted records. By default, the system does not track deleted records for a DAC. If a record of a DAC listed on the form is removed, the system saves the NoteID of the record and the date and time of the removal.
The developer can also configure how long the information about deleted records is stored. By default, the information about a deleted record is stored for 10 days.
The new form is shown in the following screenshot.
Figure: The new form
Obtaining the List of Deleted Records
To obtain the list of deleted records of a particular DAC, the developer can use the following OData request.
The developer can also filter the records by the date of removal by using the DeleteDate field in the $filter
parameter.
For example, suppose that the developer needs to retrieve the list of sales orders that have been removed since November 1, 2024, from the U100 tenant of the local Acumatica ERP instance. Further suppose that the SOOrder DAC has been added to the list on the Tables to Track Deleted Records (SM207010) form. The developer can execute the following request to obtain the list of deleted records.
A user can obtain the list of deleted records of a DAC by using this request if the user has access to this DAC through DAC-based OData.
Including the Tracking of Deleted Records in a Customization Project
The developer can include in a customization project the list of DACs for which the system tracks the deleted records. To include this list in a customization project, the developer uses the Tables to Track Deleted Records page of the Customization Project Editor, which is shown in the following screenshot. Any of the DACs that are listed on the Tables to Track Deleted Records (SM207010) form can be included in the customization project.
Figure: The new page
Web Services: New Manufacturing Endpoint
Acumatica ERP 2025 R1 provides the new MANUFACTURING/25.100.001 endpoint. A developer can review this endpoint and obtain its OpenAPI specification on the Web Service Endpoints (SM207060) form, which is shown in the following screenshot.
Figure: The new endpoint
The endpoint includes the new ProductionOrderDatesProcess entity. The developer can use this entity to update dates in released production orders and operations in a single request. (If the developer uses the ProductionOrder entity to update dates, they need to perform three API requests to update the dates in one production order.)
By using the new endpoint, the developer can also obtain the scheduling details of production orders through the following new fields:
• ProductionOrderDetail.EndDate
• ProductionOrderDetail.SchedulingMethod
• ProductionOrderDetail.StartDate
• OrderOperationDetail.EndDate
• OrderOperationDetail.StartDate
Workflow UI: Viewing of Workflow Changes
In previous versions of Acumatica ERP, a customizer had to open the Workflows page of the Customization Project editor for each customization project to learn whether a workflow for a particular form has been modified or whether a custom workflow has been created for this form.
In Acumatica ERP 2025 R1, a customizer can view the list of forms with modified workflows for all published customization projects, without the need to open the Customization Project Editor and investigate each customized screen. Also, from any form, a customizer can determine whether it has workflow modifications.
Forms with Workflow Modifications
A customizer can now view all forms with modified workflows within Acumatica ERP. Suppose that a customizer plans to work with an Acumatica ERP instance and wants to know which forms have modified workflows. Further suppose that in the instance, three customization projects have been published, each affecting one form. These customization projects have modified the respective forms as follows.
Form Modification
Task (CR306020)
A custom workflow has been created. (In an out-of-the-box system, this form does not have any workflow.)
Opportunities (CR304000)
An inherited workflow has been modified.
Cases (CR306000)
The form’s layout has been customized. (The changes do not affect the form's workflow.)
On the Customization Projects (SM204505) form of Acumatica ERP, the customizer can learn which forms have modified workflows. To do this, the customizer clicks the new Screens with Custom Workflow command on the More menu (under the new Customization Info category), as shown in the following screenshot.
Figure: The new Screens with Custom Workflow command
This opens the Screens with Custom Workflow dialog box, which lists the forms whose workflows have been modified, as shown in the following screenshot. Notice that the dialog box contains only two forms: Task and Opportunities.
Figure: The Screens with Custom Workflow dialog box
While working with a particular form, the customizer can see if any changes have been made to its workflow by clicking Tools on the form title bar. If the workflow has been customized, the system displays the Flow icon to the le of the screen ID, as shown in the following screenshot.
Figure: The Flow icon for the modified workflow
Other Change to the Customization Projects Form
On the Customization Projects (SM204505) form, the Unpublish All button on the form toolbar (and the corresponding command on the More menu) is now always available, regardless of whether any customization projects have been published.
Fixes and Enhancements
You can find fixes and minor enhancements introduced in Acumatica ERP 2025 R1 in the following document:
Acumatica ERP 2025 R1 Release Notes: Fixes and Enhancements.