How To Fix PZ367 - G/L account payments cannot be processed

SAP Error Message - Details

• Message type: E = Error

• Message class: PZ - Messages: Payment program for payment requests

• Message number: 367

• Message text: G/L account payments cannot be processed

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 PZ367 - G/L account payments cannot be processed ?

  The SAP error message PZ367, which states "G/L account payments cannot be processed," typically occurs when there are issues related to the configuration or status of the General Ledger (G/L) accounts involved in the payment process. Here are some common causes, potential solutions, and related information for this error:
  Causes:
  
  
  Account Type Restrictions: The G/L account may be configured in such a way that it does not allow for payment processing. For example, it might be set up as a balance sheet account rather than a profit and loss account.
  
  
  Account Status: The G/L account may be blocked for postings or may have been marked as inactive.
  
  
  Payment Method Configuration: The payment method being used may not be compatible with the G/L account.
  
  
  Document Type Restrictions: The document type used for the payment may not be allowed for the specific G/L account.
  
  
  Currency Issues: There may be currency-related issues, such as the G/L account not being set up to handle the currency of the transaction.
  
  
  Missing Master Data: Required master data for the G/L account or the payment process may be missing or incorrectly configured.
  
  
  Solutions:
  
  
  Check G/L Account Configuration:
  
  Go to the G/L account master data and verify that the account is set up correctly for the intended use (e.g., check if it is a revenue or expense account).
  Ensure that the account is not blocked for postings.
  
  
  
  Review Payment Method:
  
  Check the configuration of the payment method being used. Ensure that it is allowed for the G/L account in question.
  
  
  
  Document Type Verification:
  
  Ensure that the document type used for the payment is compatible with the G/L account.
  
  
  
  Currency Settings:
  
  Verify that the G/L account is set up to handle the currency of the transaction. If necessary, adjust the currency settings.
  
  
  
  Master Data Check:
  
  Ensure that all required master data (e.g., vendor/customer data, payment terms) is complete and correctly configured.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes or documentation that may provide additional insights or fixes related to this error.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes such as FS00 (G/L Account Master Data), OBPM1 (Payment Methods in Country), or OBD2 (Document Types) to review and adjust settings.
  SAP Support: If the issue persists after checking the above items, consider reaching out to SAP support for further assistance, especially if there are specific configurations unique to your organization.
  Testing: After making changes, perform a test transaction to ensure that the error has been resolved.
  
  By following these steps, you should be able to identify and resolve the issue causing the PZ367 error in SAP.