|Category||Current Platform||Modernized Platform|
|Company ID Field
|The Company ID Field in a batch header is copied into the Company ID Field in the batch control Record, ensuring the Fields are identical.||The Company ID Field in the batch control Record is not altered, which means it may not match the same Field in the batch header.
Institutions receiving ACH files must be able to accept batches in which the Company ID Field in the batch control Record does not match the batch header.
|File ID modifiers
|Output files are generally delivered to customers with sequential file ID modifiers throughout the business day.||Output files are delivered to customers with file ID modifiers assigned at the time the first item in the file was available for delivery.
Customers may notice the file ID modifiers of files received throughout the business day are not in order, especially if they request manual On Demand deliveries. Also, an AJ19 Same Day Return file may have a higher file ID modifier than a file received later in the day.
|Output file names
|An output file created at the same time as another output file for the same customer (for example, because there are too many items for just one file) will have five digits appended to its name, showing the creation time in milliseconds.||All output files have five digits appended to their names, showing the creation time in milliseconds.
Customers must be able to accept file names in this longer format.
|Originated Files||When a file is initially received by the Federal Reserve Bank for processing, customers typically see a status of FLD-Sent, FLC-Sent or Approved in FedLine Information Services until processing is complete.||Customers may see an interim status of FLD-Sent, FLC-Sent, Approved or "In Progress" in FedLine Information Services until file processing is complete.|
|Pended Files||When a file is initially received by the Federal Reserve Banks for processing, there are 5 duplicate detection criteria applied:
||The new platform is being enhanced to include two additional duplicate detection criteria and remove one detection. These two additions are expected to significantly reduce “false” duplicate detection of files.
|Acknowledgements||When a file pends and is manually released, FedACH generates three acknowledgements:
||When a file pends and is manually released, FedACH generates only two acknowledgements:
|Acknowledgements||When a batch or file is rejected at end of day (EOD), the acknowledgement shows the status message “rejected at EOD” only.||The EOD reject acknowledgement has been enhanced to contain the original error(s) that caused the file to pend and will no longer show the status message “rejected at EOD”.|
|Acknowledgements||When a file pends due to multiple errors, only the first error is captured in FedLine® Information Services and on acknowledgements.
Multiple errors are not currently displayed.
|When a file pends, only the first error will continue to be captured in FedLine Information Services. The acknowledgement has been enhanced to display multiple errors.|
|Acknowledgements||Current acknowledgements contain 60 lines per page.||New acknowledgements will contain 52 lines per page.
If your institution is “processing” the ‘FAHK’ acknowledgements or data mining the data in the file to create printer friendly reports, etc. you will need to make adjustments accordingly. Additionally, if your institution has an automated process that is hard coded for 60 lines, your institution will need to make adjustments in advance of the migration.
Sample FAHK files can be found in the FedACH Platform Modernization Resource Center
|Extensions||When extensions are activated, all files are held while files bearing the sending point routing transit number (RTN) that extended are manually released into the desired business day.
This allows the institution requesting the extension to amend or confirm the RTN in need of an extension after the extension begins.
|When extensions are activated, all incoming files will no longer be held up. Files will immediately and automatically flow into the next business day for processing unless they bear the sending point RTN supplied by the customer requesting the extension. Customers MUST supply the correct and specific sending point RTN for the file(s) requiring the extension. If not provided, the file(s) requiring the extension will not be held for processing on the current business day, but will automatically flow to process on the next business day.|
|File delivery||Customers are able to request on-demand files through FedLine Information Services. Currently these files display as “On-Demand” in FedLine.||Customers will no longer have access to request on-demand files through FedLine Information Services.
The new platform has been enhanced, allowing customers the ability to schedule (via ACH agreement) additional recurring daily file deliveries based on processing needs.
On-Demand files can still be requested by contacting FedACH and Check Services Customer Support.
All files will display as a status of “Ready” in FedLine. “On-Demand” status will no longer be displayed.
|Test Environment||All incoming and outgoing test files are processed in the current platform.||Beginning August 2020, all incoming and outgoing test files will be processed in the new modernized platform.|