R23 Return Code: What Credit Entry Refused by Receiver Means for Merchants

The R23 return code means Credit Entry Refused by Receiver. You sent an ACH credit — a refund, a payout, a disbursement — and the person or business on the other end refused it, so their bank sent the funds back to you.

That makes R23 unusual among return codes. Most point to a closed account, an invalid account number, or a bank-side decision. R23 points to a choice: the receiver looked at the money and told their bank to return it.

What follows is what that refusal means for you, why receivers do it, and how to get the payment where it was meant to go.

What the R23 Return Code Means

R23 applies to credit entries only — money you push out, not money you collect. A refused refund, a rejected vendor payout, a disbursement sent back: that is R23 territory. A payment you tried to pull from a customer's account will never come back as an R23.

When the return posts, two things are true at once. The funds are back in your account, and the obligation you were settling is still open. The refund has not been issued and the payout has not been made. The return reversed the transfer; it did nothing to resolve the transaction underneath it.

It is also not an error. The account number was valid, the account is open, and both banks did their part. The receiver refused the entry — which is exactly what the code name says.

Who Sends an R23 Return, and When

The return comes from the RDFI, the receiving depository financial institution — the receiver's bank. Your bank, the one that originated the entry, is the ODFI. The receiver instructs the RDFI to refuse the credit, and the RDFI sends the entry back through the ACH network.

The return timeframe for R23 is 2 banking days, so a refused credit comes back within 2 banking days of settlement. If a credit you sent is going to be refused, you will know the same week you sent it, not a month later during reconciliation.

Why a Receiver Refuses a Credit Entry

Three causes account for most R23 returns:

• The amount is inaccurate. The receiver expected a different figure — a refund that does not match what was agreed, a payout that does not match the invoice — and refused the credit rather than accept the wrong number. This signals a disagreement about what is owed, and that disagreement needs settling before the money moves again.
• A minimum-amount condition was not met. Some receivers set a floor on the credits they will accept, and a payment below it is refused. This signals that your payment terms and the receiver's conditions are out of step.
• The receiver does not recognize the funds. The account holder does not believe the money belongs to them and asks their bank to send it back. This signals a credit that may have gone to the wrong party, or a receiver who was not expecting a payment from you at all.

The code reads the same in all three cases. The return itself does not say which one happened — that answer has to come from the receiver.

What an R23 Return Means for Your Business

The consequences are practical. The credit never posted to the receiver. The funds are sitting back in your account. And whatever you were settling — a customer refund, a vendor payout, an affiliate disbursement — remains unpaid, even if your records marked it complete.

Start with reconciliation. Match the returned entry to the original credit by receiver, date, and amount, then reopen the obligation in your books. Skip that step and the return sits as unexplained money on your side while the receiver waits on a payment your system says went out.

Then hold off on resending. The receiver refused this exact entry once, and an identical entry is likely to be refused again — another return on your record and nothing resolved. Speak with the receiver before anything else moves.

ACH Return Code R23 vs Other Return Codes

Most return codes a merchant deals with sit on debit entries — payments you tried to collect — and they describe account problems or bank decisions. R23 sits on credit entries, and the decision belongs to the receiver. That distinction tells you who to call first.

Two contrasts make it concrete. The R06 ACH return code is a return made at the ODFI's request — the originating bank asks for the entry back, and the receiver plays no part in it. ACH return code R16 marks a frozen account — a restriction that blocks everything trying to post, with no one refusing your entry in particular. With R23, the account works and both banks agree; the receiver said no.

How to Resolve an R23 Return

Take these in order:

• Confirm the return against your records. Match the R23 entry to the original credit — receiver, date, amount — and flag the underlying obligation as open.
• Contact the receiver. The code tells you the credit was refused; only the receiver can tell you why. Ask whether the amount was wrong, whether a condition on their end was unmet, or whether the payment was unexpected altogether.
• Correct the cause. Fix the figure if the amount was inaccurate. Adjust the payment if a minimum-amount condition applied. If the receiver did not recognize the funds, confirm you have the right party before another dollar moves.
• Reinitiate with the receiver's agreement. Send the corrected credit once the receiver has confirmed they will accept it. An unchanged entry sent again without that conversation tends to come back the same way, inside the same 2 banking days.

Review Your ACH Setup

One R23 is a conversation with one receiver. A steady run of refused credits and other returns is a setup question — and high-risk payments are the business we are in. If ACH returns are complicating your refunds or payouts, contact us and we will review your ACH setup with you.