How To Fix 1J655 - Due date &1 cannot be before posting date &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 1J - BCA: Payment Order Dialog

• Message number: 655

• Message text: Due date &1 cannot be before posting date &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 1J655 - Due date &1 cannot be before posting date &2 ?

  The SAP error message 1J655 indicates that there is a problem with the due date of a financial document or transaction. Specifically, the error states that the due date (&1) cannot be set before the posting date (&2). This typically occurs in financial transactions, such as invoices or payment processing, where the system enforces rules to ensure that due dates are logically consistent with posting dates.
  Cause:
  
  Incorrect Date Entry: The user may have manually entered a due date that is earlier than the posting date.
  System Configuration: There may be settings in the system that enforce date rules which are not being adhered to.
  Data Migration Issues: If data has been migrated from another system, there may be inconsistencies in date formats or values.
  Business Logic: The business process may require that due dates always be after the posting date to ensure proper cash flow management.
  
  Solution:
  
  Check Dates: Review the due date and posting date in the transaction. Ensure that the due date is set to a date that is equal to or later than the posting date.
  Correct Entry: If the due date is incorrect, update it to a valid date that meets the criteria.
  Review Configuration: If this error occurs frequently, review the configuration settings in the SAP system to ensure they align with business requirements.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on date handling in financial transactions.
  User Training: Ensure that users are trained on the importance of entering correct dates in financial documents to avoid this error.
  
  Related Information:
  
  Transaction Codes: This error can occur in various transaction codes related to financial postings, such as FB60 (Enter Incoming Invoices), FB70 (Enter Outgoing Invoices), or F-28 (Post Incoming Payments).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team for further assistance.
  
  By ensuring that the due date is always set to a date that is on or after the posting date, you can avoid encountering this error in the future.