Fi-feba-faq feban algoritmos

Title
Archivo: Autores: FI-FEBA-FAQ_FEBAN_ALGORITMOS.docx Carlos Ancasi

Fecha:

07/03/2012

FI-FEBA-FAQ_FEBAN_ALGORITMOS.docx

http://en.sap.darkduck.com/en-SAP-FI-FAQ/setting-up-the-electronic-bank-statment Revisar bien las notas SAP.

07/03/2012

CONFIDENCIAL

PÁGINA: 1/5

Title
Archivo: Autores: FI-FEBA-FAQ_FEBAN_ALGORITMOS.docx Carlos Ancasi

Fecha:

07/03/20121.1.1 Setting up the Electronic Bank Statement 1.1.2
Switch to Russian

1.1.3 Q1: Does Electronic Bank Statement show transactions at customer or bank point of view? «+» means debit from bank point of view, but credit from client point of view. How can I distinguish incoming and outgoing payments?
A: Bank statement in format SWIFT MT940 shows transactions from the bank point of view. It means D iscompany’s outgoing payment and C is incoming payment. SAP automatically understands direction of money movement and transforms them from D/C into +/-. Anyway, test run of real bank statement is the best indicator if settings are correct or not.

1.1.4 Q2: I got full documentation for the statement in format SWIFT MT940. It has
huge list of possible transactions. Do I need to configure all ofthem in Electronic Bank Statement? How can I do it?
A: It worth asking your colleagues (like treasury and accountants) which of those transactions do actually exist in statements. Sure, not all of them will be in use. The same people will also tell you how to post each transaction in General Ledge. Then we set up these transactions as external transactions and group them into internal transactioncodes where possible.

1.1.5 Q3: Transaction code in SWIFT MT940 statement are very high-level. For
example, TRF (NTRF) can be incoming or outgoing payment. Don’t even mention smaller details. You can’t say more using the field 61. And it is field 61 which maps to posting rule. Some banks like Credit Suisse can give more details in tructured field 86. дают более детальные коды вструктурированном поле 86. But system recognizes the transaction type using the field 61. How can I ask it to look into field 86??
A: Transaction FF.5 has choice of variants for upload: with field 86 structured and unstructured. Of course, you have to configure transaction types as they are in field 86 if you use structured statement. As for NTRF transaction type for incoming and outgoing payments, they can be split bydirection of money movement. If bank uses NTRF, say, for outgoing payments and bank commissions, you cannot do much here, unfortunately. You have to do it manually. Or try to use search strings to replace the transaction type.

07/03/2012

CONFIDENCIAL

PÁGINA: 2/5

Title
Archivo: Autores: FI-FEBA-FAQ_FEBAN_ALGORITMOS.docx Carlos Ancasi

Fecha:

07/03/2012

1.1.6 Q4: How can I splitdomestic and international payments if they go under the
same transaction type in bank statement?
A : As a rule, all the payments use the same transaction type in the bank statement. It does not matter if the payment is domestic or international. That is why you cannot distinguish them in the statement. It is different in Russia, where all domestic payments are in roubles and international paymentsare in foreign currency, except for loans and deposits. Things are easier in this case.

1.1.7 Q5: Is it good idea to use special document type for the bank statement
postings? Or document type SA is good enough?
A: It is very good idea to use special document type. Of course, document type SA will suite the first posting area. But I would recommend to use document types KZ/DZ for the secondposting area, or even introduce special document type for bank statement.

1.1.8 Q6: Our chart of accounts has account number with less that 10 symbols.
How should I specify mask for the account symbol in bank statement configuration? Should it be left justified or right justified?
++++++++++ ++++++++ ++++++++

A: SAP always adds zeros on the left of numeric account number up...