Dynamics 365 Finance

The current functionality for importing electronic invoices, available since September 2024, does not cover cases where the lines of the e-invoice do not have an external item code but only a purchase category or a description of a service as free text (e.g., ticket purchases, utility payments, hotel accommodation services, etc.).This prevents it from being used by companies that do not work with the inventory module and, for example, use only the invoice journal for recording incoming invoices.

In many European countries, there is an active process of transitioning to electronic document exchange, and from 2025, e-invoices will account for more than 70% for many companies.

Please expand the capabilities of the current electronic invoice import functionality and include e-invoices in the upcoming updates for the Invoice Capture functionality.

Since the price model of Dynamics shifts to a capacity model, the storage cost of database tables becomes more and more important. Dynamics has quite some tables for which no cleanup functionality exists, but can grow large in size and thus become very expensive.

Some of the tables are marked as internal in the application, so it is also impossible to create cleanup jobs yourselve.

Examples of such tables are DIMENSIONDATAINTEGRITYLOG and DIMENSIONHASHMESSAGELOG.

When you are using financial dimensions on a detailed level (in our case, per project) these tables can grow very large (50+ GB).

• DIMENSIONDATAINTEGRITYLOG: The "DIMENSIONDATAINTEGRITYLOG" table serves as an integrity log, documenting changes and identifying issues. While it is not crucial for the regular operation of the system, it proves beneficial for troubleshooting. Truncating this table is optional. If you choose to do so, please note that it won't impact the system's immediate functionality. However, retaining the data can aid in resolving potential dimension-related problems in the future.
• DIMENSIONHASHMESSAGELOG: The "DIMENSIONHASHMESSAGELOG" table is dedicated to storing hash calculations for each dimension set and combination. Similar to the integrity log, it is not essential for the system's day-to-day functionality. Truncating this table is at your discretion. Removing this data won't cause immediate issues but keeping it could expedite the resolution of dimension-related problems that may arise later.

Although the data stored in the table is not crucial for the application, Microsoft does not want to cleanup the tables. We thus are requesting integration of this "troubleshooting data" in the long term data archival functionality or a cleanup option to remove older entries of this tables.

There are more examples of this kind of tables in other areas of the application (MCRORDERLINE2PRICEHISTORYREF, ERFormatMappingRunJobTable,...)

TrackingID#2409250030005349 - Expense Report - Approving/Rejecting multiple expense lines

Current - Expense report approved at header level

To approve at the line level - each line needs to be sent for approval. Impact > approver receives multiple (many) lines in Work items assigned to me.

Future - One expense report > Approve/Reject each line within the expense report, post expense report, not individual lines

Collection Process Automation will not send pre-dunning emails till oldest previous invoices get paid. We need a function option for user to send pre-dunning emails to all overdue invoices regardless of the payment status of oldest invoices. Or to avoid sending multiple emails for each overdue invoice, we can include them all in one pre-dunning email.

Often we use tax codes marked as use tax to incur a duty expense on a purchase order because the duty invoice is received separately and settled against the accrued ledger balance.

However, when posting a product receipt, Dynamics 365 does not create the accounting events for use tax posting even though the accounting distribution has been generated correctly.

I would like to see the account distribution being posted correctly like non-use tax.

Due to the critical nature of the Workflow process, we have created a batch job for Workflow messaging and assigned a priority of Reserved Capacity.

However when the batch processing tasks are run they are created with Priority = Normal, so they are not prioritised above other tasks/jobs.

Requirement is for batch tasks to take the priority from the parent?

When sales orders are created with empty shipping on CE without freight amount, they get integrated successfully to FnO without a problem. However, when customers try to edit and add freight amount, an error is produced that "shipping site is mandatory." When this was escalated to PG, they provided the explanation below:

This is by design.  

When customer create sales order line in CE and sync to F&O, the site and warehouse will automatically set in F&O (maybe from sales order header), but the site and warehouse are still blank in CE(since customer hasn't set), when a new sales order line update request send to F&O, the blank site and warehouse sent to F&O, it is not allowed to update site and warehouse to blank in F&O. 

Customer can use button "Price Order" on sales order header to sync F&O data(including site and warehouse) back to CE and then do other updates. 

The logic to set default value for warehouse and site on sales order line is different from F&O and CE. 

In CE, no default logic for warehouse and site. In F&O, it is complicated, it is based on default order setting on item, warehouse and site on sales order header. 

We don't have information about default order setting on item in CE, so we cannot add same default logic in CE like F&O. 

The suggested idea is to adjust the way integration works the same way with freight amount added.

MS has developed Electronic reports for Colombia Magnetic media.

But when intercompany transactions are performed these are not included in the LATAM Tables/records hence, they are not included in these reports.

The suggestion is to include intercompany transactions like Customer invoices and vendor invoices to be part of the fiscal reports.

the exclusion of this was confirmed by MS on ticket 2402200040008302

Hi,

There is one field missing on the XML output file when sending a sales invoice electronically to Chorus Pro portal in France. On a sales invoice header, the field "Customer reference" is compulsory to be sent to Chorus Pro as part of the rest of the invoice details for some customers or scenarios. On Chorus Pro portal, this is linked to "Commitment number" or in French version "Numero d'engagement".

After raising a ticket with MS, we have been told that the missing field is recognised and MS has the same output, however we are apparently the only customer asking for this so far and it will need a design change, the suggestion is for us to go ahead and do the change ourselves.

Chorus Pro invoice submissions will be mandatory soon for many businesses and I am sure more clients will request the same. I would be very helpful if MS could include the field on the template as well and any customer could benefit of it.

Thanks for understanding and please go ahead and vote for it,

Regards,

Elena

Currently users are able to add notes at the customer level, and in conjunction with the "Copy notes when transferring to sales order" Accounts receivable parameter, have those notes flow automatically to the sales order. However, if notes are added for an address setup for a customer, those notes do not flow to the sales order. Many customers can have multiple locations as "ship to" locations that have different requirements, so a single note at the customer level would not suffice. Without an improvement in this area, users would need to access the customer account, then go to the address setup to see the note added there, and then manually copy to the order (leading to mistakes and missed notes)