On July 24, 2026, the Nacha Voting Membership approved three amendments to the Nacha Operating Rules. They arrived as Supplement #2-2026, and unless you read supplements for fun, the announcement probably looked like housekeeping.

Mostly, it is. None of the three requires a system change. Two of them are documentation exercises. But one took effect the day it was approved, one lands on September 18 alongside two other rules, and one has a quiet dependency that a lot of institutions are already out of compliance with. Here's what each one does and what, if anything, your team needs to do about it.

1. The U.S. Treasury joins the ACH Contact Registry

Effective July 24, 2026 — already in force.

The ACH Contact Registry has always been a closed loop: registered financial institutions, Payments Associations, and the two ACH Operators. This amendment opens it to the U.S. Treasury's Bureau of the Fiscal Service, in both directions. BFS can now look up contacts at your institution, and you can look up contacts at BFS.

Nacha is explicit that this creates no new obligation for participating DFIs — no registration step, no operational change. What it does is remove a specific, familiar friction: the federal benefit payment, reclamation, or Green Book question that used to mean hunting for the right Treasury contact through a general line.

The part worth flagging internally is the dependency. A registry is only as good as the data in it, and the registry rules already require every ODFI and RDFI to name at least one primary and one secondary contact, keep those numbers monitored during business hours, update registration within 45 days of any change, and verify the whole record annually. Failure to register is a Class 2 Rules Violation, subject to fines under Nacha's National System of Fines.

Most institutions registered in 2020 and haven't looked since. If the person listed as your primary ACH contact left two reorgs ago, Treasury now has one more reason to find that out the hard way.

2. Currently Accepted Characters in the ACH Network

Effective January 1, 2027.

This one changes nothing about how ACH works. Today the Rules point to an external standard to describe which characters the ACH Operators accept. The amendment replaces that pointer with a table of the actual valid single-byte characters, written into the rulebook.

Nacha's own language is unusually direct about the scope: it is a documentation clarification regarding already-acceptable characters, with no change to ACH Operator processing specifications or requirements. No new characters are supported. Nothing needs to be rebuilt.

The value is in ending the interpretation arguments. If you have ever had an originator's file rejected over a character their software swore was fine, or fielded a "why did this name come through mangled" question from a corporate client, you have had the conversation this amendment is meant to end. Come January 2027, there is a definitive list to point at.

3. Funds availability exceptions for non-Same Day credit entries

Effective September 18, 2026.

This is the one to circle, mostly because of the date it shares.

September 18 is when the new funds availability requirement for non-Same Day ACH credit entries takes effect — credits must be made available by 9:00 a.m. local time on the settlement date. The same day, the Definition of IAT Entries rule also takes effect. Three rules, one Monday.

This amendment carves out a narrow exception to that 9:00 a.m. mandate. It applies to an RDFI located east of the Atlantic Time Zone and west of the International Date Line — Guam and the Northern Mariana Islands, in practice. For those institutions, a non-Same Day credit arriving after 8:00 a.m. local time on the settlement date can be made available by end of business that day, or by 9:00 a.m. the next banking day if processing has already run.

If you don't operate in those territories, the exception doesn't touch you. The September 18 requirement it modifies almost certainly does.

Staying audit-ready as the rules keep moving

The Affirmative Platform pulls originator activity, exposure, and return behavior into one live view, so when a change like this lands, the answer to "are we current?" doesn't depend on anyone's memory. It's already documented.

That same live data does double duty: it's the evidence you walk into an exam with, generated from the platform instead of assembled from spreadsheets the week before, and it's the visibility your team uses day to day to decide which originators have earned a higher limit. Compliance is the floor. What real-time data unlocks is the point.

Read the source: Nacha's announcement, Three New Nacha Rules Approved, and the full summary of upcoming rule changes. Subscribers to the Nacha Operating Rules Online Resource can access Supplement #2-2026 directly; it should be read alongside the 2026 edition of the Rules.