ACH Return Item File

Reference Guide
Table of contents
Introduction 4
About this guide 4
Related documents 4
ACH rules and regulations 4

ACH return item files — an overview 5

Items included in a return item file 5
File record types 5
Concatenated files (stacking) 6
Combined files 7
File distribution times 7
Empty (null) files 7
Blocking file control records 7
Trace numbers 8
Overview 8
If an item is not found in history 8
If an item is found in history 9
Settlement of returns 9

Helpful hints 10
File record specifications 14
File header (type 1) record 14
Company/batch header (type 5) record 16
Overview 16
Company/batch header record — all transactions except IAT 16
Company/batch header record — IAT 20
Entry detail (type 6) record 22
Entry detail (type 6) record — all transactions except IAT 22
Entry detail (type 6) record — IAT 24
IAT addenda records 26
Overview 26
First mandatory IAT addenda (type 710) record 26
Second mandatory IAT addenda (type 711) record 27
Third mandatory IAT addenda (type 712) record 28
Fourth mandatory IAT addenda (type 713) record 29
Fifth mandatory IAT addenda (type 714) record 30
Sixth mandatory IAT addenda (type 715) record 31
Seventh mandatory IAT addenda (type 716) record 32
NOC/return (798 and 799) records 33
Company/batch control (type 8) record 34
File control (type 9) record 35
Standard file control record 35

2
 Blocking file control records (optional) 35

Sample data files 36

File with transaction data 36
File with transaction data — IAT 37
File with no transactions (empty file) 37

Exception reports 38
Codes 39
Overview 39
Return reason codes — general 39
Return reason codes used by ACH operators 41
Dishonored return reason codes 41
Contested/corrected dishonored return reason codes 42
Notification of change (NOC) reason codes 42
Refused notification of change reason codes 42

Exception handling quick reference 43

3
Introduction

About this guide

This guide describes ACH return item files you receive from Wells Fargo Bank. In addition to this
introduction, the guide includes the following sections:
• ACH return item files — an overview describes where to get information about downloading ACH
return item files and describes the general layout of ACH return item files.
• Helpful hints provides tips and guidelines related to ACH return item files.
• File record specifications provides detailed file format information for ACH return item files.
• Sample data files provides an example of an ACH return item file with return data and a file without
any returns (an empty file).
• Exception reports describes reports with information for ACH returns and notifications of change
(NOCs).
• Codes lists reason codes that can be included in a detail record to indicate why an item has been
returned.
• Exception handling quick reference describes how to respond to the various types of exceptions that
can occur when an ACH transaction is processed.

Related documents
Other documents that may be of assistance include:
• ACH Quick Reference
• ACH Implementation Guide
• ACH User Guide
• ACH Rules — Corporate Edition
In addition to general information about Wells Fargo’s ACH services, the ACH User Guide provides
information about settlement of returns.

ACH rules and regulations

The Operating Rules of the National Automated Clearing House Association (NACHA) govern the
processing of ACH payments. For details about these rules, refer to the ACH Rules Corporate Edition.
Additional information can be obtained through the NACHA web site at:
www.nacha.org
In addition to the ACH Service agreement that you signed with Wells Fargo, your ACH transactions may
also be subject to other laws and regulations, such as:
• Regulation E
• Uniform Commercial Code
• Regulation CC
• State laws
• The Bank Secrecy Act of 1970 (BSA)
• Office of Foreign Assets Control (OFAC) rules and regulations

Introduction 4
ACH return item files — an overview

Items included in a return item file

A return item file can include both ACH returns and paper returns. A paper return is a check that was
processed using the Smart Decision® service and was not eligible for conversion to ACH.
For IAT transactions:
• You can receive an NOC only if the transaction is to an RDFI located within the territorial jurisdiction
of the United States (a U.S. RDFI). NOCs are not generated for IAT transactions to an RDFI in
another country.
• Whether you receive addenda records for NOCs depends on the option you select at setup.

File record types

Although ACH return item files from Wells Fargo are in a proprietary format, they are structured much
like standard NACHA return files. Like NACHA-format files, the information in an ACH return item file is
organized into records. Each file includes the following:

As shown above, each return item is usually included in its own batch. If you have four return items, for
example, the return item file will usually include four batches, one for each return item. If the same bank
returns multiple returns for the same original effective date, you may receive multiple returns within the
same batch.
If there are multiple company IDs, batches for each company ID are grouped together. For example, if you
have two return items for company ID 1111111111 and two return items for company ID 2222222222, the
file would include the following records:

ACH return item files — an overview 5

Concatenated files (stacking)
If you have multiple file IDs, you can receive your return item files as separate files, or you can receive
them as a single file. Receiving them as a single file is called “stacking” or concatenation.
With concatenated files, return items for each file are included within separate file header (type 1) records
and file control (type 9) record. For example, if there are two return items for file ID 3333333333 and two
return items for file ID 4444444444, the return item file would include the following records:

ACH return item files — an overview 6

Combined files
With the combined file option, you can receive combined files as you would with concatenation, but with
these differences:
• There is only one file header (type 1) record at the beginning of the file and one file control (type 9)
record at the end of the file. There is no file control record to mark the end of one file or file header
record to mark the end of the next file.
• Instead of the file ID being tied to the origination file, you choose the file ID to use for the return item
file.

File distribution times

Wells Fargo provides five distribution times for return item files, and you can choose to receive files at one
or more of the times listed below. If you receive your file once per day, we recommend the 5:00 a.m. CT
distribution time.
Distribution times are approximate.
1:00 a.m. CT
5:00 a.m. CT
1:00 p.m. CT
5:00 p.m. CT
9:00 p.m. CT

Empty (null) files

If there are no return items on a given business day, Wells Fargo generates an “empty” file with only a file
header (type 1) record and file control (type 9) record.
If you are set up for multiple distributions, you receive an empty file for each distribution during the day
that has no returns.
Note: Receiving empty files is optional but strongly recommended. Receiving an empty file serves as a
confirmation that you haven’t received any return items that day.

Blocking file control records

As an option, you can receive blocking file control records with your file. With this option, if the total
record count in a file is not a multiple of ten, blocking file control records are added to the end of the file.
If the total record count in a file is 18, for example, two blocking file control records are added to make the
total record count 20. Blocking file control records are 94 characters in length and consist of all 9s.
If you receive concatenated (stacked) files, you can request that blocking file control records be added
after each standard file control record or only after the last standard file control record.

ACH return item files — an overview 7

Trace numbers
Overview
Return item files have three 15-digit trace numbers for an item:
• The 6 record trace — positions 80-94 in the entry detail (type 6) record
• The 798/799 record trace — positions 80-94 in the NOC/return (type 798 or 799) record
• The original entry trace — positions 7-21 in the NOC/return (type 798 or 799) record
Each of these trace number fields is comprised of two parts:
• The first eight digits, which often (but not always) are a routing/transit number (RTN)
• The remaining seven digits
There are three different numbers that can be used to provide the content of the trace number fields in the
return item file:
• Customer trace. This is the trace number provided by your company for the original item. The first
eight digits may or may not be an RTN, depending on what is sent by your company.
• Wells Fargo trace. When we process your original ACH item, we reassign the trace number field. The
first part is the Wells Fargo RTN 09100001, and second part is a seven-digit number assigned by
Wells Fargo.
• Return trace. This is the trace number provided in the return by the financial institution that received
the transaction. The first part is either 09100001 or the eight-digit RTN for the RDFI, and the
second part is a seven-digit number assigned by the RDFI.
The content of the trace number fields in the return item file depends on whether the item was found in
the Wells Fargo ACH history database and the original trace and return trace options your company uses.
Your company can choose from the following options for original trace:
• N — the Wells Fargo trace is used in the return item file.
• Y — the customer trace is used in the return item file.
Your company can choose from the following options for return trace:
• N — the 6 record trace and 798/799 record trace are not the same.
• A, B, or C — the 6 record trace and 798/799 record trace are the same, and the content for those fields
depends on the options selected.

