Track ACH payments
ACH (Automated Clearing House) payments are electronic bank-to-bank transfers used for recurring collections and one-time bank payments. ACH payments follow a different processing timeline than card payments and require dedicated monitoring. This article explains the ACH processing stages, settlement timelines, and how to handle failures.
Important β ACH disputes are NOT defendable like card chargebacks. When a guest's bank issues an ACH return for an authorization-related reason (R07 Authorization Revoked, R10 Customer Advises Not Authorized, R29 Corporate Customer Advises Not Authorized), the funds are reversed and there is no Zenoti-mediated dispute mechanism comparable to card chargebacks. Mitigate risk by verifying bank routing/account details at mandate capture, retaining the signed mandate, and refusing ACH for guests whose history shows authorization-related returns. To enable ACH for guests in the first place, see Configure ACH payments.
Before you begin
Permission: Reconcile Payments (under Payments) β Required to view ACH payment status and processing details.
This article is for back-office staff and operations managers monitoring ACH batches that have already been initiated. To enable ACH for your organization, capture customer mandates, or set up recurring ACH for memberships, see Configure ACH payments.
What ACH payments are
ACH payments transfer funds directly between bank accounts without using card networks. They are commonly used for recurring charges such as membership fees, where the guest authorizes periodic debits from their bank account.
ACH payments are processed in batches rather than individually. This batch processing approach means ACH payments take longer to settle compared to card payments β typically two to five business days.
ACH transaction status values
ACH payments progress through a defined sequence of statuses. The reconciliation view labels each status with a friendly name; the underlying processor enum value is shown in the right column for support escalations.
| Status (article) | Meaning | Processor enum |
|---|---|---|
| Pending | Payment queued for the next batch processing window. The payment request has been created but has not yet been dispatched to the bank. | Pending = 6 |
| Initiated | Batch dispatched to the originating bank. Bank acknowledgement is pending. | Initiated = 7 |
| Settled | Bank has acknowledged the ACH entry and confirmed it has been accepted for processing. Funds are NOT yet deposited in your merchant account. Settled is an intermediate state β the transaction can still be returned within the bank's clearing window. | Cleared = 19 (or Posted = 18 depending on processor) |
| Success | Funds deposited to your merchant account. Transaction is closed for normal accounting purposes, though late returns within the NACHA return window can still occur. | Success = 8 |
| Failed | Bank rejected the ACH entry. See Failed ACH payments for return-code reference. | Failed = 9, DebitFailed = 15, Declined = 20 |
| Reversed | A previously successful debit was later reversed (guest dispute, bank-side error, or NACHA return outside the standard reversal window). | Reversal = 14 |
Settled is not the same as Success. Settled means the bank has acknowledged the entry; Success means funds are deposited. A Settled transaction can still fail if the receiving bank later issues a return β typically within 2 banking days for most reasons, up to 60 calendar days for unauthorized-debit returns (R07/R10/R29). Reconciliation reports SHOULD treat funds as "available" only when status is Success and the NACHA return window has elapsed for high-risk return reasons.
The system prevents concurrent batch processing to ensure data integrity β only one batch job runs at a time.
Settlement timeline
ACH settlement is not instantaneous. From the time you initiate a payment to the time funds are deposited:
| Day | Typical event |
|---|---|
| Day 0 | Payment created in Zenoti (status: Pending). Waits for the next batch processing window β typically the same business day if processed before the daily cut-off, otherwise the next business day. |
| Day 0 or Day 1 | Batch dispatched to originating bank (status: Initiated). |
| Day 1 to Day 2 | Originating bank routes the entry through the ACH network to the receiving (guest's) bank. Status transitions to Settled (Cleared) when the receiving bank acknowledges. |
| Day 1 to Day 3 | Funds deposited to your merchant account. Status transitions to Success. Same-day ACH (where supported by your processor) compresses this to Day 0βDay 1. |
| Day 2 to Day 60 | Return window. Settled or Success transactions can still be reversed: ~2 banking days for insufficient-funds and account-error returns; up to 60 calendar days for authorization-related returns (R07, R10, R29). Status transitions to Reversed if a return is issued. |
Total elapsed time from initiation to final-state Success is typically 2β5 business days, longer when batch dispatch crosses bank holidays. Same-day ACH (when configured) compresses this to one business day for most returns.
Bank holidays
ACH processing does not occur on bank holidays. The system maintains bank holiday calendars to avoid processing on non-business days.
- Payments submitted before a holiday weekend may take additional days to settle.
- Batch processing windows are skipped on holidays.
- Settlement confirmations are not issued on holidays.
Account for bank holidays when estimating settlement timelines, especially around major holiday periods.
Monitor ACH payments
View pending ACH payments and their current status in the reconciliation section:
- Track the progress of individual ACH payments through the four stages.
- Identify payments that have been pending longer than expected.
- Verify that payments have settled as scheduled.
Regular monitoring helps you catch delays early and keeps your reconciliation records accurate.
Field-level details
The reconciliation view surfaces each ACH payment with an identifier, amount, current status (Pending, Initiated, Settled, Success, Failed, Reversed β see ACH transaction status values), submission date, expected settlement date, and (for failures) the NACHA return code. The exact column set, sort order, and filter options differ slightly by processor configuration. For a column-by-column reference specific to your centers, contact Zenoti Support.
Failed ACH payments
An ACH payment can fail if the guest's bank rejects the transaction. The receiving bank issues a NACHA return code that classifies the failure. Common return codes:
| Return code | Reason | Description | Reversal window |
|---|---|---|---|
| R01 | Insufficient funds | The guest's bank account does not have enough funds to cover the debit. | 2 banking days |
| R02 | Account closed | The account has been closed since the mandate was authorized. | 2 banking days |
| R03 | No account / unable to locate | The account number does not match a valid account at the receiving bank. | 2 banking days |
| R04 | Invalid account number | The account number is structurally invalid. | 2 banking days |
| R07 | Authorization revoked | The guest has revoked their authorization for ACH debits. | 60 calendar days |
| R08 | Payment stopped | The guest placed a stop-payment order on the debit. | 60 calendar days |
| R10 | Customer advises not authorized | The guest told the bank the debit was not authorized. | 60 calendar days |
| R29 | Corporate customer advises not authorized | A corporate account-holder told the bank the debit was not authorized. | 60 calendar days |
| R-other | Bank processing error / other | A technical issue at the bank prevented completion, or a less common return reason applies. | Per NACHA rules β typically 2 banking days. |
Failed ACH payments are flagged in the reconciliation view with the return code and reason. The dunning processor will attempt the configured retry per Configure recurring payment rules, unless the return code is in the authorization-related set (R07/R10/R29) β in which case retry is suppressed and the FDO is alerted to contact the guest. For details on switching a guest's payment method or handling repeat failures, see Configure ACH payments.
Note: Failed ACH payments may take several business days to be reported back to your system, as the failure notification must travel through the banking network. R07/R10/R29 returns can arrive up to 60 calendar days after the original Settled status.
How ACH works (background β optional reading)
ACH (Automated Clearing House) is the United States bank-to-bank transfer network governed by NACHA (the National Automated Clearing House Association). NACHA sets the rules for how bank-to-bank entries are originated, settled, and returned. Equivalent regional networks exist in other countries β Pre-Authorized Debit (PAD) in Canada, SEPA Direct Debit in the European Union, and BECS / NPP direct debit in Australia. This article focuses on the US ACH flow; for setup and regional variants, see Configure ACH payments.