ACH Payment Processing for Small Business in 2026: B2B Invoicing, Recurring Payments, and Same-Day Settlement

Call 866-305-6454 to review ACH payment processing for your business.

ACH payment processing gives small businesses a bank-to-bank payment option for invoices, subscriptions, memberships, retainers, and high-value transactions. It can reduce reliance on card payments. It can also support predictable recurring billing.

ACH is not the same as a card transaction. It uses the Automated Clearing House network. Payments move in batches. Settlement timing depends on the submission window, payment type, bank, processor, and applicable operating rules.

A practical ACH program requires more than a payment button. It requires:

• An ACH-enabled merchant account.
• A compatible payment gateway.
• Valid customer authorization.
• Account verification controls.
• Return monitoring.
• Reconciliation procedures.
• Clear handling for consumer and business payments.
• A risk process for industries with elevated chargeback or return exposure.

Bridge Capital Partners helps businesses evaluate ACH, card, gateway, and merchant account options. Review transparent credit card processing pricing, payment gateway integration, high risk merchant account, and available merchant account features.

How ACH processing works for small business

ACH transfers move funds between eligible bank or credit union accounts through the ACH Network. The business receiving or initiating the payment is the originator. The bank or payment provider submitting the entry is generally the Originating Depository Financial Institution, or ODFI. The customer’s bank is the Receiving Depository Financial Institution, or RDFI.

The payment flow usually follows these steps:

1. The customer selects ACH or eCheck.
2. The customer provides bank account information through a secure form or connected account-verification process.
3. The customer authorizes the payment.
4. The merchant or processor creates an ACH entry.
5. The ODFI submits the entry to an ACH operator.
6. The ACH operator distributes the entry to the RDFI.
7. The RDFI posts the debit or credit.
8. Funds settle to the merchant’s account based on the selected settlement schedule.
9. The processor reports approval, settlement, return, or exception status.

The Nacha ACH Developer Guide describes the network roles and basic transaction flow.

ACH debits and ACH credits

An ACH debit pulls funds from the customer’s bank account. The merchant initiates the transaction after receiving authorization.

Common debit uses include:

• Monthly memberships.
• SaaS subscriptions.
• Installment plans.
• Insurance or service payments.
• Retainers.
• Invoice collection.
• Scheduled account withdrawals.

An ACH credit pushes funds to the recipient. The payer initiates the transaction.

Common credit uses include:

• Vendor payments.
• Payroll.
• Contractor payments.
• Refunds.
• Business-to-business disbursements.
• Treasury transfers.

A small business accepting customer payments will often use ACH debits. A business paying vendors may use ACH credits. Some companies use both.

ACH settlement windows

ACH processing is batch-based. A transaction submitted today may not post or settle today. The processor may apply an internal cutoff before the ACH operator’s cutoff. The receiving bank may also apply its own posting schedule.

Standard ACH timing depends on:

• Submission time.
• Settlement date.
• Weekends.
• Federal Reserve holidays.
• Transaction type.
• Bank participation.
• Processor risk controls.
• Whether the transaction qualifies for same-day ACH.

A processor may show a transaction as accepted before the funds are finally settled. “Approved,” “processed,” and “funded” can describe different points in the payment lifecycle.

Do not release high-value goods or services solely because an ACH entry was submitted. Confirm the processor’s risk and funding policy. ACH returns can occur after the initial submission.

ACH vs. credit card processing for small business

ACH and credit cards solve different payment problems.

Credit cards are generally familiar to customers. They support fast authorization. They work well for immediate checkout. They also provide card-network tools for authorization, tokenization, fraud screening, and dispute handling.

ACH can be more economical for recurring and high-value payments. It can also be useful when a customer prefers to pay directly from a bank account.

Cost comparison

Credit card pricing usually includes interchange, assessments, processor markup, and possible gateway or platform charges. The final cost depends on card type, transaction environment, merchant category, routing, authorization data, and pricing model.

ACH pricing may use:

• A flat fee.
• A percentage with a maximum cap.
• A monthly platform fee.
• A return fee.
• A same-day fee.
• A bank-account verification fee.
• A batch or file fee.

