IRS 1099 reporting is a critical compliance process in the United States, requiring businesses and financial institutions to report various types of non-employee income—such as payments to freelancers, interest, dividends, and rent—to the Internal Revenue Service (IRS). This ensures transparency and helps the IRS track income that may not be captured through traditional employment reporting. 

For years, Dynamics 365 Business Central has supported 1099 reporting through a familiar and straightforward process. Users could configure 1099 form boxes, designate vendors as 1099-liable, and manage reporting through the purchasing and payment workflows, culminating in year-end printing on preprinted IRS forms. However, due to frequent and often last-minute changes from the IRS—typically released in October or November—Microsoft had to delay updates, creating a stressful and unsustainable cycle for partners, customers, and users alike. 

Recognizing the need for a more resilient and modern approach, Microsoft has introduced a completely new 1099 reporting experience. This is not a redesign of the existing functionality, but a brand-new solution delivered as a preinstalled, standalone IRS Forms app in U.S. Business Central environments. This shift brings a fresh architecture and process flow, from setup to submission, with the most significant change occurring at the end of the reporting cycle. 

What does this mean to you? 

You can stop ordering preprinted 1099 forms from IRS. The new IRS Forms app no longer supports printing on preprinted forms. 

This change is driven by two key factors: 

1. Regulatory Compliance: In this moment, businesses filing 10 or more information returns, including all 1099 forms, are required to file electronically. This threshold means that even small businesses are now likely subject to e-filing requirements. 

2. Technical Simplification: Supporting preprinted forms is complex and error-prone, as even slight variations in form layout can cause misalignment. It also meant customers had to wait for Microsoft to release updates each year to unblock you. With digital files, updates are easier to manage, and the submission process becomes more reliable and efficient. 

But we haven’t forgotten about your vendors. The new app allows you to generate substitute 1099 copies with the same content as the official forms, which can be printed or emailed automatically. These reports are also configurable, enabling you to add new form boxes without needing support from Microsoft or a partner. 

We won’t cover all the new features here—there are many productivity enhancements worth exploring. We encourage you to review the full documentation: : https://learn.microsoft.com/en-us/dynamics365/business-central/localfunctionality/unitedstates/introduction-to-the-irs-forms.  

Get Ready Now 

Before this change becomes mandatory, we strongly recommend enabling the new IRS Forms app in your sandbox environment and testing it alongside your upgrade process as soon as possible. This will ensure a smoother transition and help you adapt to the new workflow with confidence. To do so, just enable new 1099 forms on the Feature Management page. 

Stay tuned. Based on early feedback from partners and MVPs, we’ll be rolling out additional improvements before the end of the year. 

The post Business Central and IRS 1099 Reporting in the USA: An Important Shift Ahead  appeared first on Microsoft Dynamics 365 Blog.

Microsoft is doing some housekeeping in Dynamics 365 Business Central–and significant changes are coming with the 2025 release Wave 1 clean-up. We want you to know about these changes and how to prepare your applications.

The Dynamics 365 Business Central Release Wave 1 clean-up means that all tables, table extensions, and table fields remaining in the Obsolete::Removed state for more than one major release will be permanently deleted. This sweeping clean-up affects the Base Application as well as all other first-party apps. Already, the removal of over 150 tables has optimized and cleaned up the application code.

With the Release Wave 1 clean-up, Microsoft will adopt a clean-up cycle every fifth release, ensuring a smooth transition.

Why this matters: Benefits of the clean-up

The April 2025 Release Wave 1 clean-up effort isn’t just about reducing database size, it’s part of a broader vision:

• Improved database performance: Removing unused schema elements will optimize performance and reduce technical debt.

• Unified Base Applications: Multiple countries (such as, Sweden, Denmark, Czechia, India, and Iceland) and partner-localized regions will move towards a unified Base Application. The goal is to have all countries based on the same codebase.
• Improved maintainability: By removing more than 10% of tables and table fields, we’ve simplified development and made it easier for developers and product owners to manage changes.
• Streamlined codebase: Cleaner code results in fewer errors and easier maintenance for developers.

Key updates and concepts

Platform support for the clean-up

2025 release wave 1 (v26) introduces platform-level support for dropping tables, table extensions and table fields that have been in the Obsolete::Removed state for more than one major release. This ensures an automated clean-up process, consistent and in alignment with Microsoft’s ongoing breaking changes process and optimization strategy.

Introducing the Step Release

A new concept, Step Release, plays an important role in cloud migration and the upgrade process:

• Mandatory for cloud migration: Customers migrating from earlier versions must upgrade to a Step Release before proceeding to newer versions.
• Purpose: The Step Release ensures all schema elements in the Obsolete::Removed state for more than the defined period are cleared out before transitioning to the latest version.
• Impact on upgrade code: The updated upgrade process excludes objects marked for removal in this release.

Important: The data from deleted tables, table extensions and table fields will also be permanently removed. Tables, table extensions and table fields in the state Obsolete::Pending are not impacted.

How to identify impacted tables, table extensions and table fields

With the Release Wave 1 clean-up, Microsoft has introduced a new preprocessor symbol, CLEANSCHEMA, to help developers identify and handle obsolete schema elements. Here’s how it works:

• The CLEANSCHEMA symbol operates similarly to the existing CLEAN symbol, with a version number showing when a table, table extension or table field was marked as Obsolete::Removed.
• For example:
  • CLEANSCHEMA24: The table, table extension, or table field marked as removed in version 24 and deleted in version 26 (2025 release wave 1).
  • CLEANSCHEMA25 or later: The object remains for at least one more cycle of 5 releases. Deletion happens in future releases- version 31 (2027 release wave 2).

What should developers do?

If your app references objects in the Obsolete::Removed state then you need to:

1. Refactor your code: Replace or remove references to these objects before April 2025.
2. Check upgrade code: Ensure that upgrade code doesn’t rely on removed tables, table extensions or table fields.
3. Monitor preprocessor symbols: Use the CLEANSCHEMA symbol to anticipate removal timelines.

Implications for cloud migration

The cloud migration path will change as part of the clean-up:

1. Customers will first migrate to version 25 (2024 release wave 1).
2. Upgrade code then handles the transition to the latest version after clearing obsolete objects.

This new process emphasizes the importance of preparing early, especially for legacy applications with dependencies on obsolete schema elements.

What if you need data from removed tables?

Microsoft recommends that you use the Point-In-Time Restore (PIT) procedure for data recovery, which is consistent with current best practices. If you anticipate needing data from obsolete tables, table extensions or table fields, ensure you plan for PIT backups before the clean-up.

Preparing for the future after the Release Wave 1 clean-up

With these changes, Microsoft continues its dedication to enhancing the maintainability of Business Central.

Next steps for partners:

1. Inspect your code: Identify any dependencies on Obsolete::Removed schema elements using the CLEANSCHEMA symbol and refactor the code accordingly.
2. Prepare migration plans: Incorporate the Step Release process into your upgrade and cloud migration strategies.

By being proactive, you’ll ensure a smooth transition and take full advantage of the benefits of a cleaner, faster, and more unified Business Central.

Additional resources:

Deleted objects in 2025 release wave

•  https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/deleted-objects-25w1

Maintaining Apps

• Update Lifecycle for Tenant Customizations – Business Central | Microsoft Learn
• Maintain AppSource apps and per-tenant extensions – Business Central | Microsoft Learn

Microsoft will host two Office Hour calls for partners to join for questions about this process and next steps:

Option 1: February 13, 4:00 – 5:00PM CET. Please register here

Option 2: February 18, 8:00 – 9:00AM CET. Please register here

The post Essential Clean-Up Guide for Partners: 2025 Release Wave 1 appeared first on Microsoft Dynamics 365 Blog.

