Microsoft Dynamics 365 for Finance and Operations - Regulatory Services, Configuration service

  • Artykuł

Important

This content is archived and is not being updated. For the latest documentation, see Microsoft Dynamics 365 product documentation. For the latest release plans, see Dynamics 365 and Microsoft Power Platform release plans.

Note

These release notes describe functionality that may not have been released yet. To see when this functionality is planned to release, please review Summary of what’s new. Delivery timelines and projected functionality may change or may not ship (see Microsoft policy). For detailed information about our products, visit the Finance and Operations documentation.

The Microsoft Dynamics 365 for Finance and Operations - Regulatory Services, Configuration service is the evolution of the regulatory configuration tool (also known as Electronic Reporting). The Configuration service allows partners and customers using multiple versions of Microsoft Dynamics 365 for Finance and Operations and earlier Microsoft Dynamics AX versions (such as AX 2012 and AX 2009 for India only) to configure regulatory features only once using a common service. The Configuration service targets a no-code programming approach, allowing power users to configure frequently changed legal requirements for regulatory reports, e-invoices, payment formats and tax rules, rather than writing code in multiple applications.

The Configuration service is the first component of Regulatory Services to be released. Regulatory Services will provide functionality that can be integrated with any business application. This service allows developers building applications to focus on their core functionality rather than worrying about meeting the increasing number of legal requirements around the globe.

The Configuration service provides the following capabilities:

  • Access to visual designers to configure regulatory reports, e-invoices, payment formats, tax rules, and other regulatory features.
  • Metadata that provides the ability to either import a description of the target application’s artifacts, such as data tables, enumeration, and classes, or use connected applications for accessing metadata. Metadata is used at design time to define data sources of a data model mapping version.
  • Support for regional deployments to enable users to select what region their data is held in. There will be a limited set of countries available with the initial GA release, but these will be added to over later releases.

Regional availability

When the Configuration service is generally available, it will be available in all regions in which Finance and Operations is available. However, data will be initially hosted only in a US datacenter.

For a complete list of regions, see the Dynamics 365 International Availability Guide.