Dynamics 365 Finance

Description:

Customer generated the depreciation proposal process filtering by fixed asset, filtered only two fixed assets (both had the same fixed asset group) and activated the batch processing button, but the system generated the depreciation journal with more fixed assets than the two selected.

Actual Outcome:

Depreciation proposal journal is showing the interval between the two selected fixed assets. You can see other fixed assets unfiltered in the proposal (depreciation journal).

e.g. Fixed Assets in the Proposal process with active batch= BUIL-000002, BUIL-000006

Fixed Assets in the depreciation journal = BUIL-000002, BUIL-000003, BUIL-000004, BUIL-000005 & BUIL-000006.

Expected Outcome:

Have the depreciation journal only with the fixed assets filtered in the Proposal depreciation.

As of now the functionality is catering to exclude/include all the charges ( billable and non-billable ) from the TCS/TDS calculations on Sale order. But certain requirement arises where the billable charges should be included for the TCS calculations and non-billable should not be considered, although non-billable charges are getting deducted while calculating TCS.

There is the new function „Allow multiple posting groups” which allows to change the customer /vendor posting group in purchase and sales documents. I would suggest that the Gen. Business Posting Group should be editable as well, because if it is possible to change the VAT Business Posting Group it is necessary to change the Sales Account as well. Please reopen the “Gen. Business Posting” with the function “Allow multiple posting groups” again.

I have a requirement form a client to be able to run the Relevant Contract Tax (RCT) report in their Irish legal entity and they have an issue as the Irish localisation does not bring functionality related to this report.

This report is the equivalent to what the CIS (Construction Industry Scheme) is for HMRC in UK.

Do you know if there is a way to enable this or if D365 F&O does not support this Irish tax report at all?

I have also seen that Ireland is not a supporting country by Tax Calculation, but this issue is more related to the tax localization functionality in Finance really rather than the Tax Calculation.

If you could provide some insight here, it would be much appreciated.

Regards,

ESM

Concerns have been raised by customers using this feature, they state that according to the Lithuanian tax legal framework, a single sales tax code should be usable for two fields in the VAT declaration (LT) report.  Currently this isn't possible to do on the format and they believe it should be corrected, to comply with the Lithuanian tax authority requirements.

Currently, when the OOB commission structure is setup for the US localization, the only option is to record the commission at the time of invoice. As company policies vary, some will record the commission at the time of customer payment of the outstanding invoice, to ensure they are not paying out commission prior to receiving payment from the customer. This is not currently an option in the US localization, however, it is available for Italy https://learn.microsoft.com/en-us/dynamics365/finance/localizations/emea-ita-exil-commission-settlement. It would be nice to be able to leverage this functionality across other localizations within the MS community.

In the default dashboard, when the user searching the legal entity with name, the query taking the search word as began. That is when the user enters the word, application is searching with starting of the legal entity, instead of this it should search anywhere on the same filed. Below is the scenario

1. In default dashboard if the user searches for the CNMF legal entity with the name as China(the full name of the CNMF is - Contoso Entertainment China).
2. Its not fetching the required legal entity since the search work is not the starting of the name.
3. If the user enters the starting word then its fetching the legal entity.

If dual write is enabled and you utilize the "change party association" functionality within Finance and Operations and change the party from an "organization type" party to a "person type" party, data corruption occurs within the Dataverse.

Expected behaviour:

After changing the party association, the "Account" record in Dataverse should be disabled or deleted. A new "Contact" record should be created to represent the new person-type customer. Consideration needs to be made about how the existing linked content in Dataverse is handled - if there's existing cases, etc. we'd likely need those migrated to the new association!

Actual behaviour:

The "Account" record representing the customer as an organization remains intact. This record cannot be edited or deleted - a dual write exception is encountered.

When saving a view on a report the filters used in the report should be saved as part of the view. This would make it easy to share queries used on reports among users.

When saving the view on a report none of the set-up is currentlv saved