315
We have noticed that when you enter a vendor document in purchasing the system records the posted date as the date it is entered. But when you pay the document the posted date is updated to the payment date. Does anyone know if there is a way to maintain the original posted date?
We like to monitor the difference between document date and posted date.
*This post is locked for comments
Did anyone ever find if this was a bug or "by design"? I don't understand the point of a "Posted Date" if it will change with another subsequent action like payment or apply.
If it's really a bug, you should be able to start a support incident with Microsoft to report it, and it will not be charged for. If it's 'by design', then you can submit a product suggestion to get this changed in a future version: connect.microsoft.com/.../program3314. If you do that, please post a link here so we can vote for it.
Perhaps if one of the Microsoft Support Engineers is reading this they could help us determine which case this falls under.
Victoria thank you very much for confirming what I suspected. Do you know if there is a way to notify Microsoft to get this bug addressed?
I think it is useful information for anyone company to have if they want to analyze the performance of their accounts payable department.
UWC Helpdesk,
I think you are right - I just checked some of our data in GP 2013 SP 2 and for a credit card vendor all transactions in a month have the same posted date, which is impossible, as we enter them throughout the month, as they come in. I don't recall this being the case before, but looking through historical data, it seems that is the case now for historical data as well. This almost feels like a bug, like the Posted Date is being set to the Modified Date.
Regardless of whether this is a bug or 'by design', it looks like you won't be able to get the information you're after out-of-the-box. One option would be to create a SQL trigger and a custom table to track the data that you want and use that for your reporting.
Smartlist by itself will allow you to list those two dates on the screen. If you want to calculate the difference, you need SmartList Builder or to drop your data into Excel and allow it to calculate there.
Otherwise, of course, Leslie is right on the money! See you at Convergence? We will be in booth 1642
Hi Leslie thanks for your help. I really appreciate it but perhaps I should have been more specific. I am trying to generate a Smartlist that compares the invoice to the posted date so that I can see the length of time it takes to post a vendor invoice. We do not use the purchase order system so I am going into Payables Transactions under smart lists. The field I am selecting is Posted Date (not Posting Date). On this report I have noticed that this field changes to payment date when the invoice is paid. In my opinion, it should remain as the original posted date.
Am I selecting the correct field or is there another date field that I should be using?
Hi,
There may be some misunderstanding about all of the dates. The 'posted date' is the system date of when you pushed the Post button. The field name is posteddt in both the PM20000 and PM30200 tables.
The General Ledger Posting date is provided by the user, it defaults to the User Date, but can be changed. The field name is pstgdate in both the PM20000 and PM30200 tables.
Once the vendor invoice is posted. Those two dates do not change. The invoice has a posted and posting date, and the payment has a posted and posting date. The 'posted date' is not updated to the payment date, ever.
When the payment is applied, a record is written to the PM30300 table. That table has its own assortment of dates. the glpostdt is the GL Posting date for when the payment was applied to the invoice. If you had also written an amount off during the apply, the write off would posting to the general ledger according to the glpostdt. If you don't write anything off, this date is used by the Historical Aged Trial Balance when you print it according to GL Posting date. The Apply Date used by the payables module is the 'Apply Date' that you set on the apply window. These dates are completely separate from the dates in the PM20000 or PM30200 tables.
It doesn't matter if you use a batch or not. If you are posting by Batch Date, the the date on the batch is the posting date. If you do not use a batch, or are posting according to document date, then the posting date will be inherited from the document date. However, this is a completely different date and can be changed by the user such that your GL Posting Date is different from your Document Date no matter how you post.
The dates used by the payables module are not as straight forward as you initially think. Consider how many dates are involved - can you describe them all? The PM Open Table (PM20000) contains 10 date fields, the PM History Table (PM30200) contains 11 dates. The Apply To History table contains 6 dates. That's 27 dates!
If you want to learn what all of these dates do, I recently posted an article to my blog that defines them all. You can read it here: dynamicsconfessions.blogspot.com/.../whats-in-date-pm-transactions.html
Please let me know if you have any questions.
Kind regards,
Leslie
When you enter documents in a batch the posted date equals the system date on the day you enter them. But if you then pay the documents the posted date changes to the payment date.
If you enter a purchase transaction without using a batch, then the posted date remains as the date the document was entered.
Hope this helps.
#1
André Arnaud de Cal...
291,622
Super User 2024 Season 2
#2
Martin Dráb
230,354
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (
