NACHA’s 2026 ACH rule changes: What Dynamics GP customers need to know
NACHA’s updated ACH operating rules took effect in March 2026, and Dynamics GP customers across North America have been asking the same question: does this require a software update? Microsoft has now weighed in with an official answer — but even without a GP patch, there are steps customers should be taking before their bank comes calling.
Here is a clear breakdown of what changed, what it means for GP users, and where action may still be required.
What are the 2026 NACHA rule changes?
NACHA, the organization that governs the U.S. ACH payment network, introduced a significant update to its operating rules effective in 2026. The new rules require organizations that send or receive ACH payments to establish documented, risk-based ACH fraud monitoring programs to identify unauthorized payments and transactions initiated under false pretenses.
The rules also introduced new standardized transaction labeling requirements. For PPD credits used for payment of wages and salaries, the Company Entry Description field must contain “PAYROLL,” and e-commerce purchases must contain “PURCHASE.” These standardized descriptions are designed to improve fraud detection at the receiving bank level.
The rollout is happening in two phases based on transaction volume:
Phase 1 (effective March 20, 2026) applies to all ODFIs and each non-Consumer Originator, Third-Party Service Provider, and Third-Party Sender with annual ACH origination volume exceeding 6 million transactions in 2023.
Phase 2 (effective June 22, 2026) expansion broadens applicability beyond large-volume originators, meaning organizations of all sizes should review their ACH fraud monitoring procedures with their bank and compliance advisors
This phased approach is important context for GP customers evaluating their own compliance obligations.
Microsoft’s official position: No GP code changes expected
In a post on the Microsoft Dynamics GP Support and Services Blog, Microsoft employee Terry Heley addressed the community directly. Based on a review of the upcoming 2026 NACHA changes, the requirements continue to target high-volume ACH originators and remain outside the scope of typical small-business use cases. As a result, no Dynamics GP–specific code changes are expected.
This follows the same rationale Microsoft applied in 2023 when prior NACHA data security requirements went into effect. At that time, the volume thresholds referenced — organizations processing more than 6 million ACH transactions annually — fell well outside the typical small-business profile that Dynamics GP is designed to support, and no system changes were made.
That said, Phase 2 of the 2026 rules — effective June 2026 — removes the volume threshold entirely, meaning all ACH originators will be subject to fraud monitoring requirements regardless of size. GP customers who are active ACH originators should confirm their compliance posture accordingly, even if no GP patch is forthcoming.
What GP customers should still do
Microsoft’s position that no code changes are planned does not mean Dynamics GP customers are entirely off the hook. There are several practical steps that still require attention.
Review your company entry descriptions
The new NACHA labeling requirements for PAYROLL and PURCHASE transactions can be configured within Dynamics GP today without a software update. Microsoft’s blog post outlines exactly where to make these changes:
For Payroll Direct Deposit, navigate to Tools > Setup > Payroll > Direct Deposit > ACH Fields Setup to update the Company Entry Description field.
For Payables EFT, go to Cards > Financial > EFT File Format, and update Field 7 (Company Entry Description) in the Batch Header Line Type.
These are configuration changes, not system updates — and they are steps GP customers should complete now if they have not already done so.
Coordinate with your bank
Banks and financial institutions may also introduce additional ACH validation, formatting, or compliance expectations in response to NACHA’s 2026 rule changes.
While these updates may not necessarily require a Dynamics GP software patch, organizations should not assume their existing ACH processes will remain unaffected. Some banks may begin enforcing stricter validation around Company Entry Descriptions such as PAYROLL or PURCHASE, while others may request updated ACH transmission procedures, fraud monitoring documentation, or revised file handling standards.
Because implementation timelines and requirements can vary by financial institution, Dynamics GP customers should proactively communicate with their bank and engage their GP support partner early if any ACH formatting or compliance changes are requested.
The broader context: Dynamics GP’s end-of-life timeline
The NACHA situation is one of several 2026 compliance topics that Dynamics GP customers are navigating simultaneously. Microsoft has confirmed that Dynamics GP will reach end of life in 2029 under the Modern Lifecycle policy. Organizations still on GP should be weighing not just near-term compliance patches, but the longer-term migration question.
In addition to NACHA, GP users have had to manage multiple payroll tax table updates in 2026 across a wide range of states, as well as a Management Reporter Web Viewer issue introduced by a recent Microsoft Edge update that has disrupted financial reporting for some customers.
These issues are manageable — but they underscore the increasing maintenance burden associated with keeping a legacy on-premises ERP compliant and operational. For organizations evaluating their options, the Dynamics GP to Business Central migration path remains the primary route Microsoft and its partner ecosystem are recommending.
Next steps
The bottom line for Dynamics GP customers: NACHA’s 2026 rule changes do not require a GP software update for most users, and Microsoft has confirmed no code changes are planned. However, the absence of a system patch does not mean there is nothing to do.
For organizations still running Dynamics GP, this moment is also a timely reminder to evaluate the long-term roadmap. Microsoft’s end-of-life announcement for Dynamics GP makes the migration conversation increasingly urgent — and each annual compliance cycle on aging infrastructure is a cost that a modern cloud ERP like Business Central would largely eliminate. If your organization needs guidance on NACHA configuration, ACH compliance, or evaluating your migration options, working with an experienced Dynamics GP partner can help you navigate both near-term compliance requirements and long-term planning.
