When uploading bank statements, error: Currency USD not permitted in account / 1234567890

[Edrilan_Berisha]

Let's assume the following situation: You upload a bank statement file into your system. It contains two statements (or more).

Statement one is for bank account 0987654321 which has the currency configured in EUR in the Manage Bank Accounts master data app.

Statement two is for bank account 1234567890 which has the currency USD. 

Now suddenly you see the error message in the log and the upload fails.

[Edrilan_Berisha · Accepted solution]

In this case you have most likely added an alternative account number which is already in use by another bank account in your system. This won't work.

So for instance here it's most likely the case, that bank account 1234567890 has the alternative bank account number maintained as 0987654321. The system has a fuzzy search, when validating the bank account master data mentioned in the file. It will try to fetch the correct bank account. Because we maintained a bank account with 0987654321 and also used this as an alternative bank account number for bank account 1234567890 - which has a different currency. The system is getting confused.

So remember: do not use alternative bank account numbers for already maintained bank account numbers in your system.

[Manohar-D · Accepted solution]

Thank you for your explanation. I’m trying to fully understand the relationship between primary and alternative account numbers in this scenario. Could you elaborate on how the system's fuzzy search works when validating bank account master data during a bank statement upload? Specifically, I’d like to understand: How the system prioritizes account matches when there’s a conflict between a primary and an alternative account number. What best practices can be followed to avoid such issues during configuration. If this error can be prevented entirely through additional validation settings or tools within the SAP system.

[Edrilan_Berisha · Accepted solution]

Hi @Manohar-D,

the fuzzy search basically, just searches in both fields for that bank account number. So it consideres both, the "normal" bank account number but also the "alternative bank account number".

If you have maintained the same number twice in public cloud, it's simply a wrong configuration. Because in SAP S/4HANA Public Cloud, you should have the number only once in your entire system. The moment you use this as an alternative number for a different bank account, the system will not know what belongs to what.

Best practice is pretty simple: each number should be defined in a unique way.

Keep in mind in the OnPrem/Private Cloud world, there are some specific cases where this makes sense. But for Public Cloud, it's just a wrong setup which should be fixed.

Best,

Edrilan Berisha