Fixed Assets GL Posting Flow Part 8

Today’s #TipTuesday is the finale of my series on Fixed Asset transactions in Dynamics GP and what G/L accounts get used where. Today is where I will walk through the rest of the catch-all set of scenarios around what kinds of asset changes impact the G/L.

The previous posts so far are:

  1. Additions with & without YTD/LTD amortization
  2. Depreciation/Amortization
  3. Retirements in the 1st year of ownership
  4. Retirements after the 1st year of ownership
  5. Different retirement types & impact on Gain/Loss Account
  6. Retirements with proceeds and sale expenses
  7. Account changes & Mass Change impact on G/L

Recap from last week

Last week’s post covers some of the scenarios under which there is a G/L impact, but on subsequent transactions. Namely:

  • Changing the G/L Accounts on the Accounts window
  • Changing G/L Accounts via Mass Change
  • Changing Book via Mass Change

Change #4 - Cost or LTD/YTD Amort change on a Book card

This kind of change is more obvious, but I’m going to cover it anyway! If you make changes to the Book card, many times you are - at a minimum - going to be prompted to reset or recalculate something (due to changing a depreciation-sensitive field). What I’m covering today is even more specific: changing the cost, up or down, or altering the YTD/LTD amortization amounts. The reasons you may need to do this are for things like a revaluation of an asset or additional improvements to an asset where you wish to add value to an existing card instead of starting a new card.

In my example, I changed Cost on Building 1’s card from $360K to $400K. When I clicked Save, I was prompted with the “you have changed a depreciation sensitive field” warning. I chose Yes, and Recalculate in my example as I was assuming there is some improvement to the building causing an increase in cost base, on a go-forward basis.

After making a change like this, if you go to G/L Posting, you will get a journal entry such as this one with the financial impact of the changes you made. If depreciation rates were changed, those would impact the next depreciation routine (unless you chose reset life or reset year).

Change #5 - Transfer or Mass Transfer with G/L changes

Not all transfers result in a G/L impact but if you transfer with a change in G/L Accounts, you will have a G/L posting as a result. In my example, I did a full transfer of my Building 3 card from one set of accounts to another as of Mar 31st, 2020. (The accounts are hidden in a detail window)

Here is the Book before the transfer.

Book before transfer

This is the transfer. I had amortized this asset up to March 31st, so I will do the transfer at that date for the cleanest example. The change is hidden in the Accounts detail window, but what I did is transfer this to “Dept 200” accounts.

Transfer window

… and this is the G/L Posting after the transfer. What you’ll notice is it moved both the cost and the LTD amortization from old accounts to new accounts. What it does not do is move amortization expense to any new G/L Accounts, because the effective date of my transfer is March 31st, hence it is assuming all prior activity stays where it was.

GL entry after transfer

Change #5B - transfer with a date other than Depreciated To Date

To follow that last thought through a little further, I did another transfer, to move this same asset back to Dept. 100 as of March 1st. Here’s the G/L posting:

Something didn’t calculate properly here and it’s a result of me getting lazy with my date selection. I chose March 1st instead of Feb 29th, which would be exactly 1 month short of where it was amortized to previously. In theory what it’s doing above is moving cost to the right account and backing out amortization I’ve already booked between March 1 and 31st. That amount should not be $1,000, it should be close but some slightly odd amount, because it’s a period less than 1 full month.

What happens on a transfer - rightly or wrongly - the transfer date becomes the Depreciated To Date on the Book. Here is the book after this transfer was done. Notice the Depreciated to Date is now March 1st?

Since I had previously amortized this asset up to March 31st, I re-ran the Depreciation routine but it didn’t recalculate the book the way it should have up to this point. Here is that G/L posting.

… and here is the new book window as of March 31st’s amortization. The end result should be the same values here are were in my original post but they are not.

I’m not sure what to think about this other than if I am going to do any transfers that have G/L impacts, I am going to be very careful to take before and after screenshots or data dumps of the book values to ensure the values return to where they should when it’s done. In this case, it’s off by $29, not a super big deal but it shouldn’t be off at all.

Change #6 - Deleting a Book card or deleting an Asset

Last scenario of the series! If you delete a Book card of an asset, or if you delete an asset entirely (under Routines), you get an explicit warning that NO G/L entry will be made as a result.

First, this is the warning if you delete the Book card of an asset.

Similarly, on the Asset Delete Utility window, the same message is essentially baked into the window to warn you.

If you delete a BOOK and re-create the book again, what you will get is a G/L posting for “adding an asset” - since adding values back to the Book window is essentially adding an asset into the system. Actually deleting it will not, so beware if you do that in order to fix something and have already sync’d the addition to the G/L.


Well… with this post, I’ve concluded the series on Fixed Asset posting flows. I believe I have covered most of the common scenarios clients run into to identify which G/L accounts get used where in Fixed Assets. While I didn’t cover all of the nuances of every type of depreciation setting, for instance, the entries should pretty much be consistent throughout even where the calculations differ.

I hope you found this helpful in understanding the Fixed Assets module better when it comes to the G/L side of things!

comments powered by Disqus
Built with Hugo
Theme Stack designed by Jimmy