What Is a SEC Code?
Categories: ACH Payments
Categories: ACH Payments
A SEC code — short for Standard Entry Class code — is a three-letter designation that identifies how an ACH transaction was authorized and what type of account it involves. Every ACH payment, whether a credit or a debit, must carry one. The SEC code tells receiving banks, originators, and processors exactly what authorization rules apply, which is why understanding SEC codes ACH payments rely on is essential for any business moving money electronically.
SEC codes are defined and maintained by NACHA, the organization that governs the ACH network in the United States. While the acronym overlaps with the Securities and Exchange Commission, the two have no relationship; in payments, SEC code meaning is entirely tied to authorization type, not securities regulation.
Each SEC code sits inside the NACHA file format, embedded directly in the batch header record of an ACH transaction. The Originating Depository Financial Institution (ODFI) is responsible for including the correct code, while the Originator — the business initiating the payment — must secure the appropriate authorization from the Receiver before the transaction is submitted.
The nature of that authorization depends entirely on which entry class code PPD, CCD, or WEB designation is used, along with whether the transaction is a debit or credit. As a general rule:
Submitting an ACH entry with the wrong standard entry class code can trigger an ACH Return, and the ODFI bears responsibility for any return fees along with resubmitting the corrected payment. Given the compliance stakes, many finance teams turn to automated verification tools. ACHgeniecan validate SEC code assignment and authorization records before a file is transmitted, reducing the risk of costly returns tied to mismatched codes.
NACHA currently permits 13 standard entry class codes, though most businesses only ever encounter a handful. Below are the codes that generate the highest volume of questions from finance and operations teams.
The PPD SEC code is used for consumer transactions — direct deposit payroll, recurring bill payments, and one-time consumer debits or credits. A recurring ACH debit for a utility bill, for example, typically posts under the PPD ach payment designation. Consumer debits under PPD require written or similarly authenticated authorization; consumer credits, such as payroll deposits, can be authorized orally or through other non-written means.
The CCD sec code applies to business-to-business transactions: vendor payments, cash concentration between accounts, payroll funding, and other corporate disbursements. Unlike PPD, CCD transactions occur between non-consumer accounts and rely on an agreement between the originator and receiver rather than consumer-style written authorization. A CCD entry can also carry a single addenda record for payment-related information, often referred to as CCD+.
The ppd vs ccd distinction ultimately comes down to who is receiving the funds. PPD is reserved for consumer accounts — individuals receiving payroll or paying personal bills — while CCD is reserved for corporate accounts, such as a business paying another business. Choosing between ccd vs ppd incorrectly can result in a return, since RDFIs validate the code against account type. [Internal link opportunity: link to ACHgenie ‘s “ACH Payment Automation” product page] Payment platforms that automatically select the correct entry class code ppd or ccd designation based on recipient account type help originators avoid this class of error entirely.
CTX functions similarly to CCD but supports up to 9,999 addenda records, making it the preferred choice for trading partners exchanging full ANSI ASC X12 or EDIFACT remittance data alongside payment. Businesses weighing ctx vs ccd should consider whether the payment needs to carry substantial remittance detail; if so, CTX is generally the better fit.
WEB entries cover transactions authorized over the internet or a mobile device, including person-to-person credit transfers. TEL entries cover debits authorized verbally by phone. Both require robust authentication and recordkeeping given the higher fraud exposure associated with remote authorization channels.
ARC, BOC, and POP codes relate to the conversion of paper checks into electronic ACH debits at lockboxes, back offices, or point-of-purchase locations, each requiring notice to the consumer before the check is accepted. RCK applies to re-presented checks returned for insufficient funds. IAT is reserved for international ACH transactions involving a financial agency outside U.S. jurisdiction.
According to Federal Reserve payments research, ACH volume continues to grow year over year as more consumer and B2B payments shift away from paper checks. As that volume increases, so does the operational burden of assigning the correct standard entry class code to every transaction, particularly for platforms processing thousands of payments across varied use cases.
Incorrect SEC codes are not merely an administrative nuisance; they can expose originators to compliance risk under NACHA Operating Rules, since certain codes carry specific authorization and recordkeeping obligations. ACHgenie addresses this by automatically mapping transaction context to the appropriate SEC code and flagging authorization gaps before submission, which helps originators stay aligned with NACHA requirements without manual review of every file.
A SEC code is a three-letter tag on every ACH transaction that tells banks how the payment was authorized — for example, in writing, verbally, or online — and whether it involves a consumer or corporate account.
Some banks display the SEC code directly on a transaction entry. Seeing “PPD” typically means a consumer-authorized payment, such as payroll or a bill debit, while “CCD” indicates a business-to-business transaction.
PPD is used for consumer accounts, such as individual payroll deposits or bill payments. CCD is used for corporate accounts, such as vendor payments or funds transfers between business accounts.
NACHA currently permits 13 standard entry class codes, though PPD, CCD, CTX, WEB, TEL, and IAT account for the large majority of transaction volume.
An incorrect SEC code can trigger an ACH Return. The ODFI is then responsible for any return fees and must resubmit the payment with the correct code, which can delay settlement and increase processing costs.
