AI, in your work.

The problem: a shifted deadline

BCApps merged a Subscription Billing correction concerning cancellation deadlines into its main branch on October 23. The merge is recorded in pull request #10444.

The original issue describes a line starting on January 1, 2026, with a 12-month initial term and 60 days’ notice. The term ended on December 31, but the cancellation deadline appeared as November 30 instead of November 1. A subsequent month-end adjustment changed the subtraction result.

The fields serve different purposes: Cancellation Possible Until indicates the deadline for timely cancellation; Term Until specifies the minimum billing term. Subscription Line End Date determines when billing ends and is independent of those two dates, according to Microsoft’s functional documentation.

What changes in the calculation

The Subscription Line code makes month-end alignment conditional in three paths: calculating the cancellation deadline, reconstructing the term end when that deadline is entered, and extending the term through Extension Term, displayed as Subsequent Term.

The new formula classifier retains alignment for months, quarters and years. It also accepts combinations such as 1Y+6M; a composite formula containing days or weeks is excluded from that alignment.

Three documented comparison cases

These synthetic inputs come from the tests added to the repository. They are expected results in code, not measurements made by Nexo. All three lines have a 12M initial term and subsequent term. Dates use year-month-day format.

Stored dates need a separate review

The commit includes no data upgrade code: stored dates remain unchanged until their next recalculation.

Nexo’s functional interpretation is that comparing two lines’ formulas alone is insufficient. It is also useful to record when their dates were calculated and which operation produced the observed result.

Microsoft documents the Update Subscription Line Dates action and its automation through codeunit 8058. That documentation describes date updates; it does not establish a general migration of values affected by this defect.

Nexo’s proposed functional review

Once a build containing the change is available, we propose the following checks in a test environment. This is editorial guidance, not a validation already performed.

• Record the Business Central and Subscription Billing versions, work date and installed extensions.
• Prepare synthetic lines with daily, weekly and monthly notice periods, including term ends both at month-end and on other dates.
• Compare an existing line before recalculation, that same line after recalculation, and a new line with identical settings.
• Also check manual entry of the cancellation deadline and term extension; record the operation performed and the before-and-after values.
• Agree acceptance criteria for each scenario before deciding which real records require intervention.

Availability: merge confirmed, distribution not established

The pull request is assigned to the Version 30.0 milestone, described as Business Central online 2027 release wave 1, with no due date specified. This is a planning reference; the consulted sources do not identify a distributed update that would establish the fix as installed.

The author reports 40 successful tests in codeunit 148156 inside a BC 29 container. That validation reported in the commit does not demonstrate that a commercial BC 29 update contains the change. Nexo has reviewed the public sources but has not repeated that execution.