Skip to content

Return Files

Overview

When an ACH transaction is returned by the receiving bank (e.g., due to insufficient funds, a closed account, or an invalid account number), your bank places a return file on their SFTP server. FiSTWorks lets you browse and download these return files directly from the ACH Drafter. See Return File Management for the full capability overview.

Accessing Return Files

  1. Navigate to ACH Drafter and click the Returns tab.
  2. The page shows your downloaded return files and provides access to browse new files from your bank.

Browsing Bank Files

  1. Click the Browse Bank Files button.
  2. The file browser modal opens.
  3. Select an SFTP profile (bank connection) from the dropdown — this determines which bank's SFTP server to browse.
  4. The system connects to the bank's SFTP server and lists available files in the configured return file directory.
  5. Select the files you want to download and click Download.

Downloaded files appear in the return files table on the Returns tab.

Understanding Return Files

Files from your bank typically contain two different kinds of entries: returns (transactions that were rejected) and NOCs (transactions that went through but need your records updated). Both arrive in the same file but should be handled differently.

Returns (R-codes)

Returns are transactions the receiving bank refused. The money was not delivered, and you usually need to take corrective action — contact the recipient, fix the problem, and resubmit. Common return codes:

Code Reason
R01 Insufficient Funds
R02 Account Closed
R03 No Account / Unable to Locate Account
R04 Invalid Account Number
R08 Payment Stopped
R10 Customer Advises Not Authorized
R29 Corporate Customer Advises Not Authorized

Notifications of Change (NOCs, C-codes)

NOCs are the opposite of returns — the transaction was delivered, but the bank is telling you your records have a detail wrong (account number, routing number, name, etc.) and giving you the corrected value. You are required by NACHA rules to update your records within 6 banking days.

See the NOC Codes reference for the full list of C-codes, what they mean, and what to do about each one.

Inspecting a File

You can upload a return file to the ACH Validator to parse its contents and review the return and NOC entries in detail.

SFTP Profile Configuration

The return file browser uses the Return File Directory configured on your SFTP profile. Make sure this path is set correctly in your bank connection settings:

  1. Go to OrganizationBank Connections.
  2. Edit the SFTP profile.
  3. Set the Return File Directory to the path where your bank places return files.

See Organization Management for more details on configuring SFTP profiles.

Tips

  • Check for return files regularly — most banks make return files available within 1-2 business days.
  • Cross-reference return codes with your original transactions to take corrective action (e.g., update a recipient's account number for R03 returns).
  • Return files are stored in your FiSTWorks account so you can review them later without reconnecting to the bank.