---
title: "Where do contract renewal dates live in Business Central?"
canonical_url: "https://cognilium.ai/blogs/where-do-contract-renewal-dates-live-business-central"
slug: "where-do-contract-renewal-dates-live-business-central"
section: "blogs"
date_published: "2026-09-11"
date_modified: "2026-09-11"
word_count: 1888
reading_time_minutes: 9
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/we-missed-a-contract-renewal"
  - "https://cognilium.ai/blogs/where-should-contracts-live-contract-repository"
  - "https://cognilium.ai/blogs/msa-sow-mou-contract-management-business-central"
---
# Where do contract renewal dates live in Business Central?

Real fields exist: Cancellation Possible Until, Term Until, Subsequent Term. The clauses that fill them sit in a document nothing reads. Blank means terminable.

## Key takeaways

- Business Central models notice periods properly — Cancellation Possible Until, Term Until, Subsequent Term, Initial Term and the line end date each do a different job.
- Cancellation Possible Until is your deadline; Term Until is what you still owe. They are different dates and confusing them costs money.
- Miss the cancellation date and Microsoft's documented behaviour is that the line bills for another term. Nothing has gone wrong, so nothing warns you.
- Blank fields mean valid indefinitely or terminable at any time — a wrong answer wearing the costume of an empty field.
- Every one of these fields is a fact about a document the ERP has never read, which is the actual problem to solve.

**On the subscription contract line, in five named fields** — and Business Central models notice periods properly, which surprises most people. **What it cannot do is fill them in**, because the notice period is a clause in a document the ERP has never read.

## Which fields actually hold a renewal date?

**Five, and they do different jobs.** Microsoft's definitions, quoted:

**The distinction between the middle two is the one that costs money.** *Cancellation Possible Until* is your **deadline to act**. *Term Until* is what you **still owe** if you act. They are not the same date and confusing them is how a company gives notice on time and still pays for a full period.

**The end date is deliberately independent:** *"The end date doesn't depend on the dates in the **Cancellation Possible Until** and **Term Until** fields."*

**And Subsequent Term does double duty** — it is both the length of the automatic extension and, in Microsoft's words, what *"determines the rhythm of updating the **Cancellation Possible Until** and **Term Until** dates."*

## How is the notice deadline actually calculated?

**Microsoft publishes a worked example, and it is worth reading closely.** For a contract line billing from the first of January that renews annually with a three-month notice period:

> *"**Term Until** is **12.31.YYYY**. The contract line should be charged for the whole year even if it's terminated in due time."*  *"**Cancellation possible until** is **09.30.YYYY**. The contract line can be terminated in due time up to this date. **If the cancellation is received later, the contract line is billed for another year.**"*

**That last sentence is the entire cost of a missed renewal, in Microsoft's own words.** Miss the September date and you own the following year. The system will not warn you it happened, because nothing went wrong — the extension is the documented behaviour.

**The two dates stay in step with each other:** *"If either the **Cancellation Possible Until** or **Term Until** dates change, the other field is recalculated. The cancellation period is always used for this calculation."*

## What happens if the fields are left blank?

**The contract becomes something nobody agreed to.** Microsoft is direct:

> *"If validity and notice periods aren't set, the contract lines are valid indefinitely or can be terminated at any time."*

**Read that as a risk in both directions.** A blank notice period on a *vendor* contract tells your system you may walk away whenever you like — which is not what the master services agreement says, and you will discover the difference when you try. A blank one on a *customer* contract quietly removes a commitment you negotiated.

**Blank is not neutral. It is a wrong answer that looks like an empty field** — and on the record an empty field looks identical whether the agreement truly has no notice period or nobody ever opened it.

**One related trap:** you cannot fix a wrongly billed line by backdating it. Microsoft: *"you can't just terminate it retroactively… you must first issue a credit memo… The credit memo resets the **Next Billing Date**, and you can terminate the contract line."*

## What keeps these dates current?

**A scheduled job, and it is not on by default.**

> *"Use the **Update Subscription Line Dates** action on the customer or vendor subscription contract to update the notice dates. **The action should always run in the job queue.**"*

