Dynamics 365 Finance

When classifying the invoices in Invoice Capture you select the Legal Entity, Vendor and the Invoice Type. When searching for the Vendor account system applies “exact” match.

A more flexible search option will be more efficient in case you don’t know the exact name. Request is to enable more flexible search option for “contains”, “begins with” etc. These options are available in most other modules of D365 Finance.

For the form "Batch job history" I would suggest a new field: "Duration".

The intention is to clearly see how long batch jobs actually were running. Batch jobs that have been running for a long time could need to be examined.

The field "Duration" should display the time the batch job ran. Calculated by the formula: "End date/time" - "Actual start date/time".

At present, the system generates umbrella error messages that are generic and often not meaningful to end users, which complicates the troubleshooting process.

For example:

• “The selected report can’t be found. Make sure the report hasn’t been deleted, or work with your administrator to find the correct report. The report exists, but its data is missing. [An internal error occurred in the provider. An error occurred connecting to the source system.]
• <“Exception has been thrown by the target of an invocation.”, “The remote server returned an error: (404) Not found.”>”

In one actual scenario, this error message occurs when there has been a change to operational data, such as a legal entity name change, which was not reflected in the financial report design (specifically the Reporting Tree definition). However, the current error message does not point users to the specific data they need to check, which prolongs the troubleshooting process and negatively impacts user productivity.

This becomes especially problematic in time-sensitive situations, where users need to generate a large number of reports quickly to avoid penalties. The lack of clarity in error messages leads to unnecessary delays and business impact.

To address this, we propose implementing more detailed and user-friendly error messages that can guide users directly to the issue, enabling them to identify and resolve problems more efficiently. Clearer messages would ultimately improve the user experience, reduce troubleshooting time, and mitigate potential business.

For example, when the legal entity name has been changed in the main system and the change has not been updated accordingly to the financial reporting tree, there should be an error like: "The report cannot be generated. Check the Reporting tree definition."

In D365 Finance, when the standard Mexican Localization is enabled, the Journal Voucher form displays the required field to specify the UUID value for each line (CFDIUUID_MX). However, when using the Excel Add-In to Read/Write over the LedgerJournalTable this field is not available.

This prevents the UUID field from being modified in bulk and quickly through the corresponding data entity, increasing user operation times by requiring them to manually specify this field for each line created, and leading to possible errors.

Suggested Improvement to Timesheet Functionality

The current process of entering timesheets using the “hours by time” method is unnecessarily complex and inefficient. It requires users to click through multiple layers of windows—each step triggering another pop-up—resulting in a fragmented and confusing workflow. This design makes it difficult to maintain a clear view of how each entry relates to the overall timesheet, increasing the likelihood of errors. There should be multiple intuitive ways to input hours, not just a single path buried under layers of interaction.

Additionally, the system allows for the entire timesheet to be deleted with a single mistaken click, without any warning or confirmation. This is particularly concerning given that there's no “Undo” option available. Mistakes are inevitable in any system, and without a safeguard such as a confirmation prompt or undo feature, users risk losing an entire timesheet unintentionally—potentially after hours of data entry.

Implementing a more user-friendly, flexible interface along with basic safety features like an “Undo” button or deletion confirmation would significantly improve usability and reduce frustration.

Currently, the Excel Add-in for Dynamics 365 Finance and Operations is only available for Excel on Windows. This limitation prevents users on macOS from accessing critical data integration and publishing features directly from Excel. Given the large number of professionals using Mac devices, it would be highly valuable to have a cross-platform version of the add-in.

We suggest Microsoft develop a version of the Excel Add-in based on the Office.js framework or another cross-platform technology, making it compatible with Excel for Mac and Excel Online. This would greatly enhance productivity and accessibility for teams working in diverse operating system environments.

Please consider adding support for macOS to ensure a more inclusive and flexible user experience across all platforms.

Create and post a Free text invoice (export invoice) with a foreign customer

Open the export invoice print copy –

Actual result:

Total invoice value (figure) is not equal to ‘Grand total’ amount

Grand total amount not showing in words

Total invoice value (words) – One Thousand and Zero Paise

Expected results:

Total invoice value (figure) should be equal as shown in ‘Grand total’ amount

Grand total amount should be shown in Words as well

Total invoice value (words) – One Thousand Dollar and Zero Cent

(Note – Should show words with currency as used in Export invoice, if export invoice posted in different currency same currency should be updated)

HI- it would be nice to know if a customer is prepay status just by pulling up the customer initially and if maybe the font was italicized, or their name was highlighted in a particular color. This would make it easier when researching a payment, we received and not having to go into the sales order or quote to understand where the payment is coming from. TIA

Currently in Microsoft Dynamics 365 Finance, there isn’t a single out-of-the-box report that directly combines all the specific details such as the Withholding Tax (WHT) settlement voucher, settlement date, and WHT transactions—in one prebuilt format. We would like to have a standard report that includes all the details for improved reporting purposes.

Currently, the "Financial Tags" functionality does not correctly handle "SalesTax" lines in invoice journals where there are general ledger lines associated with item sales tax groups linked to non-deductible sales tax codes.

When the journal contains multiple lines with item sales tax groups related to non-deductible sales tax codes, the system correctly splits these VAT lines into:

• Deductible sales tax lines: The account associated is the one linked to the posting profile.
• Non-deductible sales tax lines: The account associated is the one related to the original cost line.

The problem is that for the non-deductible sales tax lines that are posted to the same account as the original cost line, the financial tag information is assigned randomly by the system, choosing one of the financial tags and assigning the same tag to all lines.

Example:

Let's assume that only the cost center financial dimension is required (CC1/CC2).

Item sales tax group 22ND50 means that 50% is not deductible.

AMOUNT ITEM SALE TAX GROUP FIN TAG LEDGERDIMENSION

VENDOR 2000 F000001

GENERALLEDGER 1000 22ND50 X 4000001-CC1

GENERAL LEDGER 1000 22ND50 Y 4000001-CC2

In this case the voucher will be:

                        AMOUNT FIN TAG

F000001 2440

4000001-CC1 1000 X

4000001-CC1 110 X (THIS IS THE NON DEDUCTIBLE TAX LINE)

2000001-CC1 110 X (THIS IS THE SALES TAX LINE)

4000001-CC2 1000 Y

4000001-CC2 110 X (THIS IS THE NON DEDUCTIBLE TAX LINE)

2000002-CC2 110 X (THIS IS THE NON DEDUCTIBLE TAX LINE)

That's not correct because If I want to analyse the balance of FIN TAG "X" it will be wrong and also for the FIN TAG "Y".

The correct voucher must be:

                        AMOUNT FIN TAG

F000001 2440

4000001-CC1 1000 X

4000001-CC1 110 X (THIS IS THE NON DEDUCTIBLE TAX LINE)

2000001-CC1 110 X (THIS IS THE SALES TAX LINE)

4000001-CC2 1000 Y

4000001-CC2 110 Y (THIS IS THE NON DEDUCTIBLE TAX LINE)

2000002-CC2 110 Y (THIS IS THE NON DEDUCTIBLE TAX LINE)

In this case as you can see the correct FIN TAG is correctly splitted in the correct sales tax lines.