Sales and purchase agreements in F&O

Sales agreements and purchase agreements in Dynamics 365 Supply Chain Management are the formal mechanism for long-term commitments between two parties — frame agreements where a quantity, period, and price are fixed, and individual orders are "released" against them over time. They replace the older Business Central concept of blanket orders with a richer commitment model.

The shape of an agreement. A sales agreement is a parent record carrying:

• Customer — who's committing to buy.
• Effective period — start and end dates of the commitment.
• Default fields — payment terms, delivery terms, currency, etc.
• Lines — what's being committed to:
  • Product Quantity Commitment — "buy 1000 units of Product A over the period".
  • Product Value Commitment — "buy €100,000 worth of Product A".
  • Product Category Quantity Commitment — quantity across a category.
  • Product Category Value Commitment — value across a category.
  • Value Commitment — overall value across all products.

Purchase agreements mirror the structure on the procurement side.

Releases. Against an agreement, release orders are created — standard sales orders (or purchase orders) referencing the agreement. Each release decrements the agreement's remaining quantity or value. The system enforces:

• Cannot release more than the committed amount.
• Cannot release outside the effective period.
• Pricing comes from the agreement (overriding the customer's standard price list).
• Other terms (payment, delivery) default from the agreement.

Fulfilment tracking. The agreement view shows progress: committed, released, delivered, invoiced, remaining. Visibility for both sides:

• The customer-facing salesperson knows how much of the customer's commitment is still to release.
• The supply-chain side plans against the expected releases, not against ad-hoc orders.

Integration with planning. Master planning honours sales agreements — the planning engine can forecast against open agreement quantities, ensuring supply is in place to meet the commitment. The forecast pattern: if the customer committed to 1000 units over the year, the planner expects ~250 per quarter and pre-positions supply.

Purchase-side mirror. Purchase agreements work the same. A frame deal with a key supplier — "we'll buy 50,000 units of raw material A this year at €5/unit" — creates a purchase agreement; individual purchase orders release against it; supplier price honoured for the duration regardless of market movement.

Pricing. Agreement pricing can be:

• Fixed — the agreed price holds for the duration.
• Discount % — discount off the standard price list at release time.
• Markup % — for cost-plus arrangements.
• Tiered — different prices at different volume bands within the commitment.

Renewals. Agreements expire on the end date. Renewal workflows in Power Automate can prompt the salesperson 30/60/90 days before expiry to negotiate the next year's commitment.

Reporting. Sales agreement reports:

• Customer commitment summary — what every customer is committed to.
• Fulfilment progress — % consumed across active agreements.
• At-risk agreements — agreements where the customer hasn't released enough to consume the commitment, suggesting expiry without full delivery.
• Pricing analysis — actual vs committed price across the portfolio.

Common pitfalls.

• Agreements that drift — released against but never tracked to closure; expire silently.
• Pricing misalignment — agreement price changed after creation; some releases at old price, some at new.
• Multi-currency complications — agreement in customer currency but cost in supplier currency; FX swings between commitment and fulfilment.

Operational reality. Agreements demand discipline — formal commitment management, active tracking, scheduled renewals. The reward is predictable revenue and supply, and tighter customer/supplier relationships. The cost is the operational discipline; ignored, the agreements become bureaucratic noise.