Microsoft has fundamentally changed how country-specific functionality is managed within Dynamics 365 Business Central. For UK businesses, this shift to a 'delocalised' model means that features for compliance, such as Making Tax Digital (MTD) and the Construction Industry Scheme (CIS), are no longer part of the core application code.
Instead, this functionality is now delivered through an extension, similar to an app you would install on your phone. This architectural change has significant and positive implications for system upgrades, implementation projects, and ongoing maintenance, making the platform more agile and easier to manage.
What is delocalisation?
In the context of Business Central, delocalisation is the process of separating country-specific features from the main application. Previously, functionality required for a particular region, like UK tax rules, was hard-coded into the base system. Now, these features are packaged into optional extensions that can be installed directly from AppSource.
This modular approach ensures the core Business Central application remains globally consistent and lightweight. Local requirements for accounting, tax, and reporting are handled by a self-contained unit that works with the core system but does not modify it. This makes the entire platform more flexible and simplifies maintenance for businesses of all sizes.
Why Microsoft made the change
Microsoft's strategic move towards delocalisation aims to streamline the development and update cycles for Dynamics 365 Business Central. By packaging local functionality as extensions, core application updates can be released more frequently and with fewer dependencies. This ensures all users benefit from the latest platform innovations without waiting for region-specific code to be validated.
This change also empowers both partners and customers by simplifying system customisation. Before, bespoke modifications could conflict with built-in local features, creating complexity and risk during upgrades. With the clean separation offered by delocalisation, businesses now have a more stable and predictable foundation for adding both Microsoft-provided localisations and their own apps.
Benefits for multi-entity UK businesses
For UK businesses that are part of a larger, multi-entity organisation, the delocalisation model offers significant advantages. It allows for a standardised core system across all entities while enabling each one to activate the specific UK localisation extension only where needed. This harmonises group operations and data management without forcing irrelevant features on international subsidiaries.
This structure is particularly useful for managing compliance across different jurisdictions. A UK-based entity can rely on Microsoft's dedicated extension for HMRC compliance, knowing it is entirely separate from the code base used by a German or French counterpart. This reduces the risk of conflicting regional requirements and simplifies the governance of the entire ERP system.
- Simpler upgrades: Because localisation is now an extension, upgrades to the core Business Central application are less likely to be delayed by country-specific changes. This reduces downtime and keeps systems current.
- Consistent compliance: Extensions maintained by Microsoft ensure that VAT, MTD and CIS features are always up to date with HMRC requirements. Businesses no longer need to worry about custom code breaking during upgrades.
- Flexibility for multi-entity setups: Each UK entity can enable the localisation extension independently. This is useful for groups with mixed operations, such as one entity needing CIS compliance while another does not.
- Reduced customisation risk: Extensions are designed to work alongside other apps without modifying the base code. This lowers the risk of conflicts during upgrades and simplifies support.
Simple examples of delocalisation in action
The true impact of delocalisation is best understood through the practical challenges that UK businesses face every day. The move to an extension-based model simplifies how companies handle critical regulatory requirements. Instead of embedding these rules deep within the core system, they function as self-contained apps that can be easily enabled, disabled, or updated.
This new architecture directly affects core financial processes, from tax reporting to industry-specific schemes. Let's explore two common scenarios where the UK localisation extension streamlines operations and reduces the administrative burden for finance teams using Dynamics 365 Business Central.
Example 1: VAT and MTD compliance
Managing VAT and adhering to HMRC's Making Tax Digital (MTD) rules is non-negotiable for any UK business. With the UK localisation extension, Microsoft manages these features and updates them in line with new legislation. When HMRC changes MTD submission requirements, an update to the extension can be applied without altering the core Business Central system.
This means finance teams can trust that their VAT returns are calculated correctly and submitted through the approved digital channels. It removes the need for manual workarounds or costly custom development to keep pace with regulatory changes, ensuring continuous compliance and minimising the risk of penalties from HMRC.
Example 2: CIS for construction projects
The Construction Industry Scheme (CIS) adds another layer of complexity for businesses in the building sector. The UK localisation extension for Business Central includes dedicated functionality to manage CIS deductions, verify subcontractors, and generate the necessary monthly returns. This is all handled within the self-contained extension.
A business can enable this feature for its construction-focused entity while leaving it disabled for other parts of the group that are not subject to CIS rules. This targeted approach prevents unnecessary clutter in the system and ensures that only relevant processes are applied, which in turn simplifies user experience and training.
What this means for implementation
From an implementation perspective, delocalisation streamlines the initial setup of Dynamics 365 Business Central for UK companies. Instead of navigating complex base code modifications, the process now involves activating the official UK localisation extension from AppSource. This approach is faster, cleaner, and far less prone to errors during deployment.
Your implementation partner can therefore focus more time on configuring the system to your unique business processes, rather than on ensuring basic compliance is correctly coded. The extension provides a reliable, pre-built foundation for UK financial regulations, allowing for a smoother project timeline and reducing the overall complexity of getting your new ERP system live.
The bottom line: faster upgrades, stronger compliance
The move to a delocalised model for Dynamics 365 Business Central represents a fundamental improvement for UK businesses. By treating country-specific features as extensions, Microsoft has effectively separated platform innovation from regulatory maintenance. This ensures businesses receive core system updates faster, without the risk that UK-specific code will cause delays or conflicts during the upgrade process.
Ultimately, this means less business downtime, lower maintenance overheads, and a much stronger compliance posture. Your organisation can stay current with the latest Business Central capabilities while trusting that critical UK requirements like MTD and CIS are consistently managed by Microsoft. It is a smarter, more sustainable approach to ERP management.
Ready to take advantage of UK localisation extensions?
Whether you are planning a new implementation of Dynamics 365 Business Central or considering an upgrade, our team can help you navigate the delocalised landscape. We have the expertise to ensure your system is configured for seamless compliance and optimised for your specific operational needs. Contact us today to discuss how we can support your business.
Speak to our Dynamics 365 team.