If an item is not found in history

If the found/not found indicator field, position 88 in the company/batch header (type 5) record, is 6
(previously dishonored) or 8 (not found), that indicates that the return item was not found in the
Wells Fargo ACH database. In this situation, the values in the trace number fields (entry detail record
trace, NOC/return record trace, and original entry trace) may be different from a typical return.

ACH return item files — an overview 8

If an item is found in history
If an item is found in history, the content of the three trace fields for an item in the return item file
depends on the original trace and return trace options your company uses. The table below summarizes
the various combinations and includes an example of an entry detail (type 6) and return (type 799) record
for each combination. The examples are based on a return for the following record from the origination
file:
6270515012990123456 00000018130001234 BOB B BROWN SR 1123456780000044

Option selected Field content

Original trace Return trace 6 record trace 798/799 record trace Original entry trace
Return trace,
N N Wells Fargo trace Wells Fargo trace
1-8: 09100001
6260515012990123456 0000001813000 1234 BOB B BROWN SR 1091000010001234
799R08091000010001234 05150129 091000015550555

Return trace,
Y N Customer trace Customer trace
1-8: 09100001
6260515012990123456 0000001813000 1234 BOB B BROWN SR 1123456780000044
799R08123456780000044 05150129 091000015550555

N A Wells Fargo trace Wells Fargo trace Wells Fargo trace

6260515012990123456 0000001813000 1234 BOB B BROWN SR 1091000010001234
799R08091000010001234 05150129 091000010001234

Y A Customer trace Customer trace Customer trace

6260515012990123456 0000001813000 1234 BOB B BROWN SR 1123456780000044
799R08123456780000044 05150129 123456780000044

Return trace, Return trace,

N B Wells Fargo trace
1-8: 09100001 1-8: 09100001
6260515012990123456 0000001813000 1234 BOB B BROWN SR 1091000015550555
799R08091000010001234 05150129 091000015550555

Return trace, Return trace,

Y B Customer trace
1-8: 09100001 1-8: 09100001
6260515012990123456 0000001813000 1234 BOB B BROWN SR 1091000015550555
799R08123456780000044 05150129 091000015550555

Return trace, Return trace,

N C Wells Fargo trace
1-8: RDFI RTN 1-8: RDFI RTN
6260515012990123456 0000001813000 1234 BOB B BROWN SR 1123000455550555
799R08091000010001234 05150129 123000455550555

Return trace, Return trace,

Y C Customer trace
1-8: RDFI RTN 1-8: RDFI RTN
6260515012990123456 0000001813000 1234 BOB B BROWN SR 1123000455550555
799R08123456780000044 05150129 123000455550555

Settlement of returns
For information about the settlement of returns, refer to the ACH User Guide.

ACH return item files — an overview 9

Helpful hints
Testing requirements
When preparing origination files for returns testing:
• Include a minimum of 30 transactions in the file.
• Use valid routing/transit numbers for transactions. Account numbers do not need to be valid.
• Make the transactions in the file as close as possible to the type of transactions you will use in
production. Include the same types of transaction and the same type of information.
Allow for variation in data fields
Although ACH return items are expected to conform to accepted ACH standards, the formatting of data
may vary somewhat from one return item to another. Allow for this variation as much as possible to avoid
programming errors.
Review returns daily
Review your return item files daily in order to respond promptly to any items that require further action.
If you choose multiple file distribution times, you need to review files throughout the day.
To ensure that you don’t process a file multiple times, use the fields listed in the next helpful hint to
uniquely identify a file.
Data fields to use for posting purposes
For file-level posting, the following fields are typically used to validate that the file belongs to your
company, has the correct date, and is not duplicated.

Record Field Position

File header (type 1) record File ID 4-13

File creation date 24-29

File creation time 30-33

File control (type 9) record Total file debit entry amount 32-43

Total file credit entry amount 44-55

For transaction-level posting, the following fields are typically used to match and process returns with
originated items for all transactions except IAT transactions.

Record Field Position

Company/batch header Company ID 41-50

(type 5) record
Company descriptive date 64-69

Effective entry date 70-75

Found/not found indicator 88

Entry detail (type 6) record R/T number 4-12

Receiving account number 13-29

Amount 30-39

Individual ID 40-54

Helpful hints 10
 Record Field Position

Addenda (type 7) record Addenda type code 2-3

Return reason code 4-6

Addenda information 36-79

For transaction-level posting, the following fields are typically used to match and process returns with
originated items for IAT transactions.

Record Field Position

Company/batch header ISO destination country code 39-40

(type 5) record
Originator ID 41-50

ISO originating currency code 64-66

ISO destination currency code 67-69

Effective entry date 70-75

Found/not found indicator 88

Entry detail (type 6) record GO ID / receiving DFI ID 4-12

Amount 30-39

Foreign receiver’s account 40-74

number

798 or 799 addenda record Addenda type code 2-3

Return reason code 4-6

Addenda information 36-79

715 addenda record Receiver ID 4-18

Identifying a Check Conversion Administrative Return

If you use Wells Fargo’s Check Conversion Administrative Returns feature to process converted check
transactions that are returned, use the individual name field (positions 55-76 of the entry detail record) to
identify the original item. Other identifying information from the check (routing/transit number, account
number, and serial number) may be changed during the check conversion process.
Identifying a check conversion return
To identify a check conversion transaction in a return item file, use the following fields:
• Company descriptive date (positions 64-69 of the company/batch header record)
• Amount (positions 30-39 of the entry detail record)
• Individual name (positions 55-76 of the entry detail record, which is the client reference number for
the check conversion transaction)
Don’t use the routing/transit number and account number fields to identify a check conversion
transaction because Wells Fargo may make corrections to those fields, and the values for those fields in a
return item file may be different than in the original transaction you provided to Wells Fargo.