Learn how the upcoming 2024 release wave 1 will enable you to track and report your greenhouse gas emissions with ease and accuracy.

Sustainability is more than a buzzword. It’s a global imperative that demands urgent action from all sectors of society, including the business world. As regulations and expectations around environmental reporting evolve, organizations need reliable and efficient tools to measure and manage their impact on the planet.

That’s why we’re excited to announce that Dynamics 365 Business Central will soon offer new sustainability features that will help you comply with the latest standards and best practices, as well as drive positive changes for your business and the environment. Starting from the 2024 release wave 1, you’ll be able to track and report your greenhouse gas (GHG) emissions across three scopes defined by the ESG standard, using sustainability journals and built-in calculation methods. You’ll also be able to leverage the new Chart of Sustainability Accounts to organize and analyze your emission data with ease and transparency.

The new functionality is designed to oversee and regulate an organization’s environmental footprint by tracking various greenhouse gas (GHG) emissions, facilitating proper insights. This functionality will be a multi-wave investment and at this first release we delivered basic framework as a foundation for future expanding. The first version focuses on GHG emissions, and related to that the solution is focused on three emission scopes defined by the ESG standard. This feature supports the basic process of collecting emission data via sustainability journals, allowing for manual entry of known data, or utilizing built-in methods for calculating emissions footprints.

Chart of Sustainability Accounts

The Chart of Sustainability Accounts forms the foundational structured list used for recording all emissions data. It functions as a comprehensive framework that categorizes and organizes these accounts based on their attributes, such as scope or other groupings. Each account is typically assigned a unique code or number for easy reference and tracking, following the same structure as a traditional Chart of Accounts but customized specifically for monitoring sustainability-related data and metrics within an organization.

This chart typically encompasses categories such as energy consumption, greenhouse gas emissions, waste generation, and other pertinent sustainability metrics. Users have the flexibility to add Account Categories and Subcategories to define how the system behaves, selecting dedicated emissions for tracking, emission factors, formulas, and similar configurations.

In essence, the Chart of Sustainability Accounts serves as the backbone of the Sustainability feature, facilitating effective tracking, measurement, and management of sustainability-related data and metrics within the organization.

Chart of Sustainability Accounts

Sustainability Journals

Sustainability Journals are designed to track and record sustainability-related activities, and metrics within an organization, using the same user experience as other journals in Business Central. Within the journal, users have the option to input emissions manually if they possess the necessary information. Alternatively, if they lack this data, they can utilize built-in formulas to accurately calculate emissions based on specific known parameters corresponding to various types of sources and accounts.

When posting with a Sustainability Journal, entries are generated on the Sustainability Ledger. Similar to other journal types, users have the flexibility to utilize various templates and batches with specific configurations. They can opt for standard journals or recurring journals to manage sustainability data efficiently.

Sustainability Journal

Sustainability Entries

The Sustainability Ledger organizes all emission data according to the Chart of Sustainability Accounts. When a user posts the Sustainability Journal, all crucial data is recorded within the Sustainability Entries. Posting to these entries can be regulated by specific rules configured in the Sustainability Setup, and users can use dimensions in a manner consistent with other entries throughout Business Central. All reports are generated based on Sustainability Entries. Presently, there are several existing reports available for analyzing and tracking emissions. However, in future releases, Business Central will introduce additional reports for printing or submission to relevant authorities.

Future Development

As mentioned in the introduction, Microsoft will continue to enhance this feature by adding more horizontal capabilities and improving its connection with other features in Business Central, without focusing on industry-specific aspects. The development of new features will depend on research of the key elements for such solutions, compliance with regulatory requirements, and useful feedback from partners. Also, it is expected that ISV partners will use this basic framework to create industry-specific sustainability solutions.

The post Sustainability in Dynamics 365 Business Central: A New Way to Measure and Manage Your Environmental Impact appeared first on Microsoft Dynamics 365 Blog.

