Creating and Managing Subscription Contracts

In Part 3, we explored Subscription Packages and Service Commitments - the building blocks used to define what an organization offers to its customers.

The next step is to bring those predefined services into an actual customer agreement.

In Subscription & Recurring Billing, the Customer Subscription Contract represents the contractual relationship with the customer. Microsoft describes the contract as the technical representation of one or more actual contract documents that are billed together. The contract contains the commercial framework, while the associated subscriptions and subscription lines represent the individual components and recurring services.

This distinction is important because a contract isn't simply another sales document. It provides the structure Business Central uses to manage recurring obligations over the entire life of the agreement.

Understanding the Customer Subscription Contract

A Customer Subscription Contract represents the obligations your organization has agreed to fulfill for a customer.

The contract contains information about the contractual partner, invoice recipient, shipping details, accounting conditions, and other commercial information. The contract lines then define the individual services or subscription components that need to be billed.

This allows multiple subscription services to be managed under a single contractual framework.

For example, consider a customer purchasing an IT managed-service agreement that includes:

Cloud Hosting + Backup + Security Monitoring + Technical Support

Instead of managing four unrelated recurring invoices, these services can be represented through subscription lines within the customer's contract and billed according to their respective billing conditions.

Contract Header and General Information

When working with a Customer Subscription Contract, the General FastTab contains information about the contractual relationship.

This includes details such as the customer and relevant contact information. The contract also provides shipping and billing information through the Shipping and Billing FastTab, allowing organizations to specify where services are delivered and where invoices should be sent.

This structure becomes particularly useful for organizations that have complex customer relationships-for example, when the contracting customer and invoice recipient are different entities.

Subscription Contract Lines

The real billing logic is maintained at the contract-line level.

A contract can contain multiple lines, and each line represents a recurring component of the agreement. Subscription lines contain billing-related information such as quantity, billing period, and amount.

For example, a contract might contain:

Although these services belong to the same customer contract, each line can represent a different recurring service and billing requirement.

This provides the flexibility needed to manage complex subscription offerings without creating separate contracts for every service.

Creating Contract Lines

Contract lines can originate from the subscription structures configured earlier in the process.

When a subscription package and its associated subscription lines are used to create a customer agreement, the relevant services become available within the customer's contract.

Business Central also supports manually created contract lines for certain scenarios. For example, contract lines can be created for an Item or G/L Account, with fields such as subscription line start date, billing rhythm, billing base period, quantity, and calculation base. When the required information is completed, the corresponding subscription can be created automatically.

This gives consultants flexibility when designing solutions. Standardized subscription packages can be used for repeatable offerings, while manual contract lines can support more specific business scenarios.

Billing Rhythm and Billing Base Period

One of the most important aspects of a subscription contract is determining when and how frequently the customer should be billed.

Business Central supports recurring billing periods and billing frequencies, allowing organizations to structure agreements according to their commercial terms.

For example:

Monthly subscription

The customer is billed every month for the active service.

Quarterly subscription

The customer receives an invoice covering a three-month billing period.

Annual subscription

The customer is billed once per year for the agreed service period.

The billing rhythm and billing base period work together to determine how subscription charges are calculated and presented during recurring billing.

Contract Start and End Dates

Subscription contracts also need clearly defined service periods.

The Subscription Line Start Date determines when a particular subscription service becomes active. Depending on the agreement, a subscription line may also have an end date.

This is particularly important when different services within the same contract have different durations.

For example, a customer could have a three-year software agreement but purchase an additional support service for only one year.

Instead of creating a completely new contract, the relevant subscription line can have its own service period.

This makes the model flexible enough to represent real-world contractual arrangements.

Managing Changes During an Active Contract

Subscription agreements rarely remain unchanged throughout their entire lifecycle.

Customers may request additional services, upgrade their plans, reduce quantities, change billing conditions, or add new subscription components.

Business Central's subscription model allows the services associated with an active contract to change while the underlying subscription remains identifiable. Microsoft specifically notes that subscriptions can remain relatively static while their associated subscription lines change during an active contract.

This separation is extremely useful for long-running contracts because it allows organizations to maintain historical information while adapting the services being delivered.

Planned Subscription Lines

Contract changes can become particularly important when an existing service has already been billed for part of its current period.

Business Central can use planned subscription lines to preserve changes that should take effect after the existing billing period or contractual conditions have been completed.

For example, suppose a customer upgrades from a Standard plan to a Premium plan halfway through an agreement.

Instead of immediately overwriting the existing subscription information and potentially affecting historical billing, the change can be planned so that the new conditions take effect at the appropriate point in the subscription lifecycle.

