An ACH payment can reach the intended account even when part of the instruction is outdated or formatted incorrectly. A Notification of Change communicates the corrected information so the originator can improve future entries without treating the original payment as a return.
A change notice is not a payment or a return
A receiving depository financial institution may accept an ACH entry while identifying information that should be corrected. It sends a Notification of Change, often called an NOC, as a non-monetary message tied to that entry.
The message does not itself move money, reverse the accepted entry or prove that a future entry is authorized. It reports a defined correction using the applicable ACH code and the information needed for the responsible party to act.
The receiving bank describes the correction
The receiving bank links the notice to the original ACH entry and identifies the type of information that needs attention. Depending on the circumstances, the correction can concern routing, account or other entry information covered by the network rules.
Accurate references matter because the originating bank and originator need to match the notice to the right customer instruction. An incomplete or unmatched notice becomes an exception rather than a safe basis for changing payment data.
The originating side routes the notice to the owner
The originating depository financial institution receives the NOC through the ACH process, records it and makes the information available to the originator or other responsible party. Roles and timing are governed by the ACH rules and the parties' service arrangements.
The originator determines which stored instruction produced the entry. Payroll, bill payment and recurring debit systems may each keep that information in a different application, so ownership and traceability prevent a correction from stopping in a general operations queue.
Future entries are corrected through a controlled change
The responsible party updates the applicable record within required timeframes and verifies that the change is applied to the intended payment relationship. The next eligible entry should use the corrected information rather than repeatedly relying on the receiving bank to repair it.
A correction message should not become an uncontrolled shortcut for changing sensitive payment instructions. Access controls, change records and review help distinguish a legitimate NOC from a mismatched item, data-entry error or attempted redirection.
Monitoring closes the feedback loop
Operations tracks unresolved notices, repeated codes and originators that do not make required corrections. Recurrence can indicate stale customer records, weak onboarding, a system mapping problem or an ineffective handoff between the bank and its client.
The bank reconciles notices with the related entries and retains evidence of disposition. That record supports customer service and audit work while keeping the distinction clear among a change notice, a returned entry and a reversal.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.