South Africa ACB EFT Payment Files
Generate BankservAfrica ACB 181-character fixed-width EFT files for salary and vendor batches — upload straight to your own bank, no gateway, no per-transaction fees.
What this module does
South African banks accept the standard BankservAfrica ACB (Automated Clearing Bureau) electronic-funds-transfer file for bulk salary and creditor payments. This module builds that file directly from Odoo: you capture or import the payments, click Generate ACB File, download the resulting text file, and upload it to your bank's business-banking portal (FNB Online Banking Enterprise, Absa, Standard Bank, Nedbank, Capitec and others that consume the ACB format).
The file follows the published fixed-width record layout: a 180-character data record terminated by Carriage Return and Line Feed (the “181-character” record the bank documents), assembled in the correct order — installation header, user header, standard transaction records, contra record, user trailer and installation trailer.
Salary & vendor batches
Build a salary/payroll batch (record id 10/12) or a vendor/creditor batch (record id 20/22). Each batch carries a single nominated From account and one action/value date, so it imports as a clean single-contra file.
Up to 100,000 payments
The builder enforces the bank's published per-file limits of 100,000 payment records and 200 contras, and assigns the ascending 6-digit user sequence numbers automatically.
Real ACB hash total
Optionally populate the 12-digit hash total in the user trailer (record 92, positions 73–84), computed exactly as the bank re-derives it: the sum of every 11-digit recipient account (or the right-most 11 digits of a non-standard account) plus each From account once, keeping the right-most 12 digits.
Build from vendor bills
Select posted vendor bills and turn them into a ready ACB batch in one click. Amounts due are grouped per supplier and the recipient bank/branch is resolved from the supplier's bank account.
South African branch codes built in
Recipient routing uses the 6-digit South African branch code. The module ships the published universal branch codes for the major banks — FNB (250655), Absa (632005), Standard Bank (051001), Nedbank (198765), Capitec (470010), Investec, African Bank, Discovery Bank, TymeBank, Bidvest and more — and resolves the bank name from the branch code on every payment line. Every captured branch code is validated as a structurally correct 6-digit value before a file can be generated.
Account types supported
| Recipient account type | ACB code |
|---|---|
| Current / Cheque (and bond drawing) | 1 |
| Savings | 2 |
| Transmission | 3 |
| Bond | 4 |
| Subscription Share | 6 |
| Public Recipient | 0 |
| eWallet (eWallet Pro) | D |
| eWallet (Send Money) | S |
Account numbers longer than 11 digits, eWallet cellphone numbers and public-recipient references are placed in the non-standard account field, with the standard account field zero-filled, exactly as the specification requires.
Feature summary
| Salary (10/12) and vendor (20/22) batches | Yes |
| Fixed-width 180-char records, CR+LF terminated | Yes |
| Installation header / user header / contra / trailers | Yes |
| Ascending user sequence numbers | Automatic |
| 12-digit ACB hash total (optional) | Yes |
| 6-digit branch-code validation + universal codes | Yes |
| Future-dated action / value date | Yes |
| Build batch from posted vendor bills | Yes |
| Per-file limits (100,000 payments / 200 contras) | Enforced |
| Downloadable file + in-app preview + chatter audit | Yes |
How it works — BYOK, no gateway
This module only builds the ACB EFT text file for you to upload to your own bank using your own banking profile and credentials. It transmits nothing to BankservAfrica or to any external service, stores no banking passwords, and makes no claim of being an accredited bureau or system operator. Your payment data never leaves your Odoo database until you upload the file yourself.
Configuration
Under Settings → ACB EFT (South Africa) set your nominated From account branch code, account number and short originator name, and choose whether to include the hash total (enable it if your bank profile has hash-total validation switched on). Then create batches under the ACB EFT menu.
Compatible with Odoo 18 and Odoo 19. Community-only dependencies (Accounting / Invoicing).
Screenshots
Eft Batches
Build From Bills
Settings
Update date: 2026-07-02
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1040 |
| Technical Name |
l10n_za_bankserv_acb_eft |
| 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