| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 950 |
| Technical Name |
pay_aba_becs_generator |
| 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 | 950 |
| Technical Name |
pay_aba_becs_generator |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Australia ABA / BECS Payment File Generator
Bulk supplier & payroll payments as a bank-ready ABA Direct Entry file
Pay your Australian suppliers and staff in bulk by generating a standards-compliant ABA / BECS Direct Entry (Cemtex) file that you upload to your bank's business portal. The module builds the fixed-width 120-character record file — descriptive header (record 0), one detail record per payment (record 1) and the file total trailer (record 7) — validates every Bank-State-Branch (BSB) code and reconciles the trailer totals before you send. Compatible with Odoo 18 and Odoo 19, Community and Enterprise.
Record 0 / 1 / 7 engine
A real fixed-width record engine with exact byte offsets, left/right justification and zero/blank fill per the AusPayNet Direct Entry specification. Amounts are written in cents; the descriptive header carries your financial-institution mnemonic, APCA / Direct Entry user id, lodgement description, processing date and reel sequence.
Self-validating output
After generation the file is re-parsed and checked: every record is exactly 120 characters and the trailer net, credit and debit totals must reconcile to the detail records and their count. A tampered or out-of-balance file is rejected before it can reach your bank.
BSB validation & bank detection
Every BSB is structurally validated and resolved to its parent financial-institution mnemonic (CBA, ANZ, NAB, WBC and more) and state. BSBs are stored on each partner bank account, so payee details flow straight into the batch.
All transaction codes
Pay / salary (53), credit (50), pension (54), allotment (55), dividend (56), debenture / interest (57) and externally-initiated debit (13) for direct-debit collection batches.
Self-balancing files
Optionally append an offsetting record back to your trace account so a credit-only payroll batch nets to zero — the convention several Australian banks require for balanced Direct Entry files.
Build from vendor bills
A one-click wizard pulls posted, not-fully-paid vendor bills into a batch and pre-fills the payee bank details, transaction code and lodgement reference. Review, then generate.
Your bank, your credentials (BYOK)
This module performs no transmission — it only builds the file. You upload it through your own bank's channel with your own credentials. Every bank-specific value (APCA / Direct Entry user id, financial-institution mnemonic, trace BSB and account, lodgement description) is an editable company setting, overridable per batch, so nothing is hard-coded. Confirm the file layout and transaction codes against your bank's current Direct Entry / ABA specification before live use.
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