Summary:

The customer may encounter an error during the supplier import process if the same BBAN value is assigned to multiple different IBANs for the same supplier. In such cases, the supplier details in Basware AP Administration cannot be updated due to system-enforced uniqueness constraints.

For example: The BBAN value 000****1 is same for two IBAN (ABCDEFGH12345 and IJKLMN12345 ) in the following bank details of XML.

<BankAccounts>
      <SupplierBankAccount>
        <Bban>000****1</Bban>
        <Name>002</Name>
        <Iban>ABCDEFGH12345 </Iban>
        <Swift>WELADED1SOS</Swift>
      </SupplierBankAccount>
      <SupplierBankAccount>
        <Bban>000****1</Bban>
        <Name>001</Name>
        <Iban>IJKLMN12345 </Iban>
        <Swift>WELADED1LIP</Swift>
      </SupplierBankAccount>
    </BankAccounts>

Expected System Behavior:

• Ensure that the BBAN value is unique for each IBAN linked to the same supplier in Basware AP Administration.
• When a BBAN already exists in the system for the same supplier, the system displays the error message “Value already in use.”

 Resolution Steps:

• Validate BBAN Value
  Review the BBAN value for the affected supplier in the import file to ensure it is correct.
• Allow Duplicate BBANs (If Required)
  If the same BBAN is already linked to the supplier and the customer wants to add the same BBAN with a different IBAN, they must contact Basware Customer Support.

• Support should update the CMN_TENANT_SETTINGS table under Data Maintenance.
• Change the AllowDuplicateBankAccounts field from "False" to "True".

• Reprocess Supplier Update
  Once the field value is changed, the same BBAN will be accepted by the system in Basware AP.