ACH Returns & NOCs File (GS-adapted NACHA format)

The ACH Inbound Returns & NOCs File contains information of inbound and outbound Return items and Notification of Change (NOC) entries for ACH transactions originated by clients through GS Bank USA.

File Format Overview

The ACH Inbound Returns & NOC File follows a similar NACHA format (GS-adapted) as the ACH Transactions Origination File through which the transactions were originated. The file will contain Blocking File Control records as necessary, in order to ensure that total record count in the file is a multiple of 10. For example, if the file contains 26 records, there will be 4 Blocking File Control records to make the total count 30. Blocking Control records are filled with all 9’s.

Record Structure

File Header Record – type 1

The File Header Record follows the standard File Header Record format.

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘1’	1	1	1
2	PRIORITY CODE	Mandatory	Always ‘01’	2	2	3
3	IMMEDIATE DESTINATION	Mandatory	GS Bank routing number Always ‘b026015079’ (‘b’= space)	10	4	13
4	IMMEDIATE ORIGIN	Mandatory	File ID for this Return/NOC file, provided by GS Bank	10	14	23
5	FILE CREATION DATE	Mandatory	Date in ‘YYMMDD’	6	24	29
6	FILE CREATION TIME	Mandatory	Time in ‘HHMM’	4	30	33
7	FILE ID MODIFIER	Mandatory	Upper case A-Z Numeric 0-9 Will always be “0” representing the single Returns/NOC file sent at the end of each day.	1	34	34
8	RECORD SIZE	Mandatory	Always ‘094’	3	35	37
9	BLOCKING FACTOR	Mandatory	Always ‘10’	2	38	39
10	FORMAT CODE	Mandatory	Always ‘1’	1	40	40
11	IMMEDIATE DESTINATION NAME	Mandatory	Alphanumeric. Receiving client organization name.	23	41	63
12	IMMEDIATE ORIGIN NAME	Mandatory	Always “GS BANK USA”	23	64	86
13	REFERENCE CODE	Optional	Filled with blank or spaces	8	87	94

Company / Batch Header Record – type 5

The Company / Batch Header record for a Return or NOC entry largely retains field values corresponding to the original ACH transaction. These are shaded in grey below. The remaining fields are populated with codes or values pertinent to Return or NOC entries.

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘5’	1	1	1
2	SERVICE CLASS CODE	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	3	2	4
3	COMPANY NAME	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates	16	5	20
4	COMPANY DISCRETIONARY DATA	Optional	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates	20	21	40
5	COMPANY IDENTIFICATION	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates	10	41	50
6	STANDARD ENTRY CLASS CODE³	Mandatory	For NOCs, will contain the value “COR”. For Returns, will contain the SEC code of the original entry.	3	51	53
7	COMPANY ENTRY DESCRIPTION	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	10	54	63
8	COMPANY DESCRIPTIVE DATE	Optional	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	6	64	69
9	EFFECTIVE ENTRY DATE	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	6	70	75
10	SETTLEMENT DATE (JULIAN)	Mandatory	For Returns, date the return was posted to client’s account. For NOCs, will be “000”	3	76	78
11	ORIGINATOR STATUS CODE	Mandatory	Always ‘1’	1	79	79
12	ORIGINATING DFI IDENTIFICATION	Mandatory	Always ‘02601507 (first 8 digits of GS Bank’s routing number)	8	80	87
13	BATCH NUMBER	Mandatory	Numeric Start with ‘0000001’ and increment by 1 for each subsequent batch in the file.	7	88	94

³ See section on Standard Entry Class codes and their descriptions for a further description of supported codes

Entry Detail Record – type 6 – for CCD, PPD, IAT, WEB and TEL entries

The Entry Detail record for a Return or NOC entry largely retains field values corresponding to the original ACH transaction. These are shaded in grey below. The remaining fields are populated with codes or values pertinent to Return or NOC entries. Record structure for CTX entries is outlined in the next section

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘6’	1	1	1
2	TRANSACTION CODE	Mandatory	Numeric. Contains one of the following values, that indicates a Return or NOC * 21 – for original transaction codes 22, 23 * 26 – for original transaction codes 27, 28 * 31 – for original transaction codes 32, 33 * 36 – for original transaction codes 37, 38	2	2	3
3	RECEIVING DFI IDENTIFICATION	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	8	4	11
4	CHECK DIGIT	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates	1	12	12
5	RECEIVER’S ACCOUNT NUMBER AT RDFI	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	17	13	29
6	AMOUNT	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	10	30	39
7	(INDIVIDUAL) IDENTIFICATION NUMBER	Optional	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	15	40	54
8	INDIVIDUAL / RECEIVING COMPANY NAME	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	22	55	76
9	DISCRETIONARY DATA / PAYMENT TYPE CODE	Conditional	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	2	77	78
10	ADDENDA RECORD INDICATOR	Mandatory	Always 1, to indicate that an addenda record follows this entry	1	79	79
11	TRACE NUMBER	Mandatory	Numeric Unique identifier for each Entry within the batch. The first 8 digits correspond to GS Bank’s routing number ‘02601507’, followed by a sequence number in ascending order within the batch.	15	80	94

