What’s New in Microsoft Dynamics 365 Finance

The latest Microsoft Dynamics 365 Finance update brings key improvements, including features that are new, changed or enhanced, designed to make financial processes faster, more accurate, and easier to manage. All this will be available on the following schedule:

 

• Preview of release: October 2025
• General availability of release (self-update): December 2025
• General availability of release (auto-update): February 2026

 

New or Changed Features

 

A number of new and changed features have been introduced to simplify finance workflows and enhance overall efficiency.

 

Accounts Receivable

 

• Faster Global Transaction Page— Optimized performance for large datasets, allowing quicker lookups and smoother navigation.
• Structured QR-Bill Addresses (Switzerland)— Supports structured “S-type” addresses for both biller and debtor, improving accuracy and compliance in Swiss billing.

 

Fixed Assets

 

• Stable Acquisition Proposals— Recurring batch jobs for asset acquisitions now continue even if older journals are deleted, preventing interruptions.
• Consistent Asset Naming— Asset names from purchase orders remain intact; new details are added without overwriting existing data.
• Accurate Transaction Timing— Inventory sold transactions now post at the correct time for cleaner and more reliable financial tracking.
• (Preview) Intercompany Asset Transfers— A new data entity streamlines transfers between legal entities, helping organizations automate asset management.

 

Subscription Billing

 

• Optimized Batch Processing— Reduced a significant amount of chattiness in batch process.
• Faster Invoice Posting— Billing schedule invoices now post using multithreaded batch processing, allowing multiple invoices to be processed in parallel for significantly faster execution.
• (Preview) Parallel Deferral Recognition— Enhanced the subscription billing deferral recognition batch process by processing deferral data in parallel, allowing each run to complete more efficiently.

 

Enhanced Features

 

Several improvements have been made to refine existing processes, making daily finance tasks smoother and more reliable.

 

Accounts Receivable

 

• Free Text Invoice— Corrects posted invoice totals to include all line amounts, ensuring consistent reporting.
• Case Management Visibility— Invoice and Invoice line details information now appear on the Associations FastTab on My cases.

 

Credit & Collections

 

• Interest Note Flexibility— Users can now view and select the option for the Due Date and the Terms of Payment when posting a customer interest note.
• Smarter Collection Emails— Email template on the collection process automation uses the variables on the Subject line.
• Faster Interest Note Creation— Uses top-picking optimization when creating customer interest notes, to speed up processing for large transaction volumes.

 

General Ledger

 

• Account Reconciliation Agent (Production Preview)— Now provides suggested actions for In ledger not in subledger and In subledger not in ledger exception types.
• User ID Visibility in Settlements— The Ledger Settlement Inquiry page now shows the user ID that did the settlement for full audit transparency.
• Ledger Settlement Performance— The Ledger settlements page has been updated to improve the performance, although customizations may need to be updated to work with the new page.

 

Subscription Billing

 

• Automatic Discount Groups— Discount group setup in trade agreement for item prices now automatically applies to the billing schedule when created for the corresponding customer record.
• (Preview) Deferral COGS Dashboard— Dashboard monitors for visibility into deferral adjustment errors with rerun capability.
• (Preview) Process Completion Notifications— A notification message is displayed when the asynchronous process finishes so that the user is notified.
• Consistent Credit Note Exchange Rates— At the termination of billing schedule, a credit note is created against the invoices (sales orders) with the same exchange rate used at the time of invoicing.

 

Take the Next Step with AXM365

 

Ready to unlock the full potential of Microsoft Dynamics 365 Finance?

 

AXM365 helps businesses implement, optimize, and modernize their ERP systems, ensuring finance and operations teams work smarter, not harder.

Microsoft 365 Copilot: Role-Based AI Empowering Sales, Service, and Finance Teams

Microsoft takes Copilot to the next level — empowering sales, service, and finance teams with AI built for their roles.

 

The latest Microsoft 365 update introduces role-based Copilot experiences that go far beyond general productivity assistance. Sales reps, service agents, and finance professionals now get context-aware, data-connected tools that work directly within Outlook, Teams, Excel, and Dynamics 365 — transforming how work happens.

 

Sales

 

For sales teams, Copilot integrates seamlessly with leading CRM systems such as Dynamics 365 and Salesforce, providing quick access to opportunity details, customer communications, and company insights.

 

