I am looking for a way to prevent users from being able to post invoices with dates in the future. For example, posting an invoice in 2028 instead of 2018. However, the doc date verify tool does not work for us because we often have times when we need to post invoices backwards to a previously closed periods. Has anyone ever come up with a work around for this?
*This post is locked for comments
I think you may be misunderstanding my last response. What I'm saying is the tool *is supposed to* do what you are asking for. Using Doc Date Verify prevents dates that aren't in valid fiscal periods and it won't stop you from posting backwards to closed periods. When you say you tested this and found that not be the case, my suggestion is to engage your partner because it should do exactly what you are describing that you want.
I understand that the tool is working as it is supposed too, which is why I am looking for another solution. Thank you for your time.
With all due respect, the PSTL tool is supposed to do exactly what you are asking for, 100%. Doc Date Verify does not validate anything regarding periods being open or closed, merely "does this fiscal period exist".Dynamics GP without PSTL does prevent you from posting to a closed fiscal period (GL posting date) and otherwise just warns you if you are using a closed period date.
In your case if you think this was tested and your results are different, I would reach out to your partner for assistance, perhaps see if there is an updated version of PSTL, or something else going on that is interfering. What you describe is literally what this PSTL tool is designed to handle.
From the actual PSTL tool description: "With this installed, when the user keys a document date in Payables Transaction Entry, Receivables Transaction Entry, Invoice Entry, PM Manual Payment Entry, SOP Entry, IV Transaction Entry or Cash Receipts Entry, a check will be performed against the Company Fiscal Period setup to ensure the date is valid. If the document date does not exist within the valid fiscal period setup, a message will pop up for the user that reads “A fiscal period for this date has not been set up.” If a date is keyed for a closed period, the message will read “You cannot post to a date within a closed period. Do you want to continue?” So the user will be alerted with a pop up message in both instances, but may elect to continue on past the message. This will help users to catch any incorrect document dates keyed due to typing errors."
The doc date verification tool will only allow posting in the open fiscal periods. We need the ability to post in prior periods but are looking for a way to prevent posting in future years. The Doc Date Verification Tool does not work for us because it prevents us from being able to post to previous months. This has been tested extensively using the out of the box functionality and the PSTL tool... We are looking for a way to prevent posting in future years but still maintain the capability of posting in previous months. Any help is greatly appreciated.
I'm curious what you mean by "PSTL will not allow you to enter anything not within the open period"?
Doc Date Verify merely ensures that the date is within a valid fiscal period - prior or future. It has nothing to do with closed period controls. Any messages preventing a user from entering a posting date from a closed period are out-of-the-box GP functionality without PSTL.
Jen
By Disabling the DATE edit option
Dear Gents; You can allow the Users to raise the invoice ONLY with CURRENT DATE (today) by disabling the Edit option for the particular user /users.
As a special need to post the backdated or future dated invoices , you can allow the Administrator/SA user to raise /edit the invoice date.
Hope this will assist you as well.
The users can by pass the message and still enter with the fiscal periods closed. The PSTL will not allow you to enter anything that is not within the open period... So this does not work because we need to be able to enter in previous months. I just need to prevent the ability of entering in the future.
We do as well, however the user can by pass the message and still enter a future date... With the amount of transactions ap is entering on a daily basis, this happens a lot without the user even realizing they by passed the message.
Agreed. Opening and closing fiscal periods as well as utilizing the doc date verify tool in PSTL should do the trick for you.
With the doc date verify tool in PSTL, it just prompts you if you put a doc date in a future period and then you can override the prompt. Does the tool actually stop you altogether if you try to post in a historical period?
#1
André Arnaud de Cal...
291,391
Super User 2024 Season 2
#2
Martin Dráb
230,445
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