Bridge’s pricing page displays $0.25 for ACH/eCheck and an industry average of $0.75. Those figures are Bridge-published pricing comparisons. They are not a universal market price. Actual pricing depends on underwriting, volume, gateway, transaction type, and risk profile.

Use a written comparison. Do not compare only the headline fee. Include:

• Average transaction amount.
• Monthly transaction count.
• Average return rate.
• Same-day usage.
• Refund frequency.
• Recurring billing volume.
• Gateway fees.
• Account fees.
• Reserve requirements.
• Chargeback and return-management costs.

For example, a flat ACH fee may be favorable for a larger invoice. A percentage-based ACH fee with a cap may be favorable for mixed transaction sizes. A card may be better for a low-dollar transaction when immediate approval and customer convenience are priorities.

Settlement timing

Credit card authorization is usually immediate. Funding may occur later based on the merchant’s funding schedule.

ACH processing is not automatically instant. Standard settlement follows ACH processing schedules. Same-day ACH can provide same-business-day settlement when the entry qualifies and reaches the operator before the applicable deadline.

Neither method guarantees immediate usable funds in every situation. Processor underwriting, reserves, holidays, returns, and bank posting rules still apply.

When cards fit better

Credit cards often fit:

• Immediate e-commerce checkout.
• Retail transactions.
• Phone orders.
• Customers who do not want to share bank information.
• Low-dollar purchases.
• International card payments.
• Transactions requiring rapid authorization.
• Businesses using card tokens and card updater services.

When ACH fits better

ACH often fits:

• B2B invoices.
• High-ticket services.
• Monthly memberships.
• SaaS billing.
• Retainers.
• Tuition or recurring service plans.
• Vendor payments.
• Customers seeking a bank-account option.
• Businesses managing predictable payment schedules.

Many businesses should offer both. The checkout or invoice should present the payment choice clearly. The business should route each method through a properly configured account and gateway.

Same-day ACH in 2026: windows, cutoffs, fees, and operating changes

Same-day ACH is designed to support eligible payments that settle on the same business day. It does not mean that every ACH payment becomes instant. It also does not remove the need for authorization, fraud controls, account verification, or return monitoring.

The Federal Reserve FedACH processing schedule lists three same-day transmission deadlines:

Window	Transmission deadline	Target distribution	Settlement
First window	10:30 a.m. ET	Noon ET	1:00 p.m. ET
Second window	2:45 p.m. ET	4:00 p.m. ET	5:00 p.m. ET
Third window	4:45 p.m. ET	5:30 p.m. ET	6:00 p.m. ET

These are FedACH operator schedule times. A bank or processor may impose an earlier customer cutoff. Confirm the processor’s cutoff before promising same-day funding.

Same-day ACH operates on business days. Weekends and Federal Reserve holidays affect the available schedule.

What changed for same-day ACH

The same-day ACH transaction limit is $1,000,000 per entry under current Nacha rules. This is a per-entry limit. It is not a guarantee that a processor will approve an amount at that level.

A processor may impose a lower limit because of:

• New-account risk.
• Industry risk.
• Customer verification.
• Processing history.
• Return history.
• Average ticket size.
• Funding exposure.
• Reserve requirements.

Same-day entries may also carry a special interbank entry fee. The processor or bank may add a customer-facing fee. Ask for the exact fee schedule.

When same-day ACH fits

Use same-day ACH selectively for:

• Urgent B2B invoice payments.
• Time-sensitive vendor payments.
• Same-day account funding.
• Certain payroll or treasury needs.
• Operational situations where next-business-day settlement creates a problem.

Do not use same-day processing for every payment without reviewing the cost. Standard ACH may be sufficient for recurring monthly billing and invoices submitted well before the due date.

Same-day ACH does not eliminate risk

Same-day settlement does not eliminate:

• Invalid account numbers.
• Insufficient funds.
• Consumer disputes.
• Unauthorized debits.
• Duplicate submissions.
• Fraud.
• Processor holds.
• Bank posting delays.

The payment may settle faster. The business still needs controls.

B2B invoicing with ACH and remittance data

ACH can improve B2B invoice collection by giving customers a direct bank-account payment option. The invoice can include:

• Invoice number.
• Customer account number.
• Amount due.
• Due date.
• Payment terms.
• Authorized debit date.
• Payment method.
• Contact information.
• Refund and cancellation instructions.

