Microsoft Dynamics 365
I have seen this exact issue as well. I considered creating VAT registration number at the warehouse level but that would only solve issues like being able print the correct the correct VAT number for Sales and Transfer order documents. I also looked at the registration ID's but they are not intended to work with the Sales tax/VAT system.
A total solution for this would need to look deeply at TAX reporting as well, EC sales list, as well as system functionality like summary update (consolidated invoices) to ensure shipments/transfers from multiple tax authorities are not combined in a single update/document. This will be hard to change but how do user companies handle this today. It is very common for companies to have multiple VAT registrations (especially if you only do purchase in that country but not sales, then you claim the input VAT) They must be calculating their VAT manually then, to try and get it right.
I hope this:
will come with some documentation please!
This applies to sending emails from Segments, too. We'd prefer to send mass-emails by logging segments, but of course, those just come from one email. Really, these should be able to come from the Salesperson assigned to the Contacts being logged. If this is under review for implementation, it would be good to consider letting any new functionality here apply to Segments.
When changing G/L number, BC removes description, VAT codes, Posting codes, dimensions - So we can just do the work twice.
The system is supposed to work for the user, not the other way around. And i agree with Kevin, when doing bank reconciliation, this is especially painful.
@kenneth, have you tried AAD Security Group teams or AAD Office Group teams in the SaaS version (D365)? I created AAD Security Group teams in D365 and linked them to security group's Object IDs in AAD. Then I assigned security roles to each AAD Security Group team in D365. Then I add users to appropriate security group in AAD. When they log into D365 for the first time, security roles are automatically assigned to them based on their membership of the D365 team via AAD security group. I hope this makes sense to you.
I'm waiting to upgrade our AAD to P1 level so I can assign D365 license to security groups in AAD so that license is automatically assigned to everyone in the security groups.
One of the worst module of BC.
Wouldn't Microsoft consider taking this one under Review as well :-)?
this would need to be configurable though as differing organisations will have different views on rounding - in my organisation we would prefer to the nearest 0.5 or 0 as we round to the nearest half day.
this would be a great addition for both back office and MSS to ensure that managers have the most accurate information to manager their team effectively
We've just launched and this has caused us numerous issues with workarounds having to be applied to ensure colleagues are paid once data is passed through to LOKI.. This would be a game changer for us and would reduce the risk inaccuracies in keying