Dynamics 365 Finance

In the context of multiple VAT registrations, a lot of our customers which have several VAT numbers in different countries must declare single transactions in 2 countries simultaneously.

However, it’s not currently possible.

Example: a Belgian company has 2 VAT numbers : a Belgian VAT number and a Netherlands VAT number. The company makes a sale with its NL VAT number.

The base and VAT must go on the NL VAT declaration > OK, it works fine with the multi VAT registration in D365. But the base must also be declared on the BE VAT declaration (box 47 - exempt sale). > Not possible.

Our request is to be able to declare transactions in 2 countries simultaneously because we are getting more and more requests for this.

Currently, when transferring to a Pending Vendor Invoice in D365, the Invoice will be created using the Due Date that was read in Invoice Capture.

We need the Invoice's Due Date in D365 to be calculated based on the Payment Terms which were negotiated with the Vendor, so either taking them from the PO or from the Vendor itself in case of non-PO.

It could be a configurable option.

Thank you!

The legal entity override functionality concept is to have different attribute other than the default attribute of the (Main account or the Financial dimension).

This concept should also apply to the "Suspended" option, for instance if I wish to "Suspend" a specific FD value for all legal entities (80+ Legal entities) except for only 1 legal entity , I should be able to do so.

Currently, it's not allowing me to do so, whenever a FD is suspended, this attribute cannot be overriden for a specific legal entity becuase it's dimmed.

I have noticed that the same behavior is happening with the Active from/to date, once it's defined on the main level it cannot be overriden,

In Business Central using the SBS module from Binary you have the ability to create a Subscription Billing Schedule from a Sales Quote or Order. This functionality does not exist in D365 Finance.

Customers often want to create a Sales Order or Quote then create the Subscription off the initial order. Customers today need to perform redundant data entry or change their integration to import into both SO and SBS.

There needs to have the ability to place Deferral Schedules on hold in bulk using Data Entities import And Periodic Tasks. Similar to the process for Billing Schedules. During implementation of ARED many clients want to place migrated schedules at cutover on hold as they reconcile the data. Clients today need to pay for a customization in order to do place on hold or remove hold in bulk. The only other option is to place individual schedules on hold/remove hold. If a clients has thousands of deferral schedules this is cumbersome.

Description :

A new annuity model where interest calculation should occur at the beginning of the period and on the beginning balance .

Why it is needed:

Current financial systems support ordinary annuity and annuity due structures,but there is a gap when it comes to scenarios where interest must be applied upfront before any reduction in balance.Some fianncial contracts particulary in leasing ,require interest to be earned on the beginning balance at the start of the perid.

At the moment if you pay the second schedule line payment of the leasing and also the second line of the lease liability amortization schedule and then update the book version, the new book version shows a mismatch between the two schedules. The logic of the Lease Liability Amortization schedule will have to replicate the same logic of Payment Schedule.

Ref: https://msdyneng.visualstudio.com/FinOps/_workitems/edit/987997.

• What is the business impact to the customer? How does the problem impact their business? (Ability to bill, revenue loss, sales etc.). 

• “Duplicate button names (Approve, Reject and Request change) create confusion for users, making difficult to determine the correct action to take during the workflow approvals and the duplicate button names create an unprofessional and inconsistent user interface, which reflects poorly on system’s design and usability. Management has expressed concerns the reliability of the system and potentially undermining confidence in the system’s ability.”

Troubleshooting Steps (please include screenshots / do you have a VMAS machine to share?)

Issue description with customer perspective

When the customer attempts to approve a workflow in the Trial environment, they observe duplicate pop-ups when hovering over the 'Approve,' 'Reject,' or 'Request Change' options, as shown in the screenshot. I have checked our vanilla environment and observed the same behavior. We informed the customer that this is standard behavior, but they believe it might be a bug. 

With Repro Steps

Steps to reproduce

Repro Steps:

>> workspaces>> Invoices >> Pending vendor invoices assigned to me

After selecting any standard workflow 

While hovering over "Approve" or "Reject," the help text appears twice — the first in bold and the second in regular font.

Customer is in below version we have checked in 10.0.40

EXPECTED BEHAVIOR:

The customer expects the help text to either appear only once or not be displayed at all.

In the Subscription Billing module of Dynamics 365 Finance, there is a limitation in how the system calculates the deferral start date.

Scenario:

When a billing schedule is created for the period 13th Jan 2024 to 12th Jan 2025, the system currently starts the deferral from 13th Jan 2024, matching the billing start date.

However, based on the commonly used 15-day accounting rule, the deferral should instead start from 1st Jan 2024, since the billing start date (13th Jan) falls within the first 15 days of the month. This rule is widely used in revenue recognition where, if billing starts in the first half of the month, revenue is recognized from the beginning of that month.

While the system correctly handles cases where billing starts after the 15th (deferral starts from the next month), it does not apply the same logic for dates within the first 15 days — and it does not allow any configuration or automation to support this.

We are currently implementing D365 Finance using the Tax calculation service to manage complex Tax scenarios for a large Retailer. This has resulted in the configuration of thousands of lines. Making it difficult to trace back the source of the calculation, ideally D365 tracks the version and applicable rule(s) to each tax document so the accountants can validate the transactions and users have a audit trail. In case Tax calculations rules change overtime with new versions etc.