The processor should return a transaction identifier that can be mapped to the invoice in the accounting system.

Level II-style data and ACH invoices

Level II and Level III data are card-processing concepts. They can reduce interchange qualification costs for eligible commercial card transactions when required data is submitted correctly.

ACH does not use card interchange categories. Adding card Level II or Level III fields does not convert an ACH payment into a lower-cost card transaction.

However, the same discipline is useful for ACH operations. Detailed invoice and remittance information can improve:

• Automated payment matching.
• Accounts receivable posting.
• Customer account reconciliation.
• Partial payment handling.
• Department-level reporting.
• Vendor and buyer approvals.
• Exception management.

For B2B companies, choose a gateway that can connect the payment record to the invoice record. The payment amount, customer identifier, invoice number, and settlement status should flow into the accounting or enterprise resource planning system.

ACH invoice payment flow

A practical invoice workflow is:

1. Generate the invoice.
2. Offer ACH as a payment option.
3. Collect the customer’s bank information through a secure gateway page.
4. Display the debit amount and date.
5. Capture authorization.
6. Send the ACH entry.
7. Mark the invoice as pending or submitted.
8. Monitor settlement and returns.
9. Mark the invoice paid only after the processor’s defined funding condition is met.
10. Reconcile the deposit to the invoice and transaction record.

Do not use a generic “pay by bank” button without reviewing the authorization terms. The customer should understand whether the payment is one-time or recurring.

Recurring ACH for subscriptions and memberships

Recurring ACH works well when the customer has an ongoing obligation. Common examples include:

• Software subscriptions.
• Gym memberships.
• Professional retainers.
• Property services.
• Medical billing arrangements.
• Education programs.
• Maintenance plans.
• Association dues.
• Installment contracts.

The recurring authorization should clearly state:

• The business name.
• The account being debited.
• The payment amount or method for calculating the amount.
• The payment frequency.
• The first debit date.
• The duration or end condition.
• The process for changing the amount.
• The process for revoking authorization.
• A customer service phone number or other contact method.

If the amount changes, the authorization should explain how the customer will be notified and how the amount is determined.

Consumer and corporate rules

Consumer account debits can involve the Electronic Fund Transfer Act and Regulation E, in addition to Nacha rules. Recurring preauthorized transfers from a consumer account generally require written authorization or an electronically authenticated equivalent. The customer must receive a copy of the authorization.

Business account debits are not generally covered by Regulation E in the same way as consumer account debits. Nacha rules and the commercial agreement still apply. Business customers should receive clear terms and maintain an auditable authorization record.

Use the correct Standard Entry Class code. Common examples include:

• PPD: Commonly used for prearranged payments and deposits involving consumer accounts.
• CCD: Commonly used for corporate credit or debit transactions.
• CTX: Used for corporate trade exchanges with expanded remittance information.
• WEB: Used for internet-initiated consumer entries.
• TEL: Used for telephone-initiated consumer entries.

The processor or ODFI should confirm the correct code for the transaction flow. Do not select a code based only on the customer’s preferred payment channel.

WEB debits and consumer authorizations

WEB is associated with internet-initiated consumer ACH entries. It is not a general label for every ACH debit.

A WEB flow should use a secure electronic authorization process. The authorization should be:

• Clearly identified as an ACH debit authorization.
• Presented in a readable format.
• Specific about the amount or calculation method.
• Specific about timing and frequency.
• Clear about cancellation and revocation.
• Connected to a record of customer assent.
• Retained in a reproducible form.

For recurring consumer debits, the authorization should identify the recurring schedule and the conditions that end the authorization.

Written authorizations

A written authorization may be signed on paper or through an electronic signature process that satisfies applicable requirements. Retain a copy that can be reproduced.

The record should connect the authorization to:

• The customer.
• The account.
• The business.
• The payment terms.
• The date and method of authorization.

Electronic authorizations

An electronic authorization should show affirmative customer action. A prechecked box or unclear disclosure creates avoidable risk.

Use:

• An unchecked acceptance box.
• Clear authorization wording.
• A visible amount and schedule.
• A confirmation screen.
• A confirmation email or downloadable copy.
• A timestamp.
• A customer identifier.
• The applicable terms and revocation instructions.

