ACH Return Generator File Layout (Version 2)

🚧

IMPORTANT: Version 1 of the Return Generator file should continue to be utilized until Version 2 is moved to production. Please see additional information below.

On January 31st, 2024, Evolve released v3.3 of the ACH Trace file and v2 of the ACH Return Generator file on the Evolve Enterprise Plus documentation site. This release included breaking changes to both files.

We have offered a 30 day window to adhere to the file layouts. On Saturday, March 2nd, 2024, Evolve will deprecate previous versions of Trace and Return Generator files (including Return Generator v1).

If continuing to use the Return Generator file through 3/2/2024, please utilize the version 1 layout outlined here: ACH Return Generator File Layout (Version 1)

Overview

Platforms can submit the Return Generator file to Evolve to return a received ACH transaction. Once submitted, Evolve will generate a NACHA formatted ACH return file on behalf of the Platform and send the return to the Federal Reserve ACH Network.

The Platform should use the data from the vAccount ACH Receiving File and a valid return reason to submit this file. This file needs to be submitted to Evolve within 24 hours of the Platform receiving the ACH being returned. Evolve will email the Platform the details of any submitted records that could not be used to generate an ACH return file.

File Name

ReturnGen_v2_yyyyMMddHHmmss.achreturns

• ReturnGen indicates the file type
• v2 indicates the version
• yyyyMMddHHmmss is the date/time stamp for when the file was sent

File Direction

This file is sent to Evolve from the Platform.

Format Options

This file type is sent to Evolve in JSON format.

Delivery Window

This file can be delivered to Evolve at any time throughout the week (Monday-Sunday). However, this file needs to be submitted to Evolve within 24 hours of the Platform receiving the ACH being returned. Evolve processes and generates ACH returns upon receipt of this file.

Example:

If a client receives an incoming ACH on Monday that they wish to return, they will need to submit a Return Gen file containing that record by Tuesday at 8pm CST to ensure that the other Financial Institution honors the return.

File Size

This file should contain no more than 2,500 records. If there are more than 2,500 records, the Platform should submit multiple files.

File Options

ACH Return Generator JSON Sample Data

{
    "returns": [
        {
            "ODFI_trace": "242071758896195",
            "effective_date": "2020-05-12",
            "ach_company_name": "COMENITY PAY OT",
            "amount": 105,
            "return_reason": "R01",
            "client_trace": "123456789999999",
            "CoreFileKey": "1305630172514803196946222",
            "CoreBatch": 12.0,
            "CoreSeq": 1.0
        },
        {
            "ODFI_trace": "021000025622593",
            "effective_date": "2020-05-12",
            "ach_company_name": "CITY PUBLIC SRV",
            "amount": 364.61,
            "return_reason": "R01",
            "client_trace": "123456789999999",
            "CoreFileKey": "1305630172514803196946222",
            "CoreBatch": 12.0,
            "CoreSeq": 2.0
        },
        {
            "ODFI_trace": "061036010000339",
            "effective_date": "2020-05-12",
            "ach_company_name": "IRS",
            "amount": 5,
            "return_reason": "R03",
            "CoreFileKey": "8141411394634194906376641",
            "CoreBatch": 56.0,
            "CoreSeq": 1.0
        },
        {
            "ODFI_trace": "021214899147540",
            "effective_date": "2020-05-11",
            "ach_company_name": "tapx_trading_and",
            "amount": 0.56,
            "return_reason": "R01",
            "client_trace": "123456789999999",
            "CoreFileKey": "9379203039964376985965724",
            "CoreBatch": 78.0,
            "CoreSeq": 1.0
        }
    ]
}

ACH Return Generator File Table

NACHA Return Codes & Change Codes

Release Notes

Release v2 - 2024.02

1. Added "v2 - 2024.02" to "Description" subtext field at top of page.
2. Syntax updates to Purpose section.
3. Syntax update to Format Options section.
4. Syntax and punctuation updates to Delivery Window section and "Example,"
5. Updated File Options section with new JSON sample data to reflect new fields and existing field name changes.
6. Changed Trace field to ODFI_trace.
7. Added NACHA Return Codes & Change Codes link to return_reason field description.
8. Added new fields and related descriptions for each:
   1. client_trace
   2. CoreFileKey
   3. CoreBatch
   4. CoreSeq
9. Added "Release Notes" section.