UK Banking Configuration - OY17, F110

[Chris_547]

We are looking to transition our bank number configuration for our UK banks from 6 (for UK sort codes) to 11 for SWIFT codes. This is seen utilizing t-code OY17. 

Also, we currently run payments from F110 utilizing the BACS payment system at our bank using payment file uploads.

Could there be downstream effects to making this banking configuration change to the payment files or our vendor's bank numbers?

[Rob_McNally · Accepted solution]

The configuration is checking the maximum length, so it should be fine to update the configuration to increase the value in OY17

Some UK banks require a consistent use of BIC/IBAN or Sort/Account Number in the BACS file. i.e. All creditor & debtor bank institution & bank account identifiers in the file have to all be either Sort Code / Bank Account or BIC / IBANs. 

The BIC/IBAN & Sort/Account are populated in different tags in the ISO20020 BACS file format & should not be 'overpopulated' (i.e. should not appear twice - once in the sort/account & then in the BIC/IBAN tags), so update of the BACS file generation routine or DME is likely & validation/testing with the bank is highly recommended

[Chris_547 · Accepted solution]

Thank you for confirming this! We currently use sort/ account number combination and want to allow BICs to be entered. We'll definitely test our DME files if we make those changes.