web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / GL Batch Posted Date q...
Finance | Project Operations, Human Resources, ...
Suggested Answer

GL Batch Posted Date query

(0) ShareShare
ReportReport
Posted on by ttremblay 5

I have been unable to find a way to extract GL Transactions based on the actual physical date the transaction was posted. (i.e.  A financial batch Created on Oct 10, with the transaction date backdated to Oct 1, approval date of Oct 20, but finally posted on Oct 26th). I need to extract the transactions POSTED Oct 26th, and include the applicable dates like Oct 1st, to be used in a 3rd party match and kill reconciliation program.

GL20000 table has all the necessary fields EXCEPT for the date of Oct 26th (in my example above)

Thank you.

Categories:
Microsoft Dynamics GP
I have the same question (0)
  • Suggested answer
    Lisa at AonC.com Profile Picture
    Lisa at AonC.com 937 Super User 2025 Season 2 on at

    If the transaction hasn't been corrected, GL20000..DEX_ROW_TS should have what you are looking for.    (I think both LSTDTEDT and ORPSTDDT also get updated when posted.)

    For DEX_ROW_TS, you may need to adjust for UTC.

    If you don't see this data, post generic-data for the columns/data you are seeing that match your example.  

  • ttremblay Profile Picture
    ttremblay 5 on at

    Thank you Lisa. We ended up getting that same advise (to use the Dex field and adjust for UTC time zone). I am however unsure what happens if a transaction gets reversed through the 'correct' functionality whether or not there is a new record created in the GL20000 table for the reversal. Can you advise? 

  • Cheryl Waswick Profile Picture
    Cheryl Waswick on at

    Hello Tremblay,

    Yes, the DEX_ROW_TS field will be updated each time the record is touched.  So it is updated when you back out the JE using the Correct button, as well as when you perform the GL Year-end closing routing on it and it moves to history.

    I agree with Lisa that the best field to use may be the original posting date (ORPSTDDT) as this seems to capture the system date at time of posting.  

    You can also choose in tools | setup | posting | posting if you want transactions to be have the batch date or the transaction date when updating GL and coming from a submodule.   So if your batch date is always today, and you use 'batch date' on your posting and post the same day, then that would be another way to do this.

    Hope that helps,

    Thanks

    Cheryl Waswick

    Microsoft Support

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 551 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 450 Super User 2025 Season 2

#3
BillurSamdancioglu Profile Picture

BillurSamdancioglu 278 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans