Skip to content
PayOps Kit
Donate

ACH Standard Entry Class code

XCK SEC code: Destroyed Check Entry

Debit collecting a check lost or destroyed in transit.

What XCK is for

  • A debit collecting a check that was lost or destroyed in transit (in an accident, for example), using the data captured from it.

The accounts the destroyed checks are drawn on.

Authorization

XCK collects checks their makers already wrote; the Rules set which items qualify and who may originate the entries.

A summary in general terms: the Nacha Operating Rules set the exact requirements, and Regulation E adds its own for consumer accounts.

Debits, credits and addenda

Debits only. A credit sent as XCK is returned R36.

Addenda on a forward entry: none on the forward entry. Returns (addenda type 99) and Notifications of Change (type 98) follow their own layouts whatever the SEC code.

Returns

An XCK entry can be returned with R33 within 60 calendar days.

Common mix-ups

  • XCK replaces a check that never arrived; RCK re-presents one that bounced.

Where XCK sits in a NACHA file

The SEC code is a batch-level field: positions 51–53 of the Company/Batch Header record (type 5), so every entry in the batch shares it, and a file that mixes SEC codes puts them in separate batches. The batch header also carries the Company Name, Company Identification and Company Entry Description that Receivers see on their statements.

To read a XCK batch 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 XCK from code or an AI agent

REST · GET · no key
curl -s 'https://payopskit.com/api/v1/codes/XCK?set=ach-sec'
MCP · tools/call · lookup_payment_code
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "XCK",
      "set": "ach-sec"
    }
  }
}
Response (JSON)
{
  "code": "XCK",
  "set": "ach-sec",
  "found": true,
  "matches": [
    {
      "set": "ach-sec",
      "code": "XCK",
      "name": "Destroyed Check Entry",
      "description": "Debit collecting a check lost or destroyed in transit.",
      "details": {
        "direction": "debit",
        "addendaTypes": null,
        "minAddenda": 0,
        "maxAddenda": 0
      }
    }
  ]
}

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

Source: Nacha Operating Rules, Appendix Three (Standard Entry Class codes). The code’s name is the Rules’ own; the rest is this site’s plain-language summary, informational and not a substitute for the Rules or your ODFI agreement.