Navy Federal Routing Number Not Working? Read the Return Code

Verified against Nacha’s published rules and bulletin pages, the Federal Reserve’s E-Payments Routing Directory, and Navy Federal’s own pages on October 22, 2026.

If money sent to 256074974 has not shown up, the routing number is almost never the reason. We re-ran both Federal Reserve directories this morning: 2560-7497-4 is listed as NAVY FEDERAL CREDIT UNION, Vienna, VA in the FedACH directory (effective October 21, 2026) and as NAVY FCU WASH, Vienna, VA in the Fedwire directory (effective October 20, 2026). A routing number that is genuinely wrong does not vanish quietly — it comes back with a code attached. So the useful question is not “is my routing number right?” but “which code came back, and who has it?”

The answer, in one paragraph

Three separate things have to be true for an ACH payment to land, and only the first one is about the routing number. The routing number has to exist and be ACH-eligible — that is the part Navy Federal’s nine digits settle, and they settle it permanently. The account number behind it has to be a real account at that institution. And the account has to be in a state that can receive money — not closed, not frozen, not restricted. Every failure people describe as “my routing number isn’t working” sits behind door two or door three. Nacha publishes a specific code for each, and that code is the fastest route to a fix because it tells you which of the three doors slammed.

If you have not yet checked whether the number itself is valid, start with the guide on what happens when the routing number is wrong, which walks through the arithmetic check, or the lookup guide for confirming a nine-digit number against the Federal Reserve’s own directories. This page picks up where those leave off: the number is right, and the money still did not arrive.

Three different failures that get called “not working”

Before chasing return codes, it is worth separating the three situations, because only one of them produces a code at all.

• The form refused it. A website or payroll portal rejected 256074974 before anything was sent. Nothing has entered the ACH network, so there is no return code and no bank on the other end to ask. This is a validation problem inside that company’s own software.
• It never arrived. Money was sent and has not appeared. It may still be in flight, it may have been returned, or it may have gone to a different institution entirely. This is the case where a return code exists — but it lives with the sender’s bank, not with yours.
• It arrived, then left. The credit posted and was later reversed. This is a return that happened after settlement, and it is the most confusing of the three because from your side it looks like a disappearance rather than a failure.

That third case is real and it has an official mechanism behind it, not a glitch. Nacha and the IRS run opt-in programs that exist precisely so a financial institution can pull a tax refund back after it has posted — and the window for doing that is 60 days, not two. More on that below.

The codes, in Nacha’s own words

When we wrote the guide on mistyped routing numbers, we noted that Nacha does not publish one open, complete return-code table — the URLs we tried returned 404. That is still true; the full table lives in Appendix Four, Part 4.2 (Table of Return Reason Codes) of the Operating Rules, which is a paid product. What does exist is a set of rule pages and bulletins that define individual codes, and those are the ones that matter here. Every definition below is quoted from a Nacha page we pulled today.

Two details in that table are worth pausing on. First, not one of these codes is about the routing number. Every single one attaches to the account, the account’s condition, or the receiver’s decision. Second, R03 and R04 are close cousins and Nacha is explicit that a receiving institution may pick either: “the RDFI may continue to use R03 (No Account/Unable to Locate Account) or R04 (Invalid Account Number Structure) to return those entries.” You cannot tell from the code alone whether your account number was merely mistyped or is the wrong kind of number — you have to go and look at it.

Nacha also publishes which of these are routine. In its bulletin on same-day returns it singles out R02, R03 and R04 as the codes “especially useful” for fast, administrative returns — the everyday, unglamorous failures, as opposed to disputes.

How fast a return moves — and why nobody can tell you “two days”

Here is the part that rarely gets written down, and it comes from Nacha’s ACH Operations Bulletin #1-2025 (June 3, 2025) on same-day processing of returns. Nacha ran a request for information in 2024 asking receiving institutions whether they send returns in same-day windows. The answers:

“Only 59% of respondents said they use Same Day ACH processing windows to send any returns. Of those that do, 45% use same-day processing for less than half of their returns.”

So the speed at which you learn about a failed payment depends on an operational choice made by the institution receiving it. Nacha’s worked example makes the spread concrete. A $500 internet debit arrives Monday morning with settlement at 8:30 a.m. ET, and the account number is not valid. Slow path: the institution reviews it on an exception report Tuesday, transmits the return at the close of Tuesday’s processing day, and the return settles Wednesday morning at 8:30 a.m. ET. Fast path: the return is automated and goes out in a same-day window on Monday, re-crediting at 6:00 p.m. ET the same day — which Nacha calculates as a gain of 38.5 hours.

That is a 38.5-hour difference on the identical failure, decided entirely by how the receiving institution’s systems are configured. Nacha calls faster returns “a best practice” and points out that the objection some institutions raise — avoiding the Same Day Entry Fee — is based on a misreading: “the fee does not apply to returns!” It also states plainly that “The Nacha Operating Rules do not require an RDFI to wait until the Settlement Date” before sending a return.

For the standard, non-same-day path, Nacha’s own language is “the standard 2-day return timeframe.” For R23 — a credit the receiver refused — the rule is tighter and more specific: the return must reach the sending side “no later than the opening of business on the second Banking Day following the RDFI’s receipt of notification from the Receiver that it has declined the Entry.”

Four different clocks appear on this site and they belong to four different mechanisms. 8:30 a.m. ET and 6:00 p.m. ET above are ACH settlement and return-window times from Nacha’s bulletin. The 6:00 pm ET in the mobile deposit guide is a cut-off for submitting a check image — same hour, unrelated system. And 6:30 pm ET is Navy Federal’s incoming-wire same-day cut-off, which it states as “Same-day processing, if received prior to 6:30 pm ET.” Do not carry one into another.

When the money arrives and then leaves again

This is the scenario that generates the angriest searches, and it has a name. Nacha and the IRS run the IRS Refund Return Opt-In Program — “developed by the IRS and Nacha to make it easier for financial institutions to return tax refund credits in cases of suspected error or fraud.” State tax agencies run a parallel program. Under them, a refund that has already posted can be pulled back.

The mechanics, in Nacha’s words:

• Returns use R17 “along with three specific ‘subcodes’ within the Addenda Information Field” — and the three are exactly: Name Mismatch, ID Theft, Questionable Refund.
• “Participating RDFIs are allowed to transmit these R17 return entries for up 60 days from the Settlement Date of the original PPD credit entry.”
• “Participating RDFIs are not required to check for name mismatch when posting; however, utilization of the subcodes provides better direction to the tax agency when researching the return.”

Read that second bullet again: sixty days, from settlement. A refund can appear in your account and be reversed two months later, and the reversal is an ordinary, sanctioned network event rather than a mistake. This is also why a tax refund is the one payment where “it arrived” is not the end of the story.

Nacha adds a warning that is directly useful to a member. Some institutions return questionable tax credits using R03 or R23 instead of the opt-in program. Nacha says that is the wrong tool: “When such ACH returns are received by a tax agency, the agency’s disbursement system may automatically issue and mail out a replacement check to the person/entity that filed the tax return” — meaning “the item was never flagged for review and funds were ultimately disbursed, potentially to a fraudster.” And an R06 return, Nacha stresses, should only happen “at the explicit request of the ODFI.”

For the routing-number side of a federal refund — which number goes on which IRS field, and how a refund is different from a payment you owe — see the IRS tax refund guide.

What to do, in order

