FedACH® Platform Modernization Resource Center
The Federal Reserve Banks completed the implementation of the modernized platform used to support ACH processing services on January 29, 2021.
This resource center presents information about the technology modernization and the impact on FedACH Services.
- List of Customer-Facing Changes
- View FedACH platform modernization updates
- The modernized FedACH platform will be implemented on January 29, 2021 (December 22, 2020)
- Freeze period for production FedACH Services (November 23, 2020)
- FedACH platform modernization testing update (June 1, 2020)
- FedACH Platform Modernization update (December 12, 2019)
- Announcing FedACH Platform Modernization to begin in late 2019 (Sept. 25, 2018)
- Sample ACH Acknowledgment Files (FAHK)
Frequently Asked Questions (FAQs)
Updated as of February 2, 2021
The Federal Reserve Banks are committed to providing the answers and information you need during our Automated Clearing House (ACH) modernization effort. The answers to many of our customers' most frequently asked questions can be found using the links below.
If your question is not answered by the information provided on the site, please check back periodically as we will continue to update this page throughout the modernization effort. Also, the Contact page provides a comprehensive list of service and support contacts that can assist you.
- What is the FedACH Platform Modernization Project?
The Federal Reserve Banks are modernizing the platform we use to support ACH processing services by making a strategic investment in newer technology to ensure the continuing efficiency and business value of FedACH Services.
- Why is the Federal Reserve modernizing their FedACH platform?
As the payments landscape continues to evolve toward faster and more secure processing, it is essential for us to take steps now to modernize our FedACH processing platform. We have designed a more distributed processing infrastructure that will allow more flexibility and scalability.
- When will the transition to this new platform take place?
The modernized platform was implemented on January 29, 2021.
- Will a freeze period be implemented during the project?
The freeze period is running through February 12, 2021.
- Whom do I contact if I have questions related to the project?
FedACH and Check Services Customer Support are available to assist with any questions related to this project.
Additional Information on the Company Identification Field and Company Batch Header Field information:
Issue: The originator included inconsistent or no information in the Company Identification Field in the Company Batch Control Record (#8 Record) and it does not match the Company Identification Field in the Company Batch Header Record (#5 Record).
The Nacha Operating Rules (Off-site) identify the Company Identification (Field position 45-54) in the Company Batch Control Record as a Required Field; this Field carries the same information as the Mandatory Company Identification Field(Field positions 41-50) of the Company Batch Header Record.
What action is required?
The originator should ensure the Company Identification Field carries the same information in the Company Batch Header Record and Company Batch Control Record to prevent potential processing delays and/or returns from the RDFI due to their inability to process the item(s).
Why wasn’t this a problem in the past?
The previous FedACH platform copied the data in the Company Identification Field of the Batch Header Record to the Company Identification Field in the Batch Control Record to synchronize the two Fields. The new FedACH platform does not perform this copy step to synchronize the two Fields.
The Federal Reserve as an ACH operator performs compliance edits on Mandatory Fields, but is not required to perform them on Required Fields.
A Mandatory Field not meeting the NACHA data specifications will cause the ACH Operator to pend or reject files, batches, or entries. A file or, batch placed in a pending status by the ACH Operator will await action to be released or rejected based on instructions provided by the Sending Point.
The omission of a Required Field will not cause a file, batch, or entry to reject at the ACH Operator, but may cause a reject at the RDFI and may result in the return of the entry or entries.