Symptom
Customer debit/credit items (debit memo and credit memo) are not grouped in Manage Automatic Payments App. In Exception Error raised: 002(No pymt possible because items with a credit bal.still exist).
Environment
SAP S/4HANA Cloud
Reproducing the Issue
- Enter Manage Automatic Payments App.
- Schedule Proposal or Payment run.
- In Exception Error 002(No pymt possible because items with a credit bal.still exist) occurred.
- In the Log Information: Due items with currency EUR, pmnt method E - items total is < 0.
In this case example payment method E (SEPA direct debit) is used with currency EUR. Payment method E was correctly set up in SSCUI 101972 / Activity 'Set Up Payment Methods for Each Country/Region for Payment Transactions'.
- Incoming Payment
- Debit Memo
Cause
There are several reasons that can cause debit/credit balance mismatch (debit/credit items are not grouped together). For the possible reasons and solution please check KBA 2586464 - Error ID(Description): 001(No pymt possible because Items with a debit bal.still exist; see job log)
In this case example the reason for the error is that SEPA Mandate Reference number is not unique in the documents picked up by the system during the payment.
Resolution
The field mandate reference must be identical between line items that have to be grouped together.
See Also
2586464 - Error ID(Description): 001(No pymt possible because Items with a debit bal.still exist; see job log)
Keywords
SEPA, direct debit, debit memo, Manage Automatic Payments, FZ347, FZ 347, FZ 328, FZ328, BSEG-MNDID, mandate, reference, credit memo, F0770, F0 770, SSCUI 101972 , KBA , FI-FIO-AP-2CL , Fiori UI for Accounts Payable (Public Cloud) , Problem