Home → Blog → June 2027 ACH Recredit Proposal: 6 Preparation Steps for Originators and Merchants

June 2027 ACH Recredit Proposal: 6 Preparation Steps for Originators and Merchants

By admin Published
By admin · Published October 23, 2026

Call 866-305-6454 to review ACH payment processing and authorization-record procedures.

Nacha has proposed a rule change. It has not been adopted. The proposed effective date is June 18, 2027. The deadline to submit comments is December 11, 2026.

ACH originators, debt collection agencies, billing businesses, and payment providers should understand what the proposal would, and would not, change. The proposal concerns an RDFI’s timing for recrediting an account after a claim about an unauthorized debit. It does not change an originator’s authorization duties. It does not guarantee fewer returns.

What Nacha has proposed

On October 8, 2026, Nacha published a Request for Information and Request for Comment on first-party fraud topics. The RFI asks ACH Network participants for information about the scope of first-party fraud, the roles of involved parties, and possible ways to mitigate the risk. The RFC contains a specific proposed amendment to Nacha Operating Rules Section 3.11.

The proposed amendment addresses what “promptly” means when a Receiving Depository Financial Institution (RDFI) must recredit a Receiver after receiving a Written Statement of Unauthorized Debit (WSUD). In the scenarios described by Nacha, a Receiver tells the RDFI that a debit was unauthorized, and the RDFI may return the debit, generally using Return Reason Code R10.

The proposed wording would clarify that the RDFI’s obligation to promptly recredit does not require it to recredit:

The proposal does not set a specific investigation period for non-consumer accounts. It uses the standard “comparable period reasonably necessary to investigate.” Businesses should not treat that language as a fixed number of days or as permission for an RDFI to delay without limit.

Read the Nacha RFI/RFC page and the October 8, 2026 proposed rule PDF for the source text and response details.

What the proposal would not change

The proposed clarification is about RDFI recredit timing. It does not rewrite an ACH originator’s authorization responsibilities.

Originators and merchants must still ensure that entries are authorized and submitted according to the applicable authorization terms and rules. A change to how an RDFI may handle a claim would not make an invalid, revoked, or misapplied authorization valid. It would not transfer responsibility for an originator’s records to the RDFI.

The proposal also does not change the applicable return timing. Nacha says the RDFI must still recredit the customer before returning the entry. The proposed wording does not eliminate that requirement.

It does not promise that RDFIs will investigate every claim for longer. It does not guarantee that an RDFI will identify a false claim as first-party fraud. And it does not guarantee that returns will fall. Nacha says that some returns potentially could be prevented if an RDFI uses additional review time and identifies a case of first-party fraud. That is a possible outcome, not a guaranteed result.

The distinction matters. A merchant should not treat the proposal as a new defense against returns, a new right to reinstate a debit, or an extension to its own authorization process. The stated proposal addresses the RDFI’s recredit obligation. The originator’s work remains focused on authorization, accurate transaction details, records, and sound customer communication.

Why originators and merchants should pay attention

A consumer or business debit dispute can affect more than one point in the payment chain. The Receiver communicates with the RDFI. The RDFI reviews the claim and may return the entry. The Originating Depository Financial Institution (ODFI), payment provider, and originator may then need to handle the return and related account activity.

Nacha’s broader RFI explores first-party fraud and possible ways participants might identify or mitigate it. Its examples include an accountholder falsely claiming that an authorized debit was unauthorized. The RFI also asks for input on possible transaction identification and data approaches. Those broader questions are not the same as the specific proposed change to Section 3.11.

For an originator, the practical issue is evidence. If a customer disputes a debit, the business may need to determine what was authorized, how the authorization was captured, whether the entry matched its terms, and what communications occurred. A clear, retrievable record helps the business and its payment partners review the facts.

This applies across several business models:

These controls are useful whether or not the proposed rule is adopted. They should not be deferred until June 2027.

Businesses that want a refresher on the underlying rails can review ACH payment processing for small business, which covers B2B invoicing, recurring payments, and same-day settlement. Collection operations can see how return codes and WEB debit rules fit into ACH payment processing for debt collection. And teams that coordinate authorization data across systems can compare payment gateway integration options, from direct APIs to hosted checkout and SDKs.

Graphic novel illustration of a billing operator comparing an ACH authorization record, a customer communication, and a bank transaction statement

Six preparation steps for ACH originators and merchants

1. Review authorization records

Check whether each ACH debit can be traced to a clear authorization record. Confirm that the record identifies the customer, the business, the account or payment method, and the authorized payment terms. For recurring debits, make sure the record identifies the applicable schedule and explains how the amount is determined.

Review how the business captures authorization across each channel. A web checkout, recorded phone interaction, signed document, and customer-service workflow may create different kinds of records. The process should preserve the version of the authorization the customer accepted, along with the date and method of assent.

