Standard Entry Class Codes - SEC

Use and Authorization Requirements

What is an ACH SEC Code? The Nacha Operating Rules identify payment types by the type of Receiver, corporate or consumer.  The Standard Entry Class (SEC) code appears in the ACH record format of each ACH entry processed through the ACH Network. The SEC code identifies the specific record layout that is to be used to carry the payment and payment-related information. On this page we have provided the most common used SEC Codes, their purpose, type of Receiver, and authorization requirements.

In providing ACH origination services to their business clients, many financial institutions will offer different types of Online Cash Management platforms. Some platforms will use the SEC code to define the transaction type and some will use a descriptive word to define a transaction type that translates into the SEC code when the ACH file is created. You will want to consult with your financial institution to have a clear understanding of the transaction types that you are initiating to ensure the correct SEC code is used for the transaction.

Examples of descriptive words used in ACH origination platforms:

Note: International ACH Transactions (IAT) should be used for both business to business and business to consumer transactions when transactions are clearly identified as such according to Rules requirements.

Business to Business Payments and Collections

CCD - Corporate Credit or Debit Entry - Nacha Operating Rules Subsection 2.5.3

A CCD entry is used by an organization (business) to originate a debit or credit entry to an account of an organization (business). A CCD entry can be used to provide payment related information in one addenda record. The CCD addenda record can carry up to 80 characters of payment related information and must be formatted using ANSI ASC X12 at segments. The CCD addenda record is typically used to provide invoice information to the Receiver. The CCD SEC code can be used as a non-monetary (zero dollar) entry that carries payment related information only in the addenda record.

CTX - Corporate Trade Exchange - Nacha Operating Rules Subsection 2.5.5

A CTX entry is used by an organization (business) to originate a debit or credit entry to an account of an organization (business). A CTX entry can be used to provide payment related information in one or more addenda records. The CTX format supports the transfer of multiple addenda records, up to 9,999 records each with 80 characters of payment related data. Information in the CTX addenda record must be formatted as either a syntactically correct ABSI ASC X12 transaction set or a payment related UN/EDIFACT transaction. The CTX addenda record is typically used to provide payment information related to multiple invoices. he CCD SEC code can be used as a non-monetary (zero dollar) entry that carries payment related information only in the addenda record.

In addition to the Nacha Operating Rules, CCD and CTX wholesale credit transactions are governed by Article 4A of the Uniform Commercial Code.

Authorization Requirements for CCD and CTX Entries - Nacha Operating Rules Subsection 2.3.3.1

As with all ACH transactions, an ACH Originator of CCD and CTX entries must obtain the Receiver’s authorization to debit or credit the Receiver’s account. The Nacha Operating Rules do not require the authorization to be in a specific format. The Rules require that the ACH Originator have an agreement with the Receiver that binds the Receiver to the Nacha Operating Rules.

Additional information related to the origination of CCD and CTX entries can be found in the Nacha Operating Rules and Guidelines, Guidelines Chapter 39.

Documents Video Presentation - CCD Entries

CCD PowerPoint Presentation

Business to Consumer (People) Payments and Collections

PPD - Prearranged Payment and Deposit Entries - Nacha Operating Rules Subsection 2.5.12

A PPD entry is used by an organization (business) to originate to the account of a consumer (person) Receiver based on an authorization from the Receiver. The authorization for a debit PPD entry must be in writing, and signed or similarly authenticated by the Receiver. PPD entries can be used for single and recurring payments.

Authorization Requirements for PPD Entries - Nacha Operating Rules Section 2.3

Credit Entries - The ACH Originator may obtain the Receiver’s authorization for PPD credit entries in any manner permitted by applicable legal requirements. The Nacha Operating Rules do not require PPD credit entries. The ACH Originator may obtain an authorization from the Receiver that allows for a debit entry to correct a previously originated credit entry.

Debit Entries - The ACH Originator must obtain from a Receiver of a PPD entry a authorization that meets the following requirements:

  • Must be in writing

  • Must be readily identifiable as an ACH authorization (i.e., “I authorize” or similar)

  • Must have clear and readily understandable terms including:

  • The amount or how the amount is determined

  • Indicate if the authorization is for a single, multiple, or recurring entry

  • The start date and frequency of the debit

  • The date the entry will occur (i.e., 15th of each month, if a weekend or holiday, the next banking day)

  • A method for the Receiver to revoke the authorization (i.e., in writing, email or phone)

  • Receiver’s bank routing number and account number

  • Must be signed or similarly authenticated

Authorization Retention Requirements

  • Must be retained, electronically or in hardcopy format, readily and accurately reproducible, for a period of two years following the termination or revocation of the authorization.

Documents Video Presentation - PPD Entries

PPD PowerPoint Presentation

Business to Consumer (Person) Payments

  • Payment (credit) = Payroll (PPD)

  • Payment (credit) = Prearranged Deposit (PPD)

  • Collection (debit) = Prearranged Payment (PPD)

  • Collection (debit) = Internet Authorized Payment (WEB)

  • Collection (debit) = Telephone Authorized Payment (TEL)

  • Collection (debit) = International ACH Transaction (IAT)

  • Payment (credit) = International ACH Transaction (IAT)

Business to Business Payments

  • Payment (credit) = Company (CCD)

  • Collection (debit) = Company (CCD)

  • Payment (credit) = Vendor (CCD)

  • Payment (credit) = Remittance (CCD)

  • Payment (credit) = Federal Taxes (CCD)

  • Payment (credit) = Corporate Trade Exchange (CTX)

  • Collection (debit) = Corporate Trade Exchange (CTX)

Business to Consumer (People) Payments and Collections

TEL - Telephone-Initiated Entry - Nacha Operating Rules Subsection 2.5.15

A TEL entry is used by an organization (business) to originate to the account of a consumer (person) Receiver based on an authorization from the Receiver. The authorization for a debit TEL entry must be obtained via a telephone call and the Originator must establish and implement commercially reasonable procedures to verify the identity of the consumer. TEL entries can be used for single and recurring payments. A TEL entry may only be used when there is an existing relationship between the organization and the consumer. When there is not an existing relationship between the organization and the consumer, the consumer has to be the one initiating the telephone call.

Authorization Requirements for TEL Entries - Nacha Operating Rules Subsection 2.3.2.2

  • Must be readily identifiable as an ACH authorization (i.e., “I authorize” or similar)

  • Must have clear and readily understandable terms including:

  • The amount or how the amount is determined

  • Indicate if the authorization is for a single, multiple, or recurring entry

  • The start date and frequency of the debit

  • The date the entry will occur (i.e., 15th of each month, if a weekend or holiday, the next banking day)

  • A method for the Receiver to revoke the authorization (i.e., in writing, email or phone)

  • Receiver’s bank routing number and account number

In addition to the requirements above, the Nacha Operating Rules Subsection 2.5.15.3 states that the oral authorization obtained via a telephone call must also provide the consumer as part of the terms of the authorization, a telephone number for consumer inquiries that is answered during normal business hours.

Authorization Retention Requirements

  • Single entries - The Originator must either retain the original or a duplicate audio recording of the consumer’s oral authorization or the original or a copy of the written notice confirming the consumer’s oral authorization for two years from the date of the authorization.

  • Recurring entries - The Originator must retain the original or a duplicate audio recording of the consumer’s oral authorization and evidence that a copy of the authorization was provided to the consumer in compliance with Regulation E for two years from the date of termination or revocation of the authorization.

Documents Video Presentation - TEL Entries

Business to Consumer (People) Payments and Collections

WEB - Internet initiated/Mobile Entry - Nacha Operating Rules Subsection 2.5.17

A WEB entry is used by an organization (business) to originate to the account of a consumer (person) Receiver based on an authorization from the Receiver. The authorization for a debit WEB entry must be obtained via the internet or a wireless network and the Originator must establish and implement commercially reasonable procedures to verify the identity of the consumer. WEB entries can be used for single and recurring payments. WEB credit entries are used to conduct person-to-person transfers (P2P).

Authorization Requirements for WEB Entries - Nacha Operating Rules Subsection 2.3.2.2

  • Must be readily identifiable as an ACH authorization (i.e., “I authorize” or similar)

  • Must have clear and readily understandable terms including:

  • The amount or how the amount is determined

  • Indicate if the authorization is for a single, multiple, or recurring entry

  • The start date and frequency of the debit

  • The date the entry will occur (i.e., 15th of each month, if a weekend or holiday, the next banking day)

  • A method for the Receiver to revoke the authorization (i.e., in writing, email or phone)

  • Receiver’s bank routing number and account number

Authorization Retention Requirements

  • Must be retained, electronically or in hardcopy format, readily and accurately reproducible, for a period of two years following the termination or revocation of the authorization.

Annual Audit Requirements for WEB Debit Entries - Nacha Operating Rules Subsection 2.5.17.3

An Originator of a WEB debit entry must conduct, or have conducted on its behalf, annual audits to ensure that the financial information obtained from Receivers is protected by security practices and procedures that include, at a minimum, the following:

  • Physical security to protect against theft, tampering, or damage

  • Personnel and access controls to protect against unauthorized access and use

  • Network security to ensure secure capture, storage, and distribution

In addition to the annual audit requirement, the Nacha Operating Rules Subsection 2.5.17.4 states that an Originator of a WEB debit entry must establish and implement a commercially reasonable fraudulent transaction detection system to screen WEB entries for potential fraud. The fraudulent transaction detection system must, at a minimum, validate the account to be debited for the first use of such account number and for any subsequent changes to the account number. The use of prenotifications, micro-deposits, or Plaid account validation would satisfy this requirement.

Also, the Originator must establish and implement a commercially reasonable procedure to verify that the routing number used to process a WEB debit entry is valid. This requirement is outlined in the Nacha Operating Rules Subsection 2.5.17.6.

Waiting Period Following Prenotication Entries - Nacha Operating Rules Subsection 2.6.2

An Originator that has originated a prenotification entry to a Receiver’s account may initiate entries to the Receiver’s account as soon as the third banking day following the settlement date of the prenotification entry, provided the Originator has not received a return or notification of change to the prenotification entry. If a return or notification of change is received in response to a prenotification entry by the opening of business on the second banking day following the settlement date of the prenotification, the Originator must not transmit subsequent entries to the Receiver’s account until it has remedied the reason for the return entry or made the correction requested by the notification of entry.

General Rules for Micro-Entries - Nacha Operating Rules Subsection 2.7.1

An Originator may originate one or more micro-entries to a Receiver’s account prior to initiating future credit or debit entries to a Receiver’s account. A credit micro-entry must be in the amount of less than $1.00. One or more debit micro-entries must not exceed, in total, the amount of the corresponding credit micro-entry.

Micro-entry formatting requirements are addressed in the Nacha Operating Rules Subsection 2.7.2; it states that micro-entries must be submitted as a separate batch of entries and contain “ACCTVERIFY” in the Company Entry Description Field of the Company Batch Header Record. The name of the Originator identified in the Company Name Field must reflect the same Originator that will be identified in future entries to the Receiver’s account. Minor variations to the Originator’s name, for accounting or tracking purposes, are acceptable as long as the name of the Originator remains readily recognizable to the Receiver.

The Nacha Operating Rules Subsections 2.7.3 and 2.7.4 address restrictions on transmission of debit micro-entries and waiting period following the origination of micro-entries.

Subsection 2.7.3 states that an Originator that transmits one or more debit micro-entries to a Receiver’s account must simultaneously transmit for settlement, at the same time, one or more credit micro-entries credit micro-entries that, in aggregate value, are equal to or greater than the amount of the debit micro-entry(ies).

Subsection 2.7.4 states that an Originator that originated one or more micro-entries to a Receiver’s account may initiate future entries to the Receiver’s account as soon as the Originator’s process for verifying the amounts of the micro-entries has been completed.

Documents Video Presentation - WEB Entries