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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Dynamics GP Support and Services Blog / Microsoft Dynamics GP 2018 ...

Microsoft Dynamics GP 2018 R2: Transaction Level Post Through General Ledger

Views (2969)
Andrea Melroe Profile Picture Andrea Melroe 3,437

With the release of Microsoft Dynamics GP 2018 R2, users can now 'Post Through General Ledger' at the transaction level in several windows.

In prior versions of Microsoft Dynamics GP, users have the option to 'Post Through GL' for transactions that are saved to batches only (except for Bank Reconciliation).

In previous versions, any transaction posted from a sub-module that was not saved to a batch would automatically create a batch 'waiting to be posted' in General Ledger.

Note:
If you find this feature is not working for you, a few items to review.
1. For Payables, if you are using a 3rd party or customization in the posting routine, this may be a factor, we have noticed that it is not posting thru as it should, please check with any of them for updates, or try it disabled to see if it is the issue.
2. Also for Payables, if you do not print the General Ledger posting journal, the batch will post TO General Ledger. 
If you would like to see this change in the future, vote on this suggestion.
3. Reminder if you are using AA (Analytical Accounting) there is Company settings under Tools | Setup | Company | AA | Options.

 

The 'Post Through General Ledger Files' option has been added immediately under the 'Allow Transaction Posting' option in the Posting Setup window to accommodate the new 'Transaction Level Post Through GL' functionality. To open the Posting Setup window: on the Microsoft Dynamics GP menu, point to Tools, highlight Setup, point to Posting, and click on Posting.

0601.post.png

Here is a list of windows from which users can 'Post Through General Ledger Files' at the transaction level:

Sales Purchasing Inventory Payroll Project Accounting
Sales Deposits Receivings Trx Entry Transaction Entry Manual Checks Timesheet Entry
Invoice Entry Purchasing Invoice Entry Transfer Entry Equipment Log Entry
Sales Transaction Entry Returns Trx Entry Assembly Entry Misc. Log Entry
Receivables Sales Entry Payables Trx Entry Employee Expense Entry
Receivables Cash Receipts Payment Entry Billing Entry
Receivables Apply Doc Apply To Revenue Recognition Entry
Voided Trx Maintenance Purchasing Prepayments Inventory Transfer Entry
PA Returns Trx Entry

Enjoy!!

For more detailed documentation on this new feature and others with the Release of Microsoft Dynamics GP 2018 R2, please check out our Microsoft Dynamics GP 2018 R2 New Feature Blog Series.


Andrea Melroe | Sr. Technical Advisor | Microsoft Dynamics GP

Comments

*This post is locked for comments

  • Sheilajr Profile Picture Sheilajr 745
    Posted at
    Sorry, I would like to retract what I stated since after doing some additional testing I did find that the batch does go to the GL it just doesn't post automatically through the GL. I was thinking this was the reason that batches were not posting to the GL but it is not. Back to the drawing board.
  • Sheilajr Profile Picture Sheilajr 745
    Posted at
    I have an important observation on this new feature. I have a client who has noticed some transactions not hitting the GL from Payables. I did some digging and finally found that the Posting settings for the Transaction level posting was not set to Post Through the GL. Now I know that this client did not unmark that box and I have a sneaking suspicion that when they upgraded it was set to unmarked. They normally post by batch so it hasn't been an issue but I do have a problem with this not being marked automatically during the upgrade from a version that did not have this field. We should assume that ALL transactions should post through GL unless there are circumstances where they don't want to post through. I have created a script to update the new field to Marked (1) whenever there is a Allow Transaction Posting that is also marked (1). Update SY02300 Set TRXPostingThruGL = 1 where ALTRXPST=1 and TRXPostingThruGL=0 I hope this helps others in the future. Sheila Jefferson-Ross