Account access or bank-account linking is not automatically the same as payment authorization. The customer must authorize the debit itself.

Oral authorizations

Oral authorizations are generally associated with TEL entries, not WEB entries. A phone-based payment process should not be mislabeled as an internet-initiated WEB transaction.

For a TEL process, the business and processor should follow applicable Nacha requirements. The record should identify the customer, business, amount, date, account, authorization, and contact information. A recording or written confirmation may be required based on the transaction structure and processor rules.

The FTC payments and billing guidance states that businesses must take steps to ensure charges are authorized. The FTC also warns against billing for automatic shipments, continuity programs, or negative-option offers without express consent.

Retain the authorization record for the period required by the applicable Nacha rules, processor agreement, and law. Your processor should confirm the exact retention policy for each SEC code.

ACH return codes and response procedures

Returns are part of ACH operations. A return code explains why an entry could not be completed or was challenged.

The following codes are specifically relevant to small-business ACH operations.

Code	Meaning	Business response
R01	Insufficient funds	Notify the customer. Follow processor rules for any permitted reinitiation. Do not repeatedly submit without a compliant process.
R02	Account closed	Stop future debits. Contact the customer for updated account information and new authorization.
R03	No account or unable to locate account	Review routing and account data. Correct the record only with customer confirmation.
R06	ODFI requested return	Contact the processor or ODFI. Review possible duplicate, erroneous, or operational submission issues.
R07	Authorization revoked by customer	Stop future recurring debits immediately. Record the revocation. Obtain a new authorization before restarting.
R08	Payment stopped	Determine whether the customer stopped one payment or revoked the recurring authorization. Do not assume the recurring authorization remains usable.
R10	Customer advises originator is not known or authorized	Stop related debits. Investigate authorization and customer identity. Escalate to the processor.
R11	Entry not in accordance with terms of authorization	Compare the debit with the authorization. Correct the amount, date, frequency, or other terms before future processing.
R29	Corporate customer advises not authorized	Apply to the corporate-account scenario. Stop the debit and review the commercial authorization.
R51	RCK entry ineligible or improper	Applies to a Returned Check Conversion entry, not a standard WEB debit. Escalate to the processor.

R01 is a funding problem. R02 and R03 are account-data problems. R07, R10, and R11 are authorization-related. R08 involves a stop payment. R29 applies to corporate customer authorization. R51 relates to RCK entries.

Nacha return-rate controls

Nacha identifies an unauthorized debit return rate threshold of 0.5% for the applicable unauthorized return codes. Nacha also identifies a 3.0% administrative return rate level for R02, R03, and R04. An overall debit return rate level of 15.0% is also identified for review purposes, excluding RCK entries.

These are not business performance targets. They are risk-management thresholds and levels that can prompt review. The Nacha ACH Network Risk and Enforcement resource explains the categories and related procedures.

Track returns by:

• Customer.
• Account.
• Product.
• Payment channel.
• SEC code.
• Date.
• Amount.
• Return reason.
• Authorization record.
• Re-presentment status.

Re-presenting returned entries

Do not automatically retry every return.

A business should:

1. Identify the return code.
2. Determine whether the customer’s authorization remains valid.
3. Confirm whether reinitiation is allowed.
4. Correct account data when appropriate.
5. Obtain new authorization when required.
6. Use the processor’s permitted retry format.
7. Record the retry and outcome.

An unauthorized return should not simply be re-submitted. Nacha rules restrict reinitiation. If the business obtains a new authorization after the return, the transaction may be treated differently, subject to the applicable rules and processor approval.

ACH for high-risk businesses

High-risk businesses may use ACH. Approval and operating terms depend on the business model, customer base, transaction size, refund exposure, regulatory environment, and payment history.

Examples of elevated-risk models may include:

• Subscription services.
• Debt collection.
• Credit repair.
• Nutraceuticals.
• Online services.
• Digital goods.
• Telemarketing.
• Travel.
• Regulated products.
• Businesses with large recurring debits.
• Cross-border or card-not-present operations.

ACH can reduce card acceptance costs. It does not eliminate underwriting risk. A high-risk business may still face:

• Rolling reserves.
• Delayed funding.
• Transaction limits.
• Daily volume limits.
• Additional verification.
• Enhanced customer disclosures.
• Manual review.
• Higher return monitoring.
• Restrictions on recurring debits.
• Separate ACH underwriting.

