ACH return reason code
R11 return code: Customer Advises Entry Not in Accordance with the Terms of the Authorization
The consumer authorized the Originator, but this debit doesn’t follow the terms of that authorization (wrong amount or date, for example).
What R11 means
R11 is the return reason code Customer Advises Entry Not in Accordance with the Terms of the Authorization
. The consumer authorized the Originator, but this debit doesn’t follow the terms of that authorization (wrong amount or date, for example).
Consumer accounts only; for a non-consumer (corporate) account use R29.
It is sent by the RDFI as a return entry: the original entry goes back to the ODFI with an addenda record carrying R11, and the ODFI passes the return on to the Originator.
Typical causes
- The Receiver authorized the Originator, but the debit was for a different amount.
- It was debited earlier than the authorization allowed, or otherwise departs from its terms.
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).
What the Originator can do next
- Correct the error and send a new entry that matches the authorization. The Rules allow this without a new authorization when the new entry goes out within 60 days of the R11 return’s settlement date.
- It counts toward the Originator’s unauthorized return rate, which Nacha reviews above 0.5% of debits.
How R11 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.
| Positions | Field | In an R11 return |
|---|---|---|
| 1 | Record Type Code | 7 (addenda) |
| 2–3 | Addenda Type Code | 99 (return) |
| 4–6 | Return Reason Code | R11 |
| 7–21 | Original Entry Trace Number | Trace number of the entry being returned |
| 22–27 | Date of Death | YYMMDD for R14 and R15; blank otherwise |
| 28–35 | Original Receiving DFI Identification | First 8 digits of the original entry’s RDFI routing number |
| 36–79 | Addenda Information | Free text from the RDFI |
| 80–94 | Trace Number | The 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 R11 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.
curl -s 'https://payopskit.com/api/v1/codes/R11?set=ach-return'{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "lookup_payment_code",
"arguments": {
"code": "R11",
"set": "ach-return"
}
}
}{
"code": "R11",
"set": "ach-return",
"found": true,
"matches": [
{
"set": "ach-return",
"code": "R11",
"name": "Customer Advises Entry Not in Accordance with the Terms of the Authorization",
"description": "The consumer authorized the Originator, but this debit doesn’t follow the terms of that authorization (wrong amount or date, for example).",
"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": "Consumer accounts only; for a non-consumer (corporate) account use R29.",
"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=R11 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.