What is an ACH transfer and how can businesses use them?

An ACH transfer typically takes one to three business days to settle, though most complete in one business day or less. The exact timing depends on three factors: when the transfer was submitted, whether it made your bank's daily cutoff window, and whether it moved through standard ACH or Same-Day ACH. Questions like "do ACH transfers go through on Saturdays" or "why did my transfer take longer than expected" usually trace back to one of those three variables. This guide covers how cutoff windows and same-day processing affect settlement, plus how ACH credits, debits, and returns work underneath the timeline.

TLDR:

• ACH is the batch-based network banks use to move money for payroll, billing, vendor payments, and benefits, built on two transaction types: credits and debits.
• Standard ACH typically settles in 1 to 3 business days; cutoff times, not calendar days, help determine when a transfer moves.
• ACH credits are pushed by the sender, ACH debits are pulled by the receiver, and Nacha applies different settlement obligations to each.
• A returned ACH payment can create follow-on posting, reversal, retry, and reconciliation obligations rather than simply canceling the transaction, and Nacha monitors certain return rates for originators.
• Unit infrastructure supports ACH origination, settlement, and return handling inside financial workflows built through bank partner programs.¹

What Is an ACH Transfer?

ACH stands for Automated Clearing House, the batch-based electronic network that moves money between U.S. bank accounts. Nacha, the National Automated Clearinghouse Association, governs it, and the network handled over 35 billion transactions worth $93 trillion in 2025, covering everything from payroll and government benefit disbursements to subscription billing and B2B vendor payments. Unlike wire transfers, which are typically processed individually, ACH bundles transactions into batches and settles them through the Federal Reserve or The Clearing House on a schedule tied to daily processing windows. This structure helps make ACH cost-efficient at scale for high-volume, recurring payment flows. ACH transactions involve an Originating Depository Financial Institution, or ODFI, which submits the payment, and a Receiving Depository Financial Institution, or RDFI, which receives the entry and posts it to the recipient’s account.

Day to day, a bank collects ACH instructions, bundles them into a file, and submits that file to an ACH operator, either the Federal Reserve’s FedACH service or The Clearing House’s Electronic Payments Network, at a scheduled cutoff. The operator sorts entries by receiving bank and delivers them as a batch rather than processing each one individually, the way a wire typically does. Nacha writes and enforces the rules that participating financial institutions follow, from formatting and authorization to return timelines, allowing thousands of banks to move money under shared standards.

Common ACH use cases include:

• Payroll direct deposit and off-cycle pay runs
• Government benefit disbursements, including Social Security, tax refunds, and unemployment
• Subscription billing and recurring bill pay
• B2B vendor payments and invoice settlement
• Loan and insurance claim disbursements
• Person-to-person and account-to-account transfers

For teams building financial products, ACH is a foundational rail that can support payroll runs, loan disbursements, and recurring collections before a faster-payment overlay is needed.

ACH Credits vs. ACH Debits

ACH transactions are split into two types, and the direction changes settlement speed, authorization requirements, and how much risk the originator carries.

An ACH credit is a push, initiated by the sender. The originator controls timing: payroll deposits, vendor payments, tax refunds, and insurance payouts move as credits because the paying party decides when funds leave its account. Since the sender holds the funds and authorizes the transfer, credit risk generally sits more heavily with the sending side, with less reliance on action by the receiver.

An ACH debit is a pull, initiated by the receiver. Subscription billing, utility auto-pay, loan payments, and B2B invoice collection commonly run as debits because the biller requests funds directly instead of waiting on the customer to pay. Debits can carry more risk for the originator: a pull depends on account details the originator may not have directly verified, so an incorrect account number, a closed account, or insufficient funds can trigger a return after the transaction initially appeared complete. That’s why debit authorization, whether written, verbal, or online, matters under Nacha rules. It provides the record that the originator had permission to initiate the debit.

