Dynamics 365 Finance

When a lease is adjusted, the commencement date is automatically changed to the adjusted value.

In the lease details page you cannot see anymore the original start date, so you must open the older versions of the book to verify it.

We suggest a design change to keep the historical commencement date and see the adjusted value in an extra field e.g. "Lease modification date".

Thanks in advance for your attention.

Camilla

User downloaded the "General journal line entry" Open in excel template in General journal > Journal entries > General journals, added the Invoice field , saved the template as a new file. Then in Common > Office integration > Document template, Created a new one and uploaded the saved file.

Upon trying to perform again the Open in excel, the new template appeared, but would override the original template, we cannot keep the new template with default template appear in the same time. but follow the Blog https://exploredynamics365.home.blog/2020/10/18/design-your-own-open-in-excel-template-in-microsoft-dynamics-365-finance-and-operations/, seems previous D365 version had the function that can keep both new and original template on the system. Could we have re-design or back to this function?

The fields in EU sales list form:

• Item value
• Service value
• investment value

should be also be controlled by Sales tax code.

Currently, it is only controlled by the Item tax group. However, there are business scenarios (especially in construction business) with the need of specifing the type of value by Sales tax code.

In the project management and accounting module, when creating a project invoice, it should be possible to combine sending both the PDF as well as the eInvoice XML through print management settings.

Currently, the print management settings enable automatic sending of the PDF upon posting of the project invoice.

To send the eInvoice XML, the "send" button needs to be used, creating a manual step for every outgoing invoice.

This creates a lot of additional manual work for the business, as well as creating the risk to forget clicking the send button to create (mandatory) eInvoices.

The requested functionality is already live from a Sales Order & Free Text Invoice perspective in the AR module.

Currently, in the PMA print management forms, the electronic report can't be attached as a report format, creating the complication.

By extending the functionality in the current AR print destination forms towards the PMA module, the problem should be resolved.

In many business scenarios, users need to cancel a customer invoice due to billing or accounting errors, but without reopening the associated packing slip.

Currently, in standard D365 Finance & Supply Chain Management, when canceling a posted invoice, the system automatically affects the packing slip — reversing the shipment — even when there is no physical change to the delivered goods.

This creates unnecessary operational complexity and confusion in logistics tracking, especially when:

• The goods were already physically delivered and must remain “Delivered”.
• The cancellation is purely financial (for example, incorrect price, wrong tax code, or invoice issued on the wrong date).

Requested enhancement:

Add an option (parameter or dialog checkbox) to:

“Cancel posted invoice only — do not reopen or reverse packing slip.”

The system should then:

• Create the reversal (credit note) for the invoice only.
• Keep the delivery status unchanged (Delivered).
• Prevent re-processing of the shipment.

Business impact:

This feature will improve audit control, simplify accounting corrections, and align with real-world logistics flows where financial and physical processes are decoupled.

Currently, the due date for credit notes is based on the payment terms defined on the customer's account. This can result in credit notes not appearing on collection or reminder letters until several weeks after they are posted, even though the credit is immediately applicable.

I propose enhancing the system to allow credit notes to be handled separately and assigned their own due date logic. This would make it possible for credit notes to appear on collection letters immediately, while invoices continue to follow standard payment terms (e.g., 30 days). This change would improve customer communication and streamline the collections process.

The system should ensure that the default description is automatically applied to payment lines created through the payment proposal process. Currently, this default description is not applied when the method of payment’s period is set to any value other than “Invoice.

For example, in Vendor balance list, in the criteria when choosing more than one value in order to filter the values, the 2 values are collapsed, they are not separated automatically. they can only be separated by a Coma or by using different other Seperators by design. This requirement might feel inconvenient for users, especially if they are trying to get things done quickly.

example for what happens: if we need to filter 2 values ‘401000’ & ‘401200’

When selecting the first value 401000 and then selecting a 2nd value profile without add ‘comma’ between them, the new value is pasted to the previous value without delimiter: “401000401200” 

which ends up with The search is unsuccessful,

We would like to request that the Ireland VAT localisation is configured as standard OOTB, particularly the Ireland VAT report in Electronic Reporting.

Currently, when the OOB commission structure is setup for the US localization, the only option is to record the commission at the time of invoice. As company policies vary, some will record the commission at the time of customer payment of the outstanding invoice, to ensure they are not paying out commission prior to receiving payment from the customer. This is not currently an option in the US localization, however, it is available for Italy https://learn.microsoft.com/en-us/dynamics365/finance/localizations/emea-ita-exil-commission-settlement. It would be nice to be able to leverage this functionality across other localizations within the MS community.