Article

ACH Return Codes: A Guide for Construction Payments

Headshot of Ethan- Staff Solution Engineer
Ethan Albers
Nov 10, 2026
Illustration of an ACH return code (R03) document moving through payment verification and approval workflow.

An ACH return can leave a construction payment unresolved, delay reconciliation, and leave lien waiver documentation incomplete before a draw or closeout. With Nacha reporting 35.2 billion ACH Network payments valued at $93 trillion in 2025, finance teams need a precise way to diagnose exceptions. ACH return codes explain why an entry was sent back.

The next step depends on the entry direction, account type, Standard Entry Class code, and banks involved. Built connects ACH payments with lien waiver exchange so GC controllers can monitor payment and waiver status in one workflow. This guide covers code meanings, deadlines, retry rules, and construction payment controls.

That control matters now. Nacha’s March 20 and June 19, 2026 fraud-monitoring phases are complete and apply across the ACH ecosystem.

What Are ACH Return Codes?

ACH return codes are three-character identifiers that explain why an Automated Clearing House (ACH) entry was sent back. The code alone is not a complete diagnosis. Finance teams must first confirm the original entry direction, account type, Standard Entry Class code, and bank roles.

Two financial institutions participate in an ACH entry. The Originating Depository Financial Institution (ODFI) sends the entry. The Receiving Depository Financial Institution (RDFI) receives it and may return it under the applicable Nacha rule.

In 2025, the ACH Network processed 35.2 billion payments valued at $93 trillion. That figure describes the full ACH Network, not construction payment volume.

Funding debits

R01, R05, R07, R08, R09, R10, R11, and R29 are debit-centered codes within their documented boundaries. They should not be presented as ordinary explanations for an incoming subcontractor payout credit.

For example, R01 means a debit could not be covered by the available balance. It does not mean a subcontractor lacked funds to receive a credit payment.

Subcontractor payout credits

Credit entries can be returned for different reasons. R23 can apply when a receiver refuses an incoming credit. R16, R17, R20, R24, or another code may apply when its specific facts and entry requirements are met.

Complete List of ACH Return Codes

This construction-relevant table does not list every R01 through R85 code. Corporate Credit or Debit (CCD) and Corporate Trade Exchange (CTX) identify business entries. Confirm the entry direction, account type, and Nacha Rules before acting.

CodeNameConstruction-relevant meaningPayment leg
R01Insufficient FundsAvailable funds do not cover a debit entry.Debit
R02Account ClosedThe receiving account has been closed.Debit or credit, based on entry facts
R03No Account or Unable to Locate AccountThe receiving institution cannot locate the account from the submitted details.Debit or credit, based on entry facts
R04Invalid Account Number StructureThe account number structure is invalid.Debit or credit, based on entry facts
R06Returned per ODFI’s RequestThe ODFI asked the RDFI to return the entry. The request does not force the return.Debit or credit
R09Uncollected FundsThe ledger balance may cover the debit, but available funds do not.Debit
R10Customer Advises Originator Is Not Known or Not AuthorizedThe receiver does not know the originator, has no relationship with it, or did not authorize the debit.Consumer debit context
R11Customer Advises Entry Not in Accordance with the Terms of the AuthorizationAn authorization exists, but the debit did not follow its terms.Consumer debit context
R16Account Frozen or Entry Returned per OFAC InstructionThe code combines an account-frozen meaning with an Office of Foreign Assets Control (OFAC) instruction.Debit or credit
R17File Record Edit CriteriaAn RDFI may also use R17 in defined questionable-circumstances or fraud-recovery situations.Depends on the qualifying facts
R20Non-Transaction AccountThe receiving account does not permit the attempted ACH activity.Debit or credit, based on entry facts
R23Credit Entry Refused by ReceiverThe receiver refused an incoming ACH credit, and the RDFI may return it.Credit
R24Duplicate EntryThe RDFI identified an apparent duplicate entry.Debit or credit
R29Corporate Customer Advises Not AuthorizedA non-consumer receiver says a CCD or CTX debit was not authorized.Corporate debit
R31Permissible Return EntryThe RDFI may return a CCD or CTX entry that the ODFI agrees to accept.CCD or CTX entry
R51Item Related to RCK Entry Is Ineligible or ImproperThe code concerns re-presented check (RCK) activity, not a standard vendor payout credit.RCK debit context