Helpful hints 11
Archive your data files
Archive copies of your origination and return item files for research purposes. If you process consumer
transactions, for example, you need the ability to process returns for those transactions for up to 90 days.
Items not found in history
If the value of the found/not found indicator field in the company/batch header (type 5) record is 8 (not
found), Wells Fargo could not locate the original transaction in the history database. This can also be the
case for some transactions with a 6 (previously dishonored) in the found/not found indicator field.
For these returns, the information is only as accurate as provided by the receiving depository financial
institution submitting the return and may contain errors. You should review these returns to determine
whether further action is required.
Automatically redeposited and dishonored items
Returns in return item files are usually final disposition only. Any items automatically redeposited by
Wells Fargo are only included in return item files upon request. For example, if your company uses the
automatic redeposit feature, items with return reason code R01 or R09 are automatically re-presented by
Wells Fargo and are not included in your return item file unless requested.
If redeposited items are included in your file, you can identify them by the found/not found indicator
field, position 88 of the company/batch header (type 5) record.
Items that are automatically dishonored by Wells Fargo are not included in standard return item files.
Effective entry date for redeposited items
If a return is automatically redeposited by Wells Fargo, the effective entry date in the company/batch
header (type 5) record is changed to the date that the item was redeposited. If the item is returned again
and included in your return item file, the effective entry field for the return reflects this new date.
Credit union conversion
If your company uses the credit union conversion feature, Wells Fargo may change the routing/transit
(R/T) number and/or account number when the original transaction is processed. If the item is returned,
you may not be able to automatically match the return to the original entry because of the reassigned R/T
number and/or account number.
Note: Using Automated Credit Union Processing requires using the MICR-Split Service. Refer to the
ACH User Guide for information about the MICR-Split Service.
When Wells Fargo converts a credit union routing/transit number or account number, we send a
notification of change (NOC) to your company. Use that NOC to update your internal system with the new
routing/transit number and account number to prevent the problem from recurring.
Including or excluding transaction types
You can specify that items with certain transaction types be automatically included or excluded for return
item files. The following transaction types are available to be included or excluded:
• Returns
• Prenote returns
• Notifications of change (NOCs)
• Redeposits
Wells Fargo also offers 94-character record layout with addenda. For more information about this option,
contact your bank representative.

Helpful hints 12
NOCs for prenotes
If you receive an NOC for a prenote, there is no need to send a corrected prenote entry. Use the NOC to
update the data in your ACH origination system so that dollar transactions for the receiver will be
processed correctly.
You can also use the Perfect NOC® service to help you automate the process of providing updated
information for your ACH transactions. With the Perfect NOC service, we maintain a database with
information from NOCs and make any needed corrections to the ACH transactions you originate before
sending them to the ACH system. For more information about the Perfect NOC service, refer to the ACH
User Guide.
Same day ACH returns
Regarding same day returns:
• A same day ACH item that is returned follows the same timetable as returns for other items.
• Items not originated as same day can be returned in a same day return processing window.
• While there is an amount limit for originating same day items, there is no amount limit for submitting
same day returns.

Helpful hints 13
File record specifications

File header (type 1) record

No Field Position Length Description

1 Record type 1 1 Always 1.

2 Priority code 2-3 2 Always 01.

3 File ID (immediate 4-13 10 Either the file ID assigned by Wells Fargo or an ID

destination) requested by your company at setup. May be less
than ten digits.

4 Wells Fargo R/T 14-23 10 One of the following:

number (immediate • Wells Fargo routing/transit number
origin) b091000019, where b=space.
• A value requested by your company at setup.

5 File creation date 24-29 6 File creation date (YYMMDD).

6 File creation time 30-33 4 File creation time (HHMM), military format (2400),
company time.
If your company elects to receive multiple files
during the day, the file creation time approximately
reflects the designated distribution time for the file.

7 File modifier 34 1 Always A.

8 Record size 35-37 3 Always 094.

9 Blocking factor 38-39 2 Always 10.

10 Format code 40 1 Always 1.

11 Company name 41-63 23 One of the following:

(immediate • The company name from the first
destination name) company/batch header (type 5) record in this
file.
If the first return item in the file was not found
in history, then this field is blank. See the
found/not found indicator field for the
company/batch header (type 5) record.
• A value requested by your company at setup.

12 Origination bank 64-86 23 Either WELLS FARGO BANK or a value requested

(immediate origin by your company at setup.
name)

13 Reference code 87-94 8 Always blank.

File record specifications 14

File header record example

File record specifications 15

Company/batch header (type 5) record
Overview
A key field is the found/not found indicator (position 88):
• If a return item is found in the Wells Fargo ACH history database, then information for the original
item from the history database is used for the fields in this record.
• If a return item is NOT found in the history database, then the information provided with the return is
used for the fields in this record.
Note: When an item is not found in the history database, this is usually a strong indication that some
information in the return is not valid. Review these items to determine whether additional action
is needed.
The fields included in the company/batch header record depend on whether the return is for an IAT
transaction.

Company/batch header record — all transactions except IAT

No Field Position Length Description
1 Record type 1 1 Always 5.
2 Service class 2-4 3 Always 200.
3 Company name 5-20 16 Your company name.
4 Company 21-40 20 The company discretionary data from the
discretionary data company/batch header record for the original entry.
If you do not use the original company discretionary
data option, this field can also be one of the following:
• If the return item is a retired redeposit or second
redeposit, positions 31-33 is (R) and the
remainder of the field is left blank.
• If the return item is a Check Conversion
Administrative Return, positions 31-33 is (A) and
the remainder of the field is used by Wells Fargo.
5 Company ID 41-50 10 Ten-character company ID assigned by Wells Fargo.
6 Standard entry class 51-53 3 SEC code from the company/batch header record for
(SEC) code the original entry.
If you use the COR option, this is always COR for
NOCs.
Note: For Check Conversion Administrative Returns, if
you do not use the COR option, this field may be
either COR or the original SEC code.
7 Company entry 54-63 10 Company-defined description of the entry to the
description receiver, such as PAYROLL, GAS BILL, or INS
PREM.
If your company uses the Automatic Redeposit
service, this will be RETRY PYMT for a returned
redeposit.

File record specifications 16

No Field Position Length Description
8 Company descriptive 64-69 6 Company-defined reference date for the receiver (for
date descriptive purposes only). Not used to control timing
of settlement/posting. Examples:
091506 09 06 SEP 15 SEP 06
Note: If an item is not found in history, this field is
whatever was provided on the return.
For a redeposit or dishonor, if this field is not used in
the original entry, Wells Fargo may insert the original
return date in YYMMDD format.
For IAT transactions, this field includes the following:
• ISO originating currency code
• ISO destination currency code
• If you do not use the original company descriptive
date option, this field can also be one of the
following:
NORWST Indicates a credit union conversion
NOC.
ON-US Indicates a Wells Fargo-generated NOC
ADMIN, Indicates a check submitted through
ADMINN the Check Conversion process that was
returned and had one of the following
outcomes:
• Was resubmitted as a photocopy or
pre-authorized check (PAC).
• The amount was changed.
• Could not be corrected with Check
Conversion Administrative Returns.
WFBDEF, Indicates a check submitted through
WFBDMC, the Check Conversion process that was
WFBDPM processed as a MICR-Split item
(converted to a pre-authorized check).
Found on NOCs with reason code C99.
For WFBDEF, the item was processed
as MICR-Split because it matched
criteria in the check conversion
exclusion file.
For WFBDMC, the item was processed
as MICR-Split as specified by settings in
the Wells Fargo Bank Directory.
For WFBDPM, the item was processed
as MICR-Split because an item with the
same R/T number and account number
previously was processed as MICR-
Split.
WFBDDI Indicates a check submitted through
the Check Conversion process that was
returned and dishonored with Check
Conversion Administrative Returns.
Found on dishonored returns with
reason code C96.

File record specifications 17

No Field Position Length Description
9 Effective entry date 70-75 6 Effective entry date from the company/batch header
record for the original entry in format YYMMDD.
If you use the original effective date option, this field
is the original effective date for all returns, NOCs,
dishonored returns, and redeposits.
For returns, NOCs, and dishonored returns, if you do
not use the original effective date option and the
effective date falls on a weekend or holiday (or if your
origination file is received past the deadline),
Wells Fargo adjusts the date to a valid business day.
For automated redeposits, if you do not use the
original effective date option:
• On the first redeposit, this is the original effective
date.
• On the second redeposit, this is the first redeposit
date.
• For a retired redeposit, this is the second redeposit
date.
Note: If an item is not found in history, the effective
date is as provided on the return.
10 Julian settlement 76-78 3 Always 000.
date
11 Status code 79 1 Always 1.
12 Wells Fargo R/T 80-87 8 Wells Fargo routing/transit number. Always
number 09100001.

