After importing a bank statement you find that some of the automatically created postings are not according to your intentions.
E.g.: A wrong g/l account has been posted against or you find that no automatically posting should have been conducted at all.
Reproducing the Issue
1. You import a bank statement in one of the of the accepted formats (e.g.: MT940 for Germany) via Work Center Liquidity Management / View Inbound Files.
2. The bank statement is processed automatically. Consequently post-processing is not required.
3. Under Work Center Liquidity Management / View Bank Statements you click on Postprocessing -> Not Required.
4. Via the relevant bank statement line you get to the corresponding Payment Allocation containing the automatically generated Journal Entry.
Usually a bank statement file issued by bank comes with predefined external operation codes (External Transaction Codes) which describe a set of bank transactions (e.g.: direct debit, check redemption, standing order).
The automatic bank statement processing, and therefore the creation of automatic postings for certain events, depends on the definitions made in the Fine Tuning in Work Center Business Configuration / Automatically Generated Bank Statements
and the mapping of External Transaction Codes and Internal Transaction Codes for maintained import file formats.
Check the following settings under:
Work Center Business Configuration / Fine Tuning, Activity: Automatically Generated Bank Statements.
Here you find the mapping of External Transaction Codes and Internal Transaction Codes.
External Transactions Codes for 'Closing' or 'Commission' are mapped under Internal Transaction Code 'Payment Processing - Of Outgoing Bank Fees'.
In case no particular g/l account is stated here, the settings in G/L Account Determination for Cash are taking effect.
Go to Fine Tuning Activity: Charts of Accounts, Financial Reporting Structures, Account Determination / Cash.
Here you find the relevant g/l account under the Tab Interest/Charge.
In case you want to prevent the system from automatically posting transactions for certain transactions, the mapping between External Transaction Code and Internal Transaction Code has to be canceled.
Under Work Center Business Configuration / Fine Tuning, Activity: Automatically Generated Bank Statements the field for 'Internal Transaction Code' has to be left blank.
KBA , bank statement , payment allocation , transaction codes , SRD-FIN-COR , Cost & Revenue , How To