How To Fix M8795 - Different invoicing party &1 planned for document &2

SAP Error Message - Details

• Message type: E = Error

• Message class: M8 - Invoice Verification/Valuation

• Message number: 795

• Message text: Different invoicing party &1 planned for document &2

What causes this issue?

Document &V2& comes from SAP Transportation Management (SAP TM).
You entered an invoice with reference to TM documents.
In TM document &V2&, invoicing party &V1& is entered. You are now
posting the invoice to the invoicing party &V3&.
This can be due to one of two reasons:
You have entered the invoicing party &V3& and TM document &V2&.
You entered a multiple assignment. The first item refers to a TM
document with invoicing party &V3&. Another item refers to TM document
&V2&. The system copies the invoicing party from the first item to all
items, in this case &V3&.

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?

Check your entries and make any necessary corrections.
By default, this message is set as a warning. In this case, all items
are selected.
If you want to prevent items with a different invoicing party being
selected, set the system message as an error (<LB>E</>) in Customizing
for <LS>Logistics Invoice Verification</> under
<DS:SIMG.SIMG_CFMENUOLMROMRM>Define Attributes of System Messages</>.

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 M8795 - Different invoicing party &1 planned for document &2 ?

  The SAP error message M8795, which states "Different invoicing party &1 planned for document &2," typically occurs in the context of logistics and invoicing processes. This error indicates that there is a mismatch between the invoicing party specified in the document and the one that is expected or configured in the system.
  
  Cause:
  
  Inconsistent Data: The invoicing party defined in the purchase order or sales order does not match the invoicing party defined in the related document (e.g., delivery or invoice).
  Master Data Issues: There may be discrepancies in the master data for customers or vendors, such as incorrect or outdated information.
  Configuration Settings: The system configuration for the invoicing party may not align with the business requirements or the specific transaction being processed.
  Document Flow Issues: If the document flow is not properly maintained, it can lead to inconsistencies in the invoicing party.
  
  
  Solution:
  
  Check Document Details: Review the details of the document (e.g., purchase order,