---
title: "How do contracts work in Business Central vs Finance & Supply Chain Management?"
canonical_url: "https://cognilium.ai/blogs/contracts-in-business-central-vs-finance-supply-chain"
slug: "contracts-in-business-central-vs-finance-supply-chain"
section: "blogs"
date_published: "2026-09-11"
date_modified: "2026-09-11"
word_count: 2147
reading_time_minutes: 10
author: "Mudassir Marwat"
author_identifier: "0009-0008-1927-2598"
person_same_as:
  - "https://www.linkedin.com/in/mudassir-marwat/"
  - "https://orcid.org/0009-0008-1927-2598"
  - "https://github.com/mudassirmarwat"
  - "https://medium.com/@mudassir-marwat"
  - "https://www.youtube.com/@mudassir-marwat"
  - "https://dev.to/mudassirmarwat"
  - "https://hashnode.com/@mudassirmarwat"
  - "https://huggingface.co/mudassirmarwat"
  - "https://bsky.app/profile/mudassir-marwat.bsky.social"
  - "https://substack.com/@mudassirmarwat"
  - "https://topmate.io/mudassirmarwat"
  - "https://fueler.io/mudassirmarwat"
  - "https://www.instagram.com/mudassirmarwat/"
  - "https://www.facebook.com/mudassir.marwat"
  - "https://www.reddit.com/user/mudassirmarwat/"
  - "https://www.f6s.com/member/mudassir-marwat"
  - "https://cognilium.ai/founder"
entities: []
related:
  - "https://cognilium.ai/blogs/ai-contract-review-in-business-central"
  - "https://cognilium.ai/blogs/how-negotiated-terms-reach-a-purchase-agreement"
  - "https://cognilium.ai/blogs/approval-workflow-protect-negotiated-term-business-central"
---
# How do contracts work in Business Central vs Finance & Supply Chain Management?

Business Central holds a blanket order, Finance and Supply Chain holds a purchase agreement, and only one documents a rule that stops you breaking the price.

## Key takeaways

- Business Central holds a blanket order; Finance & Supply Chain Management holds a purchase agreement. Microsoft describes the first as a framework and the second as a contract that commits.
- Only Finance & SCM documents a price-enforcement policy — and it enforces it by silently breaking the link, so the order still posts and stops counting.
- Business Central guards quantity and not price. The blanket order number can be typed onto a line by hand.
- Vendor subscription contracts in Business Central are a billing feature. The lines carry billing detail; that page documents no clause and no review.
- Neither tier stores the executed document. Finance & SCM versions the record, which is a different thing.
- The tier changes what breaks, not whether the gap exists. Both need something beside them that reads the agreement.

**Neither tier holds your contract.** Business Central holds a **blanket order** — Microsoft calls it *"a framework for a long-term agreement."* Finance & Supply Chain Management holds a **purchase agreement** — *"a contract that commits an organization to buy."* Both hold terms. **Only one of them documents a rule that stops you quietly breaking the price.**

That difference decides what you have to build on top.

## What does each one actually hold?

They are not two versions of the same object. They are different objects with a similar purpose.

**The blanket order is a planning worksheet with a commercial memory.** Microsoft says so plainly: *"You can use them as a worksheet for monitoring, forecasting, and planning."* That is a genuinely useful thing and it is not the same as a contract record.

**The purchase agreement is a commercial instrument.** It has a status, a validity window, an activation step, four commitment shapes and a version history. **It behaves like a contract inside the ERP** — which is exactly why the next section matters.

## Which one actually enforces what you agreed?

**This is the real difference, and it is one policy.**

Finance & Supply Chain Management publishes a rule called **Price and discount is fixed**:

> *"The price on an order line and the price on the related commitment must be the same. If the price is changed on the order line, the link to the commitment is broken. If the link is broken, the order line doesn't contribute to the fulfillment of the commitment."*

**Read that twice.** The enforcement is real — and the failure is silent. **Change a price, and the order stops counting toward the thing you promised to buy.** No error. The order still posts. The commitment simply stops being fulfilled by it. Microsoft also documents **Max is enforced** and a **Minimum/Maximum release amount** that raises a message on divergence.

**Business Central's link is a field.** Microsoft's own description:

> *"a link between a sales order and a blanket order can be established by entering the associated blanket order number in the **Blanket Order No.** field on the sales order line."*

**A link you can type is a link you can mistype.** The page notes the blanket order number *"and line number are recorded as properties of the sales lines when created from a blanket order"*, and that *"the link between the blanket sales order and the originating sales order… is kept after posting"* — so the trace exists. There is one documented quantity guard, and it is a hard stop:

> *"the sales order line quantity must not exceed the quantity of the associated blanket order line. Otherwise, you can't post the sales order."*

**Quantity is guarded. Price is not, on that page.** So the two tiers fail in opposite directions: **Finance & SCM breaks the link silently to protect the price; Business Central keeps the link, and its blanket-order page documents no price policy at all.**

*(That article documents the sales side and says the purchasing steps are the same: "This article describes the processes for the sales blanket order side, but the steps are the same for purchasing.")*

## Doesn't Business Central have contracts now?

**Yes — and reading what they are for settles the whole argument.**

Business Central ships **vendor subscription contracts** in subscription billing. Microsoft's opening line:

> *"A vendor contract maps liabilities to suppliers or manufacturers. The structure of vendor subscription contracts is similar to purchase orders."*

And the next sentence says what the lines carry:

> *"The lines contain detailed information about the billing of the components of the contract."*