13 Found/not found 88 1 Indicates whether this return item was found in the
indicator Wells Fargo ACH history database:
1 Administrative fatal return or NOC (if your
company uses the Administrative Returns
feature)
2 First redeposit (if your company uses the
Automated Redeposit feature)
3 Second redeposit (if your company uses the
Automated Redeposit feature)
4 Administrative dishonor (if your company uses
the Administrative Returns feature)
5 Administrative deposit adjustment for MICR-
Split, photocopy request, or amount
adjustment (if your company uses the
Administrative Returns feature)
6 Previously dishonored
7 Found
8 Not found
9 Retired redeposit (if your company uses the
Automated Redeposit feature)
14 Batch number 89-94 6 Assigned starting from 000001 in ascending
sequence for each company/batch header record.

File record specifications 18

Company/batch header record example — all transactions except IAT

File record specifications 19

Company/batch header record — IAT
No Field Position Length Description
1 Record type 1 1 Always 5.
2 Service class 2-4 3 Always 200.
3 IAT indicator 5-20 16 For IAT NOCs from a U.S. RDFI, depending on the
option you use, can include IATCOR in positions 5-
10.
If the return item is a retired redeposit or second
redeposit, positions 11-13 is (R). The system also
includes additional characters in the field for internal
purposes.
4 Foreign exchange 21-22 2 The foreign exchange indicator from the
indicator company/batch header record for the original entry.
Indicates the foreign exchange conversion method
used for the transaction.
FV Fixed to variable
VF Variable to fixed
FF Fixed to fixed
5 Foreign exchange 23 1 Indicates the type of data in the foreign exchange
reference indicator reference field.
1 Foreign exchange rate
2 Foreign exchange contract number
3 Blank (transaction does not use foreign
exchange)
6 Foreign exchange 24-38 15 Foreign exchange rate or reference number, as
reference specified in the foreign exchange reference indicator
field. If the foreign exchange reference indicator is 3,
this field is blank (space filled).
7 ISO destination 39-40 2 Two-character ISO 3166 country code for the
country code beneficiary country.
8 Originator ID 41-50 10 Your Wells Fargo ACH company ID.
9 Standard entry class 51-53 3 For IAT returns, this field is the SEC code from the
(SEC) code company/batch header record for the original entry
(IAT).
For IAT NOCs, this field is COR.
10 Company entry 54-63 10 Either blank or a company-defined description of the
description entry to the receiver, such as PAYROLL or VENDOR
PMT.
11 ISO originating 64-66 3 Three-character ISO 4217 code for the originating
currency code currency.
12 ISO destination 67-69 3 Three-character ISO 4217 code for the destination
currency code currency.
13 Effective entry date 70-75 6 Effective entry date from the company/batch header
record for the original entry. Format YYMMDD. May be
changed by Wells Fargo to a valid business date.
If you use the original effective date option, this field
is the original effective date for all returns, NOCs,
dishonored returns, and redeposits.
For redeposits or retired redeposits, if you do not use
the original effective date option, this field is the
redeposit date.

File record specifications 20

14 Julian settlement 76-78 3 Always 000.
date
15 Status code 79 1 Always 1.
16 Wells Fargo R/T 80-87 8 Wells Fargo routing/transit number. Always
number 09100001.
17 Found/not found 88 1 Indicates whether this return item was found in the
indicator Wells Fargo ACH history database:
1 Administrative fatal return or NOC (if your
company uses the Check Conversion
Administrative Returns feature)
2 First redeposit (if your company uses the
Automated Redeposit feature)
3 Second redeposit (if your company uses the
Automated Redeposit feature)
4 Administrative dishonor (if your company uses
the Check Conversion Administrative Returns
feature)
5 Administrative deposit adjustment for MICR-
Split, photocopy request, or amount
adjustment (if your company uses the Check
Conversion Administrative Returns feature)
6 Previously dishonored
7 Found
8 Not found
9 Retired redeposit (if your company uses the
Automated Redeposit feature)
18 Batch number 89-94 6 Assigned starting from 000001 in ascending
sequence for each company/batch header record.

Company/batch header record example — IAT

File record specifications 21

Entry detail (type 6) record
Entry detail (type 6) record — all transactions except IAT
No Field Position Length Description
1 Record type 1 1 Always 6.
2 Return transaction 2-3 2 Indicates type of transaction being returned. These are
code * the most common codes. Refer to the ACH Rules
Corporate Edition for a complete list of codes.
21 Checking account credit transaction
26 Checking account debit transaction
31 Savings account credit transaction
36 Savings account debit transaction
41 General ledger account credit transaction
46 General ledger account debit transaction
51 Loan account credit transaction
56 Loan account debit transaction
3 R/T number * 4-12 9 If the item is found in the Wells Fargo history database,
this field contains the routing/transit number of the
receiving depository financial institution from the original
transaction.
If the item is not found in history, this field contains the
routing/transit number of the financial institution sending
the return (usually the same as the routing/transit
number of the RDFI from the original transaction).
4 Receiving account 13-29 17 Account number at the RDFI.
number *
5 Amount 30-39 10 Dollar amount of the transaction:
• Unsigned
• No decimal point
• Right-justified
• Filled with leading zeros
Example: 0000001850 would be the entry for $18.50.
For prenotes and NOCs, this field is zero-filled.
6 Individual ID * 40-54 15 ID number for the receiver, such as an employee number
or location code (alphanumeric).
For transactions converted from checks (items with SEC
code ARC, BOC, POP, or RCK), this field is the check
number.
Items with SEC code POP also include the following:
• Terminal city abbreviation in positions 49-52.
• Terminal state abbreviation in positions 53-54.
7 Individual name 55-76 22 Name of the receiver (individual or company) of the ACH
transaction, a customer reference number, or blank
(space-filled).
8 Discretionary data 77-78 2 Discretionary data field from the entry detail record for
the original entry.
* For check conversion and Perfect NOC transactions, Wells Fargo analyzes data in the original transaction
and may make corrections to this field before submitting it to the RDFI. As a result, this field for a check
conversion or Perfect NOC transaction in a return item file may be different than in the original transaction
you provided to Wells Fargo.

File record specifications 22

9 Addenda record 79 1 Always 1 to indicate that an addenda record follows this
indicator record.
10 Trace number 80-94 15 Contents of this field depend on whether the item was
found in the Wells Fargo ACH history database and the
original trace and return options used by your company.

Entry detail record example — all transactions except IAT

File record specifications 23

