Skip to Content
Product Information
Author's profile photo Viola Kaiser

How to deal with bank keys and bank account numbers

We’ve noticed that customers seem to have recurring issues with bank account numbers and bank keys when dealing with bank master data. To make your life easier, we’d like to share the following information with you:

Bank Key

First, it’s important to note that the bank key is a unique, country-dependent identifier. It is an SAP internal ID used to uniquely identify a bank. This ID, together with the country key, links to the other bank data in the system, such as name, bank number, and SWIFT code/BIC.

To make the data easier to use and more transparent, it’s possible to set up the bank key to match the bank number for your home country (bank key type 1) or to match the SWIFT code for foreign countries (bank key type 4).

If you set up the bank key to match the bank number, the key will have the same format rules as any other bank number. If you set up the bank key to match the SWIFT code, the key will be limited to 11 alphanumeric characters.

If you do not have explicit information about the length of the bank number for a country, you can enter the maximum value of 15 characters and restrict it later, once you have the exact data.

For more information, please refer to SAP note 1529550.

Bank Account

Just like the bank key, the bank account number is a country-dependent number that is related to a specific bank. It is linked to one currency at a time. If you enter an invalid account number, an error message is displayed. It may be, for example, that you entered a bank account number that is too long. Let’s say the country-specific limit for bank account numbers is 10 characters, but you entered a number with 23 characters. In that case, you’ll get an error message telling you that the data you entered has a different format than that defined in the country-specific checks. You will be asked to check your entries and correct your settings for the country-specific checks.

You can find out more about these formats by checking the “Set Country-Specific Checks” configuration step.

To do this, go into the Manage Your Solution app and select Configure Your Solution > Application Platform and Infrastructure > General Setting > Set Country-Specific Checks.

SSCUI_Overview.JPG

This “Set Country-Specific Checks” configuration step allows you to define checks for bank key length and rules for formal checks that are applied during master data maintenance. In the Overview, select the relevant country by double-clicking it. In this example we select DE – Germany.


SSCUI.JPG

On the next screen, we can see the length and checking rules that were set up for Germany. In our example, the bank account number is limited to 10 characters.


SSCUI_Detail.JPG

For more information regarding our recommended settings for certain countries, please refer to SAP note 1012293.

So far, so good. But how can you avoid such errors?

As a very simple approach, we propose that you use IBANs instead of bank account numbers, because IBANs are less error-prone. It is, of course, possible to enter both bank account number and IBAN. In this case, the IBAN always has the higher priority. This means that as soon as you maintain an IBAN, it will be used instead of the bank account number. Keep in mind that for SEPA transfers, you need to maintain an IBAN, because it is not possible to make such a transfer with only the bank account number.

We hope this makes your work with bank master data easier. If you have more questions, let us know!

Assigned Tags

      18 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Harika Gali
      Harika Gali

      The very useful document, Thank you!

      Author's profile photo Hima Paluri
      Hima Paluri

      Good one.. Thank you..

      Author's profile photo Shakeel Ahmed
      Shakeel Ahmed

      Thank you for sharing

      Author's profile photo Sandeep Kumar
      Sandeep Kumar

      Very useful, thanks for sharing.

      Author's profile photo Owen Liu
      Owen Liu

      Thanks for sharing

      Author's profile photo Ana Moreira
      Ana Moreira

      Thanks Viola, very helpful

      Author's profile photo Cassiano Lins
      Cassiano Lins

      Viola Kaiser thank you for this content!

      Author's profile photo Vijayendra Tiwari
      Vijayendra Tiwari

      Thanks for this information. Very recently only I dealt with issue related to them..

      Author's profile photo Anup Nair
      Anup Nair

      Thank you Viola, Informative Blog!

      Author's profile photo Priyank Kumar Jain
      Priyank Kumar Jain

      Thank you Viola , do you know if the set up of bank key to match bank number can be done via the data migration app as well? I mean if it is set up, does it overwrite the bank key specified in the template?

      Author's profile photo Viola Kaiser
      Viola Kaiser
      Blog Post Author

      Hi Priyank Kumar Jain, thank you for your question! Data migration does not change the bank key. Instead it just copies the values from the original system to the target system. Therefore, it is essential to make sure that the records are consistent. If you have further questions, feel free to reach out.

      Author's profile photo Rachel Suo
      Rachel Suo

      Thanks for this useful sharing!

      Author's profile photo Liling Jia
      Liling Jia

      Thanks for the sharing. it good to learn

      Author's profile photo Harika Gali
      Harika Gali

      Thanks

      Author's profile photo John Keells IT Support
      John Keells IT Support

      Hello,

       

      THanks for sharing this,I have a doubt in maintaining the bank routing control key in Bank keys.

       

      Kindly advise.

       

      Thanks

       

      Naja

      Author's profile photo Nagaraju Rayachoti
      Nagaraju Rayachoti

      Thanks for sharing this, I have checked the recommended settings for certain countries, by referring the  to SAP note 1012293. but For Countries SX-Sint Maarten, CW-Curaçao, BQ-Bonaire, Saba OY17 settings are not available, Please request to share the settings.

       

      Regards,

      Prasad

      Author's profile photo Michal Balaban
      Michal Balaban

      Hi Prasad,

      the base source for the note 1012293 is the "IBAN Registry" document, the ISO for IBAN:
      https://www.swift.com/de/node/301396

      For the "(in)dependent" territories, like the British, French, Danish or Dutch ones, there are two variants:
      1. The territory is mentioned in the ISO by the IBAN description for the "main" country. Then the same settings have to be applied
      2. The territory is not mentioned there, then it is not using the IBAN

      For countries not using the IBAN yet, we do not have any ISO based information. In case of some very "exotic" locations, where you will have to maintain a very few of bank details in the whole lifecycle of your SAP system, the recommended strategy is as follows:
      1. Do not setup any restrictive settings and wait until there is enough data in system to recognize a pattern.
      2. Then setup the validity checks so that it is respecting this pattern.

      These rules applied to the countries mentioned by you do mean:

      The Dutch oversee territories are not mentioned in the IBAN registry = do not use Dutch IBAN = different settings needed, settings for NL cannot be used.
      When you get some real bank details, they will most probably consist of a BIC and an account number. The bank key type for these countries is then 4, the bank key length then up to 11 characters (SWIFT/BIC). No other settings needed.

      Best regards
      Mike

      Author's profile photo Nagaraju Rayachoti
      Nagaraju Rayachoti

      Thank you Michal for a detailed explanation. Regards, Prasad