Business Central

Business Central subscription billing in Australia: what service and project teams should test now

A practical Australian buyer guide to Business Central subscription billing, covering recurring invoices, usage-based charging, deferrals, and the operating-model checks that matter before rollout.

Business Central now has first-party subscription billing capabilities that Australian service, managed-service, rental, and project-led teams can test directly. Microsoft's subscription billing overview describes recurring billing through contracts, subscription lines, renewals, billing templates, notice periods, and deferral-based posting. Microsoft's 2026 release wave 1 plan also lists "Reduce time spent on recurring invoicing in Subscription Billing" as generally available from 1 April 2026, so buyers should validate contract setup, recurring invoice runs, deferral posting, usage import, and reporting before assuming a third-party billing layer is required.

What Microsoft officially documents today

• Microsoft's subscription billing overview says the feature supports recurring invoices for contractually agreed services using contracts, subscription lines, billing periods, billing frequency, billing templates, notice periods, and deferral-based posting of income and expenses.
• The same overview says contracts can group multiple subscription lines so businesses can bill them together on a recurring basis, with subscription lines representing the billable obligations inside the contract.
• Microsoft's examples page says subscription billing supports automated monthly invoicing, mid-cycle proration when a customer starts or cancels partway through a period, and deferred revenue tracking and recognition.
• Microsoft's usage-based billing documentation says usage data can be imported from suppliers using files or web services, processed into pricing, and then invoiced through customer or vendor subscription contracts.
• Microsoft's 2026 release wave 1 documentation lists the recurring-invoicing improvement as generally available from 1 April 2026, and the same wave also documents an enhanced Subscription Billing Power BI app with updated KPI, churn, forecast, and drill-back reporting.

Why this matters for Australian buyers now

• Many Australian SMB and mid-market firms now sit in mixed revenue models: implementation fees, support retainers, managed services, rentals, service bundles, or variable usage charges all sitting beside one-off invoices.
• That is where spreadsheet recurring schedules and manual revenue journals start to break down. The business needs one clearer system of record for contract dates, billing cadence, price changes, credits, renewals, and deferrals.
• Microsoft's current documentation matters because it shows Business Central can now be tested as a first-party option for recurring commercial workflows, not only as a finance ledger waiting for external billing logic to arrive from somewhere else.

The strongest-fit scenarios to pressure-test first

• Managed services, support contracts, and maintenance agreements where customers are billed monthly or quarterly against a recurring service commitment.
• Equipment, software, or service bundles where an item sale triggers one or more attached recurring services. Microsoft's item setup documentation explicitly supports items that create subscription lines automatically on delivery.
• Usage-priced models where the commercial design depends on monthly quantities, transaction volume, or resource consumption rather than a fixed recurring amount.
• Businesses that care about deferred revenue visibility and recurring-revenue forecasting, not only invoice generation.

What to prove before treating it as rollout-ready

• Contract model fit. Check whether your real commercial agreements map cleanly to customer subscription contracts, subscription lines, invoice recipients, renewal timing, and notice periods.
• Billing boundary clarity. Decide which revenue belongs in subscription billing, which belongs in standard sales invoicing, and where project billing or milestone billing still sits outside this model.
• Item and service design. Microsoft documents several item behaviours including Sales with Subscription and Subscription Item. Buyers should prove that their catalogue and quoting process can use those options without creating confusion for sales, finance, or support teams.
• Usage-data process. If the business bills on consumption, prove how usage files or web-service data will arrive, who owns data quality, how errors are corrected, and how reruns are governed.
• Revenue and deferral control. Finance should test how contract invoices, credits, deferrals, and revenue recognition show up in the first month-end close.
• Reporting usefulness. Microsoft's Power BI app updates are promising, but the buyer should verify whether contract value, churn, forecast, and deferred-revenue views match the management pack the business actually uses.

Where Australian projects are most likely to go wrong

• Teams assume recurring invoicing is just a finance automation problem when it is really a commercial-data and process-ownership problem.
• They over-credit the feature because Microsoft documents it well, but do not run one real contract-change, cancellation, proration, or credit scenario end to end.
• They skip the usage-data proof step and discover late that the hard part is not invoice layout but supplier-file quality, import timing, and exception handling.
• They mix project billing, ad hoc services, recurring contracts, and support renewals without deciding which team owns each boundary.

The practical shortlist questions

• 1. Show one fixed-fee recurring contract from quote or order through contract creation, first invoice, renewal timing, and month-end revenue treatment.
• 2. Show one mid-cycle upgrade, downgrade, cancellation, or credit scenario so proration and customer communication can be assessed properly.
• 3. If usage pricing matters, show one import file or data-feed example, one error case, and one corrected rerun.
• 4. Confirm whether the expected reporting pack needs the Subscription Billing Power BI app, custom Power BI work, or additional modelling.
• 5. Name the owner for contract setup, contract change approval, billing exceptions, and deferred-revenue review.

What Australian buyers should conclude now

• Business Central subscription billing is current enough in 2026 to deserve direct evaluation wherever recurring services, rentals, managed support, or usage-priced revenue are part of the target operating model.
• The value is not only faster recurring invoices. It is better control over contract structure, billing rhythm, deferrals, credits, and recurring-revenue visibility.
• The main caution is scope discipline. Buyers should separate subscription billing from project billing, payroll, and generic AR assumptions, then prove one narrow scenario thoroughly before expanding.

FAQ

• Is subscription billing now a standard Business Central topic rather than only a partner add-on? Microsoft's current documentation and the 2026 release wave 1 updates strongly suggest yes, although each buyer still needs to prove fit against its own operating model.
• Can Business Central handle usage-based billing as well as fixed recurring billing? Yes. Microsoft documents usage-based billing as an extension of subscription billing, with imports from files or web services and invoicing through subscription contracts.
• Does Microsoft document deferred revenue support here? Yes. Microsoft's subscription billing overview and examples both describe deferral-based posting and deferred revenue recognition as part of the model.
• Should project-driven firms assume subscription billing replaces all project invoicing? No. That would be an inference too far. The safer question is which recurring revenue belongs in subscription billing and which billing events still belong in the project or services workflow.

Sources used

• Microsoft Learn article: Welcome to subscription billing.
• Microsoft Learn article: Examples for subscription billing.
• Microsoft Learn article: Subscription lines for items.
• Microsoft Learn article: Overview of usage-based billing.
• Microsoft Learn 2026 release wave 1 page: What's new and planned for Dynamics 365 Business Central.
• Microsoft Learn 2026 release wave 1 page: Enhanced Subscription Billing Power BI app.