**Billing.** The page's own sections are invoice discounts, contract invoices, recurring billing, contract deferrals, merging contract lines, closing contract lines. Assigning work to one is described as *"To bill subscription lines, they must be assigned to a contract."*

**This is a real feature and it solves a real problem.** If you buy recurring services from vendors, it is the right place to manage them. **It is contract administration** — scheduling the money — and across that page there is **no clause, no obligation beyond billing, no review, and no signed document.**

**So the answer to *"does Dynamics do contract management?"* is: it does contract administration on both tiers, and it does it well.** That is a different question from whether the record matches what you signed.

## So where does the signed document live?

**Nowhere in either tier, by design.**

Finance & SCM comes closest, and it is worth being exact about what it stores. Confirming an agreement stores *"the current version of the purchase agreement… in a history table"*, and you *"can preview or print all versions of the agreement"* and *"share the revisions with your vendor to obtain approval."*

**That is version history of the ERP record, not of the paper.** It tells you what the agreement record said in March. It cannot tell you whether the record ever matched the executed contract, because the executed contract was never in it.

**Across the four Microsoft pages behind this article** — purchase agreements, blanket orders, vendor subscription contracts and the purchasing overview — **the closest thing to a pointer at the paperwork is an external document number**, which *"refers to the vendor's numbering system."* **A reference to their filing, not yours.** That is a claim about these four pages; other pages in the Dynamics documentation may attach files to records, and attaching a file is still not reading it.

## Which one should hold your terms?

**Whichever one you already run. That is not the decision worth spending time on.**

- **On Finance & SCM**, use purchase agreements properly — activate them, set the policy, and treat a broken link as an alert rather than an accident. The enforcement is there and most implementations leave it switched off.
- **On Business Central**, accept that the vendor card and the purchase line are the contract's working memory, and that [nothing reconciles them against the document](/blogs/ai-contract-review-in-business-central).
- **On either**, an approval workflow can guard the fields after entry — [revert the edit and route it](/blogs/approval-workflow-protect-negotiated-term-business-central) — but it fires on a change, so it never sees a wrong first value.
- **On either**, the gap is the same gap. The richer tier tells you the link broke. **Neither tells you the terms were wrong when they were typed in.**

**The decision that matters is what sits beside the ERP**, reading the agreement and checking the record against it — before signature, at entry, and periodically afterwards. That is [a different job from the one CLM software does](/blogs/clm-software-or-your-erp), and it is not a feature either tier is trying to ship.

**About Cognilium** Cognilium builds AI optimization apps for Microsoft Dynamics 365 — companion apps that optimize the pricing, inventory, warehouse and planning decisions your ERP manages but can't optimize. Dynamics is your system of record. Cognilium is your system of intelligence. https://cognilium.ai · https://www.linkedin.com/company/37180269/

**Legal AI Ops.** We transform legal workflows with **agentic AI, copilots, agentic workflows and decision intelligence** — built into core workflows rather than beside them, to raise productivity and cut operational overhead. **Contract Review Copilot** is the contract-review app in that family. It ships as **Paralegent AI**, in production today. [How we build Legal AI Ops](/solutions/legal-ai-ops) — custom AI capabilities on top of legal work, against your playbook and your Dynamics 365.

Pull the last ten purchase orders raised against an agreement and check whether the link is still intact. Bring the broken ones to a 15-minute call.

## Sources

- [Purchase agreements — Supply Chain Management](https://learn.microsoft.com/en-us/dynamics365/supply-chain/procurement/purchase-agreements) · `ms.date` 2026-09-08
- [Work with blanket sales orders or purchase orders — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/sales-how-to-create-blanket-sales-orders) · `ms.date` 2026-04-07
- [Vendor subscription contracts — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/srb/working-with-contracts/vendor-contracts) · `ms.date` 2026-05-04
- [Overview of tasks to manage purchasing — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/purchasing-manage-purchasing) · `ms.date` 2026-06-17

## Fact-check

**Tier summary:** 9 × T1 (all verbatim), 5 × T2 — **0 × T4.**

**Every source in `sources:` was fetched on 2026-09-10 before the claim was written.** No page is listed because another page linked to it, and none is listed because a sibling article cited it. `ms.date` recorded per source above; the purchase-agreements page was updated **two days** before this article.

**Three absence claims, all bounded on purpose.** Claims 8, 10 and 13 are the shape Rule 2 exists for. Each names the pages actually read, and claim 13 states in the body that other Dynamics pages may attach files to records — because they may, and attaching a file is not reading it.

**No figures.** No time saved, no error rate, no customer. The only numbers are Microsoft's four commitment types and the count of pages read.

**Disclosure:** the CTA asks the reader to check their own orders first. Demo is call-only.

## Frequently asked questions

### What does each one actually hold?

They are not two versions of the same object. They are different objects with a similar purpose.

### Which one actually enforces what you agreed?

Finance & Supply Chain Management publishes a rule called Price and discount is fixed:

### Doesn't Business Central have contracts now?

Yes — and reading what they are for settles the whole argument.

### So where does the signed document live?

Finance & SCM comes closest, and it is worth being exact about what it stores. Confirming an agreement stores "the current version of the purchase agreement… in a history table", and you "can preview or print all versions of the agreement" and "share the revisions with your vendor to obtain approval."

### Which one should hold your terms?

Whichever one you already run. That is not the decision worth spending time on.

---

Canonical HTML: https://cognilium.ai/blogs/contracts-in-business-central-vs-finance-supply-chain