Nacha's settlement rules reflect different processing treatment for credits and debits: ACH debits generally cannot have a settlement date more than one banking day into the future, while credits can settle the same date, the next banking day, or in two banking days, subject to the sender’s instructions and applicable processing windows. Companies that originate debits typically need stronger account validation and return monitoring workflows, while those originating credits focus more on confirming that funds reach the intended account. Knowing which side of the transaction your product sits on shapes the authorization flow, return handling, and support experience you need to build around ACH.

How Long Does an ACH Transfer Take?

Standard ACH transfers typically settle in one to three business days, though most move faster. Nacha estimates that roughly 80% of ACH volume settles in one banking day or less. The three-day window remains a common upper bound quoted by banks, but actual settlement depends on initiation time, standard versus same-day submission, the receiving bank's posting schedule, and whether the transaction is a credit or debit. For teams assessing enterprise-grade financial infrastructure, these timing details directly shape product decisions.

How ACH Cutoff Times and Processing Windows Work

Cutoff times, not calendar days alone, help determine when an ACH transfer moves. Banks, processors, and ACH operators each have submission deadlines, and a transaction submitted after the applicable cutoff may move in the next available processing window rather than one the user expected.

Here's the path from initiation to settlement:

• The originator or its providers submit the transaction through the Originating Depository Financial Institution (ODFI) before the applicable cutoff.
• The ACH operator, either the Federal Reserve or The Clearing House, sorts and delivers the batch to the receiving bank.
• The receiving bank posts funds, usually the next business day for a transaction that made the cutoff.

A transfer submitted two hours before the cutoff may settle earlier than one submitted two hours after it. Weekends and holidays can add further delay, since ACH operators process transactions on business days. Confirm cutoff schedules with your bank or payment infrastructure provider, since some institutions run multiple batches daily. These mechanics are foundational to embedded banking experiences built on ACH infrastructure.

Same-Day ACH: Windows, Limits, and Use Cases

Same-Day ACH is designed for eligible transactions that cannot wait one to three business days. A qualifying transaction can settle within hours if it is submitted within one of three daily windows: 10:30 AM, 2:45 PM, or 4:45 PM ET. Transactions that miss the last window generally follow standard ACH timing. The per-transaction value is capped at $1 million today, with the limit scheduled to rise to $10 million in September 2027.

Same-Day ACH fits specific situations, not default use:

• Off-cycle or corrected payroll runs
• Urgent B2B payments tied to a deadline
• Insurance claim disbursements where speed affects satisfaction

In 2025, Same-Day ACH carried 1.4 billion payments worth $3.9 trillion, 16.7% more transactions than the prior year, per Nacha's ACH payments fact sheet. Availability also depends on whether the ODFI or provider offers Same-Day ACH, whether the entry is eligible, whether the applicable submission window is met, and the receiving institution’s posting practices.

ACH Timing on Weekends, Holidays, and Fridays

The ACH network generally processes and settles on banking days, so weekends and federal holidays do not count toward settlement. Friday transfers cause the most confusion:

• Before cutoff: enters Friday's batch, settles as early as Monday.
• After cutoff: rolls into Monday's batch, settling Tuesday.
• Saturday or Sunday: nothing moves until Monday's batch.

Federal holidays follow the same logic: a holiday can push the next available processing or settlement date later than a user expects. Same-Day ACH doesn't change this, since its windows also run only on business days. End-user messaging should account for these timing differences rather than relying only on a flat one to three-day assumption, a pattern especially common in vertical SaaS financial services.

Why ACH Payments Are Returned and How Returns Affect Timing

Not every ACH transaction completes as expected. A failed payment comes back as a return entry, which creates follow-on posting, reversal, retry, and reconciliation work rather than simply canceling the transaction. Returns exist because ACH runs on trust between banks instead of real-time verification, so a bad account number, a closed account, or an unauthorized debit may surface only after the transaction has entered the ACH process.