Business Central 2023 release wave 2 introduces a new global feature – Electronic Documents. Microsoft has crafted this as a foundational framework, providing a robust base for catering to localized requirements. This innovative approach allows Microsoft to efficiently deliver tailored localization apps for some countries. Furthermore, partners can leverage this model to craft their custom localizations. Given the unique e-document formats and distinct integration services prevalent in various countries, these localization apps are indispensable.

Why did Microsoft deliver it?

Before we delve into the world of E-Documents within Business Central, let’s acquaint you with an important new acronym – CTC, which stands for Continuous Transaction Control. This term signifies the imperative ‘real-time’ invoicing reporting and validation mandated by authorities. CTC encompasses a suite of digital control mechanisms to enhance tax collection and curb tax fraud. Electronic Invoicing stands as a key component of CTC, a model increasingly embraced by numerous countries.

We can easily conclude – this approach will become mandatory in many countries if it hasn’t already. The prospect of different solutions for each country poses challenges. Hence, we’ve developed one global extendable solution as an app, simplifying support for diverse countries.

Exploring the Scope of E-Invoicing Models

Understanding the landscape of E-invoicing can initially seem straightforward – creating an electronic file and transmitting it. However, the reality is more intricate. E-invoicing encompasses various models, including the 2-corner, 3-corner, and 4-corner frameworks. Each country retains autonomy to determine its preferred approach. Moreover, even in non-mandatory scenarios, businesses often opt for E-invoicing to streamline communication.

Our solution encompasses all the corner models mentioned here and facilitates additional messaging capabilities between access points, providing a comprehensive E-documents framework.

How do E-Documents Operate in Sales and Purchases?

E-Documents in Business Central facilitate seamless interaction in both sales and purchase processes. It’s a two-way system, enabling the transmission of electronic sales documents to customers while also receiving electronic documents from vendors. These electronic documents have their own distinct lifecycles, which may not always align with invoice timelines. To accommodate this, we’ve introduced a new entity, the E-Document, linked with the original document in Business Central. This entity hosts a unique information set, including statuses, logs, and potential error notifications or warnings.

Once the system is configured, posting a sales document triggers the automatic creation of an E-Document. Depending on your setup, it’s promptly dispatched to the designated service. You gain complete visibility into its status and can take additional actions as needed.

In the case of incoming purchase electronic documents, you have the flexibility to upload them to Business Central manually. However, if your access-point provider provides a document delivery service, you can configure a Job Queue for automated downloads and E-Documents creation. Here’s the magic: if you’ve mapped vendors’ items with yours through item-references or G/L accounts and there are no errors, the system will effortlessly generate purchase invoices with all the essential details. Your task? Just review and post them.

How to Expand This Functionality?

This framework has been created to speed up your productivity when building electronic invoicing applications by taking care of all the infrastructure work, like subscribing to different posting routines, writing custom mapping logic, logging, error handling, and running jobs in the background.

The framework is designed to improve your productivity in developing electronic invoicing applications. It handles essential infrastructure tasks such as subscribing to various posting routines, custom mapping logic, managing logs, handling errors, and running background jobs. This empowers you to direct your attention towards the specific electronic invoicing logic, including:

• Exporting/Importing documents from Business Central to the local format mandated by the authority.
• Establishing seamless integration with the authority’s endpoint for sending and receiving electronic documents.

To create your local E-Document:

1. Create a new extension adding dependency to the E-Document Core application.
2. Implement a document interface based on the specification mandated by the local authority, using designated endpoints for the sales: Check, Create, and CreateBatch, and GetBasicInfo and PrepareDocument when you expect to receive documents.
3. Implement an integration interface to send/receive documents to the local authority automatically.
4. Enhance user experience by implementing a setup wizard that gathers all necessary configuration details and obtains customer consent for data transmission. This streamlined process ensures a smoother onboarding experience for users.

More details with examples how to extend existing E-Document Core application can be found here.

The post E-Documents as a Global Solution for Business Central appeared first on Microsoft Dynamics 365 Blog.

