First-Party ACH Fraud: What Nacha’s Prompt-Recredit Proposal Means for Banks

Nacha is weighing a change to when banks must recredit disputed ACH debits. See what it would mean for Regulation E, ACH returns, and the reports banks use to track both.

On this page

The Nacha first-party fraud proposal would clarify when a bank must restore funds after a customer disputes an Automated Clearing House (ACH) debit. For bank teams, the practical question is how much useful evidence they can gather while meeting their obligations to customers and preserving their options under the ACH rules.

For example, a customer calls their bank about an unfamiliar debit. The company that initiated it sends back an enrollment record. That record may cover a different amount, a different date, or a payment the customer later canceled. The bank must investigate the reported error. It also needs to decide which ACH network options apply and what the evidence supports. Keep a record of each decision.

Status as of November 22, 2026. The proposal is open for comment through December 11, 2026. Nacha lists June 18, 2027 as the proposed effective date. Institutions should continue applying the current rules and Regulation E while the consultation is open. Nacha’s proposal and dates

What the Nacha first-party fraud proposal covers

The consultation contains two related parts. The Request for Information asks about the scope of first-party fraud, what different ACH participants can do about it, and whether additional transaction information or standard entry descriptions would help. Some of the ideas also relate to Pay by Bank. The Request for Comment asks for feedback on the receiving bank’s duty to promptly recredit the account after it receives a Written Statement of Unauthorized Debit (WSUD). Nacha’s formal consultation

Here, first-party fraud means a customer deliberately claims that an ACH debit they authorized was unauthorized. A customer may also fail to recognize a billing descriptor, dispute an amount, or believe they canceled an authorization before the debit. Even when a customer has paid a company before, the company may still need to show that a valid authorization covered this debit. Nacha’s explanation for ACH originators

What the prompt-recredit proposal would clarify

For consumer accounts covered by Section 3.11, the proposed language sets the earliest point at which the network’s prompt-recredit rule would require a credit. That point is when Regulation E requires provisional credit. For covered non-consumer accounts, the text describes a comparable period reasonably necessary to investigate the claim. Nacha says existing ACH return deadlines and the requirement to recredit before returning the entry would still apply. Check the requirements for the entry and account type in each case. Nacha’s proposed Section 3.11 text · Nacha’s explanation of return timing

As a result, when the evidence arrives can matter as much as what it shows. A review of closed cases may suggest a bank could have avoided some returns. Check whether staff actually had the decisive evidence before the applicable network deadline. Then ask how that evidence might have changed the decision and what the customer would have experienced.

Keep the consumer and ACH network clocks separate

When a qualifying consumer notice triggers Regulation E, start the investigation promptly. The standard deadline to determine whether an error occurred is 10 business days after the notice. If the bank needs more time, it can generally take up to 45 calendar days if it meets the rule’s conditions, including providing provisional credit within 10 business days where required. The rule substitutes 20 business days for 10 when the transfer occurred within 30 days after the first deposit to the account. Certain transfers also qualify for a 90-day investigation period. Track the provisional credit due date and the investigation due date separately.

The CFPB explains that a bank may ask for a signed statement and must proceed with the investigation while waiting for it. A bank that requires written confirmation must tell the consumer about that requirement and provide the address during the initial oral notice. If the bank then receives no written confirmation within 10 business days, the rule provides an exception to provisional credit. Document why any exception applies. CFPB Regulation E § 1005.11 and official interpretations

Track ACH return deadlines separately

Meanwhile, track ACH network deadlines from their own triggering events. Keep the return path, reason code, statement requirements, and actual return event distinct from the consumer credit and notice record. A case may have a consumer outcome, a network outcome, and a later fraud classification. Give each one its own field in the case system. EdEconomy’s Regulation E and Nacha dispute guide

RecordWhat to captureQuestion it answers
Consumer error resolutionNotice timestamp, applicable rule version, investigation events, credit and notice due dates, exceptions and rationaleDid the institution meet its consumer duties?
ACH network actionSettlement and return details, return eligibility, statement received when relevant, actual return timestampWhich network options were available and used?
Evidence and outcomeRecords available at decision time, source, later changes, reviewer, final classification with rationaleWhat did the bank establish about this particular debit?