Entry detail (type 6) record — IAT
No Field Position Length Description
1 Record type 1 1 Always 6.
2 Return transaction 2-3 2 Indicates type of transaction being returned.
code 21 Checking account credit transaction
26 Checking account debit transaction
31 Savings account credit transaction
36 Savings account debit transaction
3 GO ID / receiving 4-12 9 If the item is found in the Wells Fargo history database
DFI ID and the RDFI is located in a foreign country, this field
contains the Wells Fargo gateway operator ID
(391001268).
If the item is found in the Wells Fargo history database
and the RDFI is located in the US, this field contains the
RDFI’s routing/transit number from the original
transaction.
If the item is not found in history, this field contains the
routing/transit number of the financial institution
sending the return.
4 Number of 13-16 4 Indicates the number of addenda records in the original
addenda records transaction (0007 or 0008, for example).
5 Reserved 17-29 13 Blank (space-filled).
6 Amount 30-39 10 Amount of the original transaction.
For NOCs, this field is zero-filled.
For returns:
• If the foreign exchange indicator field in the
company/batch header record is VF, this field is
zero-filled.
• If the foreign exchange indicator field in the
company/batch header record is FV or FF, this field
is the transaction amount in the currency specified in
the ISO originating currency code field in the
company/batch header record.
7 Foreign receiver’s 40-74 35 Receiver’s account number.
account number If the receiving country uses a combined bank
ID/account number, such as the CLABE number for
Mexico or the international routing code for Belgium and
the Netherlands, this field contains that entire number.
8 Reserved 75-76 2 Blank
9 OFAC screening 77 1 Indicates whether the gateway operator found a
indicator potential block party during OFAC screening.
0 Potential blocked party not found during screening
1 Potential blocked party found during screening
10 Secondary OFAC 78 1 Secondary OFAC screening indicator from the entry
screening detail record for the original transaction.
indicator
11 Addenda record 79 1 Always 1 to indicate that an addenda record follows this
indicator record.

File record specifications 24

 12 Trace number 80-94 15 Contents of this field depend on whether the item was
found in the Wells Fargo ACH history database and
whether your company uses the original trace option.
If the item is not found in the history database, this field
is the trace number as provided by the financial
institution that sent the return.
If the item is found in the history database and you use
the original trace option, this field is the trace number
assigned by your company for the original transaction.
If the item is found in the history database and you do
not use the original trace option, this field is the trace
number assigned by Wells Fargo when processing the
originated item.
Note: This is usually the same as the trace number
assigned by Wells Fargo when processing the originated
item, but we recommend that you use the original entry
trace number field in the addenda record as the trace
number for the originated item.

Entry detail record example — IAT

File record specifications 25

IAT addenda records
Overview
IAT transactions include seven mandatory addenda records and can include up to four additional
addenda records. IAT addenda records are included prior to the 798 or 799 record for a transaction.
For IAT returns:
• Returns for international IAT transactions will include the 710-716 addenda records in your
returns data files and returns reports.
• Returns data files for domestic IAT transactions will include the 710-716 addenda records, but
your returns reports for domestic IAT transactions will not include any addenda records.
• If you originate IAT transactions with a 717 or a 718 addenda record, they will not be included in
your returns.
For IAT NOCs:
• You can receive an NOC only if the transaction is to an RDFI located within the territorial jurisdiction
of the United States (a U.S. RDFI). NOCs are not generated for IAT transactions to an RDFI in
another country.
• Whether you receive addenda records for NOCs depends on the option you select at setup.

First mandatory IAT addenda (type 710) record

Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 10.
3 Transaction type 4-6 3 Req Indicates the type of transaction.
code For check conversion transactions, this field
includes the applicable SEC code (ARC, BOC, POP,
or RCK).
For payments to Spain, valid transaction types are
DEP and SAL. SAL must be used for payroll
deposits.
For all payments to Mexico, Europe (except Spain),
Australia, and New Zealand, the transaction type is
DEP.
The following type codes are used for Canadian
credit transactions:
ANN Annuity
PEN Pension payment
DEP Deposit payment
SAL Salary payment
The following type codes are used for Canadian
debit transactions:
INS Insurance payment
PAD Corporate debit (only use if you send
transactions via our gateway operator)

File record specifications 26

4 Foreign payment 7-24 18 See If the foreign exchange indicator field in the
amount desc company/batch header record is FV, this field is
zero-filled.
If the foreign exchange indicator field in the
company/batch header record is VF or FF, this field
is the transaction amount in the currency specified
in the ISO destination currency code field in the
company/batch header record.
5 Foreign trace 25-46 22 n/a Blank (space-filled).
number
6 Receiving company 47-81 35 Req Name of the receiver (individual or company) of
name/individual the transaction.
name
7 Reserved 82-87 6 n/a Blank (space-filled).
8 Entry detail 88-94 7 Req Same as positions 88-94 of the trace number in the
sequence number related entry detail record.

Type 710 addenda record example

Second mandatory IAT addenda (type 711) record

Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 11.
3 Originator name 4-38 35 Req Originating company’s name.
4 Originator street 39-73 35 Req Street address portion of the originating
address company’s address.
5 Reserved 74-87 14 n/a Blank (space-filled).
6 Entry detail 88-94 7 Req Same as positions 88-94 of the trace number in
sequence number the related entry detail record.

Type 711 addenda record example

File record specifications 27

Third mandatory IAT addenda (type 712) record
Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 12.
3 Originator city and 4-38 35 Req City and state/province for the originating
state/province company’s address. Includes an asterisk (*)
after the city and a backslash (\) after the
state/province.
Note: If there is no data for the city element,
the field includes an asterisk, the state/province
element, and then the backslash. If there is no
data for the state/province element, the field
includes the city element followed by the
backslash.
4 Originator country 39-73 35 Req Country and postal code for the originating
and postal code company’s address. Includes an asterisk (*)
after the country and a backslash (\) after the
postal code.
Note: If there is no data for the country
element, the field includes an asterisk, the postal
code element, and then the backslash. If there is
no data for the postal code element, the field
includes the country element followed by the
backslash.
5 Reserved 74-87 14 n/a Blank (space-filled).
6 Entry detail 88-94 7 Req Same as positions 88-94 of the trace number in
sequence number the related entry detail record.

Type 712 addenda record example

File record specifications 28

Fourth mandatory IAT addenda (type 713) record
Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 13.
3 Originating DFI 4-38 35 Req Always WELLS FARGO BANK.
name
4 Originating DFI ID 39-40 2 Req Indicates the type of ID provided in the next
qualifier field. Always 01 to indicate that the next field is
an ABA routing/transit number.
5 Originating DFI ID 41-74 34 Req Always 091000019.
6 Originating DFI 75-77 3 Req Always US and a space.
branch country
code
7 Reserved 78-87 10 n/a Blank (space-filled).
8 Entry detail 88-94 7 Req Same as positions 88-94 of the trace number in
sequence number the related entry detail record.

Type 713 addenda record example

File record specifications 29

Fifth mandatory IAT addenda (type 714) record
Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 14.
3 Receiving DFI 4-38 35 Req Name of the receiving depository financial
name institution.
4 Receiving DFI ID 39-40 2 Req Indicates the type of ID provided in the next
qualifier field.
01 National clearing system number
02 SWIFT BIC (bank identifier code)
5 Receiving DFI ID 41-74 34 Req Bank ID for the RDFI. Must be the type indicated
in the previous field.
If the receiving country uses a combined bank
ID/account number, such as the CLABE number
for Mexico or the international routing code for
Belgium and the Netherlands, this field includes
that entire number.
6 Receiving DFI 75-77 3 Req Two-character ISO 3166 country code identifying
branch country where the RDFI branch for the receiver’s account
code is located, followed by a trailing space.
7 Reserved 78-87 10 n/a Blank (space-filled).
8 Entry detail 88-94 7 Req Same as positions 88-94 of the trace number in
sequence number the related entry detail record.

Type 714 addenda record example

File record specifications 30