Bridge’s high-risk merchant account program states that reserve terms are negotiated case by case. The page also identifies support for high-risk verticals and ACH acceptance. Approval is not guaranteed. Underwriting requires accurate information.

Submit:

• Business formation documents.
• Ownership information.
• Government identification.
• Processing statements.
• Bank statements.
• Website terms.
• Refund policy.
• Privacy policy.
• Customer agreements.
• Product or service descriptions.
• Recurring billing terms.
• Fulfillment evidence.
• Chargeback and return history.

Do not hide a business model from the processor. Misclassification can lead to account closure, withheld funds, or compliance escalation.

Gateway and integration options

A payment gateway connects the customer-facing payment form, merchant account, processor, and business software.

Bridge’s gateway page identifies four gateway options with ACH/eCheck support:

• NMI: Flexible for custom integrations, SaaS platforms, and businesses needing API options.
• Authorize.net: Common for small-business e-commerce and recurring billing.
• USAePay: Suitable for batch processing, call centers, and high-volume workflows.
• PayTrace: Useful for B2B payment flows and commercial payment data.

Confirm the exact ACH processor and service enrollment. Gateway support does not always mean ACH is automatically enabled. ACH may require separate underwriting, configuration, or a dedicated electronic-check processor.

NMI

NMI documentation describes ACH/eCheck support through configured electronic-check processing services. NMI supports gateway, hosted payment, tokenization, and API workflows depending on the account configuration.

Relevant documentation includes the NMI ACH and electronic check support section and NMI developer documentation.

Use NMI when the business needs:

• Custom checkout.
• API-based transactions.
• Tokenized payment data.
• Recurring billing.
• Multiple shopping-cart connections.
• ACH and card acceptance through a unified gateway environment.

Authorize.net

Authorize.net documents eCheck.Net support and recurring billing through its ARB tools. The Authorize.net eCheck API documentation identifies ACH types and recurring-use cases.

Authorize.net may fit a business that needs:

• Established e-commerce integrations.
• Hosted payment pages.
• Recurring billing.
• Customer payment profiles.
• API support.
• A familiar merchant interface.

Review the eCheck service agreement and authorization requirements before using recurring debits.

USAePay

USAePay provides ACH/eCheck support through its check-processing tools and transaction API. The USAePay transaction API documentation describes electronic-check processing fields and commands.

USAePay may fit:

• Call centers.
• Batch invoice processing.
• Custom software.
• Businesses with internal payment operations.
• Merchants needing check-sale and check-credit workflows.

Confirm the required fields, test data, check processor, and return-handling process before going live.

PayTrace

PayTrace offers Trace ACH tools for online payments, recurring ACH, payment links, virtual terminal use, and API connections. Review the PayTrace Trace ACH product page and the PayTrace API reference.

PayTrace may fit:

• B2B invoicing.
• Commercial payment acceptance.
• Recurring ACH.
• Payment vault workflows.
• Businesses using accounting or ERP integrations.
• Organizations that need batch and reporting tools.

The business still needs a merchant service provider to enable ACH and complete underwriting.

How to get started with ACH payment processing

Use this implementation sequence.

1. Define the payment use case

Identify whether the business will:

• Accept one-time B2B invoices.
• Collect recurring consumer payments.
• Collect recurring business payments.
• Send vendor payments.
• Process phone authorizations.
• Accept online bank payments.
• Use same-day ACH.
• Combine ACH with cards.

The use case determines the authorization model, SEC code, gateway, data fields, and return procedures.

2. Select the ACH merchant account

The account should support the business model and expected volume. Ask about:

• ACH pricing.
• Per-return fees.
• Same-day fees.
• Funding timing.
• Reserves.
• Transaction limits.
• Recurring billing.
• Consumer and corporate account support.
• International limitations.
• Batch processing.
• Refunds and reversals.
• Account verification.
• Reporting.

A card-only merchant account may not support ACH. ACH may require separate approval.

3. Choose the gateway

Select a gateway based on the current technology stack.

Review:

