How To Fix EDEREG_INV220 - Document &1 not unique for sender/recipient pair &2/&3

EDEREG_INV220 - Overview

• Message type: E = Error

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

• Message number: 220

• Message text: Document &1 not unique for sender/recipient pair &2/&3

What causes this issue?

Document &V1& for aggregated posting for the sender/recipient pair &V2&/
&V3& is not unique. In database table &V4&, document &V1& refers to at
least one other sender/recipient pair.

System Response

Document &V1& for aggregated posting cannot be reversed.

How to fix this error?

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

INCLUDE NA_ISU_OSS OBJECT DOKU ID TX

Procedure for System Administrators

INCLUDE NA_SYSADMIN1 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDEREG_INV220 - Document &1 not unique for sender/recipient pair &2/&3 ?

  The SAP error message EDEREG_INV220 indicates that there is a problem with the uniqueness of a document for a specific sender and recipient pair in the context of electronic invoicing or document processing. This error typically arises when the system finds multiple documents that match the same sender and recipient combination, which violates the requirement for uniqueness.
  
  Cause:
  
  Duplicate Documents: The most common cause is that there are multiple documents (invoices, credit memos, etc.) that have been created for the same sender and recipient combination, leading to ambiguity in processing.
  Incorrect Data Entry: There may be errors in the data entry process, such as incorrect sender or recipient information, which can lead to the system interpreting multiple documents as valid for the same pair.
  System 
  Configuration Issues: There may be issues with the configuration of the electronic invoicing system or the way documents are being processed and stored.
  
  
  Solution:
  
  Check for Duplicates: Review the documents in