1. Confirm the nine digits once, from a Navy Federal source. Navy Federal prints 256074974 in the header and footer of its own pages, and on its ACH page it tells you to use “your account number and routing/transit number (256074974).” We also confirmed it today in both Federal Reserve directories.
2. Check the account number twice as hard. Three of the codes above — R03, R04, R17 — are account-number codes. If you pasted an access number instead of an account number, that is an R04-shaped problem; the difference between the two numbers is covered in the access number guide.
3. Ask the sender for the return code, not for a status. “It hasn’t arrived” gets you a status. “Did you receive an R03, an R04 or an R02?” gets you the actual failure. The sender’s bank is the one holding it.
4. Check whether the account can receive at all. R02 is “Account Closed”; R16 is a frozen or legally restricted account. Neither has anything to do with what you typed.
5. If it was a tax refund, ask whether it was returned, not whether it was sent. Given the 60-day window, a refund can be taken back long after it posts, using R17 with a Name Mismatch, ID Theft or Questionable Refund subcode.
6. Use Navy Federal’s published contact routes to open a case. Its ACH page gives 1-888-842-6328 as 24/7 Member Services. The step-by-step process commitments — how long you have to report, how long the institution has to answer — are in the wrong-routing-number guide and come from Navy Federal’s own online banking agreement.

Why the wrong instinct is so persistent

The routing number is the only part of the transaction that feels like it belongs to the bank, so it is the part people re-check. But the routing number is also the part that almost never changes. Navy Federal prints 256074974 at the top and bottom of its pages, on its ACH page, and on its wire instructions; the Federal Reserve’s directories list exactly one routing number for the credit union in each of the two systems we queried. Meanwhile the two things that actually break — which account, and whether that account can receive — are invisible to the person filling in the form, because they are facts about the receiving end that no form asks you to confirm.

Nacha’s own framing supports this. The codes it recommends for fast, routine handling are all account codes. The one code family it treats as genuinely complicated — R10 and R11, with a 60-day return window and a requirement for a written statement — is about authorization for money leaving an account, not about addressing money arriving in one.

What we could not verify

• The code that covers an invalid routing number itself. We found no openly reachable Nacha page defining it. The complete table is Appendix Four, Part 4.2 of the Operating Rules, a paid product, so we are not naming or describing that code.
• Whether Navy Federal participates in the IRS or State Tax Refund Return Opt-In Programs. Nacha says participation requires signing an agreement and that “these are separate programs”; it does not publish a participating-institution list. We are not asserting Navy Federal’s status either way.
• How long Navy Federal takes to send an ACH return. Nacha publishes the institution-level practice data (59% and 45%) and the rule-level deadlines, but no institution-specific figure.
• Why any particular form or app refuses a valid routing number. We found no official specification for form-level validation. If a form rejects 256074974, the cause is that company’s own rules, and no primary source we could reach describes them.
• What Navy Federal shows a member when an ACH credit is returned. We found no published description of any in-app or online-banking notification, so this page describes no interface.
• Whether a returned ACH credit carries a fee at Navy Federal. Its ACH page says of incoming transfers, “There is no fee charged by us for this service, but other financial institutions may charge.” The published fee schedule covers returned check deposits and deposit discrepancies at ATMs, which are deposit-item adjustments rather than ACH returns — those amounts are listed in the wrong-routing-number guide.

Sources: Nacha — Return for Questionable Transaction (nacha.org/rules/return-questionable-transaction, effective June 21, 2019), ACH Operations Bulletin #1-2025 — Same-Day Processing of ACH Returns by RDFIs (June 3, 2025), New Return Reason Code for Sanctions Compliance Obligations (effective March 17, 2028), Reminder: IRS and State Tax Refund Return Opt-In Programs Open 12 Months a Year (May 28, 2024), Differentiating Unauthorized Return Reasons, and IRS Refund Return Opt-In Program. Federal Reserve Banks — E-Payments Routing Directory, FedACH (effective October 21, 2026) and Fedwire (effective October 20, 2026). Navy Federal Credit Union — Wire Transfers, Automated Clearing House (ACH) Transfers and Fees & Charges pages. All retrieved October 22, 2026. This site is not affiliated with Navy Federal Credit Union.