Dynamics 365 Finance

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.

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

When purchase lines are marked to create new assets, and items are received and invoiced as new fixed assets, only one fixed asset is created, even if the quantity is multiple of one. The quantity invoiced certainly exists on the fixed asset, but separate fixed assets need to be followed in some scenarios, which requires dividing the fixed asset into assets of quantity = 1.

Provide the Auto split functionality for fixed assets in auto mode if the FA item contains more than 1 quantity after invoice posting  OR separate functionality/utility should be given to split the fixed asset into new child fixed asset on the basis of GRN QTY.

The idea I would like to present is to prevent the error message from appearing when attempting to post a correction with the "Credit Correction" option selected and with posting validation configured on the credit side. The error appears when, in the General ledger > Chart of accounts > Accounts > Main accounts, I configure the account used for revenue posting to allow only credit postings. Setting this validation helps ensure that the system prevents posting transactions on the debit side, which is beneficial for maintaining data integrity. Next, when I attempt to create a credit note (invoice correction), I go to the Invoice tab in the top menu, then select Cancel > Create credit note. A form appears where I select the invoice to be corrected and check the Create credit note lines option. After confirming the form with the OK button, I proceed to post the invoice with the Credit Correction option selected. przetłumacz na polski At this point, upon clicking OK, the following error message appears: "The main account on combination (general ledger account) is set up to be used only for credit transactions. You must select a main account that is set up only for debit transactions, or that has no debit or credit requirements." However, according to Polish regulations, the Credit Correction option is intended to post the correction on the same side as the original transaction. Therefore, this error is problematic, as it incorrectly suggests that the system is attempting to post on the debit side, which is not the case.

Thanks,

Regards,

Rafał

Idea Summary:

In Microsoft Dynamics 365 Finance and Operations, within the Advanced Bank Reconciliation functionality, the matching rules allow users to perform automatic actions such as "Generate Voucher." However, when using this action type, it is currently not possible to input or assign a financial tag (also known as a financial dimension tag).

Proposed Enhancement:

Extend the capabilities of the "Generate Voucher" action in reconciliation matching rules to allow users to specify a financial tag. This would ensure that vouchers generated during reconciliation are properly classified and aligned with financial reporting requirements.

Business Value:

• Improved accuracy in financial reporting through better tagging and classification of generated vouchers.
• Enhanced automation by reducing the need for manual voucher adjustments post-reconciliation.
• Consistency in financial tagging across all types of transactions, including those created automatically via reconciliation rules.

Use Case:

A company that uses financial tags extensively for internal reporting needs to ensure that all transactions, including automatically generated vouchers during bank reconciliation, carry the correct tag.

Suggested Implementation:

• Add the Financial Tag field as an editable input option when configuring the “Generate Voucher” action within the reconciliation matching rule setup.
• Ensure this tag is applied to the resulting voucher transactions.