How To Fix FINS_REV_REC_CUST101 - G/L account &1 for on account billing cannot be posted to manually

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_REV_REC_CUST - Event-Based Rev. Rec.: Customizing

• Message number: 101

• Message text: G/L account &1 for on account billing cannot be posted to manually

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_REV_REC_CUST101 - G/L account &1 for on account billing cannot be posted to manually ?

  The SAP error message FINS_REV_REC_CUST101 indicates that there is an issue with posting to a specific General Ledger (G/L) account for on-account billing. This error typically arises when the system is configured in such a way that it does not allow postings to certain G/L accounts manually, particularly in the context of revenue recognition or on-account billing.
  Cause:
  
  
  Account Configuration: The G/L account in question may be configured as a reconciliation account or may have specific settings that prevent manual postings. This is common for accounts that are linked to sub-ledgers (like accounts receivable) or are used for specific purposes (like revenue recognition).
  
  
  Posting Rules: The system may have rules in place that restrict certain types of postings to ensure compliance with accounting standards or internal policies.
  
  
  Document Type Restrictions: The document type being used for the posting may not be allowed to post to the specified G/L account.
  
  
  Account Type: The G/L account may be of a type that does not allow manual postings, such as a statistical account or a non-posting account.
  
  
  Solution:
  
  
  Check G/L Account Configuration: Review the configuration of the G/L account in question. Ensure that it is set up to allow manual postings if that is required. This can be done in the SAP configuration settings (transaction code OBD4 for account types).
  
  
  Review Posting Rules: Check the posting rules associated with the document type you are using. Ensure that the document type is allowed to post to the G/L account.
  
  
  Use Correct Document Type: If the document type you are using does not allow posting to the G/L account, consider using a different document type that does.
  
  
  Consult with Finance Team: If you are unsure about the configuration or the implications of changing settings, consult with your finance or accounting team to ensure compliance with internal policies and accounting standards.
  
  
  Transaction Codes: Use transaction codes like FS00 to check the G/L account settings and OB52 to check the posting periods.
  
  
  Related Information:
  
  
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. SAP Notes can provide specific guidance or patches that may resolve the issue.
  
  
  Documentation: Review SAP documentation related to G/L account management and on-account billing to understand the implications of the settings.
  
  
  Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.