
When a customer pays a bill directly from a bank account, an employer deposits wages, or a business pays a supplier electronically, the transaction may be processed through the Automated Clearing House (ACH) network.
But how do ACH payments work once the payment is initiated?
An ACH payment does not simply move directly from one bank account to another. The transaction passes through several stages involving the business or individual initiating the payment, financial institutions, and ACH processing infrastructure. The timing and exact steps can vary depending on the type of transaction and how it is initiated. Understanding this process matters because it explains why ACH payments have processing windows, authorization requirements, settlement stages, and return procedures.
ACH payments work by electronically transmitting payment instructions between financial institutions through the ACH network. The originating party initiates the transaction, its financial institution submits the payment information, an ACH operator processes and routes it, and the receiving financial institution posts the transaction to the recipient’s account.
At a simplified level, the process looks like this:
Payment initiated → Originating bank processes instruction → ACH network routes transaction → Receiving bank receives it → Recipient’s account is credited or debited
The actual process contains several more steps, particularly when authorization, account verification, settlement, and transaction returns are involved.
Every ACH transaction starts with an originating party. That could be:
The direction of the transaction depends on whether it is an ACH credit or ACH debit.
With an ACH credit, the originator instructs money to be sent to another account.
With an ACH debit, the originator initiates a request to collect money from another account after obtaining the required authorization.
Imagine a customer has authorized a software company to collect a hypothetical $100 monthly subscription payment from their checking account.
The customer has provided the necessary bank-account information and authorization. When the monthly payment is due, the software company initiates an ACH debit for the authorized amount. The customer doesn’t manually send the $100 each month. Instead, the business initiates the collection through its ACH payment process.
The payment instruction needs to reach the ACH network through an originating financial institution. This institution is known as the Originating Depository Financial Institution (ODFI).
The ODFI submits ACH entries on behalf of its customer, known as the originator. At this point, the transaction contains information needed to identify the relevant accounts and process the payment according to the applicable ACH rules.
For businesses, this is one reason accurate payment information matters. Incorrect account details can prevent a transaction from reaching the intended account or can contribute to a returned payment.
The ACH network uses ACH operators to process and route transactions between participating financial institutions.
In the United States, the ACH system operates through established network infrastructure rather than functioning like a real-time, one-to-one messaging system between two consumer bank accounts. The ACH operator receives transaction files from originating institutions, processes them, and makes the appropriate transactions available to receiving institutions.
This processing structure is a major reason ACH transactions have defined processing windows rather than behaving exactly like instant payment methods.
The receiving financial institution is known as the Receiving Depository Financial Institution (RDFI). The RDFI receives the ACH transaction and identifies the account associated with the payment instruction.
If the transaction is an ACH credit, the recipient’s account is credited according to the applicable processing and settlement schedule. And, if it is an ACH debit, the receiving institution processes the debit against the customer’s account, subject to the transaction and account conditions. The person or business whose account is affected is referred to as the receiver in ACH terminology.
Processing and settlement are related, but they are not exactly the same thing.
Settlement is the point at which the financial obligations created by the ACH transactions are settled between participating institutions. This distinction helps explain why seeing a payment initiated does not necessarily mean the recipient has immediate access to final funds.
ACH timing can depend on:
Eligible transactions can use Same Day ACH, but that does not mean every ACH payment is automatically instantaneous. For businesses that depend on predictable cash flow, understanding these timing differences is particularly important.
Once the receiving institution processes the transaction, the appropriate account is credited or debited. For example, consider a hypothetical payroll payment:
From the employee’s perspective, the result is simply a deposit appearing in the account. The underlying process involves multiple participants and processing stages.

An ACH transaction does not always reach successful completion. A payment may be returned for reasons such as:
When a transaction is returned, the receiving institution communicates the applicable return information through the ACH system. The specific return code matters because it identifies why the transaction could not be completed and can influence what the originating business should do next.
For example, a business dealing with an insufficient-funds return may need to determine whether and when another collection attempt is appropriate. A transaction involving incorrect account information may require the customer to provide updated banking details. This is why ACH processing doesn’t necessarily end when a payment is submitted. Businesses also need procedures for monitoring returns and reconciling them with their accounting records.
Understanding why ACH transactions are returned and what individual return codes mean becomes particularly important for businesses collecting payments from customers.
The ACH process is mostly invisible to the customer.
A customer might see:
ACH DEBIT — $100.00
on a bank statement after a recurring payment.
The statement doesn’t necessarily show every processing stage that occurred behind the scenes. The transaction may have involved the business, its financial institution, an ACH operator, and the customer’s financial institution before the debit appeared on the account.
This is also why the date a business submits a transaction and the date a customer sees it posted can sometimes differ.
For a business, successful ACH processing involves more than submitting transactions. Finance and operations teams may need to:
For example, a subscription business collecting hundreds of recurring payments cannot simply assume every scheduled debit succeeded. Its payment and accounting processes need to distinguish successful transactions from returns and other exceptions.
This operational layer becomes increasingly important as ACH payment volume grows.
Consider a hypothetical online business collecting a $300 invoice from a customer through ACH debit. The process can be summarized as:
This illustrates why ACH is better understood as a processing system rather than an instant transfer between two consumer banking apps.
It depends on factors such as submission timing, processing windows, banking days, transaction type, and whether Same Day ACH applies. ACH should not automatically be assumed to be instant.
The funds ultimately move between bank accounts, but the transaction is processed through the ACH network and participating financial institutions rather than simply traveling directly between the two banks.
An ODFI, or Originating Depository Financial Institution, is the financial institution that submits ACH transactions into the network on behalf of the originating party.
An RDFI, or Receiving Depository Financial Institution, is the financial institution that receives an ACH transaction for the account holder.
Yes. An ACH transaction can be returned for reasons such as insufficient funds, invalid account information, or other conditions recognized by the ACH rules.
The answer to how ACH payments work becomes much clearer when the transaction is viewed as a sequence rather than a single transfer.
A payment begins with an originator, moves through the originating financial institution and ACH processing infrastructure, reaches the receiving financial institution, and is ultimately posted to the appropriate account. Settlement, processing windows, authorization, and return procedures all play a role along the way.
For businesses, understanding this process is useful for setting realistic payment expectations, managing cash flow, handling returned transactions, and building reliable reconciliation procedures. ACH may appear simple on a bank statement, but several coordinated steps make that final account entry possible.