ACH Fraud: Who Is Liable? Regulation E, UCC 4A, and BEC

Liability for ACH fraud splits sharply along one line: whether the debited account is a consumer account or a business account. Consumers are shielded by federal law and in most cases pay nothing, or at worst $50, if they report the problem in time. Businesses have no such federal shield; under the Uniform Commercial Code, a company can be stuck with the entire loss when its bank used a reasonable security procedure and followed it. Three bodies of rules decide the outcome in any given case: Regulation E for consumer accounts, UCC Article 4A for business accounts, and the Nacha Operating Rules that govern every bank on the ACH network.

Consumer Accounts: What Regulation E Caps

The Electronic Fund Transfer Act and Regulation E apply to accounts held by a natural person and used primarily for personal, family, or household purposes. A sole proprietor’s business checking account is outside that protection unless it meets the personal-use test.

Regulation E only covers transfers that are “unauthorized,” meaning initiated by someone with no authority to use the account. If you handed over your login credentials voluntarily and the person then misused them, the transfer may not count as unauthorized, and the caps below may not apply.

When the fraud involves a lost or stolen access device (debit card, PIN, or similar credential), liability depends on how fast you report:

  • Report within two business days of learning of the loss, and liability is capped at $50 or the amount of unauthorized transfers before notice, whichever is less.
  • Report after two business days but within 60 days of the bank sending the statement, and liability can climb to $500, but only for transfers the bank can prove earlier notice would have prevented.
  • Fail to report within 60 days of the statement, and liability is unlimited for transfers that occur after the 60-day window closes.

When no access device is involved (someone obtained your routing and account number and pushed through an ACH debit) the first two tiers fall away. The $50 and $500 figures tied to two-business-day reporting do not apply. Your obligation is simpler: review the periodic statement and report any unauthorized ACH debit within 60 days of the statement date. Miss that, and you become liable for later unauthorized transfers the bank can show it would have stopped with earlier notice.

This is the realistic path for most ACH fraud today, which rarely involves a lost debit card and usually involves stolen account numbers. In practice, a consumer who catches the fraud within 60 days of the statement owes nothing.

Provisional Credit While the Bank Investigates

Once you report an unauthorized ACH debit, the bank must investigate. If it cannot wrap up within 10 business days, it must provisionally credit the disputed amount so you can use the funds while the investigation continues. The bank may withhold up to $50 of that credit if it reasonably believes an unauthorized transfer occurred and the reporting requirements for access devices were satisfied. The full investigation can run up to 45 days.

Business Accounts: UCC Article 4A Instead

Business accounts live under a different regime. Regulation E does not apply, so there are no federal liability caps. The governing law is UCC Article 4A, adopted in all 50 states, backed by the Nacha Operating Rules and whatever the account agreement with the bank says.

The Commercially Reasonable Security Procedure Standard

Under Article 4A, if the bank and the business have agreed on a security procedure for verifying payment orders, an unauthorized transfer becomes enforceable against the business when two things are true: the security procedure was commercially reasonable, and the bank actually followed it in accepting the order. The transfer sticks to the business even though it never authorized the payment.

A business can still escape liability in that scenario, but only by proving the fraud did not come from someone with access to its payment systems, security credentials, or transmitting facilities. If a rogue employee or someone with insider access set up the transfer, the business pays. If an outside attacker with no connection to the company’s systems pulled it off, the loss may fall back on the bank.

When the bank did not offer or did not follow a commercially reasonable security procedure, the analysis flips. The bank acted at its own risk and must refund the unauthorized payment plus interest from the date it received the funds.

What counts as commercially reasonable has teeth. Federal banking regulators have said single-factor authentication (a password alone) is inadequate for high-risk transactions like ACH origination. The expected controls include multi-factor authentication, dual authorization for large transfers, transaction limits, and anomaly detection. A business relying on a lone password to send six-figure payments will struggle to argue its security was reasonable, and so will its bank.

The 24-Hour Return Window

The Nacha Operating Rules add a timing trap. Corporate unauthorized ACH debits are returned using reason code R29, and the business has just 24 hours from the settlement date to notify its bank so the return can be sent through the network. Consumers get 60 days under return code R10 for the same kind of problem. A business that does not monitor its accounts daily will miss the R29 window and lose the automated reversal path, leaving negotiation or litigation as the only routes to recover.

The One-Year Outer Deadline

UCC Section 4A-505 imposes a final cutoff. A business customer that fails to object to an unauthorized payment within one year of receiving notice of the debit is permanently barred from challenging it. The theoretical window is longer than a consumer’s 60 days, but the protection inside that window is far thinner.

Business Email Compromise: The Hardest Case

Most business ACH fraud today looks like this: a fraudster impersonates a vendor or executive by email, and an employee with payment authority sends a legitimate-looking ACH to a fraudulent account. The business authorized the payment. The underlying request was a lie, but the transfer itself came from an authorized user.

Under both Regulation E and UCC Article 4A, “unauthorized” means a transfer the account holder did not initiate or approve. A deceived-but-authorized payment is still authorized. The bank is generally under no obligation to reverse it, and the business bears the loss.

There are narrow exceptions. Courts have held banks liable when their own fraud-detection systems flagged a suspicious transaction and they processed it anyway. If the bank failed to follow its own security procedures or the agreed verification protocol, UCC 4A-203 can shift the loss back. Proving any of this takes expensive litigation with uncertain results.

When the Bank Absorbs the Loss

Every ACH transaction involves two banks: the Originating Depository Financial Institution (ODFI), which submits the entry on behalf of the party initiating it, and the Receiving Depository Financial Institution (RDFI), which holds the account being debited.

The ODFI warrants to the whole ACH network that the originator had authorization from the account holder. A fraudulent debit breaches that warranty. Once the RDFI returns the entry as unauthorized, the ODFI has to accept the return and either recover from its own customer (the originator) or eat the loss. That is how a consumer’s $50 ceiling or a cleared business claim actually gets funded: through the network’s unwinding of the ODFI’s warranty.

The RDFI’s duty runs to its own account holder. For consumer accounts, Regulation E prescribes the investigation and provisional credit. For business accounts, the RDFI’s obligations come from the account agreement and the Nacha rules. If the RDFI misses a timely return request, it can end up holding a loss that should have flowed back to the ODFI.

What to Do Right Now If an Unauthorized ACH Debit Appears

Speed decides outcomes. Every hour of delay raises the odds the funds have already been pulled from the recipient’s account.

  • Call your bank’s fraud department, not general customer service, and follow the call with written notice the same day. For a consumer, that starts the Regulation E clock. For a business, that is the only realistic shot at the 24-hour R29 return window.
  • File a police report. Many banks require one before processing a fraud claim, and it creates a contemporaneous record.
  • File a complaint with the FBI’s Internet Crime Complaint Center at ic3.gov. The FBI’s Recovery Asset Team works with banks to freeze fraudulent transfers, but only when the report is fast.
  • Save emails, screenshots, and all correspondence tied to the transaction. For a business, preserve logs showing who had access to payment systems and what security procedures were in place at the time.
  • Read your account agreement. Bank agreements sometimes impose shorter fraud-reporting deadlines than federal law or the UCC, and missing a contractual deadline can sink an otherwise valid claim.

For a business, the review after a fraud should include access controls, password policies, and dual-authorization thresholds. Courts assessing whether a security procedure was commercially reasonable look at what existed when the fraud happened; upgrades installed afterward do not help the pending claim.