US Recurring-Billing +
Recurring invoices with customer ACH / card auto-pay enrollment through the customer's own PSP key, NACHA authorizations and automatic NSF decline retries
Recurring invoices with customer ACH / card auto-pay enrollment through the customer's own PSP key, NACHA authorizations and automatic NSF decline retries
Key Features
ACH & card auto-pay enrollment
ACH & card auto-pay enrollment — capture a customer's payment method once with masked bank routing/account or a card token, a payment-method reference from the provider, and an active/revoked lifecycle.
NACHA authorization capture
NACHA authorization capture — record the Standard Entry Class code (PPD / CCD / WEB), the authorization date, a generated mandate reference and the full authorization language, so recurring debits are properly consented.
BYOK payment providers
BYOK payment providers — each provider record holds the customer's own Stripe or Authorize.Net credentials in a vault; a one-click connection test validates the key before any money moves. No gateway account is bundled.
Recurring billing plans
Recurring billing plans — per-customer plans with product/description, amount, currency, billing interval, start date, optional end date and an automatically maintained next-billing date.
Automatic invoice generation
Automatic invoice generation — a scheduler draws every plan that is due, creates and posts the customer invoice, and links it back to the plan and the enrollment.
Automatic collection
Automatic collection — on invoice generation the module requests the charge through the enrolled provider key and, on success, registers the payment and reconciles the invoice.
NSF & decline retry engine
NSF & decline retry engine — declines are classified (insufficient funds vs hard decline vs gateway error); NSF failures are retried on a configurable back-off schedule up to a maximum attempt count, hard declines are stopped and flagged fo
Transaction ledger
Transaction ledger — every attempt is stored with the normalized response code, gateway message, provider reference and attempt number for a full audit trail per invoice and per customer.
Manual run & retry wizard
Manual run & retry wizard — bill selected plans on demand or force a retry of failed transactions from a guided wizard.
Dunning activities & chatter
Dunning activities & chatter — exhausted retries raise an activity on the responsible user and everything is tracked in the chatter with multi-company scoping and dedicated user / manager roles.
Screenshots
Why Choose This Module
Unlike a generic global subscription add-on, this module is built around the way US businesses actually collect: NACHA recurring ACH debits with a captured authorization (PPD / CCD / WEB standard entry class codes), a mandate reference, and a proper NSF (insufficient funds) retry cadence. Card auto-pay is supported too. Every charge runs against your customer's own Payment Service Provider key (Stripe or Authorize.Net) using a Bring-Your-Own-Key credential vault — the module never routes money through us and ships no hard-coded gateway account.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: base, mail, account
- Support: support@pokutsoft.com
Update date: 2026-07-05
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1509 |
| Technical Name |
us_recurring_billing_ach_auto_pay_enrollment |
| License | OPL-1 |
| Website | https://pokutsoft.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module