Dynamics 365 Finance

A request to have foreign currency revaluation enabled for polish legal entities since it would streamline lots of business processes and help improve overall functionality and save time.

For Poland accountancy in D365 there is FIFO revaluation run every month to recalculate bank funds in foreign currency. Our customer besides that have requirement to recalculate balances in standard way for group reporting purposes. Unfortunately standard functionality is disabled for polish localization. Recalculation is made with different exchange rate and with different method than Poland currency revaluation. It is done at month end, reported in group consolidation tool. Then reversed at beginning of next period.

1. Parameter "Require manual matching with advance bank reconciliation find multiple documents that match on amount" is set to yes. The bank statement has transaction code 195 and two lines for the same amount of 2500 dated 01-Jul-23, but the D365 bank transaction has one line for of 2500 dated 01-Jul-23. A bank reconciliation rule is created where the bank statement line transaction code is 195 and in bank transactions, it will match with amount and date. Here, D365 is randomly matching one statement line amount of 2500 with a bank transaction line amount of 2500. D365 should stop matching if statement find two/more lines with same amount, as it could match the wrong statement line with the wrong transaction line.
2. Many customers use BAI2 statements or other statements as provided by their bank which does not mention its a reversal transaction. For the reversed transactions in the bank statement, the imported statement from BAI2 format in D365 does not enable the Reversal field. It is not possible to clear the statement reversal transaction with the statement positive transaction manually and also by the reconciliation rules in the reconciliation worksheet. Solution is required for this issue as first step in reconciliation to clear the reversed transaction.
3. Bank transaction types should allow selecting account type (Ledger, Bank etc.) and Account. A new parameter which override the 'Allow multiple transactions within one voucher' will be applicable for this. This will allow auto creation of transaction from bank for bank to bank transfer.
4. Default description for offset account. Bank account generally entered as offset account (vendor payment journal, customer payment journal). D365 should allowed auto defualt description to be created for offset accounts as well.

Other related idea for advance bank reconciliation - https://experience.dynamics.com/ideas/idea/?ideaid=09763ae3-de7e-ee11-a81c-6045bd8043.

It should be possible to set up a body text to be used when sending a sales invoice to customers by email through print management. Because emails that are sent out now for customer invoices do not contain a body text and are thus empty, the invoice very often arrives in the junk email folder of customers.

Even more convenient would be the ability to assign an email template with a body text, a subject, possibly some placeholders, in different languages.

Due to recent product defects, Fixed Asset names are currently limited to 60 characters again. However, this limitation does not make sense in some business scenarios, particularly when the client is not using Fixed Assets as Financial Dimensions.

The previous suggestion is Microsoft Idea (dynamics.com).

This behavior results in whether receiving the items in the wrong warehouse or consumes the business time to add an extra step to check the warehouse before posting every time. 

Also, there is a financial impact due to the need to transfer the items from the wrong warehouse to the desired one.

The “send on behalf of” configuration from Exchange is not respected by Dynamics. No application should be able to bypass the rules set on the Exchange server. So for example if a user doesn’t have explicit permissions to allow it, Dynamics ignores that fact and allows users to add the account in the D365 configuration “on behalf of” field.

Anybody that have Dynamcis FO, in a tenant can cross domains send mails on behalf of anybody/any domain in the tenant.

Adding security in dynamics shouldn't be the solution, as the root of this behaviour is that Exchange must be respected.

ALL of the users (for example the admins) from different environments can send mails with no limitations. No setup is needed, only activate exchange as a option, no validation, no login or approval needed.

As per best practice from Microsoft SysAdmin is needed in D365 FO DevBoxes, and often the solution for Debugging. So a lot of accounts can send those emails.

This is a security issue, as any person can add an important account of the company as sender email and try to impersonate him. The emails even reach the real mailbox for that sender. It can lead to financial loss/scams.

We wish an improvement in the process of importing FTI lines with Project ID via Open in Excel functionality so that missing funding source is added automatically to Project contract and invoice line, when customer is used for the first time for specific project. Currently when creating free text invoice lines with Project ID via Open in excel, funding source to project contract is not created and added automatically and it is expected that user adds it manually.

Same functionality for automatically adding missing funding source to project contract is expected also if free text invoice lines are imported via Data management with entity Customer Free text invoice.

We have been having issues with the ID’s in the descriptor files.

When model B refers to model A, the system expects model A to have a lower ID than model B.

However, this is not thrown as an error during build when compiling the models. Which we need to have.

We had the following situation where we delivered a package to our customers and had to suddenly release a hotfix due to this model ID problem.

On our own environments we did not have any issues. It only became an issue when our customers had their own extensions on top of our extended objects for these models. During the build of these customization modules errors were generated.

The workaround had us generating new numbers and updating our Descriptor files so that the model id's were in the correct order.

This issue has been logged with Microsoft under #2211090050000394

Current implementation for vendor electronic invoices (https://docs.microsoft.com/en-gb/dynamics365/finance/localizations/emea-ita-vend-e-invoices) does not cover the scenario where an extra-EU vendor issues both invoices for goods and for services.

In fact, while for EU vendors, all invoices must be sent to SDI (Italian exchange system), for extra-EU vendors, only invoices for services must be sent to SDI, not invoices for goods.

EU vendors > all invoices

Extra EU vendors > only services invoices

The idea is for a flag with the same logic of the Boolean field labelled eInvoice register in vendor master data on VAT codes, released products, and (optionally) on vendor invoice header.

This will be activated with three flag on Product information management parameters (released products), general ledger parameters (VAT codes), AP parameters (vendor invoice header).

If activated, it will override the same flag on vendor master data.

Alternatively, a new GER version of Vendor Invoice (IT) using certain criteria to exclude extra-EU invoices for goods will be good enough.

The new feature https://docs.microsoft.com/en-us/dynamics365-release-plan/2021wave2/finance-operations/dynamics365-finance/prevent-automatic-one-voucher-usage-fixed-assets

now prevents the ability to summarize depreciation journals when posting to the General ledger. Previously, journals would be summarized by account (Depreciation Expense) and financial dimension. This occurs despite setting the journal name to post in summary and/or the depreciation proposal to run in summary. In our example, we have 67,000+ fixed assets, so the depreciation proposal produces 67K+ lines to post to the ledger. Prior to this feature, we would have had ~20 lines.