Business Central 2023 release wave 2 introduces regional formats for reports, which adds a new dimension of customization for reports. This feature gives you more flexibility to tailor how reports print, according to your unique needs. Addressing inherent limitations, such as the inability to customize region formats for specific reports, the absence of support for designating a specific format for Customers and Vendors, and the reliance on report format settings from My Settings, this enhancement simplifies the reporting experience in Business Central. In this article, we’ll dive into the mechanics of these changes and explore how they enhance the overall reporting process in Business Central.

Behavior and Priority Order

To understand how the new regional format feature works, let’s explore its behavior and order of priority. This insight will help you grasp how Business Central determines the language and format to use for reports in different situations, so you can adjust these settings to suit your business requirements.

1. Request Page: Advanced Settings Take Center Stage

The highest priority in the report generation process resides with the advanced settings on the report request page. When you generate a report, you can specify the language and format you want to use for the report.

Advanced settings in the report request page

2. Report Object in AL: Precise Configuration

The heart of the matter lies in the AL triggers associated with the report object. Reports now include two important properties: Report.Language and Report.FormatRegion. These properties, defined within the AL triggers, play a key role in configuring reports. For many standard document reports in the Base App, these properties are set based on the Language Code and Format Region fields from the document itself. These fields get their values from the corresponding entity settings. For example, the Sales Header report gets its settings from the customer entity.

3. Language and Format in Customer/Vendor Card

If a report should be printed in the language of the recipient rather than in the working language, the developer can add code in the report to handle this. This functionality is already enabled for most reports in the standard Business Central database. The document is printed in the language that is specified in the Language Code field on the Customer or Vendor Card page.

Example of Language and Format Region Codes on the Customer page

4. Language and Format in My Settings

If the report properties mentioned earlier aren’t configured within the AL triggers, Business Central then refers to the settings in My Settings. For example, consider a scenario where a regional format isn’t defined for a customer. In this case, when you print documents associated with the customer, the Report.FormatRegion property won’t have a specific regional format set. Consequently, Business Central will turn to the regional format setting in My Settings as a fallback. While My Settings had a more prominent role in earlier versions, its current function is to step in when no alternative settings are available.

By using this order of priority, Business Central ensures that the report output language and format are based on the most relevant and specific configurations. This approach gives you greater control over language and format customization for individual reports. Ultimately, this feature streamlines the reporting process, making it more efficient and user-centric.

The post Adding Regional Formats to Reports in Business Central appeared first on Microsoft Dynamics 365 Blog.

You asked for it and we’re delivering: With 2023 release wave 1, Microsoft Dynamics 365 Business Central will expand the non-deductible value-added tax (VAT) feature to our customers worldwide. It’s required by almost all countries where VAT is used and was previously available only to our customers in Belgium, Italy, and Norway. We’re excited to make it available everywhere our Business Central customers are.

VAT is a tax that businesses must pay when they buy things. They can usually recover the tax by buying goods and services relating to their business activities. However, there are some situations in which a business incurs VAT that can’t be recovered and isn’t deductible.

The expanded functionality covers the most common scenarios and can be easily extended if you need more features.

Non-deductible VAT options

You can use proportional VAT to calculate VAT when you have both deductible and non-deductible VAT. Non-deductible VAT is included in purchase documents only. Depending on your settings, you can use fully or partly non-deductible VAT or a combination with different deductible percentages per line. You can use it configured as Normal VAT, Full VAT, and Reverse Charge VAT with or without deferrals. Before posting the purchase document, you can adjust the VAT amounts if VAT rounding in the external system and Business Central differ.

Reporting non-deductible VAT

After posting, the VAT Entry table shows separate details for deductible and non-deductible amounts and bases. When it’s time to report VAT amounts to your authorities, the Amount Type column in the VAT Statements view offers options for non-deductible and full amount or base. The Day Book VAT Entry report features new columns as well. Other reports will be updated in later releases based on our customers’ feedback.

