I can see there are also numerous other posts about valid export files for direct import to various banks (Santander, Barclays etc.).
My suggestion would be a simple TXT or DAT file export option which is in the exact format of the current exportable format for BAC but with the top 4 header rows omitted, and the bottom 4 trailing rows omitted (including the contra row). This would leave purely the payment lines and I suspect would be compatible with the import processes of most banking systems.
Currently we have a fudge which allows us to import the BAC file directly to Lloyds CBO without any manipulation or post processing but this results in errors being thrown every time we import (due to the trailing rows). Whilst this works, it is far from ideal, as when there is a genuine error it is unlikely to be spotted.
This would seem to be a relatively simple but highly impactful change for many of us.
Steve Boothroyd
supported this idea
·
Adding my vote to this.
I can see there are also numerous other posts about valid export files for direct import to various banks (Santander, Barclays etc.).
My suggestion would be a simple TXT or DAT file export option which is in the exact format of the current exportable format for BAC but with the top 4 header rows omitted, and the bottom 4 trailing rows omitted (including the contra row). This would leave purely the payment lines and I suspect would be compatible with the import processes of most banking systems.
Currently we have a fudge which allows us to import the BAC file directly to Lloyds CBO without any manipulation or post processing but this results in errors being thrown every time we import (due to the trailing rows). Whilst this works, it is far from ideal, as when there is a genuine error it is unlikely to be spotted.
This would seem to be a relatively simple but highly impactful change for many of us.