Return codes fall into a few broad categories. Administrative returns cover routine account problems: R01 (insufficient funds), R02 (closed account), R03 (no account found), and R04 (invalid account information), and are generally subject to a two-banking-day return timeframe. Unauthorized returns, including R05, R07, and R10, involve a customer dispute instead of a bank error: the account holder asserts they never approved the debit. Since these are dispute-driven, they can be filed up to 60 calendar days later, well after the transaction looked settled. Return handling ties directly to how bank accounts and wallets are structured on the product side, since a return has to reverse a balance that may have already looked available.

Nacha monitors return activity at the originator level, including an administrative return-rate level of 3% for certain administrative return codes, and an unauthorized debit return-rate threshold of 0.5%. Elevated return activity can lead to review and, depending on the facts, may result in required remediation or restrictions on origination activity. Verifying account details before origination and documenting authorization properly are the two levers that cut down on R03s and R10s, making return handling as much a product design question as a compliance one.

ACH vs. Wire Transfers vs. Instant Payments

ACH, wire transfers, and instant payment rails are not interchangeable, though users searching for ACH timing often mean any of the three. A broader look at money movement for your customers covers how these rails fit together, since each trades speed for cost and reversibility differently.

‍

FedNow and RTP only work when both institutions participate in the same network, limiting reach compared to ACH. A workflow that needs broad reach across counterparties may still need ACH or wire as a fallback, depending on the use case..

What Companies Should Know When Building ACH Into a Product

Building ACH into a product means designing around cutoff windows, not calendar days: end users expect confirmation tied to actual bank deadlines, not a flat one to three-day promise, and that touches origination logic and support scripts alike.

Same-day and standard ACH need separate handling at the infrastructure level, since eligibility and windows differ by transaction type. Credit and debit origination carry their own logic too: pushing payroll or vendor payments calls for different validation than pulling subscription payments or scheduled financing or billing payments. Return and retry logic must run automatically, since return codes can require reversal, retry, balance adjustment, and user messaging logic, covering both fast administrative returns and slower, dispute-driven unauthorized returns.

A few questions are worth asking when evaluating an ACH infrastructure provider:

• Does the provider connect directly to FedACH or The Clearing House, or route through an intermediary processing layer?
• Can the provider originate both credits and debits, with clearing periods configurable per transaction type?
• How much settlement and return visibility is exposed at the transaction level, and how close to real time is it?
• Does return handling update account balances automatically, or does the team have to match and update records manually?
• Does the provider offer a managed path for standard workflows alongside a deeper path for companies that want to own more of the logic?

Nacha monitors return activity for originators, including a 3% administrative return-rate level and a 0.5% unauthorized debit return-rate threshold. Elevated return activity can trigger review and, depending on the facts, required remediation or retraction of the origination activity. 

Debits carry more return risk than credits, since pull-based transactions depend on account details you may not have directly verified, making return-rate monitoring as much a part of the evaluation as settlement speed. Companies that need full control over origination logic, underwriting, and return handling can look into Custom implementation on Unit, while others can lean on a more managed build path on Unit.^1,2,3

How Unit Supports ACH Origination, Settlement, and Returns

Unit supports direct FedACH connectivity for bank partner programs, without an intermediary processing layer, subject to applicable program structure and bank partner requirements. This can give companies access to detailed settlement timing and network-level data that supports more accurate cutoff logic and return visibility. Unit's infrastructure supports ACH credit and debit origination through partner bank programs. Depending on program configuration, companies can initiate pushes to or pulls from end users and configure clearing periods at the payment level to reflect the risk profile of each transaction type. Full documentation is available in the Unit docs.^1,2

Return handling is built into the infrastructure. When an R01 or R02 is received, Unit’s infrastructure can surface the return code and update the payment status based on the return event. Teams can then build retry logic and end-user messaging around those events instead of relying on status polling alone. Settlement and clearing visibility can connect to accounts and wallets records accessed through Unit’s infrastructure, allowing balance updates, holds, and available-funds calculations to reflect ACH processing status based on program configuration. Teams that need greater control over origination logic, risk decisions, and how returns affect end-user accounts can use the Custom implementation path, which provides access to the core API.

