How To Fix FQ368 - G/L account & &: No payment due to posting block

SAP Error Message - Details

• Message type: E = Error

• Message class: FQ - Payment Requests and Payment Program

• Message number: 368

• Message text: G/L account & &: No payment due to posting block

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 FQ368 - G/L account & &: No payment due to posting block ?

  The SAP error message FQ368 indicates that a payment cannot be processed for a specific General Ledger (G/L) account due to a posting block. This error typically arises in the context of financial transactions, particularly when dealing with accounts payable or receivable.
  Cause:
  The error message FQ368 can be triggered by several factors, including:
  
  Posting Block Configuration: The G/L account may have a posting block set in its configuration, preventing any postings or payments from being processed.
  Account Status: The account might be flagged as blocked for payments due to various reasons, such as outstanding issues, disputes, or compliance checks.
  Document Type Restrictions: Certain document types may have restrictions that prevent payments from being processed against specific G/L accounts.
  Payment Terms: The payment terms associated with the transaction may not allow for immediate payment, leading to a posting block.
  User Authorizations: The user attempting to process the payment may lack the necessary authorizations to post to the specified G/L account.
  
  Solution:
  To resolve the FQ368 error, consider the following steps:
  
  
  Check G/L Account Configuration:
  
  Navigate to the G/L account in question and check its configuration in the SAP system. Ensure that there are no posting blocks set for the account.
  You can do this by using transaction code FS00 to view the account details.
  
  
  
  Review Account Status:
  
  Verify if the account is blocked for payments. If it is, determine the reason for the block and take appropriate action to unblock it.
  
  
  
  Examine Document Type:
  
  Check if the document type used for the transaction has any restrictions related to the G/L account. You may need to consult with your finance team or SAP configuration team.
  
  
  
  Adjust Payment Terms:
  
  Review the payment terms associated with the transaction. If they are causing the block, consider adjusting them as necessary.
  
  
  
  User Authorizations:
  
  Ensure that the user attempting to process the payment has the necessary authorizations to post to the G/L account. If not, contact your SAP security team to grant the required permissions.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes or documentation that may provide additional insights or solutions related to this error message.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB60 (Invoice), F110 (Automatic Payment), and FS00 (G/L Account Master Data) for troubleshooting.
  SAP Support: If the issue persists after following the above steps, consider reaching out to SAP support for further assistance.
  Documentation: Review your organization's internal documentation regarding G/L account management and payment processing for any specific procedures or policies that may apply.
  
  By following these steps, you should be able to identify the cause of the FQ368 error and implement the necessary solutions to resolve it.