How To Fix FH171 - Account &1 contains a balance in at least one company code

SAP Error Message - Details

• Message type: E = Error

• Message class: FH - General ledger module messages

• Message number: 171

• Message text: Account &1 contains a balance in at least one company code

What causes this issue?

You have set the deletion flag in G/L account &V1&, chart of accounts
&V2&. The balance of the account, however, is not zero in at least one
of the company codes assigned to this chart of accounts.

System Response

Depending on the system settings, this message appears as an error, a
warning, or is suppressed. In the case of an error message, the
deletion flag cannot be saved.

How to fix this error?

Check account &V1&.
INCLUDE 'CUSTOMIZED_MESSAGE_INFO' OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FH171 - Account &1 contains a balance in at least one company code ?

  The SAP error message FH171 indicates that an account (denoted by &1) has a balance in at least one company code, which prevents certain operations from being performed on that account. This error typically arises when trying to perform actions such as closing a fiscal year, deleting an account, or making changes to the account that are not allowed when there are existing balances.
  Cause:
  
  Existing Balances: The primary cause of this error is that the specified account has a non-zero balance in one or more company codes. This could be due to open transactions, unposted documents, or simply because the account has not been cleared.
  Open Periods: The account may have open periods in the fiscal year, which means that transactions can still be posted to it.
  Incorrect Account Type: The account may be a reconciliation account or a special G/L account that has specific restrictions.
  
  Solution:
  
  Check Account Balances: Use transaction codes like FS10N (Display Account Balance) or FBL3N (G/L Account Line Items) to check the balances of the account in question across different company codes.
  Clear Balances: If the account is meant to be cleared, ensure that all transactions are posted and that the account is reconciled. You may need to post clearing entries or adjustments to bring the balance to zero.
  Close Open Periods: If applicable, ensure that the fiscal periods are closed for the company codes where the account has balances. This can be done using transaction code OB52 (Open and Close Posting Periods).
  Review Transactions: Investigate any open transactions that may be affecting the account. This may involve checking for unposted documents or pending transactions.
  Consult with Finance Team: If you are unsure about the implications of clearing the account or making changes, consult with your finance or accounting team to ensure compliance with financial regulations and practices.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  FS10N: Display G/L Account Balance
  FBL3N: G/L Account Line Items
  OB52: Open and Close Posting Periods
  
  
  Account Types: Understand the type of account you are dealing with (e.g., reconciliation accounts, special G/L accounts) as they may have specific rules regarding balances and postings.
  Documentation: Refer to SAP documentation or help files for more detailed information on handling G/L accounts and fiscal year-end processes.
  
  By following these steps, you should be able to resolve the FH171 error and manage the account appropriately.