• API documentation.
• Hosted payment forms.
• Recurring billing.
• Tokenization.
• Invoice support.
• Accounting integrations.
• Webhooks.
• Return reporting.
• Batch upload capability.
• Customer payment profiles.
• Bank-account verification.
• Developer support.

Avoid selecting a gateway based only on brand recognition. The gateway must support the exact payment flow.

4. Verify bank account information

Account verification can reduce R03 and other account-data returns. Options may include:

• Micro-entry verification.
• Instant account verification.
• Database validation.
• Manual confirmation.
• Customer-entered routing and account data with processor screening.

The business should not store bank information in an unsecured spreadsheet. Use a tokenized or processor-hosted collection method when available.

5. Build the authorization process

Create separate authorization flows for:

• One-time consumer debits.
• Recurring consumer debits.
• One-time corporate debits.
• Recurring corporate debits.
• WEB entries.
• TEL entries.
• Invoice payments.
• Preauthorized installments.

Display the payment amount, timing, frequency, business name, revocation process, and customer support contact.

Provide the customer with a copy. Store the record in a reproducible format.

6. Configure reconciliation

Connect ACH transaction records to:

• Customer accounts.
• Invoice numbers.
• Subscription IDs.
• Settlement batches.
• Bank deposits.
• Return records.
• Refund records.

Use a pending status until the processor’s funding policy is satisfied. Reconcile returns separately from successful deposits.

7. Create a return-response policy

Assign responsibility for each code.

For example:

• Billing handles R01.
• Customer support handles R07 and R08.
• Compliance handles R10 and R11.
• Operations handles R02 and R03.
• The processor relationship manager handles R06, R29, and R51.
• Finance reconciles all returned funds.

Set internal deadlines. Stop future debits when authorization is revoked. Do not re-present returns without checking the rules.

8. Add same-day ACH only where justified

Same-day ACH can support urgent cash-flow needs. It can also create additional fees and operational pressure.

Define:

• Eligible transaction types.
• Submission cutoffs.
• Same-day fees.
• Customer disclosures.
• Funding expectations.
• Holiday procedures.
• Exception handling.

Do not promise same-day funds unless the processor confirms the posting and funding policy.

9. Review compliance before launch

Review the program against:

• Nacha Operating Rules.
• Regulation E where consumer accounts are involved.
• FTC payment and billing guidance.
• Processor requirements.
• Bank agreements.
• Privacy and security obligations.
• Industry-specific rules.

The IRS uses bank-account payment methods for tax payments through systems such as Direct Pay and EFTPS. The IRS payment page is relevant when a business is paying federal taxes. IRS payment procedures do not replace the ACH authorization and processing rules that apply when a business collects customer payments.

ACH payment processing checklist

Before launch, confirm:

• ACH is approved on the merchant account.
• The gateway supports the selected ACH flow.
• The correct SEC code is used.
• Consumer and corporate payments are separated.
• WEB and TEL are not confused.
• Authorization terms are clear.
• Recurring frequency is disclosed.
• Revocation instructions are visible.
• Authorization copies are delivered.
• Authorization records are retained.
• Bank-account data is protected.
• Account verification is enabled where appropriate.
• Return notifications are active.
• R01 through R03 procedures are documented.
• R06 operational escalation is assigned.
• R07, R08, R10, and R11 procedures are documented.
• R29 corporate-account handling is understood.
• R51 is recognized as an RCK issue.
• Reinitiation rules are documented.
• Same-day cutoffs are confirmed.
• Same-day fees are disclosed internally.
• Settlement is reconciled to invoices.
• High-risk reserves and limits are understood.
• Customer service can answer ACH questions.
• Finance can identify pending versus funded payments.

ACH payment processing can reduce friction in B2B collections and recurring billing. It works best when the payment method, authorization, gateway, underwriting, and reconciliation process are designed together.

Call 866-305-6454 to evaluate ACH, recurring billing, gateway integration, and merchant account options for your business.

Sources

• Nacha: How ACH Works
• Nacha: ACH Network Risk and Enforcement Topics
• Federal Reserve: FedACH Processing Schedule
• Federal Reserve: FedACH SameDay Service
• FTC: Payments and Billing
• IRS: Make a Payment
• NMI: ACH and Electronic Check Support
• Authorize.net: eCheck API Reference
• USAePay: Transaction API
• PayTrace: Trace ACH