ACH addenda records are 94-character supplemental data packets attached to electronic payments in the Automated Clearing House network, carrying remittance information like invoice numbers, purchase order references, or payment descriptions alongside the money itself.1Nacha. ACH File Details They exist so the party receiving the funds can match the deposit to its own records without picking up the phone. How many you can attach, what format the data must take, and whether any are required at all depend entirely on the transaction type.
What an Addenda Record Carries
The heart of a standard addenda record is the Payment Related Information field, an 80-character freeform alphanumeric block that travels with the payment to the receiving bank.1Nacha. ACH File Details Senders typically populate it with invoice numbers, account identifiers, purchase order references, or short descriptions like “Q2 lease payment” or “Vendor 4491 services.” The field is optional on most domestic transaction types, so it can be left blank, but leaving it blank defeats the point of attaching an addenda record in the first place.
Within that 80-character block, senders sometimes use delimiters such as asterisks or backslashes to separate distinct data elements (an invoice date from an invoice amount, say) so the receiving system can parse them out. That trick works for simple remittance. When the data genuinely needs structure, the CTX entry class uses formal EDI syntax instead, which is covered below.
Two numeric identifiers tie each addenda record to its parent payment. The Addenda Sequence Number marks the order of addenda records attached to one entry. The Entry Detail Sequence Number must match the last seven digits of the trace number on the parent transaction record.1Nacha. ACH File Details If those seven digits don’t line up, the addenda record isn’t connected to anything the processor can recognize, and the batch fails.
The 94-Character Field Layout
Every line in an ACH file is a fixed-width ASCII record exactly 94 characters long.2Nacha. ACH File Overview A line that runs 93 or 95 characters produces a format error that blocks the whole batch. For a standard addenda record, the positions break down this way:
- Position 01, one character: Record Type Code, always “7,” which identifies the line as an addenda record.1Nacha. ACH File Details
- Positions 02–03, two characters: Addenda Type Code, “05” for standard payment-related addenda.
- Positions 04–83, 80 characters: Payment Related Information, the freeform field. Optional; can be left blank.
- Positions 84–87, four characters: Addenda Sequence Number.
- Positions 88–94, seven characters: Entry Detail Sequence Number, matching the last seven digits of the parent entry’s trace number.
Alphanumeric fields are left-justified and padded on the right with spaces. Numeric fields are right-justified and padded on the left with zeros. Code fields that call for uppercase must be uppercase.2Nacha. ACH File Overview Most originators never hand-build these strings. Accounting software and payment platforms generate compliant files automatically. The layout matters when you’re debugging a rejected file or writing a custom integration, because knowing exactly where each field begins and ends is the fastest way to spot what the processor is complaining about.
How Many Addenda Records Each Transaction Type Allows
The Standard Entry Class (SEC) code on each payment sets the addenda rules: how many records are allowed, whether any are required, and what format the data has to follow. Picking the wrong SEC code isn’t only a technical problem. It can also create compliance exposure if the type you used doesn’t match the authorization you obtained from the receiver.
PPD, CCD, and WEB: One Optional Record
Prearranged Payment and Deposit (PPD) covers payments between a business and a consumer, including payroll direct deposits, recurring bill payments, and consumer refunds. When a PPD entry carries an addenda record, the entry is designated PPD+, with the plus sign signaling supplemental data.1Nacha. ACH File Details Only one addenda record is permitted per PPD entry, giving you a single 80-character block to work with.
Corporate Credit or Debit (CCD) works the same way for business-to-business payments. A CCD+ entry carries one addenda record, which is typically enough for a single invoice reference, tax payment ID, or insurance premium number.
WEB entries cover payments initiated through a website or mobile app, such as online bill pay or e-commerce debits from a consumer’s bank account. WEB allows one optional addenda record per entry, in the same 94-character layout. Whether the recipient’s bank actually shows the Payment Related Information to the account holder depends on that bank’s systems. The Nacha developer guide notes the information “may or may not be displayed to the recipient, based on the bank’s capabilities.”1Nacha. ACH File Details
CTX: Up to 9,999 Structured Records
Corporate Trade Exchange (CTX) is built for payments that cover many invoices at once. A single CTX entry can carry up to 9,999 addenda records.1Nacha. ACH File Details CTX addenda records don’t use freeform text. They use ANSI ASC X12 electronic data interchange syntax, which organizes the data into formally defined segments and elements.
Two X12 transaction sets commonly ride inside CTX addenda. The 820 (Payment Order/Remittance Advice) is used for general commercial payments and identifies payee, payer, individual invoice references, adjustment amounts, and contract line items. The 835 (Health Care Claim Payment/Advice) is the standard for medical claim remittance, carrying claim numbers, service codes, and payment adjustments. Both follow the ASC X12 Version 5010 standard. CTX entries cost more to process than PPD or CCD because of the heavier data load, so they’re used when the remittance detail actually justifies the expense.
IAT: Seven Required, Twelve Maximum
International ACH Transaction (IAT) entries have the strictest addenda rules in the network. Each IAT entry must include a minimum of seven mandatory addenda records to comply with the Bank Secrecy Act’s Travel Rule and enable OFAC sanctions screening.3Nacha. IAT Specific Data Elements The maximum is 12 records per entry, and the ACH operator will reject anything above that limit.4Federal Reserve Financial Services. International ACH Transaction (IAT) Frequently Asked Questions
Each mandatory IAT addenda record uses its own Addenda Type Code (not the standard “05”) and carries specific information about the parties and banks involved:
- 710 Record: foreign payment amount and receiver’s name.
- 711 Record: originator’s name and street address.
- 712 Record: originator’s city, state or province, country, and postal code.
- 713 Record: originating bank name, ID, and branch country code.
- 714 Record: receiving bank name, ID, and branch country code.
- 715 Record: receiver’s identification number and street address.
- 716 Record: receiver’s city, state or province, country, and postal code.
This level of detail exists so both the originating and receiving banks can screen the transaction against OFAC sanctions lists. For outbound IATs, the originating institution bears heightened responsibility because it cannot rely on an overseas receiving bank to perform OFAC screening. For inbound IATs, the receiving institution must screen regardless of whether the OFAC screening flag is set.5FFIEC BSA/AML InfoBase. Office of Foreign Assets Control A hit pulls the suspect transaction from the batch for investigation and may block it entirely.
When Addenda Data Goes Wrong
Financial institutions charge a small per-record fee for processing addenda records, which varies by bank and volume but is generally modest for standard entries. The real money sits on the error side. When a payment is returned, the originating bank charges an administrative fee for each returned item, and the payment has to be corrected and resubmitted.
Two return codes often trace back to entry data problems. R03 (No Account/Unable to Locate Account) means the receiving bank could not find a matching account. R04 (Invalid Account Number) means the account number structure itself is invalid. Both indicate that what you submitted doesn’t line up with what exists at the receiving bank. Verifying account and routing numbers before you build the file is the simplest prevention, and many banks and payment platforms offer validation services for exactly this purpose.
For addenda-specific failures, the most common mistake is a mismatch between the Entry Detail Sequence Number in the addenda record and the trace number on its parent entry. That is almost always a software configuration issue rather than a data entry one, so if you see it recur, check your file generation logic rather than the individual payments.
Storing Account Data from Addenda Records
Addenda records sometimes carry sensitive information such as account numbers or taxpayer IDs. Nacha’s data security rule requires originators, third-party service providers, and third-party senders whose ACH volume exceeds 2 million entries annually to render DFI account numbers unreadable when stored electronically.6Nacha. Supplementing Data Security Requirements Acceptable methods include encryption, truncation, tokenization, or destruction. Password-protecting a file or database does not satisfy the requirement.
The rule is technology-neutral, so no specific encryption standard is mandated. What matters is that a stored account number cannot be read without an additional decryption step. When a full account number is genuinely needed for an active business function such as customer service, the data can be readable during that task and then returned to an unreadable state once the function is complete. Organizations that cross the 2-million-entry threshold in a given year have until June 30 of the following year to comply.6Nacha. Supplementing Data Security Requirements
Separately, financial institutions must retain ACH records for six years from the date of receipt or transmission. Records can be kept in hard copy or electronic form and do not need to stay in the original processing format.7Nacha. RMAG: Preventing and Recovering from Operational Errors and Accidents If you originate ACH payments, that means your addenda records, authorization documentation, and file transmission logs should all be archived in a searchable format. Six years is a long window, and disputes or audit requests can surface well after you’ve forgotten about a particular payment.