M8805 - Invoice not automatically created, potential duplicate exists (inv. & &)

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 805

• Message text: Invoice not automatically created, potential duplicate exists (inv. & &)

What causes this issue?

The system has performed a check that prevents the creation of duplicate
invoices for invoices that are created automatically, for example using
BAPIs or SOA services.
The system has just tried to create an invoice which contains data that
is identical with data in the existing logistics invoice document &V1&
&V2&.
The following data is identical in both documents:
Company code
Document date
Reference
Currency
Supplier
Amount

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?

Compare the current invoice with the invoice &V1& &V2&.

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 M8805 - Invoice not automatically created, potential duplicate exists (inv. & &) ?

  The SAP error message M8805, which states "Invoice not automatically created, potential duplicate exists (inv. & &)," typically occurs in the context of invoice processing in the Materials Management (MM) module. This error indicates that the system has detected a potential duplicate invoice based on the criteria defined in the system.
  Cause:
  
  Duplicate Invoice Check: SAP has built-in checks to prevent the creation of duplicate invoices. If an invoice with the same reference number, vendor, and other key fields already exists in the system, it will trigger this error.
  Invoice Verification Settings: The settings in the invoice verification process may be configured to be strict, leading to more frequent duplicate checks.
  Data Entry Errors: Sometimes, the error can arise from data entry mistakes, such as entering the same invoice number for different transactions.
  
  Solution:
  
  Check for Existing Invoices: Before proceeding, verify if the invoice in question already exists in the system. You can do this by searching for the invoice number in the relevant transaction (e.g., MIRO for invoice verification).
  Review Invoice Details: Ensure that the details of the invoice you are trying to create do not match any existing invoices. Pay attention to the vendor, amount, and invoice date.
  Adjust Duplicate Check Settings: If the duplicate check is too strict for your business needs, you may consider adjusting the settings in the configuration. This should be done with caution and typically requires the involvement of a system administrator or SAP consultant.
  Use Different Invoice Number: If you confirm that the invoice is indeed a duplicate, you may need to use a different invoice number for the new transaction.
  Consult Documentation: Review SAP documentation or consult with your SAP support team for specific configurations related to invoice processing and duplicate checks.
  
  Related Information:
  
  Transaction Codes: Common transaction codes related to invoice processing include MIRO (Invoice Verification), MIR4 (Display Invoice Document), and MR8M (Cancel Invoice Document).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional insights or solutions.
  User Exits and BAdIs: If your organization has custom developments, check if there are any user exits or BAdIs that might affect the invoice processing logic.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant who can provide more tailored assistance based on your specific SAP environment and configuration.