How To Fix WS160 - Different net values at supplier and customer level

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 160

• Message text: Different net values at supplier and customer level

What causes this issue?

The current Customizing settings for settlement process type &V1& lead
to a balance when the accounting document is created for the current
document. These documents cannot be forwarded to Financial Accounting.
The different net values for customer and supplier are caused by the
settings for calculation schema &V2&.

System Response

The system does not permit further processing, as the error means that a
balance is created when the accounting document is created.

How to fix this error?

Change the calculation schema or choose a settlement process type with
the settings
<DS:DE.WVOLP>Post Sales Values</> and
<DS:DE.WSTBU>Post Tax Amount</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WS160 - Different net values at supplier and customer level ?

  Certainly! Here's a detailed explanation regarding the SAP error message WS160 - Different net values at supplier and customer level:
  
  SAP Error Message: WS160 - Different net values at supplier and customer level
  
  Cause:
  The error WS160 occurs during the invoice verification or goods receipt/invoice receipt (GR/IR) clearing process when there is a mismatch between the net values recorded at the supplier level and the customer level for a particular transaction.
  More specifically:
  
  The system compares the net amount (net value) of the invoice or credit memo at the supplier side (vendor invoice) with the net amount at the customer side (customer invoice or related document).
  If these net values differ, the system raises the WS160 error to prevent posting inconsistent financial data.
  This situation often arises in scenarios involving third-party processing, consignment, or subcontracting where both supplier and customer transactions are linked.
  It can also happen if there are rounding differences, currency conversion issues, or incorrect data entry.
  
  
  When does it typically occur?
  
  During invoice verification (transaction codes like MIRO).
  During automatic clearing of GR/IR accounts.
  In third-party order processing where vendor and customer invoices are linked.
  When posting documents involving cross-company code transactions or intercompany billing.
  
  
  Solution:
  To resolve the WS160 error, consider the following steps:
  
  
  Check the Invoice Amounts:
  
  Verify that the net amounts on the vendor invoice and the corresponding customer invoice or purchase order match.
  Look for any discrepancies in quantity, price, or currency.
  
  
  
  Review Currency and Exchange Rates:
  
  Ensure that the currency and exchange rates used in the vendor and customer documents are consistent.
  Rounding differences due to currency conversion can cause this error.
  
  
  
  Adjust the Invoice or Purchase Order:
  
  If the vendor invoice is correct, adjust the customer invoice or purchase order accordingly.
  If the purchase order or customer invoice is correct, request a corrected vendor invoice.
  
  
  
  Check for Rounding Differences:
  
  Small rounding differences can cause this error.
  Use transaction MRBR (Release Blocked Invoices) to check if the invoice is blocked due to this error.
  If rounding differences are acceptable, configure tolerance limits in transaction OMR6 (Maintain Tolerances for Invoice Verification).
  
  
  
  Reconcile GR/IR Account:
  
  Perform a GR/IR clearing to ensure that the goods receipt and invoice receipt amounts match.
  Use transaction MR11 to clear GR/IR differences if appropriate.
  
  
  
  Check for Customizing or User Exits:
  
  Sometimes, custom validations or user exits might enforce strict matching.
  Review any custom code or validations related to invoice verification.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes that might address known issues or bugs related to WS160.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  MIRO – Enter Incoming Invoice
  MRBR – Release Blocked Invoices
  MR11 – GR/IR Clearing
  ME23N – Display Purchase Order
  FB03 – Display Document
  
  
  
  Tables:
  
  BKPF – Accounting Document Header
  BSEG – Accounting Document Segment
  EKPO – Purchase Order Item
  RBKP – Invoice Document Header
  
  
  
  SAP Modules Involved:
  
  MM (Materials Management)
  FI (Financial Accounting)
  SD (Sales and Distribution) in case of third-party processing
  
  
  
  Common Scenarios:
  
  Third-party order processing where vendor invoices are passed on to customers.
  Intercompany billing where vendor and customer documents are linked.
  Consignment or subcontracting processes.
  
  
  
  
  Summary:
  The WS160 error indicates a mismatch in net values between supplier and customer documents. To fix it, verify and align the invoice amounts, check currency and rounding, adjust documents as needed, and clear GR/IR differences. Proper configuration of tolerances and review of custom validations can also help prevent this error.
  
  If you need help with a specific transaction or scenario, please provide more details!