How To Fix FM_PDOC_E012 - Posting key &1 does not allow account type &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FM_PDOC_E - Message class for Payment Directives

• Message number: 012

• Message text: Posting key &1 does not allow 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 FM_PDOC_E012 - Posting key &1 does not allow account type &2 ?

  The SAP error message FM_PDOC_E012 indicates that there is a mismatch between the posting key and the account type being used in a financial transaction. This error typically occurs in the context of Financial Management (FM) or when dealing with General Ledger (GL) accounts in SAP.
  Cause:
  The error message is triggered when:
  
  The posting key specified in the transaction does not allow the type of account you are trying to post to. For example, if you are trying to post to a balance sheet account using a posting key that is configured only for income statement accounts, this error will occur.
  The account type (e.g., asset, liability, revenue, expense) does not match the allowed account types for the specified posting key.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Posting Key Configuration:
  
  Go to the transaction code OB13 (for posting keys) and review the configuration of the posting key you are using. Ensure that it is set up to allow the account type you are trying to post to.
  
  
  
  Verify Account Type:
  
  Check the account type of the account you are trying to post to. You can do this by going to the transaction code FS00 (for G/L account master data) and reviewing the account details.
  
  
  
  Change Posting Key or Account:
  
  If the posting key is not appropriate for the account type, consider changing the posting key in your transaction to one that is compatible with the account type.
  Alternatively, if the account type is incorrect, you may need to use a different account that matches the posting key.
  
  
  
  Consult with Configuration Team:
  
  If you are unsure about the configuration or need to make changes, consult with your SAP configuration team or a functional consultant who specializes in Financial Accounting (FI) or Financial Management (FM).
  
  
  
  Review Documentation:
  
  Check SAP documentation or help resources for more details on posting keys and account types to ensure compliance with your organization's accounting policies.
  
  
  
  Related Information:
  
  Posting Keys: These are two-digit keys that determine the type of transaction being posted (e.g., debit or credit) and the type of account that can be used.
  Account Types: Common account types include:
  
  A: Asset
  L: Liability
  E: Expense
  R: Revenue
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  OB13: Maintain Posting Keys
  FS00: G/L Account Master Data
  FB50: General Ledger Document Entry
  
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.