Sources: Nacha code mapping, debit returns, R17, and R16 and R23.

Most Common ACH Return Codes Explained

This heading preserves the live page structure. The codes below often require diagnosis, but the research does not establish their frequency in construction payouts.

R01: insufficient funds

R01 applies to a debit when available funds cannot cover the entry. It does not describe an incoming credit payment to a subcontractor.

R02: account closed

R02 means the receiving account is closed. Do not retry the same account details.

Obtain updated banking information through a verified channel. Use the existing vendor record to confirm the request.

R03: no account found

R03 means the receiving institution could not locate the account using the submitted details. A transposed digit, stale account record, or account-name mismatch may require correction.

Verify the routing number, account number, and account ownership before resubmitting. Do not assume R03 indicates insufficient funds.

R04: invalid account number

R04 means the account number structure is invalid. The number may have the wrong length or fail the receiving institution’s validation.

R03 and R04 point to different account-data problems. Both require verified information before another entry is sent.

R29: corporate customer advises not authorized

R29 applies to a non-consumer CCD or CTX debit when the corporate receiver says the entry was not authorized. Its return timeframe is two banking days, not 60 calendar days.

R29 is not the same as R10. R10 covers the supported consumer context when the receiver does not know the originator, lacks a relationship with it, or did not authorize the debit.

ACH Return Deadlines, Thresholds, and Fraud Rules

Return timing depends on the code, original entry, account type, and facts. Banking days and calendar days are not interchangeable.

Standard and extended return deadlines

R29 has a two-banking-day timeframe for the supported non-consumer CCD or CTX unauthorized debit context. R11 has a 60-calendar-day window in the cited extended-return context, with a Written Statement of Unauthorized Debit required.

R23 timing runs through the second banking day after the RDFI receives notice that the receiver refused the credit. R06 has no fixed return deadline in the cited table. The RDFI must provide a decision or status within 10 banking days after a request.

Return-rate thresholds for debit entries

Nacha’s return-rate framework uses three distinct debit measures. The unauthorized debit-return threshold is 0.5%. The administrative debit return-rate level is 3% for R02, R03, and R04.

The overall debit return-rate level is 15%, excluding RCK entries. The 3% and 15% figures are review or inquiry levels. Crossing either figure does not automatically establish a Nacha Rules violation.

Nacha fraud rules that took effect in 2024 and 2026

Since October 1, 2024, an RDFI may use R17 in defined questionable-circumstances or fraud-recovery situations. For that use, the addenda must include QUESTIONABLE in the first 12 positions.

Nacha defines False Pretenses around misrepresentation of identity, authority, association, or ownership of the credited account. It does not cover ordinary disputes about nonexistent, poor-quality, or misrepresented goods and services.

The March 20 and June 19, 2026 phases cover specified ACH participants. They require risk-based procedures reasonably intended to identify unauthorized entries or entries authorized under False Pretenses.

The procedures require at least annual review. Nacha does not require universal screening of every entry before posting.

Why a returned payment can hold a construction draw

A returned payment can leave payment records, waiver status, and draw support out of sync. The GC controller must reconcile the return and confirm the related waiver.

An incomplete waiver record can delay a draw package or raise questions during owner, lender, or audit review. See these common payment issues in construction for related failure points.

How to Handle and Prevent ACH Returns on Construction Projects

A returned entry needs a code-specific response.

  1. Identify the code and payment leg. Confirm whether the original entry was a debit or credit. Check the account type and Standard Entry Class code.
  2. Contact the correct party. The bank, subcontractor, supplier, or internal payment owner may hold the information needed for resolution.
  3. Verify corrected banking information. Use an established contact method. Do not rely only on a new phone number or email included in a change request.
  4. Reinitiate only when permitted. R01 and R09 debit entries have specific retry limits. R11 has a separate correction path for eligible defects.
  5. Recheck lien waiver status. Confirm that the payment record and waiver record reflect the corrected outcome before closing the workflow.
  6. Document the exception. Keep the return code, bank communication, corrected information, approval, and final payment status together.

R06 should not be treated as a reversal. It identifies a return requested by the ODFI, and the RDFI decides whether to return the entry.