Entry Detail Record – type 6 – for CTX entries

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘6’	1	1	1
2	TRANSACTION CODE	Mandatory	Numeric. Contains one of the following values, that indicates a Return or NOC * 21 – for original transaction codes 22, 23 * 26 – for original transaction codes 27, 28 * 31 – for original transaction codes 32, 33 * 36 – for original transaction codes 37, 38	2	2	3
3	RECEIVING DFI IDENTIFICATION	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	8	4	11
4	CHECK DIGIT	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	1	12	12
5	RECEIVER’S ACCOUNT NUMBER AT RDFI	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	17	13	29
6	AMOUNT	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	10	30	39
7	IDENTIFICATION NUMBER	Optional	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	15	40	54
8	NUMBER OF ADDENDA RECORDS	Mandatory	Always “0001”	4	55	58
9	RECEIVING COMPANY NAME / ID NUMBER	Mandatory	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	16	59	74
10	RESERVED	N/A	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	2	75	76
11	DISCRETIONARY DATA	Optional	These fields are populated with the corresponding values from the original ACH entry to which the return / NOC relates.	2	77	78
12	ADDENDA RECORD INDICATOR	Mandatory	Always 1, to indicate that an addenda record follows this entry	1	79	79
13	TRACE NUMBER	Mandatory	Numeric. Unique identifier for each Entry within the batch. The first 8 digits correspond to GS Bank’s routing number ‘02601507’, followed by a sequence number in ascending order within the batch.	15	80	94

Addenda Record – type 7

The Addenda record for a Return or NOC entry provides the Return / Change Codes, together with additional information as applicable. For IAT Returns, the 7 mandatory addenda records are not included in this pseudo-NACHA format report.

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘7’	1	1	1
2	ADDENDA TYPE CODE	Mandatory	For NOCs: always ‘98’ For Returns: always ‘99’	2	2	3
3	RETURN / CHANGE CODE	Mandatory	Contains a 3-character code. For Returns, see List of Return Codes & reasons For NOCs, see List of Change Codes	3	4	6
4	ORIGINAL ENTRY TRACE NUMBER	Mandatory	Trace number from positions 80-94 of the original Entry Detail Record or Corporate Entry Detail Record.	15	7	21
5	DATE OF DEATH	Conditional	Applicable only for Return Codes R14 or R15. Entered as YYMMDD.	6	22	27
6	ORIGINAL RDFI IDENTIFICATION	Mandatory	First 8 digits of RDFI routing number from positions 4-11 of the original ACH Entry Detail record.	8	28	35
7	ADDENDA INFORMATION	Conditional	For NOCs, only the first 29 positions of this field are used to indicate the Corrected Data. The Corrected Data elements follow a format as specified in the List of Change Codes. For non-IAT Returns, this field contains additional description for return codes R11 and R17. For IAT Returns, the first 10 positions of this field contains the Original Forward Entry Payment Amount ($$$$$$$$cc). The remainder of this field contains additional description for return codes R11 and R17.	44	36	79
8	TRACE NUMBER	Mandatory	Same Trace Number as corresponding Entry Detail record for the Return/NOC.	15	80	94

Company / Batch Control Record – type 8

The Company/Batch Control Record for Return / NOC files follows the standard NACHA format, as applicable for Origination files. It is detailed below for sake of completeness below. All Entry Detail Records are hashed. Both Entry Detail Records and Addenda Records are included in the Entry/addenda counts; Batch Header and Batch Control Records are not included.

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘8’	1	1	1
2	SERVICE CLASS CODE	Mandatory	Numeric. Should be the same as the Service Class Code of the associated Company / Batch Header record.	3	2	4
3	ENTRY/ ADDENDA COUNT	Mandatory	Numeric. Total number of entry and addenda records in the batch.	6	5	10
4	ENTRY HASH	Mandatory	Numeric Sum of the 8-digit RDFI routing numbers in the Entry Detail records in the batch. Use the right-most 10 digits if the sum exceeds 10 digits, and fill with leading 0’s if less than 10 digits.	10	11	20
5	TOTAL DEBIT ENTRY DOLLAR AMOUNT	Mandatory	Dollar and Cent Sum of Entry Detail debit totals within the batch.	12	21	32
6	TOTAL CREDIT ENTRY DOLLAR AMOUNT	Mandatory	Dollar and Cent Sum of Entry Detail credit totals within the batch.	12	33	44
7	COMPANY IDENTIFICATION	Mandatory	Alphanumeric. Should be the same as the Company ID of the associated Company / Batch Header record.	10	45	54
8	MESSAGE AUTHENTICATION CODE	N/A	Alphanumeric. Not used. Fill with spaces.	19	55	73
9	RESERVED	N/A	Fill with spaces	6	74	79\
10	ORIGINATING DFI IDENTIFICATION	Mandatory	Always ‘02601507’ (first 8 digits of GS Bank’s routing number)	8	80	87
11	BATCH NUMBER	Mandatory	Numeric. Should be the same as the Batch Number of the associated Company / Batch Header record.	7	88	94

