An ACH debit lets an organization initiate an electronic withdrawal from another party’s bank account. The authorization is the permission behind the instruction, while the ACH Network carries the entry between financial institutions.
Authorization and payment processing are separate
The receiver gives an originator permission to debit a specified account under stated terms. That authorization should identify the nature of the payment, such as a one-time purchase or a recurring obligation, and provide enough information for the customer to understand what was approved.
Authorization does not reserve funds or complete the payment. The originator still has to create an ACH entry, its financial institution must accept and transmit it, and the receiving institution must be able to post it under the applicable rules.
Several parties carry the instruction
The originator sends the debit through an Originating Depository Financial Institution, or ODFI. An ACH operator sorts and delivers the entry to the Receiving Depository Financial Institution, or RDFI, which holds the account to be debited.
Each party has a different role. The originator obtains permission and supplies accurate instructions, the ODFI controls access to the network, the operator processes the batch, and the RDFI posts or returns the entry based on the account and applicable requirements.
The form of permission depends on the use case
Requirements can vary by whether the account is consumer or business, whether the debit is one-time or recurring, and how the authorization is obtained. For recurring preauthorized transfers from a consumer account, Regulation E requires a writing signed or similarly authenticated by the consumer and a copy provided to the consumer.
Nacha rules add operational requirements for ACH participants and entry types. Organizations should retain evidence of authorization, keep the terms accurate and avoid using account information for a purpose or amount outside the authority granted.
A valid authorization does not guarantee settlement
When the debit reaches the RDFI, the account may lack sufficient funds, be closed, contain incorrect information or be subject to another posting issue. The RDFI can return the entry with a reason code under the network’s timing and processing rules.
Settlement between participating institutions and posting to the customer account are connected but distinct operational events. Banks reconcile the entry, settlement totals and account records so an accepted payment is reflected consistently across systems.
Revocation, stop payment and disputes follow defined paths
A customer may revoke an authorization according to its terms and applicable rules, while a stop-payment request asks the account-holding institution not to pay an eligible future entry. Those actions are different from disputing an entry that has already posted.
Rights, deadlines and evidence can differ for consumer and business accounts and by the reason for the claim. Clear records, accessible cancellation methods, transaction alerts and prompt investigation help protect customers while allowing legitimate recurring payments to continue reliably.
Read the primary material
Banking Explained prioritizes regulators, official publications and first-party announcements.