Skip to main content
Microsoft Dynamics GP forum
Suggested answer

Setup for Posting changed and HITB stopped working after migration/upgrading to GP 18.2.1060

editSubscribe (0) ShareShare
Posted on by 150


Before migration/upgrading from GP2015 to the latest version of Dynamics GP, we had researched the possible upgrade path. We posted our question to the Microsoft Community forum and got a clear answer from Microsoft.

On May 15th, 2020 we’ve upgraded from Server1: GP2015R2 Year End 2019 (14.00.1230) -> Server2: GP2016 (as an intermediate step 16.00.0814) by restoring the GP 2015 system and company databases, and running GP2016 Utilities.  Then -> Server3: Dynamics GP Feb 2020 hotfix (18.2.1060) by restoring the GP2016 system and company databases, and running GP18.2.1060 utilities.  The upgrade process went smoothly. There was no failed table, nor any upgrade error message.

Two weeks later we discovered that all the batches that were originated from the Purchasing module did not post to the GL module. We found out what caused it.  On the screens of Tools>Setup>Posting>Posting for Purchasing Module, the checkbox ‘Post to General Ledger“ was unchecked for all individual ‘Origin” for Purchasing Series.  Origin “ALL” was marked correctly to post to GL.  After comparing the setups right before and immediately after the upgrade, it seemed that the migration/upgrading process had changed the posting setups.  The posting setup changes caused a lot of issues reconciling purchasing, inventory, and AP to GL.  In addition, Historical Inventory Trail Balance (HITB) report kept changing for previous month (4/30/2020), whenever there are inventory and receiving batches posted.  The HITB for previous month should not change if the on-going receiving and inventory batch posting dates are as of the current dates.


  1. Why would the migration/upgrade process change the posting setups?  Do we need to expect to see other system settings changed? 
  2. Is HITB still function the same way as on GP2015?  Are there any settings in Dynamics GP 18.2.1060 that would affect how HITB works?
  3. How to correct the reconciliation to GL, and HITB issues, caused by the upgrade?

Please help.  Thank you!

Olga and Li

  • Suggested answer
    Hokuminaria Profile Picture
    Hokuminaria 2,950 on at
    RE: Setup for Posting changed and HITB stopped working after migration/upgrading to GP 18.2.1060

    Hello Olga and Li,

    Microsoft is not aware of issues during the upgrade process that changes your Posting Settings. If you can replicate this, we would be happy to dig into it in a support case. The Known issue for 2018 R2 and year end update are in the link below. However, we did add an option to allow Transaction Level Posting be automatic for Transaction Level Posting.

    There was one change pertaining to the HITB. This is 'Exclude items on the HITB report with zero quantity or value. You can read about the changes in the link below.

    For your last question, this is not something we would be able to do through the forums. You would need to create a support case for one item on the HITB report to allow us to review the data. If you would like to dig into it, please create a support case.

    I hope this helps!

    Brandon Jarrett | Microsoft Support Engineer

Helpful resources

Quick Links

What Motivates a Super User?

We know many of you visit the Dynamics 365 Community and Power Platform…

Demystifying Copilot with Sundar…

Industry experts answer burning questions directly from our amazing Community…

Enabling Copilot Case and Conversation…

Agents can easily recap an ongoing chat, transcribe a voice conversation…


Andre Arnaud de Calavon Profile Picture

Andre Arnaud de Cal... 282,978 Super User

Martin Dráb Profile Picture

Martin Dráb 222,562 Super User

nmaenpaa Profile Picture

nmaenpaa 101,138

Product updates

Dynamics 365 release plans