File Control Record – type 9

The File Control Record for Return / NOC files follows the standard NACHA format, as applicable for Origination files. It is detailed below for sake of completeness below.

Field	Field Name	Requirement	Contents / Type	Length	Start Position	End Position
1	RECORD TYPE CODE	Mandatory	Always ‘9’	1	1	1
2	BATCH COUNT	Mandatory	Numeric. Number of batches in the file.	6	2	7
3	BLOCK COUNT	Mandatory	Numeric. Total number of blocks in the file. Block = 10 records (including all Header and Control records and Blocking control records).	6	8	13
4	ENTRY/ADDENDA COUNT	Mandatory	Numeric. Total number of Entry Detail and Addenda records in the file.	8	14	21
5	ENTRY HASH	Mandatory	Numeric. Sum of all Entry Hash fields in each Company/Batch Control record contained within the file. Use the right-most 10 digits if the sum exceeds 10 digits, and fill with leading 0’s if less than 10 digits.	10	22	31
6	TOTAL DEBIT ENTRY DOLLAR AMOUNT IN FILE	Mandatory	Dollar and Cent Sum of Entry Detail debit totals within the file.	12	32	43
7	TOTAL CREDIT ENTRY DOLLAR AMOUNT IN FILE	Mandatory	Dollar and Cent Sum of Entry Detail credit totals within the file.	12	44	55
8	RESERVED	N/A	Always filled with spaces	39	56	94

Was this page useful?

Give feedback to help us improve developer.gs.com and serve you better.

Goldman Sachs DeveloperPrivacy and CookiesGS Terms & ConditionsRegulatory DisclosuresSecurity

GS DAP® is owned and operated by Goldman Sachs. This site is for informational purposes only and does not constitute an offer to provide, or the solicitation of an offer to provide access to or use of GS DAP®. Any subsequent commitment by Goldman Sachs to provide access to and / or use of GS DAP® would be subject to various conditions, including, amongst others, (i) satisfactory determination and legal review of the structure of any potential product or activity, (ii) receipt of all internal and external approvals (including potentially regulatory approvals); (iii) execution of any relevant documentation in a form satisfactory to Goldman Sachs; and (iv) completion of any relevant system / technology / platform build or adaptation required or desired to support the structure of any potential product or activity. All GS DAP® features may not be available in certain jurisdictions. Not all features of GS DAP® will apply to all use cases. Use of terms (e.g., "account") on GS DAP® are for convenience only and does not imply any regulatory or legal status by such term.

Certain solutions and Institutional Services described herein are provided via our Marquee platform. The Marquee platform is for institutional and professional clients only. This site is for informational purposes only and does not constitute an offer to provide the Marquee platform services described, nor an offer to sell, or the solicitation of an offer to buy, any security. Some of the services and products described herein may not be available in certain jurisdictions or to certain types of clients. Please contact your Goldman Sachs sales representative with any questions. Any data or market information presented on the site is solely for illustrative purposes. There is no representation that any transaction can or could have been effected on such terms or at such prices. Please see https://www.goldmansachs.com/disclaimer/sec-div-disclaimers-for-electronic-comms.html for additional information.

Transaction Banking services are offered by Goldman Sachs Bank USA (“GS Bank”). GS Bank is a New York State chartered bank, a member of the Federal Reserve System and a Member FDIC.

Mosaic is a service mark of Goldman Sachs & Co. LLC. This service is made available in the United States by Goldman Sachs & Co. LLC and outside of the United States by Goldman Sachs International, or its local affiliates in accordance with applicable law and regulations. Goldman Sachs International and Goldman Sachs & Co. LLC are the distributors of the Goldman Sachs Funds. Depending upon the jurisdiction in which you are located, transactions in non-Goldman Sachs money market funds are affected by either Goldman Sachs & Co. LLC, a member of FINRA, SIPC and NYSE, or Goldman Sachs International. For additional information contact your Goldman Sachs representative. Goldman Sachs & Co. LLC, Goldman Sachs International, Goldman Sachs Liquidity Solutions, Goldman Sachs Asset Management, L.P., and the Goldman Sachs funds available through Goldman Sachs Liquidity Solutions and other affiliated entities, are under the common control of the Goldman Sachs Group, Inc.