Skip to main content

How is the SWIFT/BIC field validated for bank accounts

The following validations are used on the SWIFT/BIC field on the Bank Account page in the Mobile Employee Experience (MEE) and in the Equus Platform: follows the proper format: 4 letter bank code, 2

Updated over 2 weeks ago

The following validations are used on the SWIFT/BIC field on the Bank Account page in the Mobile Employee Experience (MEE) and in the Equus Platform:

  • follows the proper format: 4 letter bank code, 2 letter country code, 2 digit location code and an optional 3 digit branch code

  • the length is correct - 8 or 11 characters with dash or spaces

  • contains no illegal characters are added - the presence of illegal characters will not be allowed on input

If validations are not met, the user will be presented with an error message: "The SWIFT/BIC must be a valid value.” and the value will not be saved until a valid value is entered.

mceclip0.png

When a valid SWIFT/BIC is used, further checks are performed using the Account Currency and Country fields.

Below is an example where a valid SWIFT/BIC for the United Kingdom is entered and passes the country and currency validations.

When a valid SWIFT/BIC does not pass the country and/or currency validations, a yellow colored warning message is displayed underneath the field. These warnings do not indicate incorrect data but data inconsistency. Users will be allowed to save the record and warnings will persist until the user "fixes" the possible inconsistency.

After saving, Intermediate Bank Information can be added. Intermediate Bank could be a bank, credit union, or clearing house the payment moves through before reaching the final bank for ultimate payment. On the Intermediate Banks section, you can add, edit, and delete a new record.

In the Equus Platform, warnings are indicated with the

mceclip4.png

icon beside the field. Hovering the cursor over the icon will display the reason for the warning and a banner at the top of the screen reinforces the message to the user to validate.

Did this answer your question?