It helps sellers prepare for meetings, track deal status, identify risks, and manage CRM records more efficiently—all within their daily tools like Microsoft Teams, Outlook, and Copilot.

 

Service

 

The AI-powered service solution enables customer service teams to quickly generate case summaries, draft personalized response emails, and update CRM records seamlessly, all while managing rising customer expectations, increasing workloads, and fragmented toolsets.

 

Fewer clicks and faster responses allow teams to resolve issues more efficiently while maintaining high-quality, personalized customer interactions.

 

Finance

 

The AI-powered finance solution helps finance teams work more efficiently on complex tasks, like checking transactions and reviewing financial differences.

 

 

 

By bringing ERP-connected data from tools like Dynamics 365 and SAP directly into Copilot, Excel, and Outlook, teams can quickly draft customer emails with account details, speed up transaction reconciliation, flag discrepancies, prepare reports, and perform variance analysis.

 

It also helps clean, reshape, and structure ERP exports into analysis-ready reports, saving time on manual work. This allows finance professionals to focus on making informed decisions that support business growth and keep operations running smoothly.

 

 

Why It Matters

 

Overall, these role-based AI capabilities enable sales, service, and finance professionals to work smarter and faster with AI-powered insights and automation embedded right where work happens.

 

With these updates, Microsoft positions businesses to move toward what it calls “Frontier Firms” — organizations that embed AI into their core operations. The result? Less time on manual work and more time driving strategic impact.

 

Starting October 2025, these solutions will be available to help organizations scale AI adoption and accelerate productivity across key business operations.

 

Discover How AXM365 Can Support Your Implementation

 

AXM365 guides your Microsoft 365 Copilot implementation. Get in touch to improve workflows, drive productivity, and implement AI solutions designed for your business.

Partner Alert: Microsoft 365 Copilot Licensing Updates

The latest Microsoft 365 Copilot updates bring zero-rating and role-based enhancements, adding value by simplifying licensing. Existing users can now access additional features at no extra cost, with role-based capabilities for Sales, Service, and Finance fully included in Microsoft 365 Copilot.

 

Copilot Studio Value Updates

 

The update began by broadening the range of agents and features covered under the Microsoft 365 license. From now on, all Copilot Studio capabilities—including agent flows, AI tools, and deep reasoning—are available within Microsoft 365 Copilot for agents running under a licensed user’s identity.

Key Updates:

• Included Usage for Internal Scenarios

When Copilot Studio agents are used in business-to-employee (B2E) contexts by a licensed Microsoft 365 Copilot user, the activity is now fully covered under the Microsoft 365 Copilot User Subscription License (USL).

 

• Full Feature Set Coverage

Agent flows, AI tools, and deep reasoning are now part of the license.

 

• Copilot Credits as Payment

In scenarios like B2C, unlicensed Microsoft 365 Copilot users will still be charged through Copilot Credits (formerly known as “messages”).

 

• Streamlined Copilot Studio Positioning

Copilot Studio now distinguishes between two creation paths with simplified naming for the agent-building experiences:

 

• • Lite (formerly known as Agent Builders): built into Microsoft 365 Copilot for information workers;
  • Full: designed for makers and developers.

 

Both sit under Copilot Studio but serve different types of users.

 

Role-based Copilots Update

 

Microsoft 365 licensed users will gain access to role-based solutions for Sales, Service, and Finance, without requiring additional step-up SKUs. These solutions integrate with CRM and ERP systems, delivering relevant insights directly within Microsoft 365 Copilot and core apps like Outlook, Teams, and Excel.

Key Updates:

• Depending on their needs, licensed Microsoft 365 Copilot users can install sales, service, and finance solutions directly from the Agent Store.

 

Sales roles gain a complete view of opportunities, receive insights, and can ask questions—all from a personalized home page to stay prepared for customer meetings.

 

Service teams can enhance the customer experience by integrating CRM data directly with Outlook or Teams.

 

Finance teams can manage tasks, improve data preparation, review account details by accessing ERP-connected information directly within Excel and Outlook.

 

• More Value with Microsoft 365 Copilot

Users can now take full advantage of role-based capabilities in Copilot for Sales, Service, and Finance as part of their existing Copilot license, simplifying access and enhancing efficiency.

 

• Role-based Solutions

 

