As a user who needs to export multiple BACS files for multiple clients, it's currently difficult to identify which file belongs to which client.
It would be very useful if any exported BACS files are prefixed with the client name.
Brian Canner
Feb 19, 2026
When exporting a BACS file, the filename contains some useful information about the week / month in question but it does not identify the company. While this might not matter for a single-entity installation, for a payroll bureau it is a major shortcoming. The danger of loading the wrong BACS file to pay a company's payroll is terrifying.
Please look at adding, say, the "Alternative ID" from the company details screen. We, and I'm sure most of your customers, are using this for our internal client code. This would be perfect to prepend to the BACS filename.
We see this as very important for our confident use of the product and we would be grateful if you would give it your urgent consideration.
When exporting a BACS file, the filename contains some useful information about the week / month in question but it does not identify the company. While this might not matter for a single-entity installation, for a payroll bureau it is a major shortcoming. The danger of loading the wrong BACS file to pay a company's payroll is terrifying.
Please look at adding, say, the "Alternative ID" from the company details screen. We, and I'm sure most of your customers, are using this for our internal client code. This would be perfect to prepend to the BACS filename.
We see this as very important for our confident use of the product and we would be grateful if you would give it your urgent consideration.