Loading article…
Loading article…
Last updated on Aug 28, 2026
Advanced Billing lets you customize the information you send and the final action taken for Subscribers who pay via ACH. If you have ACH-based Subscribers, customize your emails to focus on updating banking information instead of card details.
ACH dunning is its own schedule type, separate from Credit Card, Direct Debit, and Remittance, so you build it from scratch rather than editing an existing schedule.
To configure an ACH dunning schedule
There are a few things to decide when setting up your dunning schedule for ACH:
Governing rules of the ACH/electronic payment system allow a total of 2 retry attempts for ACH-based payment methods on file. Advanced Billing abides by these rules and permits 2 retry attempts and 1 final action on the dunning strategy. The final action step does not contain a retry attempt.
When constructing the final action for your dunning strategy, you have two options:

Add, edit, or remove emails for each step in your ACH dunning schedule.
Keep the following limitations in mind:
Include dynamic text in your dunning emails to give the Subscriber the specific information they need, such as why their account is in dunning. See Dunning Email Parameters Reference for the full list of available parameters.

ACH payments can fail after the gateway returns a successful response, since bank transfers settle after the initial charge attempt. Use the methods below to re-collect the funds and reconcile the Subscription.
If the payment fails, the Subscription immediately transitions to Past Due status. From there, the dunning process begins attempting to collect the past-due funds.
You receive notification of a failed ACH payment directly in your Payment Gateway account, once it fails to post, typically several days after Advanced Billing originally submitted the payment. Advanced Billing itself doesn't receive this notification from the Payment Gateway, so it can't automatically flag the failure for you.
Once you've located a failed ACH payment, use one of the following methods to reconcile it.
Use this method when the Subscription has another active payment method on file besides the one that failed.
To retry with a different payment method
This method doesn't trigger any dunning emails, since a failed one-time payment doesn't move a Subscription into a Past Due state.
Use this method to attempt the same payment method again right away, instead of waiting for the next scheduled retry.
To retry the same payment method immediately
Record an External Refund in Advanced Billing. This reduces the revenue in Advanced Billing by the given amount.
As an alternative to a one-time charge, if needed, Adjust Balance on the Subscription to make the next billing amount match what you need to attempt to charge, then change the next billing date to the current timestamp.
Adjusting the balance doesn't charge right away. It increases the amount owed at the Subscription's next renewal. Changing the billing date to the current timestamp is what actually attempts to process the transaction immediately.
If the payment succeeds, move the next billing date back to the appropriate day the Subscription should renew.
If the payment fails instead, the Subscription moves into the Past Due state, which triggers the dunning process and sends an email to the Customer, assuming you have a Day 1 email configured in your dunning settings.
If Authorize.Net is configured to notify you of an ACH failure programmatically, or you listen for Stripe's charge.failed event, use the Advanced Billing API to follow the same reconciliation steps described above.
To decide whether ACH is the right collection method for a Subscription, see Choosing a Dunning Schedule.
For a full breakdown of Subscription lifecycle states, see Understand Subscription States.
Still need help?
Reach out and our support team will take it from here.