Skip to content

ACH Standard Entry Class code

CTX SEC code: Corporate Trade Exchange

Business-to-business payment with up to 9,999 addenda of EDI remittance data.

What CTX is for

  • Business-to-business payments with remittance data: up to 9,999 addenda records carrying ANSI ASC X12 data (such as an 820 payment order/remittance advice) or UN/EDIFACT syntax.
  • Used when one payment settles many invoices and the receiver needs the detail to apply it.

Business (non-consumer) accounts on both sides.

Authorization

As for CCD: a trading partner agreement between the Originator and the business Receiver that binds the Receiver to the Rules.

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 and credits.

Addenda on a forward entry: type 05, up to 9,999 per entry. Returns (addenda type 99) and Notifications of Change (type 98) follow their own layouts whatever the SEC code.

Returns

As for CCD: R29 within 2 banking days for an unauthorized debit, R31 after that with the ODFI’s agreement, R05 if it reaches a consumer account.

Common mix-ups

  • CTX or CCD+? CCD+ carries one addenda record of free text; CTX carries the full EDI remittance across up to 9,999 records.

Where CTX 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 CTX 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 CTX from code or an AI agent

REST · GET · no key
curl -s 'https://payopskit.com/api/v1/codes/CTX?set=ach-sec'
MCP · tools/call · lookup_payment_code
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "lookup_payment_code",
    "arguments": {
      "code": "CTX",
      "set": "ach-sec"
    }
  }
}
Response (JSON)
{
  "code": "CTX",
  "set": "ach-sec",
  "found": true,
  "matches": [
    {
      "set": "ach-sec",
      "code": "CTX",
      "name": "Corporate Trade Exchange",
      "description": "Business-to-business payment with up to 9,999 addenda of EDI remittance data.",
      "details": {
        "direction": "both",
        "addendaTypes": "05",
        "minAddenda": 0,
        "maxAddenda": 9999
      }
    }
  ]
}

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.