Sixth mandatory IAT addenda (type 715) record
Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 15.
3 Receiver ID 4-18 15 Opt ID number for the receiver, such as a customer
number.
4 Receiver street 19-53 35 Req Street portion of the receiver’s address.
address
5 Reserved 54-87 34 n/a Blank (space-filled).
6 Entry detail 88-94 7 Req Same as positions 88-94 of the trace number in
sequence number the related entry detail record.

Type 715 addenda record example

File record specifications 31

Seventh mandatory IAT addenda (type 716) record
Req/
No Field Position Length Description
opt
1 Record type code 1 1 Req Always 7.
2 Addenda type code 2-3 2 Req Always 16.
3 Receiver city and 4-38 35 Req City and state/province for the receiver’s
state/province address. Includes an asterisk (*)after the city
and a backslash (\) after the state/province.
Note: If there is no data for the city element,
the field includes an asterisk, the state/province
element, and then the backslash. If there is no
data for the state/province element, the field
includes the city element followed by the
backslash.
4 Receiver country 39-73 35 Req Country and postal code for the receiver’s
and postal code address. Includes an asterisk (*)after the
country and a backslash (\) after the postal
code.
Note: If there is no data for the country
element, the field includes an asterisk, the postal
code element, and then the backslash. If there is
no data for the postal code element, the field
includes the country element followed by the
backslash.
5 Reserved 74-87 14 n/a Blank (space-filled).
6 Entry detail 88-94 7 Req Same positions 88-94 of the trace number in the
sequence number related entry detail record.

File record specifications 32

NOC/return (798 and 799) records
No Field Position Length Description
1 Record type 1 1 Always 7.
2 Addenda type code 2-3 2 Indicates the type of return.
98 Notification of change (NOC)
99 All other returns
3 Return reason code 4-6 3 Return reason codes are listed in Codes.
4 Original entry trace 7-21 15 Contents of this field depend on whether the item
number was found in the Wells Fargo ACH history database
and the original trace and return options used by
your company.
5 Date of death 22-27 6 Date as YYMMDD, if applicable (date of death return
or Wells Fargo-generated NOC).
Usually blank-filled if not applicable to this return.
Note: This field includes information as provided by
the receiving depository financial institution (RDFI)
and may contain zeros or other values that do not
relate to the return reason code.
6 Original RDFI 28-35 8 Routing/transit number of the receiving depository
R/T number financial institution (RDFI) from the original entry.
7 Addenda information 36-79 44 Required if return reason code is R11 or R17.
For a notification of change (NOC), this field
contains “change” information:
NOC
code Description
C01 Incorrect DFI Account number. The correct
account is in positions 36-52.
C02 Incorrect routing/transit number. The
correct R/T is in positions 36-44.
C03 Incorrect routing/transit number and
incorrect account number. The correct R/T
is in positions 36-44, three spaces are in
positions 45-47, and the correct account
number is in positions 48-64.
C05 Incorrect transaction code. The correct
trancode is in positions 36-37.
C06 Incorrect account number and incorrect
transaction code. The correct account
number is in positions 36-52, three spaces
are in positions 53-55, and the correct
trancode is in positions 56-57.
C07 Incorrect routing/transit number, incorrect
account number, and incorrect transaction
code. The correct R/T is in positions 36-44,
the correct account number is in positions
45-61 and the correct trancode is in
positions 62-63.
8 Return trace number 80-94 15 Contents of this field depend on whether the item
was found in the Wells Fargo ACH history database
and the original trace and return options used by
your company.

File record specifications 33

Addenda record example

Company/batch control (type 8) record

No Field Position Length Description
1 Record type 1 1 Always 8.
2 Service class code 2-4 3 Always 200.
3 Entry/addenda 5-10 6 Indicates the number of entry detail (type 6)
count records and addenda (type 7) records in the batch.
For a batch that includes one entry detail record
and one addenda record, for example, this field
would be 000002.
4 Entry hash 11-20 10 The hash field is normally calculated by adding the
routing/transit numbers from positions 4-11 in all
entry detail records in the batch.
5 Total batch debit 21-32 12 If the return item in this batch is a debit, this field
entry dollar amount is the debit amount, right-justified and zero-filled.
6 Total batch credit 33-44 12 If the return item in this batch is a credit, this field
entry dollar amount is the credit amount, right-justified and zero-filled.
7 Company ID 45-54 10 The same company ID used in the company/batch
header record for this batch.
8 Message 55-73 19 Blank (space-filled).
authentication code
9 Blank 74-79 6 Blank (space-filled).
10 Well Fargo R/T 80-87 8 Wells Fargo routing/transit number. Always
number 09100001.
11 Batch number 88-94 7 The same batch number used in the company/batch
header record for the batch with a leading zero
added (this field is seven digits in length, while the
batch number in the company/batch header record
is only six digits in length).

Company/batch control record example

File record specifications 34

File control (type 9) record
Standard file control record
No Field Position Length Description
1 Record type 1 1 Always 9.
2 Batch count 2-7 6 Number of batches in the file. Right-justified and
zero-filled.
3 Block count 8-13 6 Total number of records in the file, divided by 10
and rounded up. Right-justified and zero-filled.
All records in the file, including this one, are
included in the block count.
Example: a file with 95 records would have a block
count of 000010.
4 Entry/addenda 14-21 8 Total number of entry detail and addenda records in
record count the file. Right-justified and zero-filled.
5 Entry hash total 22-31 10 Sum of entry hash fields in all company/batch
control records. Leading zeros are added as needed,
and overflow out of the high order (leftmost)
position is ignored if the sum is more than ten
digits.
6 Total file debit entry 32-43 12 The sum of entry detail debit totals within the file.
amount Right-justified and zero-filled.
7 Total file credit entry 44-55 12 The sum of entry detail credit totals within the file.
amount Right-justified and zero-filled.
8 Filler (spaces) 56-94 39 Spaces to make the record 94 characters.

Blocking file control records (optional)

You can receive optional blocking file control records, which consist of all 9s.
File control record example

File record specifications 35

Sample data files

File with transaction data

Below is an example of an ACH return item file. The file contains five batches, each with one return item.
Note: The line above the sample file is a “ruler” to help show the position of fields in each record.
123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+1234
A 1011234567890 0910000190909140559A094101ABC COMPANY WELLS FARGO BANK
B 5200ABC COMPANY 2222222222PPDPREMIUM SEP 120909120001091000017000001
C 6260515012990123456 00000018130001234 BOB B BROWN SR 1091000010111111
D 799R08091000010111111 05150129 091000010001234
E 820000000200051501290000000018130000000000002222222222 091000010000001
5200ABC COMPANY (R) 2222222222PPDPREMIUM SEP 120909120001091000019000002
6262642790914321123443 00000050000001333 RONALD REED 1091000010222222
799R01091000010222222 26427909 091000010002345
820000000200264279090000000050000000000000002222222222 091000010000002
5200ABC COMPANY 1111111111PPDPREMIUM SEP 120909120001091000017000003
6260841006385656565 00000039920001357 SHERYL S SMITH 1091000010333333
799R07091000010333333 08410063 091000010003456
820000000200084100630000000039920000000000001111111111 091000010000003
5200ABC COMPANY 1111111111PPDPREMIUM SEP 120909120001091000017000004
6261211330050120120120 00000000000001579 WAYNE WILSON 1091000010444444
798C02091000010444444 12113300121140218 091000010004567
820000000200121133000000000000000000000000001111111111 091000010000004
5200ABC COMPANY 2222222222PPDPREMIUM SEP 120909120001091000017000005
6260653054369898989898 00000000000002345 GEORGE GONZALES 1091000010555555
798C05091000010555555 0653054337 091000010005678
820000000200065305430000000000000000000000002222222221 091000010000005
F 9000005000003000000100058631944000000010805000000000000