This helps maintain billing accuracy and provides a cleaner audit trail.

Extending Subscription Contracts

Contracts may need to be extended when customers continue using the service beyond the original agreement period.

Business Central provides an Extend Contract capability that can be used to extend subscription contracts. The extension can create new subscription lines based on the existing subscription and its conditions.

This is useful for scenarios where a customer continues receiving a service without fundamentally changing the subscription offering.

For example:

Original Contract

01-Jan-2026 > 31-Dec-2026

Extension

01-Jan-2027 > 31-Dec-2027

The contract can continue while maintaining the relevant subscription information and billing structure.

Contract Renewals

Renewal is slightly different from simply extending a contract.

A renewal generally represents a new contractual period that may require customer confirmation, updated pricing, or revised terms.

Business Central provides a Create Contract Renewal Quote process for contract lines approaching their end date. Users can specify the renewal term and create sales quotes for the relevant contract lines.

This provides an important commercial control point.

Instead of automatically extending every contract indefinitely, organizations can review upcoming expirations and decide whether the customer should be renewed, modified, or allowed to expire.

Contract Amendments and Pricing Changes

One of the most common real-world subscription scenarios is a change in commercial conditions.

Consider a customer currently paying:

$500/month > Premium Support

After six months, the customer upgrades to:

$750/month > Premium Support + Security Monitoring

The subscription contract needs to reflect the additional service and revised commercial conditions while preserving the history of what was previously billed.

This is where careful contract-line management becomes important.

Changes to pricing, quantities, discounts, billing periods, or other conditions should be handled in a way that doesn't unintentionally alter previously posted transactions.

Contract Deferrals

Subscription contracts are often associated with services that span multiple accounting periods.

For example, a customer may pay $12,000 upfront for a 12-month subscription.

The invoice may be posted for the full amount, but the business may need to recognize revenue over the period in which the service is delivered.

Business Central supports contract deferrals for this scenario. When configured, contract deferrals can move customer-side revenue or vendor-side costs into future periods and release them to income or expense over time.

This provides an important connection between subscription management and financial reporting.

Contract Status and Lifecycle Management

A subscription contract should be viewed as a lifecycle rather than a single transaction.

A typical lifecycle can be represented as:

Contract Creation > Subscription Activation > Recurring Billing > Contract Amendment > Extension / Renewal > Continued Billing > Contract Closure

Each stage can require different business decisions and controls.

For consultants, designing these lifecycle rules during implementation is important because it determines how users will handle real-world customer changes.

Real-World Example

Consider a company providing Managed IT Services.

A customer signs a 12-month agreement containing:

Managed IT Support - $1,000/month

Cloud Backup - $300/month

Security Monitoring - $500/month

The consultant creates the Customer Subscription Contract and adds the required subscription lines.

The contract becomes the central place for managing these recurring services.

Every billing cycle, the applicable subscription lines become candidates for recurring billing. The customer receives the corresponding invoice, while the financial entries are posted in Business Central.

After six months, the customer requests an additional security service.

Instead of creating an entirely new customer relationship, the additional service can be incorporated into the existing subscription structure.

At the end of the 12-month term, the organization can review the contract for renewal and create the appropriate renewal proposal.

This demonstrates why subscription contracts are more than recurring invoices-they provide a framework for managing the entire commercial relationship.

Key Takeaways
 
A Customer Subscription Contract is the commercial framework that brings together the customer, billing information, and associated subscription services.

Subscription lines contain the recurring billing information, including the service, quantity, billing period, and amount.

Contracts can evolve over time as customers upgrade, downgrade, add services, or change commercial conditions.

Extensions and renewals provide different lifecycle options, allowing businesses to continue agreements while maintaining appropriate contractual controls.

Contract deferrals connect subscription billing with financial reporting, particularly when revenue or costs need to be recognized over multiple accounting periods.

Final Thoughts

Subscription contracts are where the configuration discussed in the earlier parts of this series starts becoming a real business transaction.

Subscription Packages define the offering, Service Commitments define the recurring obligations, and the Customer Subscription Contract brings those elements together into an agreement that can be billed and managed over time.

Understanding this relationship is essential for anyone implementing Subscription & Recurring Billing in Business Central.

The next major question is: How does Business Central actually turn these active subscription contracts into invoices?

That's where recurring billing and billing proposals come into the picture.

In the next part, we'll follow the billing process from an active subscription contract to a billing proposal, invoice creation, posting, and financial impact. We'll also explore billing periods, invoice grouping, reviewing billing proposals, and the controls consultants should consider before automating recurring invoicing.