How To Fix FINS_RECON204 - &1: Balance in BSEG_ADD is not zero in third local currency &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 204

• Message text: &1: Balance in BSEG_ADD is not zero in third local currency &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_RECON204 - &1: Balance in BSEG_ADD is not zero in third local currency &2 ?

  The SAP error message FINS_RECON204 indicates that there is a discrepancy in the balance of the BSEG_ADD table for a specific document in the third local currency. This typically occurs during the reconciliation process when the system expects the balance to be zero, but it is not.
  Cause:
  
  Currency Conversion Issues: There may be issues with currency conversion rates or settings that lead to incorrect balances in the third local currency.
  Incomplete Transactions: Transactions may not have been fully processed or posted, leading to discrepancies.
  Manual Adjustments: Manual entries or adjustments in the financial documents may not have been properly accounted for in the third local currency.
  Configuration Issues: Incorrect configuration in the financial settings related to currency handling or local currency settings can lead to this error.
  Data Integrity Issues: There may be data integrity issues in the BSEG_ADD table, such as missing or incorrect entries.
  
  Solution:
  
  Check Transaction Data: Review the transactions related to the document in question. Ensure that all entries are complete and correctly posted.
  Review Currency Settings: Verify the currency settings in the system. Check if the exchange rates are correctly maintained and if the third local currency is properly configured.
  Reconcile Balances: Perform a reconciliation of the balances in the BSEG_ADD table. Identify any discrepancies and correct them.
  Use Transaction Codes: Utilize transaction codes like FB03 (Display Document) to view the document details and FBL3N (G/L Account Line Items) to analyze the line items for discrepancies.
  Run Reports: Use reports such as F.01 (Financial Statement) or S_ALR_87012357 (G/L Account Balances) to analyze the balances and identify where the discrepancies are occurring.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on resolving it.
  Contact Support: If the issue persists, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  BSEG_ADD Table: This table contains additional line item data for accounting documents, including information related to local currencies.
  Local Currency Settings: Ensure that the local currency settings in the company code configuration are correctly set up.
  Transaction Codes: Familiarize yourself with relevant transaction codes for financial reporting and document management in SAP.
  SAP Community: Engage with the SAP Community forums for insights and solutions shared by other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.