Batch payment - Custom column mapping and layout configuration for CSV payment files
At the moment we have to manipulate a .csv file in order to get it accepted by our bank. The .bacs file is useless because it doesn't pick up individual beneficiary references and the .csv has the wrong columns in the wrong order.
Systems I have used before allow you to 'map' your .csv output file in your company settings. You add the amount of columns you need and then choose what goes into each one.
Having this capability would mean it wouldn't matter what Bank you use, you would be able to use the .csv option without compromising the file.
The systems I have used previously are much less used than Xero, so it can't be a difficult thing to program.
Karen Sparkes
shared this idea
Thanks for raising this suggestion. The request is to choose which columns are included in a batch payment CSV and control their order.
This could make it easier to prepare payment files for banks with different upload requirements, without needing to edit the exported file in Excel each time.
I’ve moved this to Gaining Support so we can continue gathering feedback. If this would be useful, add your vote and share what your bank requires.
-
Karen Sparkes
commented
Our bank uses the Sage/Sif Pegasus file. That uses columns 'Sort Code', 'Beneficiary Name', 'Bank Account Number', 'Amount' and 'Beneficiary Reference', along with a fixed column with '99' in it.