3556042 - Automatic On-Account Allocation for Non-Self-Initiated Payments in Bank Statement

You process a bank statements either uploaded by bank statement file or web service.
You notice that certain transactions will generate automatic on-account payments against business partner without any apparent clearing logic. 
For example Incoming Bank Transfers will automatically post and credited against customer account. 
Your expectation is that such transactions shall remain open for Postprocessing.

SAP Business ByDesign

1. In the Liquidity Management work center go to Bank Statement view.
2. Select the relevant posted bank statement transaction.
3. In the column Postprocessing, follow the link Not Required.
4. This will open on-account clearing, Clearing Status: Completed.
5. View View All and Document Flow you can access associated Payment Allocation from bank statement.

Alternatively you can find affected Payment Allocations in the Payment Management work center under Payment Allocation view. 

What we see here is the designed and intended system behaviour for automatic clearing of non-self-initiated payments.
As opposed to self-initiated payments (for example Outgoing Bank Transfers from Payment Run) - the default assumption is that no existing transactions are to be confirmed. Rather a clearing of open documents (for example Customer Invoices) shall be achieved.

Those candidate documents typically are identified via a matching of references in document and payment references contained in the bank statement item. The vehicle to achieve such a matching is the setup of suited Rules for Analyzing Memo Lines. 

In the absence fitting references in invoicing document and bank statement or non-effective Rules for Analyzing Memo Lines at least an on-account payment shall be achieved where possible. This payment can be later cleared in AR Accounting for example in the customer account monitor. 
This is the accepted and expected system behavior in bank statement processing, facilitating a sufficient degree of automation based on generally applied business scenarios.

In such a scenario this means that if the business partner can be identified unambiguously an automatic on-account payment and payment clearing will result.

The business partner typically can identified in the statement transaction by identifiers as name or IBAN, if present. 

This is the expected system behaviour.

In case you have a particular requirement that involves no automatic clearing of candidate documents by employing Rules for Analyzing Memo Lines and to also prevent automatic on-account payments, you could consider blanking the Payment Method associated with relevant External Transaction Code, for example XYZ.

• Business Configuration work center. 
• Select Automatically Generated Bank Statements activity. 
• Select Edit import formats for automatic generated bank statements.
• Choose applicable Import Format.
• Here External Transaction Code XYZ is linked with Payment Method 'Payment Processing - Of Incoming Bank Transfer'.

Outlined clearing definition is based on the character of processed bank statement transaction as non-self-initiated payment, for example Incoming Bank Transfer.

By keeping the Payment Method blank - bank statement transaction showing External Transaction Code XYZ will be interpreted as Other Incoming Payments. 
As a result described clearing logic will not apply and associated payment allocations will remain open for processing. 

KB0919061 - Automatic On-Account Clearing of Outgoing Direct Debit in Bank Statement

KBA , SRD-FIN-CLM , Cash and Liquity Managment , Problem