Comments
Actually, I think this is an application bug because if I have one or more dimensions as mandatory [Default Dim Account Type - Table 15 G/ Account - Posting Value = Required Code], when I execute the VAT calculation, I need to change this parameterization. So, this is a problem: the general ledger entries run out of dimensions, which causes problems in financial reporting due to the lack of dimensions that should be mandatory. And, customers will change an important setting which in itself is not a good solution either.
I am really curious what the design engineer at Microsoft was thinking when they decided on this whole logic that only uses item’s cost and not the SKUs??? Why would they assume that companies would create variants of the item and somehow magically their costs will all be the same as the item’s cost???
I fully agree, we are especially blocked by some colleagues who need to organise webinars by hidding names (as one can do in GoToWebinar or other pro systems) and they have started using Teams Premium but these options are not available when creating the Webinar from Dynamics 365 which is a major blocker and most of these users might simply stop using Teams and keep using GoToWebinar or Zoom.
@Nikola MIt is in the nature of things.see also here: https://vatdesk.eu/en/reverse-charge-mechanism/In the area of sales, only the assessment basis, i.e. the net amount, is reported to the tax authorities for reverse charge cases. This is why we in BC don't calculate VAT for this case and don't post any G/L entry for this. In purchasing, we have to report both the purchase VAT and the reverse charge VAT to the authorities. Therefore, we create a VAT entry and evaluate it twice in the VAT statement, once positively and once negatively. And we post the VAT amount in G/L as well:
