ACH SEC Codes: Complete Reference Guide
Complete guide to all ACH Standard Entry Class (SEC) codes. Learn what PPD, CCD, CTX, WEB, TEL, and every other SEC code means, when to use each, and how they appear in NACHA files.
What Are SEC Codes?
SEC stands for Standard Entry Class. An SEC code is a three-character alphanumeric code placed in the Batch Header Record of every ACH batch. It tells the receiving bank (RDFI) what type of transaction the batch contains and, critically, what rules govern authorization, returns, and consumer protections for the entries in that batch.
SEC codes are defined and maintained by Nacha (the National Automated Clearing House Association), which sets the operating rules for the ACH network. Every ACH entry must belong to a batch with a valid SEC code — there is no "generic" or default option.
Think of the SEC code as a label that answers three questions at once: Who is the receiver (consumer or business)? How was the transaction authorized (written, internet, phone)? What special rules apply (addenda requirements, return windows, check conversion notices)?
Why SEC Codes Matter
Selecting the correct SEC code is not optional — it has direct implications for compliance, returns, and the legal standing of your transactions.
Compliance
Nacha rules require the SEC code to accurately reflect how the payment was authorized. Misclassifying an internet payment as PPD instead of WEB, for example, is a rule violation that can trigger audits and fines.
Authorization Requirements
Each SEC code carries different authorization requirements. PPD needs a signed agreement. WEB requires a secure internet session. TEL requires a recorded or confirmed phone call. Using the wrong code can void your authorization.
Return Rules
Return timeframes differ by SEC code. Consumer SEC codes (PPD, WEB, TEL) allow a 60-calendar-day window for unauthorized return claims. Corporate codes (CCD, CTX) have only a 2-banking-day window for most returns. This materially affects your risk exposure.
Complete SEC Code Reference Table
Below is a comprehensive table of all 15 Standard Entry Class codes currently defined by Nacha. Use this as a quick-reference when building NACHA files or reviewing ACH transactions.
| Code | Full Name | Type | Description | Common Use Cases |
|---|---|---|---|---|
| PPD | Prearranged Payment and Deposit | Consumer | Pre-authorized recurring or one-time debits and credits to consumer accounts. | Payroll direct deposit, mortgage payments, subscription billing, utility auto-pay |
| CCD | Corporate Credit or Debit | Corporate | Business-to-business credit or debit entries authorized by the receiver. | Vendor payments, B2B invoices, corporate cash concentration |
| CTX | Corporate Trade Exchange | Corporate | B2B payments that include addenda records with payment-related information (e.g., ANSI X12 or UN/EDIFACT). | EDI payments, trade payments with remittance data, ERP-integrated B2B payments |
| WEB | Internet-Initiated Entry | Consumer | Debit entries authorized by the consumer via the internet or a wireless network. | E-commerce payments, online bill pay, subscription sign-ups, SaaS billing |
| TEL | Telephone-Initiated Entry | Consumer | One-time debit entries authorized by the consumer over the telephone. | Phone order payments, call center collections, one-time phone-authorized debits |
| POS | Point of Sale | Consumer | Debit entries initiated at an electronic point-of-sale terminal, similar to a debit card transaction. | Retail debit transactions at POS terminals |
| ARC | Accounts Receivable Conversion | Consumer | Converts a consumer check received via U.S. mail or at a drop box into an ACH debit entry. | Converting mailed-in checks to electronic payments, lockbox processing |
| BOC | Back Office Conversion | Consumer | Converts a consumer check received at a point of purchase or manned bill payment location during back-office processing. | Back-office check conversion for retail and bill payment locations |
| POP | Point of Purchase | Consumer | One-time debit entry converting a consumer check at the point of purchase. The original check is voided and returned. | Check conversion at retail checkout counters |
| RCK | Re-presented Check Entry | Consumer | Allows an originator to re-present a returned (bounced) check as an ACH debit, up to two times. | Collecting on NSF checks, bounced check recovery |
| IAT | International ACH Transaction | Both | ACH entries involving a financial agency outside the U.S. Requires additional addenda records with OFAC-screening data. | Cross-border payments, international wire alternatives, foreign vendor payments |
| DNE | Death Notification Entry | Both | Used by federal government agencies to notify depository institutions of the death of a benefit recipient. | Social Security death notifications, federal benefit account updates |
| ENR | Automated Enrollment Entry | Both | Used by depository institutions to transmit enrollment information for direct deposit of government benefits. | Social Security direct deposit enrollment, government benefit sign-ups |
| TRX | Check Truncation Entry | Both | Used for truncated check items processed through the ACH network under check truncation agreements. | Check truncation, image-based check clearing via ACH |
| XCK | Destroyed Check Entry | Both | Used to process destroyed checks through the ACH network when the original check cannot be presented. | Processing checks that were destroyed or lost during collection |
Most Common SEC Codes
While there are 15 SEC codes, four of them account for the overwhelming majority of ACH volume. Here is a deeper look at each.
PPD — Prearranged Payment and Deposit
PPD is the workhorse of consumer ACH. It covers any pre-authorized credit or debit to a personal account. The key requirement is that the consumer has signed a written authorization (physical or electronic) before the first entry is originated. PPD supports both one-time and recurring transactions.
When to use PPD: Payroll direct deposits, recurring mortgage or rent payments, insurance premiums, gym memberships, or any consumer debit authorized via a signed form.
CCD — Corporate Credit or Debit
CCD is the business-to-business equivalent of PPD. It is used for credits or debits between commercial accounts. Authorization can be more flexible — a signed agreement, authenticated electronic authorization, or standing corporate arrangement. CCD entries do not support addenda records.
When to use CCD: Vendor payments, B2B invoice settlements, intracompany cash transfers, franchise fee collections, or any simple corporate payment without remittance detail.
CTX — Corporate Trade Exchange
CTX is similar to CCD but supports one or more addenda records containing payment-related information in ANSI X12 or UN/EDIFACT format. This makes CTX ideal for businesses that need to include remittance detail, invoice references, or EDI data alongside the payment.
When to use CTX: Payments that need attached remittance data, EDI-integrated supply chain payments, or any B2B transaction where the receiver's ERP system needs machine-readable detail to auto-apply the payment.
WEB — Internet-Initiated Entry
WEB covers any consumer debit authorized through the internet or a wireless network. It has specific requirements: the originator must use a commercially reasonable method of authentication, the authorization must be readily identifiable as an internet authorization, and for recurring debits, the consumer must be notified before each subsequent debit or be given a way to revoke.
When to use WEB: E-commerce checkout, SaaS subscription billing, online donation forms, web-based bill pay, or any consumer payment initiated through a web browser or mobile app.
How SEC Codes Appear in NACHA Files
In a NACHA-formatted ACH file, the SEC code occupies positions 51–53 of the Batch Header Record (Record Type 5). Each batch in the file has exactly one Batch Header, and therefore exactly one SEC code that applies to all entries in that batch.
Here is an annotated example of a Batch Header Record with the SEC code highlighted:
5200ACME CORP ACME PAYMENTS 1234567890PPD PAYROLL 260220260220 1021000890000001
^^^
Positions 51-53
SEC Code = PPDBreaking down the relevant portion of the Batch Header:
| Position | Length | Field Name | Example Value |
|---|---|---|---|
| 1–1 | 1 | Record Type Code | 5 |
| 2–4 | 3 | Service Class Code | 200 |
| 51–53 | 3 | Standard Entry Class Code | PPD |
| 54–63 | 10 | Company Entry Description | PAYROLL |
Choosing the Right SEC Code
Follow this decision tree to select the correct SEC code for your ACH transaction:
Step 1: Is the receiver a consumer or a business?
Consumer → Go to Step 2
Business → Go to Step 3
Step 2: How was the consumer payment authorized?
Internet or mobile app? → Use WEB
Telephone call? → Use TEL
Signed form (recurring or one-time)? → Use PPD
At a point-of-sale terminal? → Use POS
Converting a paper check? → Use ARC, BOC, or POP depending on where/when the check was received
Step 3: Does the business payment need remittance data?
Yes, needs addenda records (EDI/remittance detail)? → Use CTX
No, simple credit or debit? → Use CCD
Special cases:
Cross-border transaction? → Use IAT (regardless of consumer/business)
Re-presenting a bounced check? → Use RCK
Frequently Asked Questions
- How many ACH SEC codes are there?
- There are currently 15 Standard Entry Class (SEC) codes defined by Nacha. The most commonly used are PPD, CCD, CTX, and WEB, which cover the vast majority of ACH transactions.
- What is the most common SEC code?
- PPD (Prearranged Payment and Deposit) is the most widely used SEC code. It covers consumer direct deposits, payroll, and pre-authorized bill payments.
- Where does the SEC code appear in a NACHA file?
- The SEC code occupies positions 51 through 53 (three characters) in the Batch Header Record (Record Type 5) of a NACHA file.
- Can I use different SEC codes in the same NACHA file?
- Yes. A single NACHA file can contain multiple batches, and each batch can use a different SEC code. However, all entries within a single batch must share the same SEC code.
- What happens if I use the wrong SEC code?
- Using an incorrect SEC code can result in returns, compliance violations, and potential fines from Nacha. The receiving bank (RDFI) may also reject entries if the SEC code does not match the authorization method used.
Generate NACHA files with the right SEC codes, automatically
BatchPay QB pulls your transactions from QuickBooks and builds compliant NACHA files with the correct SEC codes, batch headers, and formatting. No manual data entry required.
Start Free Trial