Desktop - 26.10
Release Date: 12/11/2026
This release checks bank statement files before it imports them, and imports OFX files that are saved on one line, such as Standard Bank's OFX download. It also fixes several smaller bank import issues.
Enhancements
Accounting > Bank Import: Menu (button) > Import now checks the whole bank file before it imports anything:
- If the file has a problem, nothing is imported. One message lists every problem (up to 20), each with its transaction or line number. For example:
- An amount with a comma as the decimal separator, or with a thousands separator. Amounts must look like -1234.56.
- A date that is not valid.
- A file that is not an OFX bank statement, or that does not suit the bank account's import type.
- A file without an account number, so it cannot be checked against the selected bank account.
- A comma inside a quoted value in a .csv file.
- A .csv line with fewer columns than the import type needs.
- Correct the file, or the bank account's import type (Import column on Setup > Accounting > Accounts (tab)), and import it again (see How to Import a Bank File and How to Copy and Paste Bank Data on Import in Bank Import & Allocations Tutorial, and Accounting in Error Messages).
Fixes
Fixed: Accounting > Bank Import – OFX files saved on one line, such as Standard Bank's OFX download, did not import and showed "List index out of bounds". They now import like any other OFX file.
Fixed: Accounting > Bank Import – On a computer whose Windows regional settings use a comma as the decimal separator, every imported amount was 0. Amounts are now read correctly, whatever the regional settings.
Fixed: Accounting > Bank Import – A file with a date that was not valid stopped the import part of the way through, and the transactions before that date stayed imported. An amount that could not be read was imported as 0. Both now stop the import before anything is saved.
Fixed: Accounting > Bank Import – The file is now moved to the Imported folder only when transactions were imported. A file that does not match the bank account, has a problem, or contains only transactions that were already imported stays where it is (see How to Import a Bank File in Bank Import & Allocations Tutorial).
Fixed: Accounting > Bank Import – A file that did not match the selected bank account also showed "Zero records have been imported". Only the message about the bank account appears now.
Fixed: Accounting > Bank Import > Matching Record – A matching record only appeared when the bank entry just before it, with the same text, had been posted. A Pending entry in between, or a posted entry imported later, hid the match. The matching record is now the latest posted entry with the same text in the same bank account, whatever its order in the bank statement. Entries from other bank accounts are no longer matched (see How to Import a Transaction Into the Ledger in Bank Import & Allocations Tutorial).