How To Fix FINS_RECON225 - &1: Fields in BSAK do not match

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 225

• Message text: &1: Fields in BSAK do not match

What causes this issue?

For entry &V1& there is a mismatch between view BSAK and the former
table (stored in BSAK_BCK) in one of the following fields:
BUDAT (posting date)
BLDAT (document date)
DMBTR (amount in local currency)
LIFNR (vendor number)
SAKNR (GL account number)
ZUONR (assignment number)
To compare the entries in your system, please compare the following
fields:
BKPF-BUDAT <-> BSAK_BCK-BUDAT
BKPF-BLDAT <-> BSAK_BCK-BLDAT
BSEG-DMBTR <-> BSAK_BCK-DMBTR
BSEG-LIFNR <-> BSAK_BCK-LIFNR
BSEG-SAKNR <-> BSAK_BCK-SAKNR
BSEG-ZUONR <-> BSAK_BCK-ZUONR

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?

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 FINS_RECON225 - &1: Fields in BSAK do not match ?

  The SAP error message FINS_RECON225 indicates that there is a mismatch between the fields in the BSAK (Accounting Document Segment: Cleared Items) table. This error typically arises during reconciliation processes, such as when trying to clear open items in accounts payable or accounts receivable.
  Cause:
  The error can occur due to several reasons, including:
  
  
  Data Inconsistency: There may be inconsistencies in the data between the accounting documents and the cleared items. This can happen if there are manual changes or if the data was not properly updated during a transaction.
  
  
  Configuration Issues: Incorrect configuration in the financial settings or in the reconciliation process can lead to mismatches.
  
  
  Missing or Incorrect Entries: If certain entries are missing or if there are incorrect entries in the BSAK table, it can lead to this error.
  
  
  Custom Developments: If there are custom programs or enhancements that manipulate financial data, they might inadvertently cause inconsistencies.
  
  
  Solution:
  To resolve the FINS_RECON225 error, you can follow these steps:
  
  
  Check Data Consistency:
  
  Use transaction codes like SE16 or SE11 to view the BSAK table and check for any inconsistencies in the data.
  Compare the entries in BSAK with the corresponding entries in the accounting documents (BKPF and BSEG tables).
  
  
  
  Run Reconciliation Reports:
  
  Use standard SAP reconciliation reports to identify discrepancies. Reports like F.13 (Automatic Clearing) can help in identifying and clearing discrepancies.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the Financial Accounting (FI) module to ensure that they are set up correctly for the reconciliation process.
  
  
  
  Analyze Custom Code:
  
  If there are any custom developments, review the code to ensure that it does not interfere with standard SAP processes.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that might address this specific error. There may be patches or updates that resolve known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after performing the above checks, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like FB03 (Display Document), FBL1N (Vendor Line Item Display), and FBL3N (G/L Account Line Item Display) to analyze the documents involved.
  Tables: Understand the structure of relevant tables such as BSAK, BKPF (Accounting Document Header), and BSEG (Accounting Document Segment) to troubleshoot effectively.
  Documentation: Review SAP documentation and user manuals related to financial reconciliation processes for additional insights.
  
  By following these steps, you should be able to identify the root cause of the FINS_RECON225 error and implement a solution to resolve it.