| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 996 |
| Technical Name |
pay_bacs_standard18 |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 996 |
| Technical Name |
pay_bacs_standard18 |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
UK BACS Standard 18
Generate Bacs Direct Credit & Direct Debit bulk payment files straight from Odoo — modulus-checked, contra-balanced, ready to submit
Produce a fully-formed BACS Standard 18 file for the United Kingdom three-day clearing cycle. Configure your Service User Number and originating account once, add payment lines, and Odoo builds the 80-column header block, fixed 100-character data records and control-total trailers. Upload it to your sponsoring bank with your own credentials — no payment data leaves your server.
Exact Standard 18 layout
VOL1, HDR1, HDR2 and UHL1 header labels, fixed 100-character data records and UTL1 / EOF1 / EOF2 trailers with reconciling control totals. Correct field offsets, the BACS-safe character set and amounts in pence.
Modulus-checked accounts
Every destination sort code and account number is validated with the published Vocalink modulus algorithms (MOD10, MOD11 and double-alternate DBLAL) before the file is built — catching typos and transpositions that would otherwise bounce three days later.
Three-day processing calendar
A built-in Bacs working-day calendar (weekends plus England & Wales bank holidays, including the Easter-linked days) derives the entry/credit date from your input day, or works back from a desired entry date to the latest valid submission day inside the 30-day advance window.
Credits and Direct Debits
Bacs Direct Credit items and direct-debit collections with first, regular, re-presented and final transaction codes. An optional balancing contra record is appended so the submission nets to zero, as most sponsoring banks require.
Validate before you submit
A pre-submission check blocks hard errors — a malformed Service User Number, a failed modulus check, a missing reference — and warns on weak references, so problems are caught on your screen rather than in a reject report three days later.
Bring your own bank channel
This module builds the Standard 18 file locally and hands it to you. You submit it through your own Bacstel-IP or bank submission software with your own Service User Number and certificate. Nothing is transmitted to any third party by this module.
Compatible with Odoo 18 and 19.
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