Dynamics 365 Finance

When pushing a personalized/published view or workspace to (multiple) users, it is not clear if the view/workspace has been succesfully pushed to all users. In the past we have noticed that sometimes views are not pushed correctly to all the users, but only to some users. A validation would be more sufficient to follow up on this.

When using "Generate voucher" in Advanced bank reconciliation, it asked user to define description for the generated transaction. However, the defined description is only applied to one voucher transaction with posting type of "Bank statement". And the other voucher transaction with posting type of "Bank" still has the auto description as "Bank statement line post table". The defined description should be applied to both voucher transactions. This causes a difficulty in managing the financial database of end users.

The parameter named "Maximum Batch Threads" on the "SysServerConfig" auto defaults to 16 ever night even if you change it. This is due to batch auto scaling (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/batch-capacity#batch-auto-scaling). Considering it can't be effectively changed by users. This should be either removed or disabled.

In many European countries, the usage of the electronic invoice feature has become mandatory for big and middle size companies in 2024, and in the short term it will be for small sized companies as well.

Hence, not only a solution to issue sales and project electronic invoices are needed (as the standard already covers) but also a functionality where the AP clerk team may manage the electronic invoices received from their vendors.

It will be really handful as well to be able to import, validate, manage and post the post those E-invoices within the vendor invoice process automation functionality that already exists, similar to the Invoice Capture + Vendor Invoice Automation functionality.

For large companies - Financial reports are often locked down by the reporting tree to limit the viewing or generating of certain reports to groups of people.

The default financial reports do not have trees to lock them down and may allow people to see data they should not have access to if they are generated since they are using the main account categories setup in the system.

This is a security issue and should be resolved immediately. Right now if you delete the default reports, they come right back after a service restart.

There is possibility in many forms to add field called created by to list view so that user can check who have actually created the record. For example in All customers form you can add created by field based on tables Global address book, People, Worker and Person name. Created by field from Global address book (DirPartyTable) shows in most of the cases the correct user id who have for example created the new customer but not always. That's why new created by field is needed at least for All customers and All vendors forms. New created by field should fetch correct user id from table location that shows the user id who have created the new record. In All customers form the correct id could be retrieved from CustTable and in All vendors form VendTable shows correct user id in created by field.

When

1. utlizing Dual Write, map Customers V3 (accounts)
2. Tax Exempt Number is set mandatory by configuration in F&O

Creation of accounts cannot be performed in CE, i e Dual Write's integrated customer master scenario is thus broken. In order to walk the talk, this issue needs resolution.

Above is due to the fact that Tax Exempt Number is a supported table that needs to be referenced in F&O, whilst it is a single field in CE. There is no ability to insert the record in the supporting table in F&O from a synchronised text field in CE

According to the Dual Write product team, above issue belongs the Accounts Receivable product team. Thus this entry.

The Spanish electronic invoice management providers want the prefix ES mandatory in the VAT number of the xml sent to them. For the management of the SII instead, the Spanish customs agency does not require the prefix in the VAT number.

By design there is only one field to manage the company's VAT number.

It requires the management of the two cases, currently managed manually.

When the Date of VAT Register functionality turned on which allows user to change the date of VAT transactions already settled, without creating a contra entry to ensure the net movement is zero.

Due to this same transaction could be settled multiple times to the VAT authorities, which is incorrect.

Expectation: System should give validation such as any notification which alerts the user when they try to change the data of VAT register for already settled and paid transactions.

WIth the "Reject duplicate" invoice number setup in the accounts payable parameters, we expected to forbide the creation of two pending invoices with the same number.

But it is not the current behaviour while one of this two invoices is not posted but on going into the workflow

So I suggested to extend the feature "Prohibit submission to workflow when the invoice number already exists on a posted invoice", to un-posted invoice also,

Thank you for taking into account this idea and voting for it,

Bests regards