How To Fix EDEREG_INV663 - Cannot find G/L account for offsetting entry

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 663

• Message text: Cannot find G/L account for offsetting entry

What causes this issue?

The system cannot detertmine a general ledget account for the offsetting
entry for sender/recipient pair &V1& / &V2&.

System Response

During creation of the aggregated incoming bill, it is not possible to
provide detailed information on the data record in table TINV_INV_TRANSF
(<LS>Transfer Table for Bill Data to FI-CA</>) that caused the error.
In addition to the information on sender/recipient pair, you can also
enter data for the receipt date of the transfer records and the planned
date of payment (due date).
Date of receipt: &V3&
Due date: &V4&

How to fix this error?

Use the information to check whether the bill data in the transfer dable
is consistent.
If the data is inconsistent and you use a customer-specific module to
transfer the data, you must adjust the data transfer module.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDEREG_INV663 - Cannot find G/L account for offsetting entry ?

  The SAP error message EDEREG_INV663 ("Cannot find G/L account for offsetting entry") typically occurs during the processing of financial transactions, particularly in the context of invoice verification or posting. This error indicates that the system is unable to find a General Ledger (G/L) account that is required for the offsetting entry of a transaction.
  Causes:
  
  
  Missing G/L Account Configuration: The G/L account that should be used for the offsetting entry may not be defined in the system. This can happen if the account has not been created or if it has been marked as inactive.
  
  
  Incorrect Account Assignment: The account assignment in the transaction may be incorrect or not aligned with the configuration in the system.
  
  
  Account Determination Issues: The account determination settings for the relevant transaction type may not be properly configured. This can include settings in the configuration for automatic account determination in the relevant module (e.g., MM, SD).
  
  
  Document Type Restrictions: The document type being used may not have the necessary G/L accounts assigned for the offsetting entries.
  
  
  Missing Master Data: The master data for the vendor, customer, or material may not be complete, leading to the inability to determine the correct G/L account.
  
  
  Solutions:
  
  
  Check G/L Account Configuration:
  
  Go to the transaction code OBY6 (or the relevant configuration path) to check if the G/L account is defined and active.
  Ensure that the account is assigned to the correct account group and is not blocked for postings.
  
  
  
  Review Account Assignment:
  
  Verify the account assignment in the transaction that is causing the error. Ensure that the correct G/L accounts are being referenced.
  
  
  
  Account Determination Settings:
  
  Check the configuration for automatic account determination in the relevant module (e.g., OBYC for inventory management).
  Ensure that the necessary settings for the transaction type are correctly configured.
  
  
  
  Document Type Configuration:
  
  Review the configuration for the document type being used. Ensure that it has the necessary G/L accounts assigned for offsetting entries.
  
  
  
  Master Data Review:
  
  Check the master data for the vendor, customer, or material involved in the transaction. Ensure that all required fields are filled out and that the data is complete.
  
  
  
  Consult with Finance Team:
  
  If you are unsure about the correct G/L accounts or configurations, consult with your finance or accounting team to ensure compliance with accounting practices.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBYC (Automatic Account Determination), FS00 (G/L Account Master Data), and OBY6 (Chart of Accounts).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation or help files for detailed information on G/L account determination and configuration.
  
  By following these steps, you should be able to identify the root cause of the error and implement the necessary changes to resolve it.