1J670 - The earliest possible due date is &1 for posting date &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 670

• Message text: The earliest possible due date is &1 for posting date &2

What causes this issue?

The latest date on which the system can post the SEPA direct debit order
is based on the due date and the minimum number of interbank working
days. This data is specified for a one-time payment order in Customizing
activity
<DS:SIMG.BA-CA-V_TBKK_SDDDAYS>Define Processing Time for SEPA Orders
</>:
Latest posting date = due date - minimum number of interbank working
days before the due date for one-time payment orders
The posting date of a SEPA direct debit order must always be on or
before the latest posting date.

System Response

The system cannot post the SEPA direct debit order.

How to fix this error?

Create the SEPA direct debit order with a due date on or after the
earliest due date.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

AnswerBot

• What is the cause and solution for SAP error message 1J670 - The earliest possible due date is &1 for posting date &2 ?

  The SAP error message 1J670 indicates that there is a restriction on the earliest possible due date for a transaction based on the posting date. This error typically arises in the context of financial transactions, such as invoice postings or payment processing, where the system enforces certain rules regarding due dates.
  Cause:
  The error message "The earliest possible due date is &1 for posting date &2" usually occurs due to one of the following reasons:
  
  
  Configuration Settings: The system has been configured to enforce specific rules regarding due dates based on the posting date. This could be due to settings in the payment terms or in the financial document settings.
  
  
  Payment Terms: The payment terms assigned to the transaction may specify a minimum period before a due date can be set. For example, if the payment terms indicate that payment is due 30 days after the invoice date, and the posting date is set to today, the earliest due date would be 30 days from today.
  
  
  Document Type Restrictions: Certain document types may have restrictions on due dates based on company policies or legal requirements.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Payment Terms: Review the payment terms assigned to the transaction. Ensure that they are set correctly and that the due date aligns with the expected payment schedule.
  
  
  Adjust Posting Date: If possible, adjust the posting date to a date that allows for a valid due date based on the payment terms.
  
  
  Review Configuration: If you have access to configuration settings, check the settings related to payment terms and due date calculations. You may need to consult with your SAP administrator or finance team to make necessary adjustments.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for specific details on how due dates are calculated and any relevant configuration settings.
  
  
  Contact Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support or your internal IT support team for further assistance.
  
  
  Related Information:
  
  Transaction Codes: You may want to check related transaction codes such as FB60 (Enter Incoming Invoices) or F-28 (Post Incoming Payments) to see where the error is occurring.
  SAP Notes: Look for SAP Notes related to this error message for any patches or updates that may address the issue.
  User Exits and BAdIs: If your organization has custom logic implemented, check for any user exits or BAdIs that might affect due date calculations.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.