What teams can access through Unit's ACH APIs:

• Same-day ACH: Send payments that may settle the same banking day if eligible and submitted within applicable windows
• Return codes: Understand the specific reason why a payment was returned
• ACH trace numbers: Share proof that the payment was originated
• Company identifiers: Configure company identifiers and statement descriptors, subject to applicable rules and bank partner requirements
• Tags: Attach your own metadata to connect entities on Unit with concepts on your platform
• Full payment monitoring: Track originated payments that haven't been transmitted yet, preview when funds are expected to arrive, and programmatically monitor returns

Final Thoughts on How ACH Transfers Work

ACH is a batch-based network with its own participants, rules, and risk logic. It is shaped by the difference between credits and debits, governed by cutoff windows, and supported by a return system that identifies certain problems after a transaction enters a batch. Timing is one output of that system, not the whole system. Companies building on ACH need to design for origination logic, authorization records, return handling, and account balances that accurately reflect settlement status. Connect with our team to talk through how Unit supports ACH origination, settlement, and returns for your product.^1,2

The content in this article is provided for general informational and educational purposes only and should not be construed as legal, tax, accounting, or regulatory advice. Unit does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information provided, and the content may not reflect all considerations relevant to a particular business, product, or use case.

Requirements may vary based on product structure, jurisdiction, bank partner, program design, and other factors.

1. Unit is a financial technology company and is not a bank. Banking services are provided by Unit's bank partner(s), Members FDIC. Unit provides technology infrastructure and program management services to enable clients to offer financial products.

2. Banking and payment services are provided by Unit's bank partners, Members FDIC, and are subject to applicable program terms, eligibility, and approval requirements.

3. Unit supports compliance, risk, and operational workflows, subject to applicable program responsibilities and partner requirements. Compliance, risk management, and fraud prevention remain the responsibility of Unit's bank partner(s) and clients in accordance with applicable program agreements.

FAQ

How long does an ACH transfer take from bank to bank?

Standard ACH transfers settle in one to three business days, though roughly 80% of volume settles in one banking day or less, per Nacha. Actual timing depends on your bank's cutoff window, the applicable ACH processing window, and whether the transaction is a credit or debit.

Do ACH transfers go through on Saturdays, Sundays, or federal holidays?

No. The ACH network generally processes and settles on banking days, so weekends and federal holidays do not count toward ACH settlement timing. A transfer initiated after Friday's cutoff may move in the next available processing window, which can push settlement later than the user expects if a weekend or federal holiday intervenes.

What does ACH stand for and how does it work?

ACH stands for Automated Clearing House, the batch-based electronic network that moves money between U.S. bank accounts. Banks submit payment instructions in batches to an ACH operator, either the Federal Reserve's FedACH service or The Clearing House's Electronic Payments Network, which sorts and delivers them to the receiving bank under rules Nacha writes and enforces across thousands of banks.

What's the fastest way to settle an ACH transfer same day?

Same-Day ACH settles within hours if the transaction makes one of three daily windows: 10:30 AM, 2:45 PM, or 4:45 PM ET. The transaction must be eligible, the ODFI or provider must support Same-Day ACH, and the applicable submission window must be met. The per-transaction cap is $1 million today, rising to $10 million in September 2027. Miss the 4:45 PM ET window and the payment generally moves in a later processing window or follows standard ACH timing, depending on the submission and program setup.

Why are ACH payments returned?

A payment comes back as a return when something prevents it from posting, most often a closed account, an invalid account number, or insufficient funds. Some returns are dispute-driven instead: the account holder says they never authorized the debit. Administrative returns like R01 and R02 are generally subject to a two-banking-day return timeframe, while unauthorized returns can be filed up to 60 calendar days later. Either way, a return creates reversal, retry, balance adjustment, and reconciliation work rather than simply canceling the transaction.