Do not rely only on a payment processor’s transaction entry as proof of authorization. A transaction record may show that a debit was submitted. It may not, by itself, show the customer’s agreement to the amount, timing, frequency, or purpose of the debit.

Identify gaps now. Where a record is difficult to retrieve, incomplete, or disconnected from the transaction, assign an owner to correct the process. Keep the applicable Nacha Rules, legal requirements, and processor instructions in view when designing or updating authorization procedures.

2. Match each debit to its terms

Compare submitted entries with the authorization that applies to them. Review the amount, timing, frequency, and other transaction details. Confirm that changes to a payment plan, billing schedule, or amount have a documented basis and are handled according to the terms and applicable requirements.

This review is particularly important for recurring billing. A customer may have authorized recurring payments, but the business still needs to ensure that each entry follows the applicable terms. A valid recurring authorization should not be treated as blanket permission to submit any amount on any date.

For one-time payments, link the transaction to the specific payment instruction or agreement. For installments, connect each debit to the installment schedule. For a collection payment, link the payment to the account and payment arrangement involved.

Build a practical way to identify exceptions. For example, flag debits that do not match the recorded amount or schedule, and route them for review before submission. The right control will depend on the business’s systems and payment flow. The goal is to spot a mismatch before it becomes a dispute.

3. Organize evidence for retrieval

Store authorization records and transaction details so the relevant team can retrieve them together. The record set may include the authorization, confirmation sent to the customer, transaction date and amount, account identifier, and relevant customer communications.

Set a clear process for responding to a claim. The responsible team should know where to find the records, who may review them, and how to preserve the review outcome. If the payment provider or ODFI needs specific documentation, confirm the submission process in advance.

Use access controls appropriate to the sensitivity of the information. Avoid informal recordkeeping that leaves bank-account details or customer documents in unprotected files or personal inboxes. Follow applicable retention and security requirements. Confirm exact retention periods with qualified compliance staff, counsel, and payment partners rather than relying on assumptions.

A documented process can also help separate different kinds of issues. A claim that the customer did not authorize the debit is not necessarily the same as a claim that the amount, date, or frequency did not match the authorization. A useful recordkeeping system makes the relevant facts easier to distinguish.

4. Train staff on dispute handling

Make sure customer service, billing, collections, and payment operations understand how an ACH claim is routed. Staff should know how to record the customer’s explanation, preserve relevant communications, and escalate the matter under internal procedures.

Do not coach customers to describe a transaction inaccurately. Do not ask staff to characterize a claim as first-party fraud based on an assumption. The proposed rule does not authorize a merchant to decide the outcome of an RDFI’s review. Keep communications factual and follow the established escalation path.

Review how the business handles a request to cancel or revoke recurring authorization. The process should identify the customer’s instruction, apply it to future activity as required, and record what action the business took. Teams should also know how to handle a question about a particular payment without confusing it with a request to end future debits.

For collection agencies and other sensitive billing operations, standardize what staff may say about a pending or disputed payment. Train teams to avoid promises about return outcomes, recredit timing, or a customer’s legal rights unless those statements have been reviewed and approved by the appropriate compliance function.

5. Check provider and processor procedures

Ask the ODFI, processor, or payment provider how it currently handles unauthorized debit claims and what records it may request. Identify how the provider communicates a return, what detail accompanies it, and where the originator should send supporting documentation or operational questions.

Ask which party is responsible for each task. For example, determine who receives a return notice, who notifies the merchant, who can access the transaction record, and who coordinates follow-up. Clarify how the provider handles a claim involving a consumer account versus a non-consumer account, as applicable to the program.

Do not assume that all providers use the same review process or implementation timeline. Nacha’s proposed effective date concerns the Rules language. Nacha states that it does not require operational changes to be implemented on that date. An RDFI that chooses to make changes may implement them on its own timeline, after communication and education.

Keep provider guidance separate from the proposal itself. Ask whether any provider instruction reflects a current rule, an existing contractual process, or a planned operational change. Record the answer and the date received.

6. Monitor the proposal and document decisions

Assign someone to review Nacha updates and assess whether the proposal progresses, changes, or is not adopted. Use the official RFI/RFC page and proposed rule document as the primary references. Do not update customer terms or operating procedures based only on summaries or assumptions.

If the proposal is adopted, review the final text and effective-date information before making changes. Compare the adopted rule with current procedures. Identify whether any update is needed to staff training, escalation, records, or provider coordination. Do not assume that a proposal’s wording will be identical to a final rule.

Keep a short internal record of decisions. Note what was reviewed, which teams were consulted, whether existing procedures were adequate, and what further action is assigned. This makes it easier to revisit the assessment if Nacha issues a revised proposal or final language.