Microsoft names the automated route as well: *"You can add the update of the end dates to the job queue by using **Update Serv. Comm. Term. Dates** (Codeunit 8058) to run automatically. Typically, businesses run the codeunit once a day and outside business hours."*

**So the renewal calendar depends on a job queue entry somebody has to set up.** If it is not scheduled, the dates are stale rather than absent — which is worse, because a stale date still looks like an answer. It is the same dependency that [makes an unattended job queue a silent control](/blogs/approval-workflow-protect-negotiated-term-business-central).

## So where does the data actually come from?

**A clause in the agreement, typed in by a person who read it once.**

Every one of those date fields is a fact about a document: the initial term, the renewal length, the notice period. **Business Central models them well and sources them not at all.** The chain is:

1. Somebody reads the MSA and finds the termination clause.
1. Somebody translates *"ninety days prior to the end of the then-current term"* into **Notice Period** and **Subsequent Term**.
1. Somebody types it onto the contract line.
1. **Nothing ever checks step three against step one again.**

**The same chain runs for every document type in the portfolio** — and [an MSA, a SOW and an MOU each behave differently](/blogs/msa-sow-mou-contract-management-business-central).

**And nothing re-checks after an amendment.** A renegotiated notice period arrives as a signed amendment in an inbox; the contract line keeps the number typed in two years ago.

**This is document intelligence, and it is the same capability as invoice extraction pointed at a different document.** Microsoft already lists contracts as a supported type for agent attachments — and [caps PDFs at ten pages](/blogs/build-contract-agent-agent-designer-business-central), which is why an agreement needs its own extraction path rather than the built-in one.

**The shape that works is a sidecar app** — one that runs in your own Azure tenancy, reads the agreement where it already lives, extracts the termination clause, and writes the notice period onto the contract line for a person to confirm. **The document does not move and the ERP stays the system of record.** That is the whole architecture: Dynamics manages the renewal, and something beside it works out what the renewal actually says.

**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 your five largest vendor agreements and check whether the notice period on the contract line matches the termination clause in the document. Bring the mismatches to a 15-minute call.

## Sources

- [Cancel planned subscription lines — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/srb/working-with-contracts/service-commitment-cancellation) · `ms.date` 2025-07-11, updated 2026-01-12
- [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
- [Attachment capabilities and limitations (preview) — Business Central](https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/ai/ai-development-toolkit-attachments) · `ms.date` 2026-05-03

## Fact-check

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

**All three sources fetched on 2026-09-10 before the claims were written.** The renewal-mechanics page carries `ms.date` 2025-07-11 with a January 2026 update — **the oldest source in this cluster**, noted here rather than hidden, and its field names were checked against the vendor-contracts page fetched the same day.

**Claim 9 is deliberately not an absence claim.** We do not write *"Microsoft documents no validation."* We say a blank field and a genuine absence are indistinguishable **to anyone reading the record**, which follows from the field model itself.

**No figures of ours.** The dates in §2 are Microsoft's own worked example, quoted with their formatting. **No digits appear in either lifted block** — the codeunit number and the example dates stay in the body.

**Product claims.** §5 describes the architecture we build in capability language — *"the shape that works is a sidecar app"* — with **no customer, no count, no measured result, and no claim that it runs in anyone's business.** Paralegent AI is named only in the standing footer.

## Frequently asked questions

### Which fields actually hold a renewal date?

Five, and they do different jobs. Microsoft's definitions, quoted:

### How is the notice deadline actually calculated?

Microsoft publishes a worked example, and it is worth reading closely. For a contract line billing from the first of January that renews annually with a three-month notice period:

### What happens if the fields are left blank?

The contract becomes something nobody agreed to. Microsoft is direct:

### What keeps these dates current?

Microsoft names the automated route as well: "You can add the update of the end dates to the job queue by using Update Serv. Comm. Term. Dates (Codeunit 8058) to run automatically. Typically, businesses run the codeunit once a day and outside business hours."

### So where does the data actually come from?

A clause in the agreement, typed in by a person who read it once.

---

Canonical HTML: https://cognilium.ai/blogs/where-do-contract-renewal-dates-live-business-central