Posting Groups in Assembly Order in NAV

In my previous articles about using of posting groups in Dynamics NAV, I didn’t describe using of posting groups in Assembly Orders. Assembly Orders are here in the few last versions of NAV and I want to show them as well.

Using of Assembly Orders is not so complex and we can use only Items on header and Items and Resources in lines. Because of that, we can use only Inventory Setup and General Posting Setup. You can see the flow chart with description of usage these posting groups:

AssOrdFlCh.jpg

When we post one Assembly Order, we will get the following G/L Entries:

AssOrdEntr.jpg

Advertisement

Posting Groups in Service Management in NAV

I’ve already wrote 27 articles about using of Posting Groups in NAV. Now, I’ll continue this series with the new topic – Service. When we use Service Order, all posting will be based on the following flow-chart:

ServiceFlCh.jpg

You can notice, this is very similar with postings in Sales, but we have some specifics about using of additional fees. But if you look at the part based on Service Lines, everything is the same. I want to accent that this part is drawn for items ()because of usage Inventory Posting Group and Location); if you use G/L Account or Resource, there will not be inventory postings.

Now, let look at the posting results. First, if we decide to post “Ship and Consume” from Service Line, that means these lines have been used for servicing but cannot be included in the invoice to the customer and we will have only inventory postings if we used items (in other cases, we will not have anything for posting):

Serv1.jpg

But if we decide to post “Ship and Invoice” from Service Line, the result will be different. In this case, we have some additional entries except inventory posting:

Serv2.jpg

And on the end, we need to finish posting from Service Order. If we have not some additional fees for invoicing, it will not be anything for posting, but if we have additional fees, it looks the same (for “Ship and Consume” and “Ship and Invoice” examples):

Serv3.jpg

 

Posting Groups #27 – Deferrals in Sales

Few days ago I’ve published how you can use Posting Groups in Microsoft Dynamics NAV 2016 when you have purchase where you use Deferrals. Now, I want to show you how it looks like when you use Deferrals in sales process. In my old post, you can find everything about using Posting Groups in standard sales process. Now, I’ll show difference. One of the main difference is that system doesn’t use inventory posting groups when posts sales invoice (the same as in purchase scenario).

In the following chart, you can understand how system uses Posting Groups when we have deferrals on Sales document:

SalDefChart.jpg

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

SalDefEntries.jpg

When you use Items and Resources, system will use Sales Account from General Posting Setup, but if you use G/L Account in the sales line, system will use this G/L Account you typed.

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.

And I’ve forgot one things in the last post. If you want to see all lines using Navigate, you have to delete Posting Date in Navigate page or if you didn’t it, you have to delete Posting Date from filters in General Ledger Entry.

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.

What is Posting Preview in NAV 2016?

I’m sure that your clients many times asked to make some feature to see results of posting before they post document, at least G/L entries as report. My clients asked for this a hundred times.

This was on first sight very simple requirement, but in practice… Now with NAV 2016, we finally got it. And not only we did get it… we have got the awesome feature. It looks like so simply and because of that it is awesome.

You just need to click on Preview Posting command in your ribbon and you will get completely navigated page with all entries (G/L entries, Customer/Vendor entries, VAT entries, Value entries…). Everything is the same as you already post this document, but this is not posted. All links are here… perfect.

PreviewPosting

Of course, you will not see Document No. for example; this is because we still have not this data.

You can find this feature on almost all documents and journals. It miss maybe only on few of them. This solution is based on temporary tables. When you look at these objects, everything will be clearer.

PreviewObjects

Try it and you will see how good it is.

Posting Groups #17 – FA Reclassification Journal Posting

If we need to transfer, split up or combine our fixed assets, we can do it using the FA reclassification journal. In my following example, I split up my existed FA, but everything is almost the same in other examples. Using the FA reclassification journal, system uses only FA Posting Group for G/L entries allocation.

When you Reclassify your journal, you will get lines in FA G/L Journal. After you post it, you can see this posting result in G/L entries in following table:

FA ReclassJ

Posting Groups #16 – FA Depreciation Posting

Depreciation is a method of allocating the cost of a Fixed Asset over its useful life. In NAV for this purpose, you can run batch job Calculate Depreciation. In this posting process, system will use only FA Posting Groups.

Assuming you checked, ‘Insert Bal. Account’ on Calculate Depreciation batch job, you will get following G/L entries as posting result:

FA_Depr_post

Posting Groups #15 – FA Purchase Posting

In my first post about posting groups, I show you what results are when you post item purchase. I also show how looks like when we post Item Charge purchase. Now, in this post, I will describe some difference when you want to purchase Fixed Asset. Generally, it is a similar process, but it still has some difference. Some posting groups will not be used, but we also have one new posting groups – FA Posting Group. On this setup, we can configure all accounts in relation with fixed assets processes.

Process of using all posting groups in FA purchase process is shown on following flowchart:

FA Pch FlwCh

Depending on the FA Posting Type on Purchase Line, we can get two different results. If we want to buy new fixed asset, we will choose Acquisition Cost type and we will get following G/L entries:

FA Pch Inv

But, we can also choose Maintenance FA Posting Type to post maintenance for some existing fixed asset. In this situation, we will get following G/L entries:

FAm Pch Inv

In previous example, I didn’t use discounts, because I have already showed it when I described item purchase. In this case, everything is the same.