How To Fix >3428 - Number of payments (&1) does not equal control total (&2)

>3428 - Overview

• Message type: E = Error

• Message class: >3 - Lock management messages

• Message number: 428

• Message text: Number of payments (&1) does not equal control total (&2)

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message >3428 - Number of payments (&1) does not equal control total (&2) ?

  The SAP error message 3428 indicates a discrepancy between the number of payments processed and the control total specified in a payment run. This error typically occurs during the execution of payment runs in the SAP system, particularly in the context of financial accounting and accounts payable.
  
  Cause:
  The error message 3428 arises when the number of individual payment items (payments) does not match the control total that has been defined for the payment run. This can happen due to several reasons:
  
  Data Entry Errors: Incorrect entries in the payment proposal or payment run can lead to mismatches.
  Missing Payments: Some payments may not have been included in the payment run due to selection criteria or filters applied.
  Technical Issues: System errors or interruptions during the payment run process can cause discrepancies.
  Manual Adjustments: If manual changes were made to the payment proposal after it was generated, this could lead to inconsistencies.
  
  Configuration Issues: Incorrect configuration in