cancel
Showing results for 
Search instead for 
Did you mean: 

Electronic Bank Statement config for 17BAI external code 856

rb2020
Participant
0 Kudos

We are using EBS upload for bank statements in the United States under standard BAI2, identified as 17BAI in SAP on product S/4 HANA Public Cloud.

Our bank is communicating a pair of transaction codes for sweeps between bank accounts, 856 (sweep in, a positive transaction) and 868 (sweep out, a negative transaction). 856 and 868 are not standard BAI2 codes, and the standard has no 8xx range.

For transaction 856, we add a code to the table in "assign external transaction types to posting rules" under "make global settings for electronic bank statements". If the code is added with a + sign, the system will not recognize the code.  It must be added with a - sign. On advise from Support, this is because SAP is configured on the backend to recognize any code greater than 400 as an outflow (besides the 700 range), regardless of the +/- symbol in the table. This makes the +/- symbol merely informational in that table, not determinative, which is surprising. Shouldn't the table then just fill it in for you, instead of allowing you to change it?

So to the 856 and "-" table line, we add posting rule F006, which is debit bank main, credit bank technical as leg one.  The second leg is intended to be credit technical, debit [whatever account is chosen in reprocessing]. 

However, what happens, is that because the system understands the transaction originally as outgoing, we end up with:

Leg 1 (correct):

Dr. Main Cash

Cr. Technical Cash

In the reprocessing screen however the header field for payment shows a negative number, and if you click on 'post to G/L' then the system shows:

Cr. Main Cash (this is locked/grayed out, and obviously a mismatch to leg 1 creating a cash imbalance)

Dr. [user to insert G/L account to post to]

Does anyone have experience with solving for transaction 856? I understand it is not just our bank that provides this code. Or another external transaction type in the 800 range that is an incoming transaction?

We are being told by SAP support that this is just how it works, and we need to have our bank provide only standard codes (which does not make sense to us, since SAP provides a configuration experience to cater for additional codes if you need to).

 

Accepted Solutions (0)

Answers (1)

Answers (1)

Edrilan_Berisha
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi rb2020,

 

also here I can simply point you to please have look into the SAP Note (from the year 2002): https://me.sap.com/notes/210257/E.

We have been telling all customers since then to talk to their banks and to provide a transaction code which is well defined in the BAI standard.

 

Best,

Edrilan Berisha

SAP S/4HANA Cloud Financials Development