How To Fix EDEREG_INV807 - ID for payment advice note processing not unique

SAP Error Message - Details

• Message type: E = Error

• Message class: EDEREG_INV - Error Messages for Payment Management in a Deregulated Env.

• Message number: 807

• Message text: ID for payment advice note processing not unique

What causes this issue?

Within a payment run, you have cleared items that have different
origins. However, the origin of an item decides what data is used to
prepare the "deregulated" payment advice note.
If the origin is <ZH>from aggregated posting of invoicing service
provider</>, the payment advice note data is taken from the transfer
table (DFKKTHI).
If the origin is <ZH>form payment on account for deregulated end
customers</>, the payment advice note data is derived using the
distribution lot</>.
If the origin is <ZH>from aggregated bill receipt</>, the payment advice
note data is taken from the transfer table (TINV_INV_TRANSF).

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Ensure that only items from one of the aforementioned origins are
processed for each payment run. You can do this, for example, by using
different payment methods and corresponding selections for the payment
run.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDEREG_INV807 - ID for payment advice note processing not unique ?

  The SAP error message EDEREG_INV807 typically indicates that there is an issue with the uniqueness of the payment advice note being processed. This error can occur in scenarios where the system expects a unique identifier for the payment advice note, but it finds duplicates or conflicting entries.
  
  Cause:
  
  Duplicate Payment Advice Notes: The most common cause is that there are multiple entries in the system with the same identifier (e.g., payment advice number) that are being processed simultaneously or have been entered incorrectly.
  Incorrect Configuration: There may be configuration settings in the SAP system that are not set up to handle the uniqueness of payment advice notes properly.
  Data Entry Errors: Manual data entry errors can lead to duplicate entries being created inadvertently.
  Integration Issues: If the payment advice notes are being imported from an external system, there may be issues with the data being sent, leading to duplicates.
  
  
  Solution:
  
  Check for Duplicates: Review the payment advice