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 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 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.

Bank reconciliation is a crucial step for businesses. It involves comparing the cash balance on a company’s balance sheet to the corresponding amount on its bank statement, and identifying any discrepancies that may require accounting adjustments. This process can be time-consuming and labor-intensive, as it requires careful matching of records and generation of reports.

Advanced bank reconciliation in Dynamics 365 Finance helps businesses manage this process more efficiently. Within this feature, the existing bank reconciliation statement report in advanced bank reconciliation is redesigned with the following enhancements:

• Redesigned report header information to include amount fields: company ending balance, company unreconciled amount, company reconciled amount, bank ending balance, bank unreconciled amount, and bank reconciled amount
• Redesigned report body to include bank reconciled transactions, bank unreconciled transactions, company reconciled transactions, and company unreconciled transactions.
• Report snapshot is saved when marking the bank reconciliation worksheet as reconciled. When cash clerks run the report later, the data in the report is retrieved from the snapshot instead of the real-time transaction tables.

Bridging posting is a two-step process that is used when payments are posted. It can help ensure a smoother and more timely bank reconciliation process. In the first step, a payment is posted to a bridging account. In the second step, the posted bridging account entry is reversed and posted to the bank main account when the payment transaction clears the bank statement.

Currently, for the second step, cash clerks need to manually process it in the general ledger. This feature automates the second step by clearing the bridged transactions in advanced bank reconciliation.

This feature provides the following capabilities to automate the process:

• Define bridging posting main account by bank account.
• Select bank account for bridged payment without generating bank account transactions.
• Automatic clear bridged transactions during bank reconciliation.

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.

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.

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.

The default engine for tags allows an organization to define its own rules to default financial tags. Rules can be defined per transaction entry point (general journal, free text invoice, PO, vendor invoice journal, and so on), per financial tag and per transaction level (header, lines, account, offset account, distributions). The rules can also be written using three different options. First, natural language can be entered into Copilot, which will convert them into the technical rule. The rule can be defined with an expression builder or the technical rule itself can be entered.

Before activating a rule, they can be simulated against posted transactions to preview the results of the rule. The posted transaction isn't updated, but simply used for validation of the rule.

For the first release, defaulting rules can be created for a subset of transaction entry points, such as the general journal. Support for additional journals and documents will continue to be added with each release.

Financial tags support user-defined fields across various transactions and financial documents in procurement-to-pay processing. Organizations can create and enter up to 20 customizable fields on transactions, stored on accounting entries. When the feature is enabled, it applies to the following transactions and documents:

• Purchase order and accounting distributions on purchase orders
• Product receipt journal
• Pending vendor invoice and accounting distribution in pending vendor invoices

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.

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 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 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.

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.

Increasing the length of invoice numbers for vendors lets you extend specific extended data types based on unique business processes. Extending the data types that determine the length of vendor invoice numbers won't adversely affect other extended data types.

To try this feature, you need to ask for a flight to be turned on.

Bank reconciliation is a crucial step for businesses. It involves comparing the cash balance on a company’s balance sheet to the corresponding amount on its bank statement, and identifying any discrepancies that may require accounting adjustments. This process can be time-consuming and labor-intensive, as it requires careful matching of records and generation of reports.

Advanced bank reconciliation in Dynamics 365 Finance helps businesses manage this process more efficiently. Within this feature, the existing matching rule in advanced bank reconciliation is enhanced with the following functions:

• Automatic post voucher
• Automatic post customer payment journal
• Automatic post vendor payment journal
• Automatic settle open customer invoices with bank statement lines

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.

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.

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.

Bank reconciliation is a crucial step for businesses. It involves comparing the cash balance on a company’s balance sheet to the corresponding amount on its bank statement, and identifying any discrepancies that may require accounting adjustments. This process can be time-consuming and labor-intensive, as it requires careful matching of records and generation of reports.

Advanced bank reconciliation in Dynamics 365 Finance can help businesses manage this process more efficiently. The following functions will be available in advanced bank reconciliation to automate the cash application:

• Generate customer payment journal.

  • Automatic generation: Users can configure reconciliation matching rules to automate this. Customer international bank account number (IBAN) or bank account number can be used to match the related bank account info on a bank statement to search the customer account automatically.
  • Manual generation: Users can manually create customer payment journals from a bank reconciliation worksheet.

• Generate vendor payment journal from bank reconciliation worksheet.

  • Automatic generation: Users can configure reconciliation matching rules to automate this.
  • Manual generation: Users can manually create vendor payment journals from a bank reconciliation worksheet.

• Post voucher with redesigned user experience.

  • Automatic posting: Users can configure reconciliation matching rules to automate this.
  • Manual posting: Users can manually post GL vouchers from a bank reconciliation worksheet per bank statement line.

• Settle open customer invoices with bank statement lines.

  • Automatic settlement: Users can configure reconciliation matching rules to automate this. Bank statement lines will be matched with open customer invoices based on user-defined criteria like invoice number, sales order number, payment ID, and payment reference. The customer account is retrieved automatically from matched invoices.
  • Manual settlement: Users can manually settle open customer invoices from a bank reconciliation worksheet.

The enhanced bank reconciliation feature now includes the ability to duplicate reconciliation matching rules, making rule creation more straightforward. This also includes an option to copy related financial details defined for each rule. This enhancement ensures the reconciliation rule configuration process remains accurate while allowing users to customize duplicated rules for unique bank reconciliation scenarios. The goal is to establish an automated reconciliation process that effectively addresses various use cases.

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 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.

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.

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.

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.

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.

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 uses Application Object Server (AOS) resources to eliminate the need for external conversion services. Using these in-app capabilities ensures efficient and secure document processing to reduce dependency on tools outside of Finance while maintaining high performance and reliability. This enhancement supports a wide range of business scenarios that provide users with the flexibility to generate and distribute professional-grade PDF documents directly within the application.

The advantages of in-app PDF conversion, when the (Preview) In-App PDF conversion for Configurable Business Documents (CBD) feature is enabled, are:

• The PDF document that is produced is not limited to 300 pages.
• The Word document that is converted can contain a large number of content controls.
• Internet connectivity isn't required in on-premises deployments.

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.

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 Bolivia is available. While the country localization will provide the following capabilities, not all of them might be available for preview.

Country-specific features for Bolivia

• 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
    • Declaration reports standard VAT purchases book
    • Declaration reports standard VAT sales book
    • Declaration reports VAT purchases book - Credit and Debit Memo
    • File export Archivo DaVinci IVAT Purchases - Credit and Debit Memo
    • Declaration Reports VAT Sales Book - Credit and Debit Memo
    • File export Archivo DaVinci IVAT Sales – Credit and Debit Memo
    • File export Archivo DaVinci - VAT Purchases
    • File export Archivo DaVinci - VAT Sales
    • File export Bank Book - Purchase
    • File export Bank Book - Sales

• Tax

  • Fiscal document
    • State identification
    • CA Number

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