{"id":2432,"date":"2023-01-11T07:06:00","date_gmt":"2023-01-11T07:06:00","guid":{"rendered":"https:\/\/cssi.com\/gp\/?p=2432"},"modified":"2022-12-15T17:08:59","modified_gmt":"2022-12-15T17:08:59","slug":"using-gps-doc-date-verify","status":"publish","type":"post","link":"https:\/\/cssi.com\/gp\/2023\/01\/11\/using-gps-doc-date-verify\/","title":{"rendered":"Using GP’s Doc Date Verify"},"content":{"rendered":"\n

Controlling the Posting of Future-Dated Transactions in GP<\/h2>\n\n\n\n

This is a free tool that is part of the Professional Services Tools Library (PSTL) toolkit.\u00a0 It prevents the posting of future-dated transactions in subsidiary modules.\u00a0<\/p>\n\n\n\n

If your Posting Setup is set to post to G\/L by batch date, GP would allow a document date to be used even though that fiscal period is not yet set up in GP.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

If the Posting date is coming from the batch ID, then GP would accept an incorrectly entered Document date.\u00a0 In the example below, the document date contains a typo.\u00a0 But it posted to AP!\u00a0 And it won\u2019t appear on an aging report as of the current date.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

To prevent this, enable Doc Date Verify.\u00a0 Launch PSTL by selecting it from the GP Navigation Pane.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

In the Misc. Tools section, click on both the radio button and the check box next to Doc Date Verify. \u00a0Click on the X in the upper right-hand corner when finished.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This must be enabled on each workstation.<\/p>\n\n\n\n

Once this is enabled, any time a future date is entered into a transaction, you\u2019ll get the error message below.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Doc Date Verify works in the following windows:<\/p>\n\n\n\n