Dynamics 365 Finance

'Bulk editing in grids' is a feature On by default in 10.0.44. 

We request that this feature is never made mandatory as a user could inadvertently incorrectly mass update a grid, causing operational stop for the company and a major clean up issue. 

This feature should never be forced on clients and ideally Disabled by default, so clients have to directly opt-in.

Currently, it is not possible to recognize multiple Purchase Orders within the same invoice that is read by Invoice capture.

Within a business, it can often happen that suppliers can send one invoice combining multiple Purchase Orders.

Hence, instead of having an automated way to capture the vendor invoices, the business has to manually review the invoices and assign the right PO on each line of the PO invoice before transferring to F&O.

This has a big impact on the purpose of Invoice capture and the automation of the process to facilitate the business processes of the Finance team.

The recognization of multi PO within one invoice would be then very appreciated.

When we have a tax combination " Group and group Item' with a sales tax code shared between them with a Zero Rate it throughs an error that the tax combination is not valid.

This happened because the result of the combination is Zero, so the tax code validation read the combination as a wrong one.

To resolve that we need to turn the toggle for "Check sales tax code " to None or Warning.

But this is not the best option as we need the validation when we have a wrong combination to prevent users from proceed also we need to use the Zero rate so we trace which transactions were posted using this VAT code >tracing error or missing tax transactions becomes easier.

So the suggestion would be to remove the Zero tax code form the validation as long as the setup for the sales tax code, Item and group is correct it should proceed as normal with no error. 

When adding an excel page break into a configurable business document, most customers would like the document to be converted into PDF. This is so the document cannot be amended externally.

Despite the PDF conversion being available, the page breaks do not carry across from excel into PDF. As a result, when more and more lines are added to the output document, the document font and document itself gets smaller and smaller, in an attempt to squeeze it on one page.

This is a very poor user experience and will look unprofessional in front of customers when sent out via email from D365F&O.

This really needs to rectified if more customers are to use configurable business document via electronic reporting, for a better user experience.

Background:

Currently, reversing a Free Text Invoice (FTI) in D365 Finance requires a manual workaround due to limitations in the reversal functionality. The reversal process does not generate a legally compliant credit note, particularly in terms of invoice numbering, referencing the original FTI and the reason for the reversal . This has led to increased manual effort, risk of human error, and non-compliance with EU invoicing regulations.

Customer Feedback Summary:

• The reversal function does not issue a legally correct invoice.
• Manual creation of credit notes is required, which is error-prone.
• Credit notes must have a unique invoice ID, as per EU law.
• Settlement between the original invoice and the credit note is not automatic.
• 
  

Proposed Enhancement:

Introduce a fully automated process for reversing Free Text Invoices that includes:

Legally Compliant Credit Note Generation:

• Ensure the credit note has a unique invoice ID.
• Maintain a clear reference to the original invoice.
• Automatically settle the credit note against the original invoice in the General Ledger.
• Eliminate the need for manual matching and reduce reconciliation errors.
• Provide a one-click reversal option that handles both document creation and settlement.
• Include audit trail and traceability between the original and credit note invoices.

When we generate check payment on a payment journal with multiple vendors, the current design is that the check number will be generated and assigned according to the alphabetical order of vendor names.

The generation and assignment of check number should be following the either the line number or the voucher number. This is a more logical behavior and aligns with the original design on AX2012.

Hi,

Would it be possible to have a standard form in the AP module that provides visibility on intercompany balances?

Many customers do not have intercompany automated purchase invoice posting. Therefore, having a dedicated functionality to verify intercompany balances would be highly valuable.

For example, if Company A sends an invoice to Company B, we need to ensure that the invoice has indeed been posted.

Best regards,

The requirement here is to see the work items assigned to the users in 365 Finance. We have the ‘Workflow history’ page where we can see all the workflow items using the status filter. However, it is not feasible to add the ‘UserName’ to this page or cannot filter the records on this page based on the username to whom the records are assigned for approval.

We tried adding the username to the workflow history page. However, Username or User ID is not available to be added to the page.

We also tried to add the Username or User ID column using the ‘Advanced filter or sort’ button.

We added the ‘Work items’ table and tried using the ‘User’ option but this also did not help filter the work item records that are pending with the concerned user on the Workflow history page.

Presently, the user to whom a workflow instance is assigned can be seen from the individual workflow history, but this is a time-consuming activity as these details need to be verified on each and every workflow instance individually.

The requirement is to have the details of the user, to whom the workflow instance is assigned, to be available on the Workflow history page itself.

The objective behind having this information is to enable the System administrator to identify and follow up on the pending work items or get the pending work items delegated to another user.

Description:

When the year-end close process is executed, the Trial Balance Snapshot includes year-end close entries. This behavior is unexpected, as the Trial Balance report excludes these entries.

Expected Outcome:

As observed in the Trial Balance report—where year-end close entries are not included—we expected the Trial Balance Snapshot to reflect the same behavior.

We would need to apply the process to fixed assts since we manage different books with different posting layers.

It would make the foreign currency revaluation process very flexible.

I guess could be nice to add a currency parameter called "Posting layer" to the Foreign currency revaluation form (General ledger > Periodic tasks > Foreign currency revaluation) and have the possibility to select the posting layer to be revaluate.

The exchange rate gain/loss transaction with transaction type like "Foreign currency revaluation" created has to maintain:

• the same posting layer of the original transaction revaluated
• the same financial dimension of the original transaction revaluated