How To Fix ACSS4_PAYMENTRUN006 - Not allowed to post document in company code &1 with account type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: ACSS4_PAYMENTRUN - Payment Run Integration with Business Integrity Screening

• Message number: 006

• Message text: Not allowed to post document in company code &1 with account type &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 ACSS4_PAYMENTRUN006 - Not allowed to post document in company code &1 with account type &2 ?

  The SAP error message ACSS4_PAYMENTRUN006 indicates that there is an issue with posting a document in a specific company code due to restrictions related to the account type. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Account Type Restrictions: The error typically arises when trying to post a document to an account that is not allowed for the specified company code. This could be due to configuration settings in the system that restrict certain account types from being used in specific company codes.
  Company Code Settings: The company code may have specific settings that prevent posting to certain account types (e.g., asset accounts, liability accounts, etc.).
  Document Type Restrictions: The document type being used for the posting may not be compatible with the account type or company code.
  
  Solution:
  
  
  Check Account Type Configuration:
  
  Go to the configuration settings for the company code and verify the allowed account types. Ensure that the account type you are trying to post to is permitted for the company code in question.
  You can check this in the SAP configuration under Financial Accounting (FI) > General Ledger Accounting > Master Data > G/L Accounts > Prepare G/L Account Creation.
  
  
  
  Review Company Code Settings:
  
  Ensure that the company code settings allow postings to the account type you are using. This can be checked in the company code settings under Financial Accounting (FI) > Financial Accounting Global Settings > Company Code > Edit, Copy, Delete, Check Company Code.
  
  
  
  Document Type Verification:
  
  Check the document type being used for the posting. Ensure that it is compatible with the account type and company code. You can find document type settings under Financial Accounting (FI) > Financial Accounting Global Settings > Document > Document Types.
  
  
  
  User Authorizations:
  
  Ensure that the user has the necessary authorizations to post to the specified account type in the company code. This can be checked with your SAP security team.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that might address this specific error message. Sometimes, there are known issues or patches that can resolve the problem.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBY6 (to check company code settings), FS00 (to check G/L account settings), and OBD2 (to check document types).
  SAP Support: If the issue persists after checking the above configurations, consider reaching out to SAP support for further assistance.
  Testing: After making any changes, perform a test posting to ensure that the issue has been resolved.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.