An R20 return on a non-transaction account means the ACH network sent your payment back because the receiving account isn’t configured to accept that kind of electronic transfer. The money wasn’t lost. It bounced because the destination — usually a savings account, money market account, certificate of deposit, or bank-held IRA — is classified by the bank as a place to hold funds rather than move them.
Which Accounts Get Flagged as Non-Transaction
Banks sort their products into two buckets. Transaction accounts, like checking and demand deposit accounts, are built for frequent debits and credits and handle ACH traffic without issue. Non-transaction accounts are built for storage.
The accounts most likely to trigger an R20 return include:
- Traditional and high-yield savings accounts, where many banks still restrict certain electronic debits.
- Money market deposit accounts, even ones that come with checks or a debit card.
- Certificates of deposit, where funds are generally locked until maturity and can’t accept or send ACH transfers.
- IRAs and similar retirement accounts held at a bank, which often reject incoming ACH debits outright.
Classification depends on the individual bank’s policies and the specific account agreement. Two savings accounts at two different banks can behave differently — one might allow unlimited ACH activity while the other blocks it. There is no universal rule.
Why the Rejection Still Happens After Regulation D Changed
The transaction versus non-transaction split comes from the Federal Reserve’s Regulation D, which historically capped certain outgoing transfers from savings and money market accounts at six per month and required banks to hold different reserves depending on account type. The Fed suspended that six-transfer limit in April 2020 and later amended Regulation D to remove it permanently.
Removing the federal rule didn’t force banks to reclassify anything. Many kept the old transaction limits in place, either because their systems weren’t updated or because the non-transaction label lets them hold lower reserves. So R20 returns still happen routinely, even though the rule that originally drove them is gone. Whether your specific account triggers one comes down entirely to how your bank configured that product.
How the Mistake Usually Happens
Most R20 returns trace back to one of three scenarios.
The most common is a wrong account number. Someone sets up a direct deposit, autopay, or one-time transfer and types the savings account number instead of the checking account number. The digits look alike and the error is easy to make.
The second involves a reassigned or converted account. If you closed a checking account and the bank later reused that number for a savings product, payments routed to the old number can come back R20.
The third is deliberate. Someone links a savings account to a payroll system or billing platform, assuming all electronic transfers work the same way, and finds out that the bank doesn’t permit outgoing ACH debits from that account type.
How to Fix It
If you meant to use your checking account, update the account details with whoever initiated the payment — your employer’s payroll department, the biller, or the payment platform. Verify both the routing number and the account number, because some banks assign different routing numbers to different account types.
If you intentionally used a savings or money market account and want to keep using it, call the bank. Ask whether the account permits incoming and outgoing ACH transactions. Some banks will enable ACH access on request. Others won’t, in which case you’ll need to route the payment through a checking account instead.
For a bounced direct deposit, the funds usually return to your employer’s payroll account. Contact payroll or HR, confirm they received the return, and provide corrected account information. Reissuing the payment may take an extra pay cycle.
For a bounced bill payment, check whether the biller marked the payment late or assessed a fee. You’re generally still responsible for paying on time, so send a replacement payment while you sort out the account issue.
Fees and Downstream Consequences
Some banks charge the account holder a return item fee when an ACH transaction bounces, regardless of the reason. Fees vary — anywhere from nothing to $25 or more, depending on your bank’s schedule. Check your account agreement.
The sender’s side can charge too. If your first autopay debit on a loan comes back R20, the lender may treat it as a bounced payment and add a returned payment charge on top of any late fee.
A single R20 return won’t hit your credit report. ACH return codes are internal banking communications and don’t reach credit bureaus. What can reach the bureaus is the fallout: if the returned payment causes you to miss a due date and the creditor reports the late payment, that late mark can affect your credit. The R20 itself is invisible; the consequences of a missed bill are not.
Repeated ACH returns of any type can also flag your account in bank-screening databases like ChexSystems or Early Warning Services, though this is more commonly tied to insufficient-funds or closed-account returns than to R20.
A Note on R20 Versus Canadian Credit R-Ratings
The “R” in R20 sometimes gets confused with the R-rating system on Canadian credit reports. That system runs from R0 (too new to rate) to R9 (bad debt or sent to collections) and stops at R9. There is no R20 in it, and it has nothing to do with ACH return codes. U.S. credit reports don’t use R-ratings at all; they use the Metro 2 format. If you’re seeing R20 in connection with a bank transaction, it’s an ACH return code, not a credit designation.