Setting up to use non-deductible VAT

Non-deductible VAT is included in the base application but isn’t enabled by default. To use this feature, you must enable it on the VAT Setup page.

After enabling the feature, configure VAT posting group combinations for use as non-deductible VAT. Enable them and add a percentage for deduction.

If needed, you can fine-tune the settings for better results. You can choose to configure the impact of non-deductible VAT on the item cost, fixed asset acquisition cost, or job cost.  You can also configure how to treat non-deductible amounts. If you want these amounts to be posted only in General Ledger entries but use them as an additional cost in purchase, you can add it in the setup.

We added all the non-deductible VAT logic and events to the Non-Deductible VAT Management codeunit. If you need to get the non-deductible VAT percentage not just from the VAT posting setup, use the OnBeforeGetNonDeductibleVATPctForPurchLine integration event and return the Non-Deductible VAT % based on the purchase line.

Deprecating existing functionalities

As part of expanding the non-deductible VAT feature worldwide, we’re deprecating the specific solutions for Belgium, Italy, and Norway starting with Business Central 2023 release wave 2 (version 23). You’ll have three releases after version 23 to adjust your extensions to the W1 solution.

Non-deductible VAT will be available in May with 2023 release wave 2 for all countries/regions using the W1 base app and all countries/regions using local base apps other than Belgium, Italy, Norway, and Spain.

Next steps

If you see some obstacles in this process, please get in touch with us. The best channel for communication is our Yammer group for partners, https://aka.ms/BCYammer (requires partner credentials to log in).

To learn more, watch the on-demand session “What’s new: Non-deductible and partly deductible VAT” at the latest Business Central launch event. Register and watch here: https://aka.ms/BCLE.

Not yet a Dynamics 365 Business Central customer? Take a tour and get a free trial.

The post Non-deductible VAT coming to Dynamics 365 Business Central worldwide appeared first on Microsoft Dynamics 365 Blog.

Intrastat is the system the European Union (EU) uses to collect statistics on the trade in goods among EU member nations. Microsoft Dynamics 365 Business Central customers that operate in the EU can use the Intrastat Report to meet their monthly reporting requirements. With 2022 release wave 2 of Business Central, we’re introducing a redesigned Intrastat reporting experience with extended features. Here’s what you need to know.

Test in a sandbox first

The new experience is disabled by default. You’ll need to enable it on the Feature Management page in Business Central. We suggest you enable and test it in a sandbox environment with a copy of your production data first. Once you activate the new user experience in your production environment, you can’t go back to the old Intrastat functionality.

New Intrastat reporting experience

The old Intrastat Report was based on journals. In the new report, you’ll see a list of entries, and when you create a new Intrastat Report, it opens on the document page.

Additionally, Intrastat reporting is no longer part of the base application, but is now an extension.

Enhanced functionality

• Data Exchange Framework for reporting. Almost all EU countries require a file for reporting. Previously we created a hardcoded file. Now we use the Data Exchange Framework, and you can easily create timestamped files for export. We include prepared formats for countries for which we have localizations. You can change the out-of-box report or make your own, especially if we don’t have a localization for your country.

• Configurable Checklist Report. After you fill in the Intrastat Report, you can run a configurable Checklist Report to make sure the information you entered is correct, and that all fields you indicated are mandatory have been entered.
• Fixed asset reporting. You can also include fixed assets in your report.
• Weight and supplementary unit management. For both goods and fixed assets, you can easily configure the weight and supplementary unit of measure and, if needed, recalculate weights and supplementary units without changing any other values.
• Manual corrections. You can manually correct your lines, and edited lines are indicated.
• More report configuration options. The new Intrastat Report configuration has more options, and you can also adjust your reporting in the Data Exchange Definition settings. You can set file export preferences, default values, which country will be the base for reporting, how to treat VAT numbers, and more.
• Service Declaration is coming soon as a separate app. Service Declaration, or Intrastat for Services, will be available in November 2022 as a separate app. Business Central will report services that come from the purchase and sale of items configured as services, resources, and item charges.