Key for the sample file with transaction data:

A File header (type 1) record.
B Company/batch header (type 5) record for the first batch in the file.
C Entry detail (type 6) record.
D Addenda (type 7) record.
E Company/batch control (type 8) record for the first batch in the file.
F File control (type 9) record.

Sample data files 36

File with transaction data — IAT
The following is an example of a return item file with one IAT return and one IAT NOC.
Note: The line above each sample file is a “ruler” to help show the position of fields in each record.
123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+1234
1011234567890 0910000190909250559A094101ABC COMPANY WELLS FARGO BANK
5200 FV2123456 GB2222222222IATPAYMENT USDEUR0909220001091000017000001
6213910012680007 000005505000000001288 1091000010000001
710DEP000000000000000000 EUROSUPPLY INC 0000001
711ABC CORPORATION 1234 MAIN STREET 0000001
712ANYTOWN*CA\ US*99999\ 0000001
A 713WELLS FARGO BANK 01091000019 US 0000001
714XYZ BANK 02LOYDGB21008 GB 0000001
715101202303 12345B MAPLETON PLACE 0000001
716LONDON*\ GB*SE50AN\ 0000001
B 799R02091000010000006 39100126 091000010001234
820000000900391001260000000000000000000550502222222222 091000010000001
C 5200IATCOR FV2123456 GB2222222222CORPAYMENT USDEUR0909220001091000017000002
6213910012680007 000000000000000001289 1091000010000002
D 798C01091000010000012 391001260000001299 091000010002345
820000000900391001260000000000000000000000002222222222 091000010000002
9000001000002000000090039100126000000000000000000055050

A Addenda records For IAT transactions, addenda records 710-716 are reproduced here.
B 799 record 799 record for an IAT return.
C 5 record for an NOC For IAT NOCs, includes IATCOR in positions 5-10 and COR in positions 51-
53.
D 798 record 798 record for an IAT NOC.

File with no transactions (empty file)

Below is an example of an ACH return item file with no transactions (also called an empty file).
Note: If you cancel the ACH origination service, your origination file/company ID will be deleted after
60 days. At that point, you will no longer receive empty return item files.
Note: The line above the sample file is a “ruler” to help show the position of fields in each record.
123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+1234
A 10112345678 0910000190909140528A094101WELLS FARGO WELLS FARGO BANK
B 9000000000001000000000000000000000000000000000000000000

Key for the sample empty file:

A File header (type 1) record.
Note: In an empty file, the file ID field is usually an eight-digit number that is part of the batch
ID you use for transmissions and is not your usual file ID.
B File control (type 9) record.

Sample data files 37

Exception reports
The return item file provides information for ACH returns and notifications of change (NOCs) in data file
format, but you may also receive exception reports in the following traditional reports. For samples of
these reports, refer to the ACH User Guide.
Note: Dishonored returns, contested/corrected dishonored returns, and refused NOCs are not allowed
for IAT transactions.
The Treasury Information Reporting ACH Return/NOC report lists information for return items
and notifications of change.
The exception report cover page summarizes the exceptions for a particular ACH file and company
ID.
The Return Item report provides an overview of the day’s returns. It lists all of the day’s return items
for each ACH file. All items in the report will be credited or debited to your account as of the effective date
shown on the cover page.
The Redeposited Item report (for customers using the Automatic Redeposit service) lists all return
items redeposited for the day.
The Dishonor Return Item report lists all return items that have been automatically dishonored by
Wells Fargo. Reasons that Wells Fargo automatically generates a dishonored return include:
• A return that is a duplicate of a previous return.
• A return containing a trancode mismatch.
The Contested/Corrected Dishonor Return report lists the day’s contested and corrected
dishonored returns and provides a detailed history for each item.
The Notification of Change report lists all NOCs processed during the day. The report lists the
addenda record, which describes the correction, for each item.
The Refused Notification of Change report lists the day’s refused NOCs and provides a detailed
history for each item.
The Prenote Return Item report lists the day’s returned prenotes.
The Administrative Returns Adjustment report lists converted check items which are returned
and processed using Check Conversion Administrative Returns. This report is only generated if your
company uses the Check Conversion Administrative Returns option for converted checks.
The Customer Activity Report (CAR) lists settlement information, adjustment detail, and a summary
of return activity.
The Return Reason Analysis report provides a monthly analysis comparing your origination activity
to your returns. The report is organized by return reason code and presents grand totals for each return
category, such as returns, NOCs, and dishonored returns.
The Recap report summarizes returns, redeposits, dishonored returns, and NOCs by volume and
amount. This report is only available if you receive traditional exception reports electronically (through
the Commercial Electronic Office portal, by Secure Document Delivery, or by transmission).

Exception reports 38
Codes

Overview
This section lists reason codes that can be included in a detail record to indicate why an item has been
returned. The codes are divided into several groups:
• General return reason codes
• Return reason codes used by ACH operators
• Dishonored return reason codes
• Contested/corrected dishonored return reason codes
• Notification of change (NOC) reason codes
• Refused notification of change reason codes

Return reason codes — general

Codes shown in teal are designated by NACHA as administrative debit returns and are subject to a
NACHA-specified administrative return rate threshold.
Codes shown in red are designated by NACHA as unauthorized returns and are subject to a NACHA-
specified unauthorized return rate threshold.
For more information about NACHA-specified thresholds for administrative debit returns and
unauthorized returns, refer to the ACH Rules — Corporate Edition.
R01 Insufficient funds in receiver’s account (debit transactions only)
R02 Receiver’s account is closed
R03 No account on file (RDFI is unable to locate account); not used for ARC, BOC, or POP item
without individual name field
R04 Invalid account number
R05 Unauthorized debit to consumer account (SEC code CCD, CTX, IAT)
R06 Returned at Wells Fargo’s request
R07 ACH authorization has been revoked by the receiver (adjustment entry)
R08 Payment on this item has been stopped
R09 Insufficient collected funds in the account being charged (uncollected)
R10 Customer advises not authorized (SEC consumer codes except ARC, BOC, IAT, POP); notice
not provided, improper source document, amount not accurately obtained from source
document
R11 Check truncation return (specify)
R12 Account sold to another financial institution
R14 Representative payee deceased or cannot continue in that capacity
R15 Beneficiary or account holder other than representative payee deceased
R16 Account funds frozen or item returned at OFAC request
R17 Item returned because of invalid data; refer to addenda for information
R20 Account does not allow ACH transactions or limit for transactions has been exceeded
R21 Invalid company identification (SEC code CIE)