Review evidence for the specific debit

Start with the transaction and the customer’s account of what happened. Ask what makes the debit unfamiliar or incorrect. Request the authorization and enough supporting detail to connect it to the disputed transaction. For recurring debits, check whether the scope or timing changed and whether the customer canceled or revoked authorization. Where the descriptor caused confusion, capture the name that appeared to the customer and the name the originator uses in its records. Nacha’s discussion of how receiving banks review written statements

An analyst can distinguish an unauthorized debit, an authorized debit subject to another dispute, a processing error, an unresolved case, and a confirmed deliberately false claim. Give reviewers an explicit “insufficient evidence” outcome. Treat repeat claims, a name match, and past payments as context and document the evidence behind the conclusion. A return code describes an action on the network. Keep it in a separate field from the investigative finding. EdEconomy’s guide to fraud data quality and labels

Build a report that tests the proposal’s operational premise

Use one row per disputed ACH entry and a separate event log for notices, evidence requests, responses, credits, returns, and decisions. Join the two on an internal case and entry identifier. Store when each event happened and when staff could see it. That way, analysts can reconstruct what staff knew at each decision point and exclude evidence that arrived later.

Next, pick a defined group of closed cases to review before considering changes to the live workflow. Compare the actual network action with the decision you would make using only records staff had at the chosen cutoff. Keep the original consumer credit and notice record alongside the comparison. Review potential changes in return accuracy, customer access to funds, and staff workload together.

Measures for a first-party fraud evidence report

MeasureHow to calculate itWhat to show beside it
Evidence available by the decision pointCases with usable evidence by the applicable cutoff divided by eligible cases reviewedCases with missing or conflicting evidence, plus the cutoff used
Authorization evidence turnaroundMedian and 90th percentile from evidence request to usable responseOutstanding requests and response rate
Unresolved shareUnresolved cases divided by the reviewed cohort after a defined follow-up periodCohort dates, exclusions, and the treatment of later updates
Decisions changed after re-reviewDecisions changed divided by cases actually re-examinedReason for re-review and the direction of each change
Consumer credit and notice timelinessTimely actions divided by actions due, calculated separately for each dutyCounts by applicable rule, exceptions, and changed customer outcomes

These are suggested operational measures. Define which cases belong in each denominator and who owns each field. For example, seeing authorization evidence by the decision point in 63 of 100 eligible cases gives 63% evidence availability. Label the remaining 37 according to whether a response was late, unusable, or still outstanding. Keep that result separate from the number of deliberate false claims and the dollar value recovered. EdEconomy’s fraud operations dashboard template

Use that breakdown to choose what to fix first. For example, if most missing records arrived late, compare time to request with time to receive a usable response. If most responses arrived on time but lacked proof for the specific debit, improve the evidence request. In both cases, confirm that any workflow change preserves timely consumer credit and notices.

A worked example with a disputed utility payment

In this synthetic case, a customer reports a $146 ACH debit from a utility they previously used. The originating side supplies an enrollment confirmation. The bank records that confirmation as evidence of prior enrollment and asks for the authorization terms and the specific billing record. The customer explains that they canceled autopay and provides an email confirmation.

At the network decision point, staff have the original enrollment record and are still comparing the cancellation and billing dates. They log the evidence they have, the network option they use, and the initial unresolved classification. Meanwhile, the consumer team continues its investigation and records the required credit or notice separately. Later, the originator confirms it processed the debit after the autopay cancellation took effect. Staff record that finding and retain the earlier classification in the event history.

For the dashboard, this case counts as a late evidence response and a classification change. The enrollment record shows the customer once authorized payments. The later response shows the authorization had ended before this debit. The event history lets the bank test whether faster access to cancellation records would improve future decisions.

What to watch after the comment deadline

Track the December 11 comment deadline for the Nacha first-party fraud proposal. If Nacha issues a final rule, compare the final language and effective date with the proposal before revising training, workflows, or dashboards. In the meantime, payments, disputes, compliance, and analytics teams can agree on how to preserve authorization evidence, track the separate deadlines, and measure the impact on customers. Nacha’s consultation and status page · EdEconomy’s Banking Fraud hub

Share your love

Leave a Reply

Your email address will not be published. Required fields are marked *