Posting Groups #26 – Deferrals in Purchase

Last year I had a series of articles about using Posting Groups in Microsoft Dynamics NAV. Now, I want to continue with some small updates.

I already wrote about using Posting Groups in purchasing process, but now I want to add a model when we use Deferrals (a very nice new feature in NAV 2016). In this case, we have some differences compared with a standard posting. System will use some different rules about Posting Groups (you can check standard purchase posting model here). In the following chart, you can understand how system uses Posting Groups when we have deferrals on Purchase document:

PG_Purch_Deferr.png

When we post document and get purchase posted invoice, we will get the following G/L Entries. You can find completely description of them in the next table:

Entries_Purch_Deferr.png

You can notice that we have more line amounts. Number of lines is based on number of period defined in Deferral Template. For each period, we have two lines (positive and negative). We have always first period lines, but other period lines are behind all entries, because they have not the same posting date. Their posting date is based on setup in Deferral Template.

Advertisements

Posting Groups #25 – Job WIP Posting (3 – Cost Value)

In one of my previous posts, I have already described how you can post Job WIP entries if you use Cost Value as recognized cost in WIP posting method. But, it was only part of posting when you calculate Job WIP for the first time. But if you have already posted Job WIP entries and want to post WIP, again after new usage posting (as Contract).

In this situation, system first need to post correction of previous Job WIP entries and that post new entries. You can see how there G/L entries look like on following table:

Job WIP Posting 3a

When we speak about “Remaining Cost in Comparison with Schedule”, we already think about relation between Contract usage posting and values as Schedule.

Posting Groups #24 – Job WIP Posting (2)

If you have the same example as in previous post, but with using different methods of WIP posting (e.g. Completed Contract, Cost of Sales or Contract-Invoiced Cost), you will get the some different results. To repeat, my example was only posted usage of resources and items, without invoicing. System calculates WIP for all Resource and Item usage, based on Unit Cost and consumed Quantity. Result of this posting is following:

Job WIP Posting 2

Posting Groups #23 – Job WIP Posting (1)

As the most of projects are jobs performing usually several months (or several years), WIP calculation is very important part of Job Management. From NAV 2013, we have new functionality for WIP calculation in Jobs – the WIP cockpit. I already described how this feature works in my older post and now, I want to show you results of WIP posting in G/L Entry.

When you want to post WIP to G/L, system will use only Jobs Posting Groups for determining what account need to use. Considering, there are not only one method of WIP posting, it means system doesn’t post results on the same way every time.

In this first example, I have used following WIP posting methods as recognized costs: Cost Value and Usage (Total Cost). Results for these two methods are the same.

System calculates WIP for all Resource and Item usage, based on Unit Cost and consumed Quantity. Result of this posting is following:

Job WIP Posting 1

Posting Groups #22 – Item Purchase for Job

If you want to purchase items directly for some Job, you can do it using e.g. Purchase Order and posting it. Flowchart of posting groups usage is the same as in post I already wrote about item purchase posting. There is only one additional step in comparison with standard item purchasing; you have to choose Job No. and Job Task No. in each line on Purchase Order.

This is not currently real example of Job Posting Groups using, but it still has some specifics when you have purchasing for Job. When you post this document, you will get both of posting documents – Purchase Receipt and Purchase Invoice, as well. But when you look in Purchase Receipt, you will see that you have two Item Ledger Entries for each line in document. One of them is Purchase, but second in Negative Adjmt. with the same quantity. It actually means that in the same posting process, system post item purchase (as usually) and item consumption for Job purpose. This posting also creates one Job Ledger Entry for each line in document with Usage Entry Type for each Negative Adjmt. line in ILE.

When you look at G/L Entries, you will see the following result of this posting:

ItemPurchJob

Posting Groups #21 – FA Disposal Posting

When you want to post disposal of Fixed Assets, you can do it using FA G/L Journals. You must choose Disposal as FA Posting Type. In my examples, I post this journals with marked Depr. until FA Posting Date field.

You can get two different types of G/L entries, depends of setup in Depreciation Book. You can choose Net or Gross method on Disposal Calculation Method field.

In my first example, I have used net method. In this example I used FA with already posted some depreciation and write-down entries.

FA Disp Nm

In my second example, I have used gross method. In this example I used FA with already posted some depreciation and appreciation entries (entries can be different, depends your FA has had appreciation or write-down).

FA Disp Gm

All of these posting results depend only of FA Posting Type.

Posting Groups #20 – FA Write-Down and Appreciation

When you want to change Fixed Asset value, you can do it on few ways. In this post, I will show you how you can do it using Write-Down and Appreciation in what will be results of these postings in G/L entry, based on posting groups you use.

Both of these posting types, you can do using FA G/L Journals. Posting depends on FA Posting Type.

In my first example, I will use Write-Down FA Posting Type. If we do not mark Depr. until FA Posting Date field, the result will be as following:

FA WD 1

But, if we mark this field, result will with some difference (system will post depreciation in the same register):

FA WD 2

In my second example, I will use Appreciation FA Posting Type. Again, in my first posting I will not mark Depr. until FA Posting Date field and result will be as following:

FA App 1

If we however mark Depr. until FA Posting Date field, the result will be as following:

FA App 2

But, we have common fact with all of these examples. In all of them, system only uses FA Posting Groups and manually configured Balance Account No.