Microsoft 365 Copilot now includes role-based solutions for Sales, Service, and Finance, enabling customers to purchase a full suite of features that boost efficiency and streamline workflows.

 

Maximize Your Microsoft 365 Investment

 

AXM365 guides you through seamless implementation. Reach out today to transform your workflows and explore tailored solutions for your business.

We Are Microsoft FastTrack Portfolio Partner

AXM365  has been officially recognised as a Microsoft FastTrack Portfolio Partner, joining a select group of global partners acknowledged for their consistent delivery of high-impact Dynamics 365 solutions and alignment with Microsoft’s Success by Design framework.

 

This recognition is awarded to partners who demonstrate excellence in project execution, a strong commitment to customer success, and the ability to scale solutions across industries and geographies. It reflects our strategic focus on cloud-first, AI-enabled business transformation and our ability to deliver measurable outcomes through innovation and collaboration.

 

As a FastTrack Portfolio Partner, AXM365:

 

• Operate with a global Centre of Excellence mindset, ensuring consistency and best practices across engagements
• Collaborate closely with Microsoft engineering and FastTrack teams to accelerate solution delivery
• Support clients in adopting AI-driven and cloud-native technologies with confidence and clarity

 

This recognition strengthens our position as a trusted advisor in the Microsoft ecosystem and reinforces our commitment to helping organisations modernise operations, enhance customer experiences, and unlock new value through technology.

‘View Details’ Button Does Not Work on EDT Fields Used in Forms Displaying Records from Customized Tables

In previous versions of Microsoft Dynamics AX, table relationships could be defined in the Application object tree under the Relations node of either an EDT node or a specific table node.

 

Starting with Microsoft Dynamics AX 2012, the use of relations on EDT is obsolete and should be deleted in its future versions.

 

All table relations defined under an EDT should be migrated since they should be defined on tables only. If this is not done correctly, the ‘View details’ option can be unavailable for EDT fields used in forms displaying records from customized tables. This problem might occur even though the ReferenceTable property on the EDT is set to some table and this EDT matches the type of the primary index from the corresponding reference table.

 

Our team came to a different possible solution to this problem, which is explained in the text below:

 

Firstly, you need to create a self-relation in the table whose primary index matches the EDT.

 

 

Another option is to create a hidden menu item button, which opens the main form of the data from the table whose primary index matches the given EDT.

 

Next, on the grid displaying the records from this table set this button as a default action. ‘View button’ option will appear on right-clicking the first field in the grid.

 

It is important to note that this is not the best solution since this works only on forms containing a grid with the corresponding table set as the main data source.

 

If you want to use this field from the same table in other forms, the ‘View details’ button won’t be shown again, unless the previously mentioned conditions are fulfilled. This approach is used in the Sales agreements list page.

 

 

Zero Cost Price on Purchase Line Inventory Transactions

One of our clients experienced the following issue: Posting a purchase order invoice resulted in an inventory transaction with zero cost.

 

However, the postings in the General ledger were correct. The stock valuation model was Weighted average date. The AX version is AX2012, R2, CU7.

 

We went trough the execution of the invoice posting and noticed that the cost price calculation is based on the accounting distributions. The logic takes into account all distributions on the line with the same financial dimensions as the PO line. In our case these are different.

 

We assume this is because the PO is created from a PRQ. The accounting distribution has the same dimension as the PRQ line while the PO line dimensions are blank.

 

The cost price calculation starts in InventCostInputAmount class, getInputAmountFromDistribution method where the ledger dimension selection criteria is defined based on the purchase line. Then actual calculation is implemented in SourceDocumentLineProvider class. getDistributedAmountInAccountingCurrency method where AccountingDistribution entries are selected based on the previously defined ledger dimension combination.

 

This seems to be a common issue since it was experienced by others as well. The proposed solution from Microsoft is the following hotfix: KB 2967526 “Deleting a financial dimension affects the distributions on a purchase order receipt, invoice vouchers and inventory costs”.

How Does ERP Improve Business Workflow?

How Does ERP Improve Business Workflow?

 

A company doesn’t need ERP software to be successful. However, it will force an organization to improve its business processes which can lead to cost savings and increased profit margins. Every company is different and has its own unique set of challenges, but most companies will face mainly the following problems:

 

