R17

File Record Edit Criteria

Your ACH file contains formatting errors or invalid field information that prevents processing.

On This Page
High-Priority Return Code

This ACH return code indicates that your payment file contains formatting errors, missing required fields, or invalid data that doesn't meet NACHA technical standards. Since 2019, R17 has also been used to flag questionable or suspicious transactions, with banks required to include "QUESTIONABLE" in the description when used for this purpose.

Error message: "The entry contains invalid account information or formatting that cannot be processed by the RDFI due to file record edit criteria violations."

What Causes ACH Return Code R17?

The R17 ACH return code means "File Record Edit Criteria" and indicates that your ACH payment file contains formatting errors, missing required fields, or invalid data that prevents the receiving bank from processing the transaction. This is typically a technical issue with how your payment file was structured rather than a problem with the customer's account or funds availability.

In 2019, NACHA expanded the use of R17 to also flag questionable or suspicious transactions. When used for this purpose, the receiving bank must include "QUESTIONABLE" in the addenda information field to differentiate these returns from routine formatting errors. This helps banks identify potentially fraudulent activity while maintaining the original technical use of the code.

Can You Retry R17 Payments?

You can retry R17 payments after identifying and correcting the specific formatting or field errors in your ACH file. For technical formatting issues, fix the file structure and resubmit. However, if the return includes "QUESTIONABLE" in the description, you should investigate the transaction for potential fraud before reprocessing.

Common Causes
  • Missing required fields in ACH file structure
  • Invalid characters in numeric fields (letters where numbers expected)
  • Incorrect account number format or length
  • File doesn't meet NACHA formatting standards
  • Account type mismatch with transaction requirements
  • Key Information
  • Return timeframe: 2 banking days
  • Can retry after correcting file formatting errors
  • Technical issue with file structure, not customer's account
  • May indicate questionable transaction if "QUESTIONABLE" appears in description
  • Usually caused by payment processing software configuration errors
  • How to Respond to an R17 Code

    An R17 return typically indicates technical formatting problems with your ACH file that require correction before resubmitting the transaction.

    When Your Customer's Payment Fails

    • Review the Exact Transaction Details
      Examine the specific field information flagged in the R17 return to identify formatting errors.
    • Check for "QUESTIONABLE" Description
      If present, investigate the transaction for potential fraud before reprocessing.
    • Correct File Formatting Issues
      Fix missing fields, invalid characters, or incorrect data structure in your ACH file.
    • Validate Against NACHA Standards
      Ensure your payment file meets all technical requirements before resubmitting.
    Email Template

    Subject: Payment Processing Issue - Technical Error

    Hi [Customer Name],

    We encountered a technical formatting issue with your recent payment that prevented it from processing successfully. This was due to how our payment file was structured, not any issue with your account.

    We've identified and corrected the formatting problem and will reprocess your payment within the next business day. You don't need to take any action on your end.

    We apologize for any inconvenience and will ensure this technical issue doesn't happen again.

    Thanks,

    [Your Company Name]

    When Your Payment to Vendors Fails

    An R17 return on vendor payments indicates a technical problem with your ACH file formatting rather than any issue with the vendor's account. This requires reviewing and correcting your payment processing setup.

    1. Review the specific field that caused the R17 return in your payment file
    2. Check your ACH file generation software for configuration errors
    3. Validate that all required fields are properly formatted according to NACHA standards
    4. Reprocess the vendor payment after correcting the file structure issues

    Get Unlimited Free ACH Payments

    Get unlimited free ACH transfers, smart retries, and real-time payment visibility with Nickel.

    Free unlimited ACH transfers

    Smart retry scheduling

    Real-time payment visibility