Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
I'm getting this "You must select a value in <dimension> field in combination with the following dimension values that are valid" for my withholding tax account when posting a payment journal.
System is not getting any dimension for the withholding tax entry. I've checked all the account structure and the journal dimension and it is fine. There is also no advanced rule structure nor customization in payment posting.
As per main account structure of the WHT account, we don't fixed any dimension value as it should come from the transaction. Only few vendors has this kind of error, other payments with wht proceeds on posting.
Thanks in advance for any suggestion regarding this issue.
Can you find a 'common denominator' of the payments that cause the trouble?
You mentioned that some payments work but others not.
I assume that the ones that don't work are possibly related to the same vendor, invoice type (expense vs. PO invoice), same employee who recorded the invoices, etc.
Thank you for the quick response.
It is always coming from same vendor. Vendor setup looks fine. And invoices settled on this are from PO invoice type.
My problem is there are hundred of invoices settled on this payment line and as per error message there is only few invoice among them causing it. I think i need to pinpoint these invoices having error and investigate from that.
Do you know some way to point these invoices? In the error message it shows temporary payment voucher number sequence assigning in each invoice but don't know how i can link this to which invoice?
Do you have the post and transfer option available for this journal that posts all lines that are ok and transfers those with errors to a new journal?
If this is available in your journal then this would be an option to identify the errorenous lines.
I already have identified the erroneous line from the payment journal and transfer it to another journal.
However, error comes from one of the invoices settled on this payment journal. Same error when posting, and cannot identify which among the number of invoices has the problem.
Thanks & Regards,
Unfortunately, there is no warning or error that gives you the exact line where this occurred.
In the past I often experienced that cash discount and related tax postings are the underlying reason. Can you check whether this vendor also has a cash discount associated?
A quick fix is temporarily fixing the financial dimensions for account that causes the trouble. This is, however only a short term solution and need a subsequent investigation to avoid the issue in the future.
Thanks for all the replies. Yes, what we were doing in the past was just temporarily fix the dimension to the account but we cannot do this everytime we post a payment journal.Vendor has no cash discount and for tax, all invoices has related withholding tax that they add only upon payment.
Many thanks for this update.
You mentioned that only some vendors are affected but others not.
I would recommend that you check them and test it in a demo environment first.
Just post some invoices and payments for those that always make trouble and then for those vendors that don't.
Once you have such a good&bad pair you have to compare the vendors and transactions completely in detail.
There must be a difference that causes the trouble.
Business Applications communities