Nacha requests comments by December 11, 2026. ACH Network participants can use the official RFI/RFC page to review how to respond. Originators and merchants that do not submit a response should still monitor the proposal and keep their authorization practices current.

Graphic novel illustration showing an ACH payment moving between a business, ACH network, and receiving bank, with a separate claim-investigation path

Considerations for debt collection and billing businesses

Debt collection agencies and billing businesses should pay particular attention to the link between the payment record and the underlying customer instruction. A debit may be part of a payment arrangement, invoice, subscription, or other agreement. Staff should be able to retrieve the terms that apply to that specific debit.

Keep payment authorization distinct from other customer documents. A service agreement, account record, or conversation about a balance may provide context, but the business should be able to identify the authorization relevant to the ACH entry. Make sure the record explains the payment method and terms rather than assuming that a general relationship establishes permission for a particular debit.

For recurring payment arrangements, review how the business handles changes. If an amount, due date, frequency, or payment schedule changes, determine what communication or additional authorization is required under the applicable terms and rules. Record the change and connect it to the payments that follow.

Create a clear process for stopping future entries when required. The team that receives a customer instruction should know how to route it to billing operations, confirm that the relevant account is updated, and document the result. Avoid relying on handoffs that are not tracked.

These steps do not determine whether a particular claim is valid. They help the business present accurate records and handle customer instructions consistently. They also remain useful if the proposed rule is changed or not adopted.

What payment providers can do now

Payment providers can review whether merchants have a clear path to transaction and authorization records. They can also assess how return notices, customer inquiries, and supporting documents move between the provider, ODFI, and originator.

Providers should avoid presenting the proposal as a reduction in merchant authorization obligations or as a guarantee that a claim will be investigated for a specific period. The proposal refers to RDFI recredit timing. It does not state that every RDFI will use the additional review time contemplated by the clarification.

Providers can prepare neutral communications that distinguish the proposed rule from current requirements. They can explain that the RFC response deadline is December 11, 2026, and that June 18, 2027 is a proposed effective date, not a confirmed implementation date for operational changes.

They can also make sure merchants know whom to contact for procedural questions. If a merchant receives an unauthorized return, it should follow its provider’s instructions and applicable rules. It should not assume the proposed change creates a new path to resubmit a debit that has been returned as unauthorized.

Timeline and proposal status

Nacha published the RFI/RFC and proposed rule materials on October 8, 2026. Responses are due December 11, 2026. Nacha lists June 18, 2027 as the proposed effective date for the Rules language.

As of this draft, the change remains a proposal. The dates describe the current RFI/RFC process and proposal. They do not mean the amendment has been adopted.

Nacha also states that the proposed effective date would not require RDFIs to implement operational changes on that date. RDFIs that choose to incorporate the provisions could do so on their own timeline. Merchants should therefore confirm any operational instructions with their own payment partners instead of assuming that every provider will change its process at the same time. For context on how a finished Nacha rule change phases in across the network, review how the Same Day ACH dollar limit increase works for B2B payments.

Questions ACH merchants should ask

Does this proposal change how an originator obtains authorization?
No. The proposed clarification concerns the RDFI’s obligation to recredit an account after a claim. It does not change an originator’s authorization duties.

Does it change return timing?
No. Nacha states that the proposal would not change the applicable return timing.

Would the RDFI still need to recredit before returning the entry?
Yes. The proposal does not remove the requirement to recredit the customer before returning the entry.

Does the proposal guarantee fewer returns?
No. Nacha says some returns potentially could be prevented if an RDFI identifies a case of first-party fraud during review. That outcome is not guaranteed.

When would the proposed change take effect?
Nacha lists June 18, 2027 as the proposed effective date. The proposal has not been adopted. Nacha says the date would not require operational changes to be implemented on that day.

What should a merchant do now?
Review authorization and records, confirm provider procedures, train relevant staff, and monitor Nacha’s official materials. Do not change authorization practices based on an assumption that the proposal is final.

Prepare records now; track the proposal

The proposed change is narrow. It concerns the timing of an RDFI’s recredit obligation during an unauthorized debit claim. It does not revise merchant authorization duties, alter return timing, remove the recredit-before-return requirement, or guarantee fewer returns.

ACH originators, debt collection agencies, billing businesses, and payment providers should review their current processes before the proposal advances. Keep authorization records linked to the related entries. Make dispute handling clear. Confirm provider procedures. Monitor Nacha’s official materials for any revised proposal or final rule.

Call 866-305-6454 to discuss ACH processing, payment-provider coordination, and merchant account options.

Primary sources

Draft checklist for review

Need Help With Payment Processing?

Talk to our team about rates, gateways, and solutions for your business.

Get a Free Quote →