Skip to content

ACH return reason code

R05 return code: Unauthorized Debit to Consumer Account Using Corporate SEC Code

A consumer account was debited under a corporate SEC code (CCD or CTX) without the consumer’s authorization.

What R05 means

R05 is the return reason code Unauthorized Debit to Consumer Account Using Corporate SEC Code. A consumer account was debited under a corporate SEC code (CCD or CTX) without the consumer’s authorization.

A debit to a consumer account sent with a corporate SEC code (CCD or CTX) that the consumer did not authorize.

It is sent by the RDFI as a return entry: the original entry goes back to the ODFI with an addenda record carrying R05, and the ODFI passes the return on to the Originator.

A Written Statement of Unauthorized Debit from the Receiver is required for this extended return. Since October 1, 2024 the RDFI must also send the return by the opening of the 6th banking day after it finishes reviewing the signed statement, still inside the 60-day window; check the Rules for details and exceptions.

Typical causes

  • A debit sent as CCD or CTX (business-to-business codes) reached an account the RDFI holds as a consumer account.
  • The consumer did not authorize it — often a sole proprietor or a payer whose personal account was given as the business account.

Return timeframe

Extended return: available to the ODFI by opening of business on the banking day after the 60th calendar day following the settlement date of the original entry.

The extended window needs the Receiver’s Written Statement of Unauthorized Debit: a signed or similarly authenticated statement the Receiver gives the RDFI. The RDFI must have it before returning the entry and keeps it, providing a copy to the ODFI on request. Since October 1, 2024 the RDFI must also send the return by the opening of the sixth banking day after it finishes reviewing the statement, so a return can be due well before the 60 days run out.

Corporate accounts have no 60-day window for unauthorized debits: a business disputes one with R29 within 2 banking days.

Worked example

For an entry that settled on Wednesday, November 25, 2026, the day before Thanksgiving: must be available to the ODFI by opening of business on Monday, January 25, 2027, the banking day after the 60th calendar day (Sunday, January 24, 2027).

Try your own settlement date in the ACH date calculator

What the Originator can do next

  • Stop debiting this account under a corporate SEC code.
  • To debit a consumer account, get a consumer authorization that meets the Rules and use a consumer SEC code such as PPD, WEB or TEL.
  • It counts toward the Originator’s unauthorized return rate, which Nacha reviews above 0.5% of debits.

How R05 appears in a NACHA file

A return is the original entry detail record (type 6) sent back with a return transaction code — 21 or 26 for a checking account, 31 or 36 for savings (21 and 31 return a credit, 26 and 36 a debit) — the original amount, and an addenda record of type 99 that carries the reason. The batch keeps the original entry’s SEC code.

Return addenda record (type 99) with R05
PositionsFieldIn an R05 return
1Record Type Code7 (addenda)
2–3Addenda Type Code99 (return)
4–6Return Reason CodeR05
7–21Original Entry Trace NumberTrace number of the entry being returned
22–27Date of DeathYYMMDD for R14 and R15; blank otherwise
28–35Original Receiving DFI IdentificationFirst 8 digits of the original entry’s RDFI routing number
36–79Addenda InformationFree text from the RDFI
80–94Trace NumberThe return entry’s own trace number

To read a return file record by record, open the file in NACHA Navigator, a free sister site that parses NACHA files in your browser without uploading them.

Look up R05 from code or an AI agent

The code table on this page is the one behind the REST API and the MCP server, so a script or an AI agent gets the same answer as JSON. No key and no account.

REST · GET · no key
curl -s 'https://payopskit.com/api/v1/codes/R05?set=ach-return'
MCP · tools/call · lookup_payment_code
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "R05",
      "set": "ach-return"
    }
  }
}
Response (JSON)
{
  "code": "R05",
  "set": "ach-return",
  "found": true,
  "matches": [
    {
      "set": "ach-return",
      "code": "R05",
      "name": "Unauthorized Debit to Consumer Account Using Corporate SEC Code",
      "description": "A consumer account was debited under a corporate SEC code (CCD or CTX) without the consumer’s authorization.",
      "details": {
        "category": "return",
        "timeframe": "Extended return: available to the ODFI by opening of business on the banking day after the 60th calendar day following the settlement date of the original entry",
        "timeframeKind": "calendar-days",
        "timeframeDays": 60,
        "timeframeFrom": "original-settlement",
        "account": "consumer",
        "accountNote": "A debit to a consumer account sent with a corporate SEC code (CCD or CTX) that the consumer did not authorize.",
        "writtenStatement": true,
        "initiatedBy": "RDFI",
        "note": null,
        "effectiveFrom": null,
        "upcomingChange": null,
        "caveat": "A Written Statement of Unauthorized Debit from the Receiver is required for this extended return. Since October 1, 2024 the RDFI must also send the return by the opening of the 6th banking day after it finishes reviewing the signed statement, still inside the 60-day window; check the Rules for details and exceptions."
      }
    }
  ]
}

The MCP server is at /mcp (Streamable HTTP, no key); the API and MCP docs show how to connect Claude, Cursor or VS Code.

The deadline for a settlement date: GET /api/v1/ach/return-deadline?settlement_date=2026-11-25&code=R05 or the MCP tool ach_return_deadline.

Source: Nacha Operating Rules, Appendix Four (Return Entries). The code’s title is the Rules’ own; the rest is this site’s plain-language summary. It is informational and not a substitute for the Rules, your ACH Operator’s schedule or your ODFI agreement.