An R20 return on a non-transaction account means the bank on the receiving end rejected an ACH payment because the account it was sent to isn’t configured to accept that type of electronic transfer. The money wasn’t lost. The transaction bounced back to the sender, and it needs to be redirected to an account the bank treats as a transaction account, usually a checking account.
What a Non-Transaction Account Is
Banks sort their deposit products into two groups. Transaction accounts, like checking and demand deposit accounts, are built for frequent debits and credits and accept ACH activity by default. Non-transaction accounts are built to hold money rather than move it, and they often block or limit ACH transfers.
The accounts most likely to generate an R20 are:
- Traditional and high-yield savings accounts, which still restrict certain electronic debits at many banks.
- Money market deposit accounts, even ones that offer checks or a debit card.
- Certificates of deposit, where the funds are locked until maturity.
- IRAs and similar retirement accounts held at a bank, which may reject incoming ACH debits outright.
Classification is set by each bank’s policies and the specific account agreement, so two savings accounts at two different banks can behave differently. One might allow unlimited ACH debits; the other might block them.
Why This Rule Still Exists
The transaction versus non-transaction split traces back to the Federal Reserve’s Regulation D, which 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 the six-transfer limit in April 2020 and later removed it permanently.
Removing the federal requirement didn’t force banks to reclassify anything. Many kept the old limits and the non-transaction label in place, either because they hadn’t updated their systems or because the classification lets them hold lower reserves. R20 returns still happen routinely, and whether any given account triggers one depends entirely on how the account-holding bank has configured that product.
Why Your Payment Came Back R20
Most R20 returns fall into one of three patterns.
The most common is a mistyped account number. Savings and checking account numbers look similar, and it’s easy to enter the savings number when setting up a direct deposit, autopay, or one-time transfer.
The second is a payment sent to an account that was closed and whose number the bank later reassigned to a savings product. Payments still routed to the old number come back as R20.
The third is deliberate use of a savings or money market account for a transfer the bank doesn’t allow. Linking a savings account to a billing platform can work at one bank and fail at another with the same product name.
How to Fix It
The fix is almost always to switch to a transaction account. If you meant to use checking and entered savings by mistake, update the routing and account details with whoever sent the payment: your employer’s payroll department, the biller, or the payment platform. Verify both numbers, because some banks use different routing numbers for different account types.
If you intended to use the savings or money market account, call the bank that holds it and ask whether the account permits incoming and outgoing ACH activity. Some banks will enable ACH on request. Others won’t, and in that case the transaction has to go through a checking account.
For a returned direct deposit, the funds go back to your employer’s payroll account. Contact payroll or HR to confirm they received the return and to give them corrected account details. Most employers will reissue the payment, though it can take an extra pay cycle.
For a returned bill payment, check whether the biller marked the payment as missed or added a late fee. If the return caused you to miss a due date, you’re generally still on the hook for paying on time, so send a replacement payment while you sort out the account issue.
Fees and Credit Impact
Some banks charge a return item fee on the account holder’s side regardless of the reason, ranging anywhere from nothing to $25 or more. Your account agreement or fee disclosure will say. On the sending side, a lender or biller may treat the bounced debit like any other returned payment and add a returned payment charge on top of any late fee.
A single R20 doesn’t appear on your credit report. ACH return codes are internal to the banking system and aren’t reported to credit bureaus. What can reach your credit is the downstream effect: if the returned payment causes you to miss a due date and the creditor reports the late payment, that late payment can affect your score. The R20 itself is invisible; the missed bill might not be.
Repeated ACH returns of any kind can also flag an account in bank-screening databases like ChexSystems or Early Warning Services. That’s more of a concern with insufficient-funds or closed-account returns than with R20, but a pattern across multiple accounts can draw attention.
R20 Is Not a Credit Rating
The “R” in R20 sometimes gets confused with the R-rating system on Canadian credit reports, which runs from R0 to R9 and describes how current an account is. That system stops at R9; there is no R20 in it, and it has nothing to do with ACH returns. U.S. credit reports don’t use R-ratings at all. If you’re seeing R20 tied to a bank transaction, it’s an ACH return code.