An ACH entry tells the network how to move money, but the receiver may also need information explaining what the payment is for. An addenda record carries permitted payment-related data alongside the entry so banks and customers can identify, post and reconcile the transaction more accurately.
The addenda travels with an ACH entry
An addenda record is an additional data record associated with a specific ACH entry. It can carry an invoice reference, account reference, remittance detail or other information allowed for that entry type, while identifiers keep it linked to the related payment.
The addenda does not move a second amount and is not a separate authorization. The monetary entry determines the debit or credit, while the associated record provides context that the receiving bank or customer may use after the payment arrives.
The entry class determines the permitted structure
ACH Standard Entry Class codes describe the payment application and help determine whether addenda are optional or required, how many may accompany an entry and what their fields mean. Corporate, consumer and international entries do not all use addenda in the same way.
Originators and their banks therefore build files to the format applicable to the selected entry class rather than treating the addenda as a free-form note. Unsupported counts, invalid record relationships or incorrectly placed data can cause rejection, truncation or manual repair.
Structured information can improve remittance matching
A business receiving a credit may need to match the deposit with one or many invoices. Consistent remittance conventions and reference values help accounts-receivable systems connect the ACH entry with the right customer, invoice or obligation without relying only on amount and date.
Useful structure also reduces ambiguity between trading partners. The parties still agree on the convention and meaning of the data because a correctly formatted record can contain a reference that is stale, incomplete or unknown to the receiver's system.
Validation protects the payment and the data
The originating side validates record type, sequence, field format and the relationship between the entry and its addenda before release. Access and approval controls cover the full file because altering payment-related information can misdirect posting or conceal the purpose of an otherwise valid transfer.
Sensitive information is limited to what the format, agreement and business purpose require. An addenda record is not a safe place for passwords, full credentials or unrelated personal data merely because it can travel through the payment chain.
Delivery and reconciliation complete the value
The receiving bank makes applicable payment-related information available through reporting, files or other agreed services. The receiver then uses the entry amount, trace information and addenda detail together when posting cash and resolving unmatched items.
Operations reconcile that the entry and all expected addenda were received, interpreted and delivered without duplication or loss. When data cannot be converted or matched, the original record and identifiers remain available for investigation rather than being replaced by an unsupported manual description.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.