We have a customer on GP 2018.5.1584 and have created several new databases for newly acquired companies. We used the PSTL copy company settings, in all of them. They post payables by the transaction date and when we look at the posting setup - this is what it says it is set to. This applies to transactions, payments, check batches.
What they have found is when they create a batch for anything the posting date is grayed out as expected. But the actual posting date uses the batch creation date to post ALL transactions, even with check batches. So it is causing a huge issue with batches posting into the wrong period.
We have tried running checklinks of the posting setup and it found no errors. They now one company with over a year's worth of transactions using the wrong posting dates.
Has anyone else experienced this? If so, how did you fix it? Or what can we do to correct all the data?
@MKAEK - I don't believe that the Posting/Batch information is ever active for Purchasing Prepayments. (Purchasing Prepayments are adding to a Purchase Order and since a Purchase Order is not itself an accounting transaction, there is no Batch Number associated with it.
The behavior of the PO Prepayment feature is dependent on the options selected in Purchase Order Setup.
This happened to me, too. I think there is a bug in the PSTL Copy Company utility. After using it to copy settings to two new companies, all of the Purchasing Posting Date From settings were set to Batch, even Purchasing Prepayments, which is disabled in the UI and cannot normally be changed by the user from the default value of Transaction.
When you are reviewing Posting Setup, are you first selecting a specific Origin? If the Origin is set to All, you are seeing the GP defaults, not the actual company settings for each specific origin. For payables payments, the selection for the company-specific window would look like this:
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.