ACH Return Generator File Layout (Version 1)

🚧
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 you would like to review version 2 of the Return Generator file effective 3/2/2024 in order to prepare for the upcoming version changeover, please visit ACH Return Generator File Layout (Version 2).

Overview

Platforms can submit this file to Evolve to return a received ACH. 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 their 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_v1_yyyyMMddHHmmss.achreturns

ReturnGen_v1indicates the file type and version.
yyyyMMddHHmmssis the timestamp for when the file is sent.

Note: File name is limited to 40 characters.

File Direction

This file is sent to Evolve from the Platform.

Format Options

This file type is available 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, that they wish to return, on Monday. They need to submit a Return Gen file with that record in it 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": [
        {
            "trace": "242071758896195",
            "effective_date": "2020-05-12",
            "ach_company_name": "COMENITY PAY OT",
            "amount": 105,
            "return_reason": "R01"
        },
        {
            "trace": "021000025622593",
            "effective_date": "2020-05-12",
            "ach_company_name": "CITY PUBLIC SRV",
            "amount": 364.61,
            "return_reason": "R01"
        },
        {
            "trace": "061036010000339",
            "effective_date": "2020-05-12",
            "ach_company_name": "IRS",
            "amount": 5,
            "return_reason": "R03"
        },
        {
            "trace": "021214899147540",
            "effective_date": "2020-05-11",
            "ach_company_name": "tapx_trading_and",
            "amount": 0.56,
            "return_reason": "R01"
        }
    ]
}

ACH Return Generator File Table

Field Name	Data Type	Data Validation	Description
trace	string	required	15 character trace number. Insert leading zeros if necessary. See Trace in the ACH Receiving File Layout.
effective_date	string	required	The effective date of the received ACH (yyyy-MM-dd). See EffectiveDate in the ACH Receiving File Layout.
ach_company_name	string	required	The name of the company that originated the received ACH. See PostingData in the ACH Receiving File Layout.
amount	decimal	required	The unsigned amount of the received ACH. See Amount in the ACH Receiving File Layout.
return_reason	string	required	Represent the reason for returning the received ACH with a NACHA return code. See NACHA Return Codes table.

NACHA Return Codes & Change Codes

Field Name	Description
C01	Incorrect bank account number
C02	Incorrect routing number
C03	Incorrect routing and account number
C05	Incorrect Payment Code
R01	Insufficient Funds
R02	Account Closed
R03	No Account/Unable to Locate Account
R04	Invalid Account Number
R06	Returned per ODFI’s Request
R07	Authorization Revoked by Customer
R08	Stop Payment on Item
R09	Uncollected Funds
R10	Customer Advises Not Authorized
R11	Check Truncation Entry Return
R12	Branch Sold to Another DFI
R13	RDFI not qualified to participate
R14	Representative Payee Deceased
R15	Beneficiary or Account Holder Deceased
R16	Account Frozen
R17	File Record Edit Criteria
R20	Non-Transaction Account
R21	Invalid Company Identification
R22	Invalid Individual ID Number
R23	Credit Entry Refused by Receiver
R24	Duplicate Entry
R28	Check digit for routing number is incorrect
R29	Corporate Customer Advises Not Authorized
R31	Permissible Return Entry
R33	Return of XCK Entry
R34	Limited Participation D.F.I.
R35	Return of Improper Debit Entry
R36	Return of Improper Credit Entry
R37	Source Document Presented for Payment
R38	Stop Payment on Source Document
R39	Improper Source Document
R40	Non Participant in E.N.R. Program
R41	Invalid Transaction Code (E.N.R. only)
R42	Routing Number/Check Digit Error
R43	Invalid D.F.I. Account Number
R44	Invalid Individual I.D. Number
R45	Invalid Individual Name
R46	Invalid Representative Payee Indicator
R47	Duplicate Enrollment
R50	State Law Prohibits Truncated Checks
R51	NULL
R52	Stop Pay on Item
R53	Item and ACH Entry Presented for Payment
R61	Misrouted Return
R67	Duplicate Return
R68	Untimely Return
R69	Field Errors
R70	Permissible Return Entry Not Accepted
R71	Misrouted Dishonor Return
R72	Untimely Dishonored Return
R73	Timely Original Return
R74	Corrected Return
R75	Original Return not a Duplicate
R76	No Errors Found
R80	Cross-Border Payment Coding Error
R81	Non-Participant in Cross-Border Program
R82	Invalid Foreign Receiving D.F.I. Identification
R83	Foreign Receiving D.F.I. Unable to Settle
R84	Entry Not Processed by O.G.O.

🚧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.