SEC Codes Requirements for ACH

This table displays the SEC codes that Galileo supports for ACH transactions. You can see SEC codes in these places:

standardEntryClassCode, inside templateValues:
- Create Simulated Incoming ACH Transaction request
- Get Simulated Incoming ACH Transaction response
- Get All Simulated Incoming ACH Transactions response

This table explains how to populate the identNumber parameter of the Create ACH Transaction endpoint request (or identificationNumber of Create Simulated Incoming ACH Transaction), according to the originator and receiver account types.

SEC code	Required	Payment type	Account types	Details
`CCD` Corporate Debit or Credit	No	Credits and debits, single or recurring	B2B	Used to facilitate B2B payments between accounts belonging to the same or different business entities. In `identNumber`, you may pass the accounting number by which the receiver is known to the ODFI. It is included for further identification and for descriptive purposes. For this transaction type the `companyName` that you passed when creating the corporate account will be written to the Receiving Company Name field of the Entry Detail Record of the outgoing Nacha file.
`CIE` Customer Initiated Entry	Yes	Outgoing credit only	C2B	Used by the receiver (payee) to update accounts receivable records. In `identNumber`, you must pass an accounting number by which the originator is known to the receiver, such as the number shown on an invoice, statement, billhead, notice, or other communication as the reference. Numbers may be a sequence and alphanumeric. The `BTBG` program parameter must be set to `Y`.
`PPD` Prearranged payment and deposit	No	Credits and debits	B2C	Entry originated by a non-consumer organization to a consumer account based on a standing or single-entry authorization from that consumer. Typical uses are for personal payments such as payroll, pension, dividend, etc., or for collection of bill payments for various purposes such as utility dues, insurance, loan payments, etc. For this transaction type the `companyName` that you passed when creating the corporate account will be written to the Individual Name field of the Entry Detail Record of the outgoing Nacha file.
`WEB` Internet / Mobile	Yes	Debit	C2C	Used by a non-consumer originator to debit a consumer account, for recurring or non-recurring transactions, based on an authorization that is received other than by oral communication, i.e. via the internet or a wireless network. For a person-to-person (P2P) entry, the `identNumber` field must contain the name of the P2P originator for use by the RDFI on the periodic statement.