Microsoft Dynamics 365 Business Central 2026 Release Wave 1 does more than add new finance, manufacturing and AI features. It also changes how organisations can record sustainability data, report payment behaviour, audit permissions, manage extensions and move information from legacy systems into the cloud.
Part 1 of this series covered Business Central Copilot, AI agents and manufacturing. Part 2 looked at finance, electronic documents and the Business Central Shopify connector. This final part focuses on the platform work that sits behind a reliable Business Central ERP environment: sustainability reporting, data governance, security administration and Business Central migration.
Several of these updates are already generally available. The reimplementation tooling is different: it entered public preview on 30 June 2026 and has no general-availability date in the current release plan. That distinction matters when a Business Central consultant is deciding what can be used in a production project and what still belongs in a controlled sandbox evaluation.
The practical question is not how many new switches can be enabled. It is whether the organisation has the data, ownership and controls needed to use the capability properly. Carbon reporting built on incomplete emission data is still unreliable. A clearer permissions screen does not correct an over-permissioned security model by itself. Better migration tooling cannot decide which legacy data is worth carrying forward.
Three key takeaways
- 1.Sustainability data is moving closer to everyday ERP transactions. New Business Central APIs and sales-document layouts make it easier to exchange emission information and show estimated CO₂e on quotes and invoices.
- 2.Governance is becoming easier to inspect and automate. Administrators can review permissions across installed apps, manage per-tenant extensions from the admin centre and examine database index usage at company level.
- 3.Cloud migration is becoming more reusable, but project decisions still matter. The platform now supports migration engines for SQL-based systems, while a preview reimplementation route aims to move useful Business Central data without importing every obsolete customisation.
How is sustainability management changing in Business Central?
Sustainability management is increasingly connected to finance, purchasing and supply-chain data. Organisations may need to understand the emissions associated with suppliers, products, transport, facilities or production activity, then use that information in internal decisions and external ESG reporting.
Keeping carbon accounting in a separate spreadsheet creates familiar problems. The finance team, sustainability lead and operational teams may use different versions of the same data. Emission factors can be applied inconsistently. A reported total may be difficult to trace back to the purchase or activity that created it.
Business Central sustainability management provides a place to record emission factors, post sustainability entries and calculate CO₂e values alongside the operational and financial records already held in the ERP. Release Wave 1 improves the ways that information can leave the system and appear on customer-facing documents.
New sustainability APIs for Business Central integration
Microsoft has added four APIs covering sustainability goals, ESG reporting staging data, emission value entries and purchase lines with sustainability detail. Together, they give a Business Central integration more structured access to information that previously risked being exported and handled manually.
The Business Central sustainability APIs became generally available on 5 June 2026. Microsoft positions them for automated ESG reporting, synchronising sustainability goals and exchanging emission details with procurement or reporting systems.
That creates useful options for organisations whose sustainability process extends beyond Microsoft Business Central. A reporting team may need emission entries in Microsoft Fabric or Power BI. Procurement may need supplier and purchase-line information in a separate data platform. A group may want to combine Business Central data from several entities before producing a consolidated disclosure.
The API is only the transport layer. The implementation still needs agreed ownership, mappings, refresh schedules, validation rules and exception handling. If two systems can update the same sustainability goal or purchase-line detail, the organisation should define which one is authoritative before the integration is switched on.
Carbon-footprint information on sales quotes and invoices
Release Wave 1 also adds ESG-focused Word layouts for sales quotes and sales invoices. These layouts can show estimated CO₂e per unit and total emissions, with a disclaimer explaining the source and nature of the figures.
Sustainability tracking is becoming a compliance requirement in many sectors. Having carbon accounting native in Business Central means your finance and operations data are already aligned - no separate data export required.
Microsoft lists the new carbon-footprint sales document layouts as generally available from 1 April 2026. They use values calculated through the Sustainability module and do not require a bespoke report layout before an organisation can start evaluating them.
For a manufacturer or distributor, this may help answer customer requests for product-level carbon information without creating a separate document by hand. It also raises a governance question: once an estimated figure appears on a commercial document, the calculation method, units and caveats must be understood by the people issuing it.
Why sustainability data quality matters
Carbon accounting is sensitive to master data. The same activity can produce very different results if the wrong emission factor, unit of measure, fuel type or calculation period is used. A Business Central implementation should therefore treat sustainability setup as governed business data rather than an optional reporting field.
Before relying on the output, the team should agree which Scope 1, Scope 2 and relevant Scope 3 activities are in scope, where the source data comes from and who approves changes to emission factors. It should also document how estimates are labelled, how corrections are handled and how the result is reconciled with any external sustainability platform.
A sensible first use case is narrow. Test one material category, supplier group or operational process, trace the values from source transaction to final report and compare the result with the organisation's existing method. That gives the business evidence before it expands the Business Central sustainability model.
UK Payment Practices reporting
The main UK-specific addition in the current Release Wave 1 plan is Payment Practices reporting. Business Central now supports additional information required by the Reporting on Payment Practices and Performance (Amendment) Regulations 2024.
The updated UK Payment Practices functionality became generally available on 5 June 2026. It adds measures including the total value of payments made during the reporting period, payments made late against agreed terms and the proportion of late payments connected to disputes. The report can be exported as a CSV file.
A dispute mechanism on purchase invoices helps connect delayed payment to the reason it was held. This is more useful than compiling the figures at the end of the reporting period because the context is recorded when the issue occurs.
Finance teams should still test the report against their real payment terms, settlement patterns and dispute process. Supplier records, due dates and payment applications need to be accurate, and users need a consistent rule for recording a genuine dispute. Otherwise the report may be complete in format but weak in evidence.
Stronger Business Central governance and administration
Many ERP problems are not caused by a missing business feature. They come from permissions that have accumulated over time, extensions with unclear ownership, performance issues that are difficult to diagnose or a migration process built around one-off scripts. The 2026 governance updates address each of those areas.
These changes are particularly relevant to a Business Central support partner or internal platform team responsible for several environments. They create a clearer administrative surface, but they do not replace the need for change control, release ownership and a documented support model.
A clearer view of user and group permissions
The new Permissions Overview page brings permission sets from installed apps and extensions into one view. Administrators can filter by object, scope, extension or permission set, then use FactBoxes to see the security groups and users affected.
Microsoft made the permissions audit capability generally available on 1 May 2026. It can help answer practical questions such as which permission sets allow a user to edit customer records or which extension grants access to a particular object.
The improvement is visibility, not automatic remediation. An access review still needs to compare the permission model with job responsibilities, segregation-of-duties rules and joiner, mover and leaver processes. Temporary access should have an expiry route, and changes should be tested so that a security correction does not prevent users from completing essential work.
Managing per-tenant extensions from the admin centre
Per-tenant extensions, usually shortened to PTEs, are custom Business Central extensions installed for one tenant. They can hold important company-specific functionality, which makes their deployment and version history part of the organisation's operational risk.
From 7 July 2026, administrators gained fuller PTE lifecycle management in the Business Central admin centre. They can upload packages, install them immediately or schedule the installation, view upcoming versions and use admin-centre APIs to support deployment automation.
This can make Business Central upgrade and support work more predictable, particularly where a partner uses a controlled build and release pipeline. The important safeguards remain the same: source control, peer review, automated tests, sandbox deployment, dependency checks, rollback planning and clear approval before production release.
An easier installation process should not encourage unmanaged customisation. Every extension should have an owner, a business purpose, a supported version and a decision about whether standard Business Central functionality could replace it in future.
Company-level database index management
Business Central administrators can now inspect database index information through the user interface, including storage use, SQL Server usage statistics and whether an index was defined in AL or generated by the system. Selected non-unique indexes can be disabled for an individual company.
The database index management update became generally available on 1 April 2026. Microsoft protects primary keys, unique indexes, SIFT indexes and system ID indexes from being disabled. Re-enabling an index is queued for the next scheduled midnight process.
This is a specialist tool, not a routine housekeeping task. Removing a lightly used index may reduce storage or improve write performance, but it can also slow a report, integration or month-end process that runs infrequently. Changes should be based on telemetry and a known performance hypothesis, then monitored after deployment.
Business Central cloud migration and reimplementation
A Business Central migration is rarely just a technical transfer. Legacy ERP environments contain data that the organisation still needs, data retained only for audit and years of setup or customisation that may no longer reflect the way the business works.
Release Wave 1 adds two different migration routes. One expands the framework for moving from SQL-based source systems. The other provides a preview reference implementation for reimplementing an older Business Central environment without carrying every historical customisation into the new cloud tenant.
Migration from SQL-based source systems
Developers can now build reusable migration engines for SQL-based applications and connect them to the standard Cloud Migration wizard. The extension defines how data is mapped, replicated and transformed, while the familiar migration interface shows progress and errors.
Microsoft lists the generic SQL cloud migration framework as generally available from 1 April 2026. It gives Business Central migration partners and software vendors a supported way to package repeatable migration logic instead of rebuilding an ad hoc script for every customer.
Repeatable tooling can reduce technical risk but it does not remove the need for data profiling and reconciliation. Customer, vendor and item records may contain duplicates. Units of measure and posting groups may not map cleanly. Historical transactions may use codes that no longer exist. The migration design should state what will move, what will be archived and how totals will be proved before cutover.
Reimplementation without carrying every legacy customisation
The reimplementation tool takes a different approach. Its aim is to move essential master data, selected transactional information, opening balances and required setup from an older Business Central environment into a new implementation, while leaving obsolete customisations behind.
The current Business Central reimplementation tooling entered public preview on 30 June 2026. Microsoft's initial reference scope covers company migration from Business Central version 14 and is designed so developers can add further migration modules.
That makes it relevant to organisations considering a Business Central upgrade, Dynamics NAV to Business Central migration or wider ERP modernisation. It may support a cleaner move than upgrading every historic extension and process, but it should not be presented as a universal migration path while the feature remains in preview and the documented source scope is limited.
A reimplementation also requires more business decisions than a technical upgrade. Posting structures, dimensions, workflows, security roles, integrations and reporting may all need redesign. The benefit comes from choosing what the future system should contain, not from reproducing the old environment more quickly.
What should organisations review before enabling these updates?
- 1.Confirm availability and scope. Check the current release status, country availability, licensing and the Business Central version used by each environment.
- 2.Choose a real business process. Start with a defined sustainability report, permission review, extension release or migration scenario rather than enabling a feature without an owner.
- 3.Review data and controls. Validate emission factors, supplier terms, permission assignments, extension dependencies and migration mappings before testing begins.
- 4.Use a representative sandbox. Include normal transactions, difficult exceptions, realistic data volumes and the integrations or PTEs that will be present in production.
- 5.Agree ownership and rollback. Name the person responsible for approvals, monitoring, incident handling and reversal if the result is not as expected.
- 6.Measure the outcome. Compare reporting effort, data quality, access-review time, deployment reliability or migration reconciliation against an agreed baseline.
Does your organisation need a Business Central upgrade?
A new release is not automatically a reason to start a Business Central upgrade project. The stronger case is a known operational or technical problem: sustainability data that cannot be traced, payment reporting assembled manually, permissions that are difficult to audit, extension deployments that rely on one person or an ageing ERP system that is expensive to maintain.
A Business Central health check should confirm version support, extension compatibility, integrations, security, performance and data quality. It should then map relevant release features to the processes that need improvement. This creates a Business Central roadmap based on value and risk rather than the length of Microsoft's feature list.
For customers planning a legacy ERP migration, the review should also compare upgrade, reimplementation and replacement options. The lowest-risk route may be an in-place upgrade, a cleaner Business Central reimplementation or a phased migration that retains a read-only archive for historical information.
Work with a Dynamics 365 Business Central partner in the UK
InteliSense IT is a Microsoft Dynamics 365 Business Central partner supporting UK organisations with implementation, integration, upgrades, migration and managed services.
Our Business Central consultants can assess sustainability data, review permissions and extensions, test release features and design a controlled Business Central cloud migration. We also help organisations decide when standard functionality is sufficient and when AL development, Power Platform, Microsoft Fabric or Power BI should form part of the wider architecture.
The work begins with the process and the evidence behind it. For sustainability, that means the source and ownership of emission data. For governance, it means real users, permission sets and release responsibilities. For migration, it means agreeing which records are operationally useful and proving that balances and transactions reconcile before cutover.
For organisations already running Microsoft Business Central, our Business Central support team can help with release readiness, extension lifecycle management, security reviews, integration monitoring and a practical upgrade roadmap.
Frequently asked questions
What sustainability features are included in Business Central 2026 Release Wave 1?
The release adds four sustainability APIs and new Word layouts that can display estimated CO₂e values on sales quotes and invoices. Both features are generally available, although the underlying data and reporting method still need careful governance.
Can Business Central integrate sustainability data with external systems?
Yes. The new APIs provide access to sustainability goals, ESG reporting staging data, emission value entries and purchase lines with sustainability detail. The integration still needs defined mappings, ownership and validation rules.
Can Business Central show carbon-footprint data on invoices?
Yes. New ESG-focused Word layouts can show estimated CO₂e per unit and total emissions on supported sales invoices and quotes, with a disclaimer about the estimates.
What changed for UK Payment Practices reporting?
The UK localisation now records additional payment-value, late-payment and dispute information required by the amended reporting regulations. The result can be exported as CSV for submission or further processing.
What is the Business Central Permissions Overview page?
It is a consolidated view of permissions from installed apps and extensions. Administrators can filter by object, scope, extension or permission set and see which users or security groups are affected.
Can administrators manage PTEs from the Business Central admin centre?
Yes. Administrators can upload, install, schedule and review per-tenant extension versions through the admin centre, with APIs available for controlled deployment automation.
Can Business Central migrate data from any SQL database?
The 2026 framework allows developers and partners to build reusable migration extensions for SQL-based source systems. A project still needs source analysis, mapping, transformation, reconciliation and cutover controls.
Is the Business Central reimplementation tool generally available?
No. It entered public preview on 30 June 2026, and the current release plan does not list a general-availability date. Microsoft's initial reference scope covers company migration from Business Central version 14.
When should we use a Business Central consultant?
A Business Central consultant can help assess process fit, configure sustainability and governance features, review extensions, design integrations and choose an appropriate upgrade or migration route.
Start with a Business Central release-readiness assessment
Release Wave 1 gives Business Central customers better tools for sustainability reporting, compliance, administration and cloud migration. The useful change is not the feature itself. It is the reduction in manual work or risk when that feature is applied to a well-understood process.
Start with one measurable problem. Trace the data and decisions behind it, test the relevant Business Central functionality against real scenarios and agree what success will look like. That produces a defensible next step, whether the answer is configuration, integration, an extension change or a wider Business Central migration.
InteliSense IT can review your Dynamics 365 Business Central environment, assess readiness for the sustainability, governance and migration updates and build a practical roadmap around the processes that need to improve.
Speak to InteliSense IT about a Microsoft Dynamics 365 Business Central release-readiness assessment.
Feature availability, licensing, localisation and release dates can change. Review Microsoft's current documentation before making implementation decisions.
