Subscription billing in Dynamics 365 Finance

Subscription Billing is a relatively recent addition to Dynamics 365 Finance, built to handle the recurring-revenue, contract-driven business models that are now common across software, telecoms, equipment-as-a-service, and B2B services. It replaces a long history of customer-built workarounds for handling subscriptions in AX/F&O.

Three integrated components

Subscription Billing combines three working units:

1. Recurring Contract Billing — manages contracts, billing schedules, mid-term changes (add/remove products, prorations, upgrades/downgrades), and renewals.
2. Revenue and Expense Deferrals — manages straight-line and milestone deferrals of revenue or expense across periods, automating the journals.
3. Multiple Element Allocations — handles the ASC 606 / IFRS 15 problem of allocating contract revenue across performance obligations when a contract bundles multiple products or services.

Contracts

A subscription contract holds the customer, term, billing cadence, products, prices, discounts, and any special clauses. Contracts can be billed monthly, quarterly, annually, on milestones, or on usage. Mid-term changes (adding a seat, upgrading a tier, partial cancellation) prorate automatically.

Revenue recognition

Revenue recognition is decoupled from billing — invoicing a customer for an annual contract doesn't recognise twelve months of revenue at once. The deferral component spreads revenue across the contract period to comply with accounting standards. Performance-obligation-based recognition handles bundled contracts.

Usage billing

For consumption-based components, usage data feeds Subscription Billing through a Data Management interface or an API, where it's priced and billed alongside the recurring component on the same invoice.

Pricing

Tiered pricing, volume discounts, ramp-ups, and prepaid balances are all configurable without custom code.

Integration with the rest of F&O

Subscription Billing posts to the standard AR sub-ledger, so customer balances, payments, and statements work as normal. Revenue recognition entries land in the GL with deferred-revenue control accounts and recognised-revenue accounts mapped by product.

Reporting

ARR (annual recurring revenue), MRR (monthly recurring revenue), churn, contract value, and waterfall reports are produced via Power BI templates that ship with the module.

Where it doesn't fit

Very high-volume B2C subscriptions (tens of millions of subscribers) typically sit better with a dedicated subscription platform (Stripe Billing, Zuora) that feeds F&O the financial summary. For B2B subscription businesses up to mid-market, Subscription Billing is increasingly the right answer in-product.