The first reconciliation copilot automations focus on reconciling subledgers to the general ledger balances. SSRS reports will be a thing of the past, and will be replaced with a near-real time process that proactively notifies the finance team of any reconciliation issues. Upon recognition of an issue, Copilot identifies the mismatched transactions, and provides a solution. That solution may be changing a setting on the main account (such as don't allow manual entry) or may recognize when a posting profile has changed, causing a different balance sheet account to be used for reconciliation. An audit trail will be maintained when issues are identified, along with the solution. Copilot will learn from the solutions of the past, and move toward automatic resolution to any reconciliation issues (longer-term vision). Again, it's all tracked with an audit trail for actions taken by Copilot.

The first releases will focus on a subset of subledgers: accounts payable, accounts receivable, tax, and bank. Additional subledgers, such as fixed assets and inventory, will be added in future releases.

The central immersive homepage for AP clerks contains:

• Overall status of autonomous invoice processing.
• Daily work summary for the AP clerk.
• AI-guided worklist for AP clerk: list of invoices with exceptions, list of invoices for approval.
• Various insight reports.

The new Document explorer workspace enhances document management with these powerful capabilities:

• Natural language document search.
• Document search across legal entities.
• End-to-end document relationship views.

In public preview, the following modules and documents are supported:

• Accounts Payable: Purchase orders, product receipts, vendor invoices, vendor payments.
• Accounts Receivable: Sales orders, packing slips, customer invoices, customer payments.
• Cash and Bank Management: Bank statements.

The Asset book page now includes a Summary by Copilot FastTab that summarizes the currently selected asset book and shows status on the asset historical transactions and insights about the asset future.

Copilot offers an overview of fixed assets, including acquisition dates, service dates, and initial acquisition costs. It summarizes acquisition adjustments, write-ups/downs, and total accumulated depreciation, calculating the net book value (NBV). Additionally, it provides future-focused insights, such as remaining depreciation periods, upcoming depreciation periods reminders, and disposal considerations based on the asset book's depreciation method and service life.

Receipt matching errors could occur for multiple reasons such as if the receipt is not logged by the warehouse manager or the vendor has not yet delivered goods to the customer or the goods are in transit.

Copilot is integrated in the pending vendor invoice list, enabling AP clerks to select a vendor invoice with an error, analyze in the invoice, and correct the error in a single location.

In future releases, Copilot will help with corrections around failed prepayments and workflow submission errors.

Currently, when a purchase order is posted incorrectly, accounts payable clerks must follow several time-consuming steps to rectify the issue. These include adding a negative quantity line, posting a product receipt, creating and posting a credit note, adding a third line to the purchase order, posting the receipt again, and finally posting the correct invoice.

To streamline this process, the new feature automatically reverses a posted purchase order invoice and resets the purchase order status. Depending on the product receipt status, the purchase status will revert to either Ordered or Received. However, if the subsequent process after purchase order invoice posting occurs, such as settlement, financial period-end activities, or cost revaluation, the reversal will be blocked.

Copilot can assist AP clerks in identifying and rectifying various invoice errors, including receipt matching errors, prepayment application error, workflow submission error, accounting distributions, duplicate invoice number, invalid bank account errors, and more.

Advanced bank reconciliation in Dynamics 365 Finance helps businesses manage this process more efficiently. In the Cancel customer payment journals from bank reconciliation worksheet feature, the existing reconciliation functionality is enhanced with an option to cancel customer payment journals directly from the bank reconciliation worksheet.

Within this feature, the existing bank reconciliation statement report in advanced bank reconciliation is updated with the following enhancements:

• Redesigned report body to include details about trading party, trading party name, and type.
• Report body to include voucher and voucher description.

The first reconciliation automations focus on reconciling subledgers to the general ledger balances. SSRS reports will be a thing of the past, and are replaced with a near-real time process that proactively notifies the finance team of any reconciliation issues. Upon recognition of an issue, each transaction provides numerous options for possible solutions. That solution may be changing a setting on the main account (such as don't allow manual entry) or may recognize when a posting profile has changed, causing a different balance sheet account to be used for reconciliation. An audit trail will be maintained when issues are identified, along with the solution.

The first public preview included the subledger-to-ledger reconciliation automation but it did not include recommendations by the Account reconciliation agent for how to address exceptions. The second public preview will introduce the agent functionality for recommending the action to take to address the exception for individual transactions. Copilot will learn from the solutions of the past, and move toward automatic resolution to any reconciliation issues (longer-term vision). Again, it's all tracked with an audit trail for actions taken by Copilot.

This feature provides additional legal entity bank account lifecycle management capabilities in Dynamics 365 Finance:

• Approval workflow for bank account activation, modification, and deactivation.
• Configurable protected fields to determine whether bank account modification needs approval.
• Approver can review proposed changes on bank account.
• Bank account change history for auditing purposes.
• Additional signer master data on bank account.

The existing advanced bank reconciliation feature is enhanced to support generation of a single vendor payment journal for multiple vendor payment lines during the bank reconciliation process. The functionality will allow users to determine the posting for the journal:

• A single payment journal per reconciliation worksheet
• A single payment journal per bank reconciliation rule
• A single payment journal for selected lines

The primary focus of this release is creating a new set of financial journals using the new journal framework. For this wave, we'll begin by focusing on the architecture of a new journal framework. During this phase, we are taking into consideration the goodness of the current journals while also addressing the challenges faced by finance users. For the first release of the new journal framework, we will introduce a new general journal that supports the following:

• Ledger account adjustments only (for phase 1).
• Exponentially better performance for the end-to-end process of importing, validation, and posting of vouchers/journals.
• Importing and manual entry of vouchers for multiple companies within a single journal. For example, you can create a journal and enter transactions for USMF and USSI without creating a new journal and signing in/out. This will be limited to legal entities based on your security access.
• Move processing down to the voucher level. Validation, approvals, and posting can be initiated at the journal level still, but the processing will be done at the voucher level.
• Introduction of a 'Voucher type' that is used to identify what type of transaction is being entered. This allows for better lifecycle control of each type of transaction.
• New entities for both Odata and DMF for the new general journal.

As the new journal framework is finalized, all financial journals will continue to evolve as follows:

• Add support for the additional account types (vendor, customer, assets, project, bank, and so on) to the general journal.
• Evaluate all other journals and determine how to create a new version of those journals using the new journal framework.
• Improve the reversal experience for all voucher types.
• Reevaluate existing functionality such as how accrual entries are posted or how periodic journal/voucher templates work.
• Address the data model issues to fix the One voucher issues.
• Evaluate the addition of new journals such as a bank transfer journal.

As new journals are introduced with the new journal framework, they will be communicated with new release plan features.

User security governance is a set of advanced features that provide useful tools to system administrators for role management, license auditing, enhanced audit trails, and versioning, supported with some useful reports around license usage and separation of duties violations.

The Preview automatic bank reconciliation matching results feature includes the following:

• Matching rule simulation.
• Matching preview and option to update bank reconciliation results.
• Ability to select matching rules that should be manually reviewed before posting results during reconciliation process.
• Pending review screen for user to investigate matching results.
• Option to review bank reconciliation matching exceptions.

Key improvements include the ability to identify the source (from) asset and destination (to) asset, select either spot or historical exchange rates for reporting currency, and preview fields that display asset values before and after the split in accounting and reporting currencies. Users can split assets by amount or percentage. A new Fixed asset split list page offers a detailed audit trail, and the feature supports split updates across legal entities.

The Fixed asset inter-company transfer allows users to transfer assets between legal entities by selecting the source asset and its book, previewing key financial details such as acquisition cost, accumulated depreciation, and net book value (NBV). The transfer can be processed as disposal. Users can choose to either create the destination asset automatically or select precreated assets. The feature copies asset data to the destination entity, allows previewing of destination values, and automates the posting of acquisition in the destination asset and disposal transactions in the source asset.

The solution for enhanced budget control management in Dynamics 365 Finance offers the option to select multiple account structures during budget control configuration. The solution introduces flexibility and enhances process flow for customers who are using multiple account structures in their organization.

Planned improvements in this area allow more precise budget control on various levels, as well as enhanced reporting opportunities. Budget control for multiple account structures in Dynamics 365 Finance include the following capabilities:

• Option to select several account structures during budget control configuration.
• Allow budget dimension rule flexibility.
• Improved budget control reporting.

The existing advanced bank reconciliation matching rule data entity is enhanced with the following functions:

• Option to upload 1-to-many and many-to-1 matching rules.
• Support all matching types.
• Support upload of various matching criterias and conditions.

Financial tags are already introduced into some inquiry pages, such as the Voucher transactions page. This feature will introduce the financial tags into the Accounting source explorer inquiry within Finance.

In addition, we will also add the financial tags to the data model for Record to Report within Business performance analytics, making them available as dimensions for analysis.

The current accounting source explorer page in Dynamics 365 Finance is a key tool for accounting personnel to view financial transactions. The current limitation to view data from one company or legal entity at a time causes a great deal of wasted time switching to each company and reloading the data into the accounting source explorer page.

This update to the accounting source explorer will allow exporting of transactional data quickly and easily for the selected companies. The ability to export data from multiple companies to Excel will also let the accounting team do deeper analysis across companies.

The key change for this feature will be an improved export option that will allow the user to select which companies they want to export data from along with the other existing filter options in the accounting source explorer.

We continue to extend the scope of the supported countries in LATAM to address the needs of multiple global and local customers. Out-of-the box localization for Dominican Republic is available. While the country localization will provide the following capabilities, not all of them might be available for preview.

Country-specific features for Dominican Republic

• Invoicing

  • Electronic Invoicing
    • Electronic Invoice format
  • Other invoicing
    • Invoice layout for sales order invoice, free text invoice, and project invoice

• Reporting

  • General ledger and tax reports
    • Declaration reports general ledger
    • Declaration reports trial balance
    • File export Report with Purchases of Goods and Services to issue Report 606
    • File export Report with the Sales of Goods and Services to issue Report 607
    • File export Report with voided receipts to issue report 608

We continue to extend the scope of the supported countries in LATAM to address the needs of multiple global and local customers. Out-of-the box localization for Peru is available. While the country localization will provide the following capabilities, not all of them might be available for preview.

Country-specific features for Peru

• Invoicing

  • Electronic Invoicing
    • Electronic Invoice format
  • Other invoicing
    • Invoice layout for sales order invoice, free text invoice, and project invoice

• Reporting

  • General ledger and tax reports
    • Declaration Reports Cash and Bank Ledger
    • Declaration Reports General Ledger
    • Declaration Reports Trial Balance
    • Declaration Reports Purchases Register Report
    • Declaration Reports Sales Register Report
    • File export Annual declaration of operations with third parties (DAOT): Purchases and Sales
    • File export Electronic Journal Book
    • File export Electronic Ledger
    • File export Electronic Purchase Book
    • File export Electronic Sales Book
    • File export Withholdings File - SUNAT

Electronic invoicing is the primary billing model in Mexico, where it is used in 100% of commercial transactions. This system has become a tool to improve fiscal control and mitigate high evasion rates. Countries such as Mexico have dedicated laws to ensure the authenticity of these documents via authorized trust service providers, who act like electronic notaries, stamping documents and applying electronic time seals to guarantee their long-term integrity and legal weight.

The e-invoice in Mexico, known as the CFDI (Comprobante Fiscal Digital por Internet), is well established throughout Mexican society. Created in 2004, it has been subject to updates and changes over the years to ensure a better user experience for taxpayers and to correct issues detected over time. Issuers must digitally sign all invoices using a unique system that involves the encryption of the "original string" data made up of a series of characters extracted from defined fields. An additional electronic signature, called a "Stamp" must be generated by an SAT-accredited (Servicio de Administración Tributaria, the Tax administration Service) third-party trust service provider called a PAC (Proveedores autorizados de certificación, an authorized digital signature service provider), after the invoice content and structure has been validated. The PAC stamp makes the document valid for tax purposes. All tax receipts must be stamped by a PAC, which then reports the document to the SAT online. The SAT will subsequently make it available to the issuer and recipient in their respective tax mailbox.

Microsoft Dynamics 365 Finance supports out-of-the-box integration with Interfactura PAC web services, a key player in Mexico’s electronic invoicing system. This integration is essential for the certification of the CFDI electronic invoice document, a system that is integral to Mexico’s commercial transactions.

In the absence of the publication of the technical regulation governing the new electronic invoicing system in Spain, the law provides for the following obligations in the private sector that will be satisfied with this feature:

• Ability to issue, send, and receive electronic invoices.
• Inform the status of invoices.
• Guarantee possibility to exchange electronic invoices between technological solutions or platforms.
• Ability to access, view, import, and visualize the electronic invoice for the recipients.

Microsoft has released the Guatemalan electronic invoicing feature of the last-mile integration with the Guatemalan Tax Authorities via the Certification Authorization Provider Edicom. It covers the required end-to-end process of the outbound flow of e-invoices submission.

In addition to the Globalization feature update, the functionality also contains code changes in Microsoft Dynamics 365 Finance. The electronic invoicing Globalization feature for Guatemala (outbound flow) requires that you use Dynamics 365 Finance version 10.0.40, build number 10.0.1935.60 or later.

This feature can only be imported into the new Globalization Studio and isn't supported by Regulatory Configuration Service (RCS).

Microsoft has released the Uruguayan electronic invoicing feature of the last-mile integration with the Uruguayan Tax Authorities via the Certification Authorization Provider Edicom. It covers the required end-to-end process of the outbound flow of e-invoices submission.

In addition to the globalization feature update, the functionality also contains code changes in Microsoft Dynamics 365 Finance. The electronic invoicing globalization feature for Uruguay (outbound flow) requires that you use Dynamics 365 Finance version 10.0.40, build number 10.0.1935.60 or later.

This feature can only be imported into the new Globalization Studio and isn't supported by Regulatory Configuration Service (RCS).

When you configure ER destinations for business documents in Microsoft Excel format, the conversion performs outside the current Finance instance by default. You can enable the Utilize application resources to perform CBD documents conversion from Excel to PDF format feature to convert generated Word documents to PDF format locally by using application server resources in the current Finance instance.

We continue to extend the scope of the supported countries to address the needs of multiple global and local customers. Out-of-the box localization for Republic of Türkiye is available. The country localization indicated below is provisional and may change prior to general availability. Additionally, not all of the following capabilities might be available for preview.

• Exchange rate import from CBRT.
• Continuous serial numbers for invoices and packing slips.
• Currency conversion in purchase and sales orders.
• Exchange rate difference invoices.
• Electronic invoice generation and submission.
• Cheque and promissory note enhancements.
• Pro-rata depreciation of fixed assets and depreciation rounding per year.
• Inflation adjustments.
• E-Ledger generation and submission.

In a legal entity with the Support multiple VAT registration numbers feature enabled, you can generate VAT Declaration, EU Sales List, and Intrastat reports. A list of supported countries and tax regulatory reports is available at Reporting for multiple VAT registrations.

For this release, we plan to extend the list of supported countries and tax regulatory reports. We plan to release EU Sales List correction for Poland (VAT_UEK) with support of multiple VAT registration numbers.

The following capabilities are planned for JPK_KR_PD reporting:

• Adding an option to define main accounts markers (S_12) using Financial Dimensions and report trial balance (ZOiS) section based on dedicated dimension set including main account and the markers.
• Adding an option to report the journal entry number (D_1) using Journalizing journals.
• Adding an option to report the date of the economic transaction (D_6) for vendor invoices using the Date of Vendor VAT Register field.
• Adding the report Settlement of income tax section (RPD).
• Adding Microsoft Excel format to preview the data.

When you enable the Security enhancements in UK MTD VAT integration feature, UK MTD VAT TEST and UK MTD VAT electronic message processing automatically updates to enhance the security of your Dynamics 365 Finance integration for direct VAT return submissions for your UK VAT registration.

The following Web service actions have been changed to Executable class:

• Retrieve VAT obligations
• Test retrieve VAT obligations
• Submit VAT return
• Test submit VAT return
• Request VAT liabilities
• Request VAT payments

Microsoft has released the Bolivian electronic invoicing feature of the integration with the Bolivian Tax Authorities. This feature can only be imported into the new Globalization Studio and isn't supported in Regulatory Configuration Service (RCS).

We are introducing the automated tax calculation feature based on the core tax master data available in the legal entity through Tax Data Migration.

This function eases the migration of the core tax master data to our more advanced tax calculation engine, automatically adding necessary new records to ensure a complete and accurate data transfer. The auto-created tax feature will be generated based on the existing tax codes, sales tax groups, and item sales tax groups of the current legal entity.

This feature aims to comply with the Belgium-specific requirements for enforcing electronic invoicing for business-to-business communications starting January 1, 2026.

You can communicate invoices and credit notes created from sales orders, free text invoices, or project invoices in the PEPPOL-based XML format that complies with the Belgian electronic invoicing standards.

Poland is introducing legislation to establish the continuous transaction control (CTC) system. The Polish CTC system, called Krajowy System of e-Faktur (KSeF), was made available for all taxpayers in 2022 for voluntary adoption.

To comply with these legal requirements, the following functionality is implemented and available as public preview: Electronic invoicing for Poland

• Generation of XML files of Sales, Project, and Advance electronic invoices in the legally required format provided by KSeF.
• Automatic submission of generated electronic invoices to KSeF.
• Import of incoming Vendor electronic invoices issued and available for recipients on the KSeF platform.

The legal requirements are not fully finalized yet. As of now, the KSeF system will be rolled out as mandatory, in phases, depending on a company's size, following this implementation timeline:

• February 1, 2026, for large taxpayers (over PLN 200 million per annum).
• April 1, 2026, for all taxpayers.

This feature satisfies the Denmark-specific requirements for implementing OIOUBL format version 3.0. You can export invoices and credit notes created from sales orders, free text invoices, or project invoice proposals into XML format that complies with the updated Danish electronic invoicing standards.

OIOUBL 3 Invoice Package Postponed - Revised Schedule:

The Danish Business Authority expects the OIOUBL 3 invoice package to be upgraded from Release Candidate to Final Release in mid-May 2025.

After that, it's expected to be voluntarily implemented until mid-November 2025, when support for OIOUBL 3 is to be made mandatory in Nemhandel.

End-of-life for OIOUBL 2.1 is expected in mid-May 2026.