| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 59 |
| Technical Name |
us_payment_nacha_memo |
| License | OPL-1 |
| Website | https://odoo-pro.com.ua |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 59 |
| Technical Name |
us_payment_nacha_memo |
| License | OPL-1 |
| Website | https://odoo-pro.com.ua |
NACHA Addenda Extension for Odoo
Adds 05 Addenda records and correct Entry/Addenda counts to Odoo`s l10n_us_payment_nacha.
This lightweight extension enhances Odoo`s native NACHA ACH export by emitting a single 05 Addenda record per payment (when a memo is present), setting the Addenda Record Indicator, and fixing the Entry/Addenda Count in Batch (record 8) and File (record 9) control records. No new menus or models - just compliant output, out of the box.
Key Features
- 05 Addenda support - Adds one 05 record per payment when Memo is set (up to 80 characters).
- Addenda Record Indicator - Column 79 automatically set to 1 when addenda exists, otherwise 0.
- Correct Entry/Addenda counts - Batch (record 8) and File (record 9) totals include addenda.
- Seamless integration - Works with account.batch.payment; no extra steps or configuration.
- Minimal & safe - Python overrides only; no database schema changes.
Why you need this
Many U.S. banks require payment information (invoice number, reference, etc.) in ACH files. Odoo`s standard NACHA export does not include 05 addenda by default. This extension ensures your files are NACHA-compliant and accepted by banks without manual edits.
Terminology: ACH is the U.S. electronic payments network; NACHA is the governing body and file-format specification. This module focuses on the NACHA file format.
Compatibility
- Odoo 18.0
- Depends on Odoo Enterprise addon l10n_us_payment_nacha
- Works on Odoo.sh, On-Premise
Installation
- Install official l10n_us_payment_nacha.
- Install this module us_payment_nacha_memo.
- Generate ACH/NACHA file from Accounting → Batch Payments as usual.
How it works
- If a payment`s Memo is set, the export adds a single 05 addenda with that memo (trimmed/padded to 80 chars).
- The addenda indicator on the entry line is set to 1.
- Batch/File control records include the addenda in the Entry/Addenda counts.
Note: If your bank requires multiple 05 addenda per entry, contact support - this extension can be adapted.
What`s included
- Python overrides of: _generate_nacha_entry_detail, _generate_nacha_batch_control_record, _generate_nacha_file_control_record.
- No UI changes, no extra configuration.
Support & Customization
Need help or a bank-specific variant? Contact o.ieroshenko@gmail.com.
© Oksana Yeroshenko - This extension modifies Odoo`s l10n_us_payment_nacha output only. Licensing as per the module manifest.
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