3456499 - Overallocation of Incoming Direct Debits Based on Memo Line Rule

You have executed a number of Incoming Direct Debits against customers, for example by running a Receivables - Payment Run. Subsequently a payment file has been created (for example: SEPA Direct Debit).
A bank statement in format MT940 confirming these Incoming Direct Debits is processed thereafter.
You have set up a Rule for Analyzing Memo Lines, Type: 9 - DME Reference, in order to effect an automatic confirmation of relevant Direct Debit payments.
Related Payment Allocations remain in status 'Postprocessing Required'.
When accessing concerned Payment Allocations you notice an over-allocation for each related bank statement transaction.
This will turn the Open Amount in each allocation negative.

SAP Business ByDesign

You can access the relevant payment allocations either in:

• Payment Management work center.
• Navigate to Payment Allocations view.
• Select the relevant payment allocation.

- or via the posted bank statement.

• Liquidity Management work center.
• Bank Statements view.
• Navigate to the relevant bank statement and edit.
• Follow the link Postprocessing required to access the relevant payment allocation.

Rules for Analyzing Memo Lines can be defined either via:

• Business Configuration work center.
• Global Settings for Payment.
• Create and edit rules for analyzing memo lines.

or - by editing any open Bank Statement Payment Allocation.

The bank statement records confirmed Direct Debits in single transactions instead of 1 batch transaction.
The result of a rule of type DME Reference (Data medium exchange) usually refers to the Payment Message ID which is assigned when creating a payment file.
In case an unambiguous and relevant result is obtained this will facilitate a 1:N automatic allocation and confirmation of payments represented in a bank statement transaction.
The application of such a rule hence assumes that all payments contained in the payment file are contained in 1 bank statement transaction (batch transaction).
This means that the full amount of all candidate Direct Debits sharing the same DME Reference (Payment Message ID) will be allocated in each Payment Allocation. 

Example: 

3 Incoming Direct Debits are created for 3 customers.

Payment File 500 is created with assigned Payment Message ID 513 and sent to your house bank. 

Subsequently an MT940 bank statement XYZ is processed containing these payments.

For all 3 items 513 is obtained as result in a Rule for Analyzing Memo Lines (Type: 9 - DME Reference).

Payment File 500 (Payment Message ID: 513) contains 3 Direct Debits over an amount of 6,000.00 EUR.

Following the logic that for a single line-item all related payments associated with Payment Message ID 513 shall be confirmed - resulting Payment Allocations will propose all Direct Debits for confirmation for each line-item. 

For Example: 

Item ID 1, Payment Allocation External Reference XYZ/1:

Application of Rule Type '9 - DME Reference' assumes the allocation of all related payments associated with a Payment Message ID for a bank statement transaction (1:N). In other words, all associated open payments are contained in one batch-transaction.

In case there is more than 1 payment and confirmed payments are recorded in several line-items Rule Type '9 - DME Reference' should not be applied.

In such a scenario the unique External Payment Reference would be expected for each line-item. 
The External Payment Reference in MT940 would be contained in transaction-block :61:.

For Example: 

:61:2404090409CR1000,00NTRFAAA

Would automatically confirm Direct Debit AAA over 1,000.00 EUR.
As this is a intrinsic clearing-functionality, no memo-line rules are taking effect.

Alternatively the house-bank would have to be advised to bundle all payments into one batch-transaction as outlined above.

The same logic applies for Outgoing Bank Transfers.

Bank Statement  Payment Allocation  DME Reference , KBA , SRD-FIN-CLM , Cash and Liquity Managment , Problem