SAP Knowledge Base Article - Public

1679400 - Wrong Postings after Uploading Bank Statement - SAP Business ByDesign

Symptom

  • After importing a bank statement, you find that some of the automatically created postings are not according to your intentions.
  • For example: a wrong G/L account has been posted against, or you find that no automatically posting should have been conducted at all.

Environment

SAP Business ByDesign

Reproducing the Issue

  1. You import a bank statement in one of the of the accepted formats (for example, MT940 for Germany) via work center Liquidity Management / View Inbound Files view.
  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.

Cause

  • Usually, a bank statement file issued by bank comes with predefined external operation codes (External Transaction Codes) which describe a set of bank transactions (for example, 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 activity, and the mapping of External Transaction Codes and Internal Transaction Codes for maintained import file formats.

Resolution

  • 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.

For example:

  • 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 will 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 must 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.

 

 

 

 

Keywords

bank statement upload; External Transactions Codes; g/l accounts; internal transaction codes; Automatically Generated Bank Statements , KBA , SRD-FIN-COR , Cost & Revenue , How To

Product

SAP Business ByDesign all versions