| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1490 |
| Technical Name |
us_customer_ach_debit_authorization_collection |
| License | OPL-1 |
| Website | https://pokutsoft.com |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 1490 |
| Technical Name |
us_customer_ach_debit_authorization_collection |
| License | OPL-1 |
| Website | https://pokutsoft.com |
| Versions | 18.0 19.0 |
US Customer ACH Debit
Customer ACH Debit Authorization & Collection File builder with ABA validation and NACHA-style output (BYOK)
Customer ACH Debit Authorization & Collection File builder with ABA validation and NACHA-style output (BYOK)
Key Features
Capture the customer mandate
ABA routing number (validated with the official mod-10 checksum), account number stored full but displayed masked (last four only), account type (checking / savings), Standard Entry Class code (WEB / PPD / CCD), authorization type (single /
SEC-code-specific rules
WEB (internet-initiated consumer debits) requires capturing the authorization-method evidence (how and when the consumer authorized the debit). PPD requires a signed authorization date. CCD is for corporate counterparties.
Revocation tracking
a revoked flag and revoked date freeze the mandate so it is never selected again.
Each recurring mandate carries a next-debit date that
Each recurring mandate carries a next-debit date that is advanced automatically by its frequency (weekly, bi-weekly, monthly, quarterly, annual) every time it is collected.
A collection run selects the authorizations that are
A collection run selects the authorizations that are due (recurring whose next-debit date is reached, plus ad-hoc single mandates) and builds a NACHA-style ACH debit batch file:
File Header Record (type 1)
File Header Record (type 1)
Batch Header Record (type 5), one batch per
Batch Header Record (type 5), one batch per SEC code
Entry Detail Record (type 6) with transaction code
Entry Detail Record (type 6) with transaction code 27 (checking debit) or 37 (savings debit)
Addenda Record (type 7) for WEB entries
Addenda Record (type 7) for WEB entries
Batch Control Record (type 8) with entry/addenda count,
Batch Control Record (type 8) with entry/addenda count, entry hash and total debit amount
File Control Record (type 9) with batch count,
File Control Record (type 9) with batch count, block count, entry/addenda count, entry hash and total debit amount
Records are fixed 94-character lines, blocked to a
Records are fixed 94-character lines, blocked to a factor of 10 with all-9 filler records, exactly as a depository institution expects.
Why Choose This Module
Manage your customers' ACH debit authorizations and build the NACHA-style collection file that your own bank (ODFI) originates. This module is BYOK (bring-your-own-key): it validates and governs the mandate data and produces a standards-compliant file, but it never originates or transmits ACH entries itself.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: 35+
- Author: Pokutsoft
- Dependencies: account
- Support: support@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