• Inefficient scheduling of resources;
• Slow production cycles;
• Uncontrolled purchasing procedures;
• Inefficient materials requirement planning;
• Data inconsistencies;
• Decreasing customer loyalty;
• High overhead costs;
• Delayed financial tracking and analysis.

 

If the companies are encountering any of these problems, the business will have a negative impact at the end. In the case of experiencing some of these problems, it is more than evident that your company can benefit from investing in ERP software.

 

ERP software can help define best practices, optimize activities and help you regain control over your processes. By streamlining operations and providing business process automation, ERP software improves the accuracy of information and accelerates data flow, helping free up the employees to focus on more complex issues that require personalized attention. As a result, productivity is dramatically increased and operating and overhead costs are dramatically reduced.

 

1. ERP Software Improves Visibility

 

Through a singular base, ERP software organizes the data essential to the business. It provides visibility to all the systems and processes and integrates them so all employees have access to the information they need, when they need it, to do their jobs more efficiently.

 

Storing company information in one common database makes it easier to manage and share information among key individuals within the company. Employees often use their own spreadsheets and databases to perform their jobs and, as a result, the other people in the organization find it difficult to obtain the information they need in a format they can use.

 

By implementing a single, unifying system, ERP software, you create a common “language” throughout the company that simplifies communication and makes it easier to understand and share important information.

 

2. ERP Software Streamlines Operations

 

Business processes and activities have become increasingly complex, requiring multiple teams and divisions to operate as a single, cohesive unit on a single project. Without an ERP software, creating that kind of cross-departmental coordination and workflow execution can be very challenging and very time consuming, which means quite costly.

 

ERP software helps companies streamline their business processes in the following ways:

 

Eliminating Data Entry errors

 

Data redundancy, besides being time consuming, increases the chances to make a mistake when entering the same data in multiple places. Once data has been entered into an ERP system it automatically updates the data throughout the entire system, ensuring that employees have access to the same and most up-to- date information with the click of a button.

 

Enhancing Workflow

 

ERP software helps companies improve efficiency by providing a way to standardize work sequences throughout all processes.

 

Providing Consistent Directions

 

Companies with employees who have easy access to work documentation see production errors go down and quality go up. ERP software gives employees the ability to document work steps and processes. That way other employees know how to perform the work on a consistent basis, keeping quality on a standardized level.

 

Collaborating with Suppliers, Customers and Remote Employees

 

The ERP software gives you the ability to connect with your business partners as well. Each member of your staff can log on to the ERP software wherever they are located acquiring crucial information in order to give an outstanding performance. Certain partners can also gain remote access to the information they need around the clock.

 

Working with Multiple Languages and Business Rules

 

For companies who operate globally, ERP software gives them the ability to document directions in multiple languages and adapt the procedures to local practices.

 

Effective ERP software is crucial to a company’s success because of its ability to manage the business across all departments in real time. Most of the processes consume both time and money. To be profitable and competitive, businesses must streamline operations across all departments, including automating critical yet routine activities, standardizing their speed and quality as much as possible.

 

With lots of enterprise resource planning solution available, you might wonder which is the perfect one for you. Talk with Axapta Masters’ experts to find out. 

Sales Order XX Has Been Updated by Another User – Packing Slip Posting

The error message “Sales order XX has been updated by another user.” is a standard error message when user tries to update (post document) against a sales order but in the mean time another user already did updated the same order.

 

In general, AX captures the quantities remaining when posting parameter form opens and check if these values are the same when posting executed. In case of a change, the error message appears.

 

This is a safety mechanism that prevents updating the same lines and quantities more times. However this error message can also be a result of customization.

 

One of my clients asked for a customization in packing slip grouping/splitting. Standard AX offers a setup for this but is some cases this setup does not fit the customer needs. In such a case SalesFormLetterParmData classes need to be customized. I did changed the ParmData class to meet the customer requirements. Everything was working just fine until we got the error message “Sales order XX has been updated by another user.”

 

At first I thought that multiple users tried to update the same order at the same time since we experienced this in test environment. But very soon I figured out that it was not updated by another user because the order was not updated at all.

 

Investigating the problem, I found out that one sales order line was part of multiple packing slips. This was the origin of the problem. When Packing slip update function called AX creates SalesParmLine records for each SalesLine that need to be updated. Besides other information like ItemId, InventTransId, quantities etc. AX also copies remaining quantities from SalesLine into SalesParmLine table. This information is stored into the following fields:

 