Technical information

• Now modularized and open source. With the new Intrastat application, the Business Central development team continues to apply the strategy of modularizing the common application layer (base application). At the same time, we’re providing more capabilities for partners to contribute by making both the Intrastat app and report formats open source.

• Developed for extensibility. The central part of the design is the Intrastat core app. The app allows a partner to define business in two ways:
  • Use the app logic with the report format exposed through the Data Exchange Framework to generate the report
  • For a heavily customized solution, define logic through the standard report configuration on the VAT Report Configuration page (suggest lines, content, response handler, and validation object)
    
    To support extensibility, the app has 47 integration events. If you need to submit more than that, use the standard process.
• Customizable formats. After receiving many requests to allow easier report format modifications, we decided to expose the format through the Data Exchange Framework to support text and XML files. Microsoft will continue to provide changes in accordance with local market law requirements, but users may customize the format and keep their own version of the format definition. The Intrastat core application will have a common format defined in DataExchDefMap.xml in the AppResources folder.
• Country formats. The Intrastat core extension supports all countries and follows the existing Intrastat logic. For several countries, the required Intrastat format is significantly different. Microsoft is releasing country-specific apps, which will be developed on top of the Intrastat core app. Both Intrastat core and country apps will be preinstalled by default but must be enabled in Feature Management. Developers can choose to develop their solution on top of a common application layer, the Intrastat common application, or an Intrastat country app.
• Open-source app. Our goal is to open the source code completely, both the app code and report formats. The formats will be exposed as Data Exchange Framework schema and shared through GitHub. Like other first-party apps, the app code will be available on GitHub at ALAppExtensions/Apps/W1 at main · microsoft/ALAppExtensions (github.com).

When will the new Intrastat reporting experience be available?

The new Intrastat experience is available starting in October 2022 with 2022 release wave 2 for all countries using the W1 version and country apps for Austria, Spain, and Sweden. Other country-based apps for Microsoft localizations only will be available in November 2022. Service Declaration will be available as an additional app in the same release starting in November.

For EU countries without Microsoft localization

What if you’re in an EU country where Microsoft doesn’t provide localization? In that case, partners can start by adding country-based features on top of the Intrastat core app as soon as the W1 version is available.

If you see some obstacles in this process, please contact us. Our intention was not to create a new Intrastat only for Microsoft localizations, but to create a solution that our partners can easily extend to meet local requirements.

Action needed

You should transition to the new Intrastat app soon. The existing Intrastat functionality will be supported until 2023 release wave 2 to provide enough time for a smooth transition. However, we encourage Business Central customers to move to the new Intrastat app before then.

Important notes:

• Existing Intrastat functionality is being deprecated. The Intrastat objects in the base application (27 in total) will be tagged for obsoletion and will be available until 2023 release wave 2.
• The transition process is one-directional. Once you move to the new Intrastat app, users will not be able to return to the old experience.
• No data will be transferred in the transition.
• There is no overlap between the existing and new Intrastat objects, so there is no risk of data corruption.
• Users who try to access existing Intrastat pages will be redirected to the new experience.
• To modify the assisted setup, use the following setting:
  [EventSubscriber(ObjectType::Codeunit, Codeunit::"Feature Management Facade", 'OnAfterFeatureEnableConfirmed', '', true, true)]

Learn more

For more information about the new Intrastat reporting experience, read the documentation:

Work with Intrastat Reporting – Business Central | Microsoft Learn

Set Up Intrastat Reporting – Business Central | Microsoft Learn

Learn about more globalization features in Dynamics 365: Reduce complexity across global operations with Dynamics 365 – Microsoft Dynamics 365 Blog

New to Dynamics 365 Business Central? Try it for free.

The post Intrastat reporting redesigned in Dynamics 365 Business Central appeared first on Microsoft Dynamics 365 Blog.