How To Fix M8414 - Invoice doc. &1/&2 was created via evaluated receipt settlement

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 414

• Message text: Invoice doc. &1/&2 was created via evaluated receipt settlement

What causes this issue?

The invoice to be canceled &V1& / &V2& was created during evaluated
receipt settlement (ERS).
INCLUDE MM_IV_MELDUNGEN OBJECT DOKU ID TX

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?

Depending on how you have set up this message, you can cancel the
invoice created during evaluated receipt settlement (ERS). Note that in
this case there will be no automatic settlement - of the delivery that
you have not yet paid - using ERS. This means that you need to manually
create a new invoice.
If you want invoice creation to take place completely using ERS, then
you must cancel the goods receipt and not the invoice document. ERS
will then create the relevant cancellation invoice document for the
canceled goods movement. When the goods receipt is entered again, ERS
creates the invoice document according to the goods receipt quantity
and the conditions from the purchasing document that are valid at that
time.
This method is the only means of guaranteeing that the messages that
may be created during ERS are also issued.

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 M8414 - Invoice doc. &1/&2 was created via evaluated receipt settlement ?

  The SAP error message M8414 indicates that an invoice document was created via Evaluated Receipt Settlement (ERS) and is typically related to issues with the handling of invoices in the context of ERS. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  ERS Process: The error arises when an invoice is generated through the ERS process, which is used to automate the invoice verification process for goods received. This process relies on the goods receipt (GR) data to create an invoice automatically.
  Document Status: The invoice document may be in a status that does not allow further processing, or there may be inconsistencies in the data related to the goods receipt or the invoice.
  Configuration Issues: There may be configuration issues in the system related to the ERS process, such as settings in the purchasing or invoice verification modules.
  
  Solutions:
  
  Check Document Status: Verify the status of the invoice document and the associated goods receipt. Ensure that the documents are in a state that allows for further processing.
  Review ERS Configuration: Check the configuration settings for ERS in the SAP system. Ensure that all necessary parameters are correctly set up for the ERS process to function properly.
  Manual Invoice Entry: If the ERS process is causing issues, consider entering the invoice manually as a temporary workaround until the underlying issue is resolved.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error message. SAP frequently updates its knowledge base with solutions for known issues.
  System Logs: Review system logs and error messages for additional context that may help identify the root cause of the issue.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  Related Information:
  
  Evaluated Receipt Settlement (ERS): Understand the ERS process and how it integrates with the procurement and invoice verification processes in SAP.
  SAP Documentation: Refer to SAP Help documentation for detailed information on ERS and invoice processing.
  Training and Best Practices: Ensure that users involved in the procurement and invoice verification processes are trained on best practices for using ERS to minimize errors.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the M8414 error message in SAP.