Review and edit payment-related addenda information. Free, no signup, and your file is processed locally in your browser.
Primary topic: ACH addenda builder
The ACH addenda builder creates or edits payment-related addenda information attached to eligible ACH entries. Use this ACH addenda builder as a practical first step, then review its results carefully. addenda rules differ by SEC code and use case, so verify content requirements with the receiver and your bank.
A reliable ACH addenda builder workflow starts by confirming the business purpose before changing or exporting any data. This page is designed for creates or edits payment-related addenda information attached to eligible ACH entries. It performs the supported work locally, so the source does not need to be sent to a conversion service. Use the ACH addenda builder with an approved source and a clearly defined expected result.
Start with an ACH file and the payment information that should accompany a selected entry. Work from a copy, preserve leading zeros and remove unrelated report headings or totals that could be mistaken for transaction data.
Use the on-page controls, then compare the displayed batch count, entry count, total debits and total credits with the source expectation. Investigate warnings instead of assuming that a downloadable result is correct.
The expected result is an updated file containing type 7 addenda records and recalculated entry and control counts. Before transmission or downstream import, review SEC-code eligibility, addenda type, character limits, sequence numbers, trace linkage and the exact payment information, save the source separately and follow your organization’s approval process.
Confirm that the selected input really contains an ACH file and the payment information that should accompany a selected entry. A renamed extension does not convert a spreadsheet, PDF or binary export into a valid ACH-related source.
Compare entries one batch at a time. Missing rows, duplicated rows, amount scaling, debit-versus-credit selection and malformed addenda can all change counts or monetary totals.
Format validation does not verify enrollment or bank policy. addenda rules differ by SEC code and use case, so verify content requirements with the receiver and your bank. Ask the ODFI for the rejection code and compare it with the company profile, identifiers and processing date.
It creates or edits payment-related addenda information attached to eligible ACH entries. The ACH addenda builder processes the data locally in your browser and does not require an account.
It needs an ACH file and the payment information that should accompany a selected entry. Files remain on your device during processing.
You will get an updated file containing type 7 addenda records and recalculated entry and control counts. Review the result before using it in an operational workflow.
Check SEC-code eligibility, addenda type, character limits, sequence numbers, trace linkage and the exact payment information. Also remember that addenda rules differ by SEC code and use case, so verify content requirements with the receiver and your bank.
No. Processing creates a separate result in browser memory and leaves the source file unchanged. Keep the original as the audit baseline until the new output has been reviewed and accepted.
Confirm that the files share compatible originator and processing settings, then review SEC-code eligibility, addenda type, character limits, sequence numbers, trace linkage and the exact payment information. Do not rely on matching filenames or creation dates alone.
When the tool creates a new ACH output, it rebuilds affected counts, hashes, debit and credit totals, batch controls, file controls, block count and padding from the resulting entries.
Preserve the source, review a preview, validate the output and obtain any required approval before transmission. addenda rules differ by SEC code and use case, so verify content requirements with the receiver and your bank.
Technical explanations are checked against these primary sources. Bank-specific requirements can be narrower than general format guidance.
Sources reviewed August 20, 2026. Nacha owns and maintains the linked materials.
ACH files use the NACHA fixed-width format: every record is 94 characters, files contain one or more batches, and control records reconcile entry counts, routing-number hashes, debits and credits. Always confirm bank-specific settings with your financial institution before uploading a production file.