R24

On This Page

High-Priority Return Code

This ACH return code indicates that the receiving bank has identified what appears to be a duplicate transaction with matching data elements such as trace number, date, dollar amount, or other identifying information. R24 requires careful handling because you must verify whether it's actually a duplicate before taking action to avoid processing errors or double reversals.

‍

Error message: "The RDFI has received what appears to be a duplicate entry; i.e., the trace number, date, dollar amount and/or other data matches another transaction."

What Causes ACH Return Code R24?

The R24 ACH return code means "Duplicate Entry" and indicates that the receiving bank has detected what appears to be a duplicate transaction based on matching data elements like trace numbers, dates, dollar amounts, or other identifying information. This code serves as a protective mechanism to prevent the same transaction from being processed multiple times.

Duplicate entries can occur due to technical glitches, system errors, or unintentional resubmission of transactions. The ACH system uses various data points to identify potential duplicates and flags them for review. However, it's important to note that the system may sometimes flag legitimate transactions as duplicates if they share similar characteristics, requiring careful investigation before taking action.

Can You Retry R24 Payments?

You should not automatically retry R24 payments without first verifying whether the transaction is actually a duplicate. If it's a legitimate duplicate and the original transaction processed correctly, no action is needed. If it's not actually a duplicate, you'll need to work with the customer and their bank to ensure proper processing.

Common Causes

Unintentional resubmission of the same transaction due to system errors

Technical glitches causing duplicate processing attempts

Matching trace numbers, dates, and amounts from separate transactions

System timeouts leading to multiple submission attempts

Human error resulting in duplicate manual entries

Key Information

Return timeframe: 2 banking days

Must verify if transaction is actually a duplicate before taking action

Can reverse erroneous duplicates up to 5 business days after settlement

Should not process return if transaction already reversed

Requires careful investigation to avoid double processing errors

How to Respond to an R24 Code

‍

An R24 return requires careful investigation to determine if the transaction is actually a duplicate before taking any corrective action.

When Your Customer's Payment Fails

Verify Transaction Details
Check if this is actually a duplicate by comparing trace numbers, dates, amounts, and other identifying data.
Confirm Original Transaction Status
Determine if the previous transaction was processed correctly and funds were transferred.
Investigate System Records
Review your payment processing logs to understand how the duplicate occurred.
Take Appropriate Action
If it's a legitimate duplicate with successful original processing, no action needed. If not a duplicate, contact customer and bank for resolution.

Email Template

Subject: Payment Processing Review - Duplicate Transaction Detected

Hi [Customer Name],

‍

Our system detected what appears to be a duplicate payment transaction. We're currently investigating to determine if this is actually a duplicate or if there was a processing error.

‍

We'll review our records and confirm the status of your original payment. If the original transaction processed successfully, no further action is needed. If there was an error, we'll work to resolve it immediately.

‍

We'll contact you within 24 hours with an update on the investigation and next steps.

‍

Thanks,

‍

[Your Company Name]

When Your Payment to Vendors Fails

An R24 return on vendor payments requires careful investigation to verify if it's actually a duplicate. Check your payment records before taking action to avoid processing errors.

Review payment processing logs to determine if a duplicate was actually sent
Verify the status of the original transaction to confirm if it processed successfully
Contact the vendor to confirm receipt of the original payment if needed
Only take corrective action if you confirm there was a legitimate processing error