Codes 39
R22 Invalid individual ID (SEC code CIE, MTE)
R23 Credit entry refused by receiver
R24 Duplicate entry
R29 Corporate customer advises not authorized
R31 Permissible return entry (SEC code CCD, CTX)
R33 Return of item (SEC code XCK)
R37 Source document presented for payment (SEC code ARC, BOC, POP)
R38 Stop payment on source document (SEC code ARC, BOC)
R39 Improper source document (SEC code ARC, BOC, POP)
R40 Return of item by government agency (SEC code ENR)
R41 Invalid transaction code (SEC code ENR)
R42 Routing/transit number check digit error (SEC code of ENR)
R43 Invalid account number (SEC code of ENR)
R44 Invalid individual ID (SEC code ENR)
R45 Invalid individual name or company name (SEC code ENR)
R46 Invalid representative payee indicator code (SEC code ENR)
R47 Duplicate enrollment (SEC code ENR)
R50 State law affecting RCK acceptance (SEC code RCK)
R51 Item is ineligible, notice not provided, signature not genuine, or original item altered for
adjustment entry (SEC code RCK)
R52 Stop payment on item (SEC code RCK)
R53 Item and ACH entry presented for payment (SEC code RCK)
R80 IAT entry coding error (SEC code IAT)
R81 Non-participant in IAT program (SEC code IAT)
R82 Invalid foreign RDFI identification (SEC code IAT)
R83 Foreign RDFI unable to settle (SEC code IAT)
R84 IAT entry not processed by gateway operator (SEC code IAT)
R85 Incorrectly coded outbound international payment (SEC code IAT)
R94 Check Conversion Administrative Return item was processed and resubmitted as a photocopy
R95 Check Conversion Administrative Return item was processed as MICR-Split and resubmitted
as a PAC (pre-authorized check)
R97 Check Conversion Administrative Return item was processed and resubmitted with corrected
dollar amount
R98 Indicates a returned PAC (pre-authorized check); RDFI provided a text reason and indicated a
new account number on the PAC itself
R99 Indicates a returned PAC (pre-authorized check); RDFI provided a text reason on the PAC
itself for which there is no equivalent ACH return reason code

Codes 40
Return reason codes used by ACH operators
R13 Invalid ACH routing number
R18 Improper effective date
R19 Amount error: a prenote’s amount is not zero, or a non-prenote item’s amount is zero;
amount is greater than $25,000 (SEC code ARC, BOC, POP)
R25 Addenda record error
R26 Mandatory field error
R27 Trace number error
R28 Routing/transit number check digit error
R30 RDFI not participant in check truncation program
R32 RDFI non-settlement
R34 Limited participation ODFI
R35 Return of improper debit entry
R36 Return of improper credit entry

Dishonored return reason codes

R61 Misrouted return — RDFI for original entry has placed incorrect routing/transit number in
RDFI identification field
R62 Return of erroneous or reversing debit
R67 Duplicate return — Wells Fargo received more than one return for an entry
R68 Untimely return — return was not sent within established timeframe
R69 Field errors. One or more of the following codes is included in the addenda information field
to indicate the type of incorrect information in the return; for multiple errors, codes are
separated by an asterisk (01*03, for example)
01 Incorrect RDFI account — account number for return is different than original entry
02 Incorrect trace — trace number for return is different than original entry
03 Incorrect amount — amount for return is different than original entry
04 Incorrect individual ID — individual ID for return is different than original entry
05 Incorrect transaction code — transaction code for return is different than original entry
06 Incorrect company ID — company ID for return is different than original entry
07 Incorrect effective date — effective date in return is different than original entry
R70 Permissible return entry not accepted / not requested by ODFI
C96 Check Conversion Administrative Return dishonor (dollar amount will be zero)

Codes 41
Contested/corrected dishonored return reason codes
R71 Misrouted dishonored return — Wells Fargo placed incorrect routing/transit number in the
RDFI identification field
R72 Untimely return — dishonored return not sent within established timeframe
R73 Timely original return — RDFI certifies that original return entry was sent within established
timeframe for original returns
R74 Corrected return — RDFI is correcting a previous return entry that was dishonored because it
contained incomplete or incorrect information
R75 Original return not a duplicate
R76 No errors found
R77 Non-acceptance of R62 dishonored return

Notification of change (NOC) reason codes

C01 Incorrect account number
C02 Incorrect routing/transit number
C03 Incorrect routing/transit number and incorrect account number
C05 Incorrect transaction code
C06 Incorrect account number and incorrect transaction code
C07 Incorrect routing/transit number, account number, and transaction code
C08 Incorrect foreign RDFI identification (SEC code IAT)
C09 Incorrect individual ID or receiver ID
C13 Addenda format error
C14 Incorrect SEC code for outbound international ACH transaction
C99 Converted to MICR draft (check conversion items)

Note: For reason code C96, see Error! Reference source not found..

Refused notification of change reason codes

C61 Misrouted NOC
C62 Incorrect trace number
C63 Incorrect company ID
C64 Incorrect individual ID
C65 Incorrectly formatted corrected data
C66 Incorrect discretionary data
C67 Routing/transit number not from original entry
C68 Account number not from original entry
C69 Incorrect transaction code

Codes 42
Exception handling quick reference
Exception type What Wells Fargo does What you should do
Reject (rejected when • Notifies your company • Review your input source
Wells Fargo processes • Identifies item via reject • If needed, contact receiver
file) reporting (especially for payroll)
• Submit new, corrected entry or (if
needed) proceed outside ACH
system
Prenote return Identifies item via return • Review report
reporting • If needed, contact receiver
• Modify ACH database
• Submit new, corrected prenote
entry, if needed
Debit return for • Identifies item on redeposited No action required; if needed, update
insufficient or uncollected item reports your internal systems to indicate that
funds — automatic • Charges your company the item was returned as unpaid
redeposit option 1, first account for return on date
return or automatic return is received
redeposit option 2, first or • Credits your company account
second return for return on date redeposit is
effective dated
Debit return for • Identifies item on return item • Inform receiver that there are
insufficient or uncollected reports as retired redeposit insufficient or uncollected funds
funds — automatic • Charges your company • Update your accounts receivable
redeposit option 1, second account for the return on date and ACH database, if appropriate
return or automatic return is received
redeposit option 2, third
return
Other credit or debit • Identifies item on return item • Identify reason for return
returns reports • Match it with original entry
• Charges or credits your • Decide whether to redeposit,
company account for return dishonor, submit new corrected
entry, contact receiver, and/or
proceed outside ACH system
• Update ACH database, if
appropriate
Dishonored return — • Identifies item on dishonored No action required, but be aware that
automatic dishonor return item reports any dishonor may be contested or
service • Charges or credits your corrected
company account for return
• Charges or credits company
account for dishonor
Requested dishonored Charges or credits your company • Decide whether return is untimely,
return account for dishonor incorrect, or does not belong to you
• If so, call Wells Fargo with your
instructions at (800) 745-2426,
option 2

Exception handling quick reference 43

Exception type What Wells Fargo does What you should do
Contested/ corrected • Identifies item on return item • Review and decide if correction is
dishonored return reports and contested/ acceptable
corrected dishonored return • If acceptable, take normal action
reports for returns
• Charges or credits your • If contested or if correction is not
company account for return acceptable, handle outside ACH
system
Notification of Change Identifies item on NOC reports • Identify reason for NOC
(NOC) • Match it with original entry
• Determine whether to make change
on your ACH database or refuse the
NOC
Note: If you use the Perfect NOC®
service, Wells Fargo processes these
for you.
Refused NOC — automatic Identifies item on refused NOC No action required (be prepared for
reports RDFI’s corrected NOC)
Refused NOC — requested • Decide whether NOC is inaccurate
• If so, call Wells Fargo with your
instructions at (800) 745-2426,
option 2
OR
Contact RDFI directly

Exception handling quick reference 44