# What Is an ACH Notice of Change and How Does It Relate to Return Codes?
[ACH return codes](https://securemerchantsolution.com/blog/ach-return-codes/) tell you that a payment failed. A Notice of Change, often shortened to NOC, tells you something different: the payment may have gone through, but the bank wants you to correct certain details for next time. Many businesses ignore these notices, and that is how small data errors grow into repeated returns.
This guide explains what NOCs are, which change codes appear most often, and how to respond. Deadlines and procedures can change, so confirm current details with your bank, your processor, and Nacha.
What Is a Notice of Change?
A Notice of Change is a message from the receiving bank saying that information in your ACH entry was wrong or outdated, even though the entry could still be processed. It points out what should be corrected, such as an account number or routing number, so future entries are accurate.
Think of it as a polite warning before a problem turns into a return.
How Is It Different From a Return?
A return reverses the payment and sends the money back. A NOC does not reverse the payment. It asks you to update your records. If you ignore it, later entries with the old details may be returned, or the bank may be able to take action.
Return codes begin with R. Change codes begin with C.
Which Change Codes Are Common?
Examples of change codes include:
C01: Incorrect account number.
C02: Incorrect routing number.
C03: Incorrect routing number and account number.
C05: Incorrect transaction code.
C06: Incorrect account number and transaction code.
C07: Incorrect routing number, account number, and transaction code.
Your notice will state the exact code and the corrected information, so read it carefully.
Where Can You Learn the Basics?
Change codes can look just like return codes at first glance. Resources such as [Secure Merchant Solution](https://securemerchantsolution.com/) publish plain-language guides on payment topics, which can help you understand what a notice means before you update anything.
Use any guide as background, and confirm details with your processor.
Why Do Banks Send NOCs?
Accounts change. A customer may switch banks, a bank may merge or change routing numbers, or a customer may have mistyped a digit. Rather than reject every payment, banks sometimes process it and send a notice so the originator can fix the data.
Acting on the notice keeps future payments clean.
How Quickly Must You Respond?
Rules generally expect originators to make the requested change within a short period, commonly within a few banking days or before the next entry is sent, whichever is later. Check the exact deadline with your processor, since details and exceptions apply.
Build the deadline into your routine, so notices do not sit in an inbox.
How Do You Update Your Records Safely?
Follow a clear process:
Verify that the notice came from your bank or processor.
Compare the corrected information with what you hold.
Update the customer record in your system.
Note the date, code, and who made the change.
Confirm with the customer when appropriate, using a secure method.
Test the next payment, if your process allows.
Never send full bank details by email or text while confirming a change.
What About Automation?
Many processors can deliver NOCs through reports or automatic updates. Ask what your provider supports, and whether changes are applied automatically or need manual review. Automation saves time, but still check samples to make sure updates are accurate.
How Do NOCs Help Reduce Returns?
Every corrected record is one less future R02, R03, or R04. Businesses that process NOCs promptly tend to see fewer account-error returns, and a lower overall return rate protects your standing with your bank.
Track how many NOCs you receive, since a spike may point to a problem with how you collect data.
What Records Should You Keep?
Keep the notice, the date received, the change made, the person responsible, and any customer contact. These records show good faith if a question arises later and help you spot patterns.
What Mistakes Should You Avoid?
Ignoring notices because the payment cleared
Missing the response deadline
Updating a record without checking the source
Sending bank details through insecure channels
Treating a change code like a return code
Failing to review why notices keep appearing
Conclusion
A Notice of Change is an early warning, not a failure, and acting on it quickly keeps your ACH data clean. Learn the common change codes, build the deadline into your routine, update records carefully, and track patterns. Confirm current rules and deadlines with your bank, your processor, and Nacha, and you will see fewer returns later.
FAQ
1. Does a Notice of Change mean my payment failed?
Not necessarily. The payment may have processed, but the bank wants you to correct details.
2. What does C01 mean?
Incorrect account number. The notice provides the corrected information.
3. How fast must I update my records?
Usually within a short period set by the rules. Ask your processor for the exact deadline.
4. What happens if I ignore a notice?
Future payments using old details may be returned.