Business scenario
Currently, purchase agreements in Dynamics 365 Finance & Operations validate the agreement based on the requested receipt/delivery date.
As a result, a Purchase Order that is created and confirmed before the Purchase Agreement expiration date can lose its association with the agreement when the delivery date falls after the agreement expiration date.
Many organizations consider the contractual commitment to be made when the Purchase Order is issued or confirmed, not when the goods are physically delivered.
Example
- Purchase Agreement valid until 31-Dec-2026
- Purchase Order created and confirmed on 20-Dec-2026
- Requested delivery date 15-Jan-2027
From a business and contractual perspective, the Purchase Order was placed while the agreement was still valid. However, D365FO evaluates the delivery/receipt date and therefore the agreement can no longer be applied.
Requested enhancement
Introduce a configurable parameter for Purchase Agreement validity validation, for example:
- Requested delivery date (current behavior)
- Purchase Order creation date
- Purchase Order confirmation date
Alternatively:
- "Allow release orders to be created before agreement expiration date, even when delivery date exceeds expiration date."
Business benefits
- Better alignment with common procurement contract practices.
- Reduced need for customizations.
- Greater flexibility across industries and countries.
- Backward compatibility by keeping the current delivery-date logic as the default option.
- Improved user experience and fewer unexpected agreement delinkings.
Expected result
Organizations can choose whether the Purchase Agreement validity is determined by:
- Delivery/receipt date (current standard behavior), or
- Purchase Order date, or
- Purchase Order confirmation date.
This would make Purchase Agreements more flexible while preserving existing standard functionality for customers who prefer the current behavior.