A reversal is a sender-originated correction for a permitted error, including a duplicate payment, incorrect amount, wrong date, or unintended account. Nacha requires reversals within five banking days. A reversal is not a general cancellation or guaranteed recovery method.

Prevention starts with verified bank details, controlled change requests, and clear payment ownership. Keep records current across projects and review exception patterns before the next payment run.

ACH remains useful when teams apply those controls. Read more about using ACH for construction payments and how lien waivers affect construction payments.

How Built Helps Construction Teams Manage ACH Payments

Built connects ACH payments and lien waiver exchange in one construction payment workflow. Its standard ACH payments are free to the sender, while recipients may pay for faster access.

Subcontractors can receive an email and complete the waiver flow without maintaining a full account. Its payment status visibility gives GC finance teams a shared record for follow-up and reconciliation.

Rod Heisler Construction reports that its process prompts waiver collection and helps trade partners get paid faster. Waltz Construction reports that reducing check cutting and compliance follow-up gives its team more time for project financial work.

Talk to our team about connecting payments, waiver collection, and payment status in one workflow.

ACH Return Code FAQs

What does ACH return code R01 mean?

R01 means insufficient funds for a debit entry. It does not describe a standard credit payout to a subcontractor or supplier. A debit returned as R01 may be reinitiated no more than twice within 180 days of the original settlement date.

The reinitiated entry must use RETRY PYMT and preserve required identifying fields. This retry rule does not apply to every return code.

What is the difference between R03 and R04?

R03 and R04 are administrative return codes tied to account information. R03 indicates that the receiving institution could not locate the account using the submitted details. R04 indicates that the account number structure is invalid.

Before resubmitting, verify the routing number, account number, and account ownership through an established contact channel. Neither code establishes that a subcontractor payout failed because the recipient lacked funds.

Is R29 the same as R10?

No. R29 applies to a non-consumer CCD or CTX debit when the corporate receiver says the entry was not authorized. Its return timeframe is two banking days.

R10 applies in the supported consumer context when the receiver does not know the originator or has no relationship with it. R10 also applies when the receiver did not authorize the debit. Do not substitute R10 consumer rules for a corporate CCD or CTX debit.

What does R16 mean?

As of November 9, 2026, R16 means “Account Frozen/Entry Returned Per OFAC Instruction”. The code can apply to consumer and non-consumer accounts. An R16 return does not prove that every case involved a sanctions decision.

Nacha plans to separate the meanings through a future R90 and R16 rule change on March 17, 2028. That change is not current practice.

How long does it take to process an ACH return?

ACH return timing depends on the code and transaction context. R29 has a two-banking-day timeframe for the supported non-consumer CCD or CTX unauthorized debit context. R11 uses a 60-calendar-day window in the cited extended-return context.

R23 timing runs to the second banking day after the receiving bank is notified that the receiver refused the credit. R06 has no fixed return deadline in the cited table.

Can you resubmit an ACH payment after it is returned?

Sometimes. A debit returned as R01 or R09 may be reinitiated no more than twice within 180 days of the original settlement date. The description field must use RETRY PYMT.

An eligible R11 defect may be corrected and submitted as a new entry within 60 days of the R11 return entry’s settlement date. These rules do not create a general right to retry every returned debit or credit.

What is the difference between an ACH return and an ACH reversal?

An ACH return is sent back by the receiving side because the entry could not be accepted. An ACH reversal is originated by the sender to correct a permitted error. Those errors include a duplicate payment, incorrect amount, wrong date, or payment sent to an unintended account.

Reversals must be transmitted within five banking days. A reversal is not a general cancellation or guaranteed recovery method, and it may also be returned.

Headshot of Ethan- Staff Solution Engineer
Written by Ethan Albers
Ethan Albers is a Staff Solution Engineer at Built. He’s spent time on the actual jobsite, not just behind a screen, and it shows up in the way he talks to developers and GCs. Before Built, he worked project and field engineering roles at Turner Construction, including a stretch on healthcare renovation projects for the Cleveland Clinic. He’s based in Nashville and holds a mechanical engineering degree from Case Western Reserve University.

Built Payments for Construction

Free ACH, lien waivers tied to every payment, and subs paid in 1 to 2 days. One workflow from waiver to funds.

Illustration of an ACH return code (R03) document moving through payment verification and approval workflow.