• RemainBefore
• RemainBeforeInvent
• RemainBeforeInventPhysical
• RemainAfter
• RemainAfterInvent

 

In case when one sales line is split between multiple packing slips that should be posted in one go (same ParmIdI there is an issue. The first packing slip goes well without any issues and this action reduces the Remain fields on SalesLine. When second packing slip goes trough the validation process AX finds out that the Remain values on SalesLine and SalesParmLine differ and “Sales order XX has been updated by another user.” error message appears.

 

In order to avoid this Remain field on the SalesParmLines need to be maintained. For example, sales line has quantity 10 where 7 goes to first packing slip and 3 goes to second one. The second SalesParmLine record need to have Remain quantities reduced by 7. This way AX will validate that the remain quantity is 3 (which is correct) and will proceed with the posting.

 

The validation for remain quantities is executed twice, once when Parm form displayed and once when user clicks on OK button (when posting trough code or in batch is only once). Before form opening both SalesParmRecords must have the same values because they are compared with the original SalesLine. For the second check, after OK click, we need to udate Remain quantities. This is important because we need to change the values after prompt method on SalesFormLetter class, but before run method.

 

Another attention point are the units of measurement. The Remain fields that contain “Invent” in the name store quantities in inventory unit while the rest in sales unit. If these are different then inventory unit conversion is needed in order to calculate the inventory remain fields.

Problem with Vendor Settlement – SpecTrans Issue

One of my clients reported an issue that the settlement is not possible for vendor transactions (Accounts payable > Common > All vendors > Tab: Invoice > Settle open transactions). The records were marked with red exclamation and when the user try to mark the record gets the an error message:

 

“This transaction has been marked for settlement by another user.”

 

This error message is very clear and when I saw it I said that someone else already marked the transaction for settlement. The interesting part came when they said that they are sure that this is not correct.

 

Using the Specifications form (Inquires > Specifications) I tried to find the transaction that was marked against. The result was no transaction in the specification form.

 

On the other side the “Is marked” column shows that there is a related transaction.

 

This column is actually a display method that use SpecTrans table to decide if the transaction is already marked.

 

Select firstonly crossCompany RecId from specTrans where

(specTrans.SpecCompany != specCompany ||
specTrans.SpecTableId != specTableId ||
specTrans.SpecRecId != specRecId) &&
specTrans.RefCompany == _refCompany &&
specTrans.RefTableId == _refTableId &&
specTrans.RefRecId == _refRecId;

 

(Ref fields consist the relationship with Vendor open transaction in our case – VendOpenTrans)

 

This findings suggested that there is data inconsistency.

 

I created a simple job to find the marked lines that are inconsistent:

 

static void findMarkedTrans(Args _args)
{
VendTransOpen VendTransOpen;
SpecTrans     specTrans;
while select VendTransOpen
where VendTransOpen.AccountNum == ‘VendAccount’
join specTrans
where specTrans.RefRecId == VendTransOpen.RecId
&&    specTrans.RefTableId == tableNum(VendTransOpen)
&&    specTrans.RefCompany == ‘DataAreaId’
{
info(strFmt(‘%1 %2 %3’, specTrans.SpecCompany, tableId2name(specTrans.SpecTableId), specTrans.SpecRecId));
}
}

 

Using the Spec field I found out the records that marked those transactions. Then I just open the table I got from the job (in my case LedgerJournalTrans) and filtered by Record ID. As you assume, there we no data!

 

If you check the documentation for the SpecTrans table you can see that the description is “The SpecTrans table contains records that relate to transactions for the settlement and settlement reversal processes. Records are deleted after they are processed.” So, in this case SpecTrans table was not “cleaned up” properly.

 

Cleaning up the SpecTrans table from inconsistent records resolved the issue.

 

It is hard to say what is the reason for this issue. Probably it was an AOS crush during the time of posting. Unfortunately this happens sometimes and the consequences can be much bigger.

 

I experienced a case where the AOS crush caused to be impossible to post vendor invoices. The solution in this case was pretty similar, clean up a “temporary table”.

 

Another one resulted in even worse situation. The inventory transactions (Invoiced lines) and the postings in the ledger were not inconsistent.