New Cumulative Updates for NAV 2013/2013R2

Five days ago, I published post about new Cumulative Update for NAV 2015. Now, last two days, Microsoft also has published new Cumulative Updates for NAV 2013 (CU26) – Build 40940 and for NAV 2013 R2 (CU19) – Bulid 40941.

Both of them have also platform and application hotfixes and some local application hotfixes.

Advertisements

Posting Groups #12 – Payment Posting

When we post payments, we usually have payments for customers and from vendors. In the same time, we should have bank account posting as balance accounts. Bank account is not necessary, but it is the best practice.

When we post payments from bank statement, we will get the same G/L entries, regardless we have payment in local currency or in some other. These are entries as following:

1PaymStat

If we use non-local currency in payment process, after running Adjust Exchange Rate batch job, we will get the following G/L entries:

2PaymAdjustER

In previous example, you could see result if used currency exchange rate was increased. But, if exchange rate was decreased, the posting results in G/L entries would be as following:

3PaymAdjustER

All previous results were unrealized exchange rates gains or losses, but when we apply these payments, we will get realized exchange rates as on following table:

4PaymApply

All postings, based on difference currency code, use posting groups and accounts as on following flow chart:

AdjFlowChart

Posting Groups #11 – Prepayments Posting

Before I start with this post, I want to emphasize once again, in all my examples I use W1 database. I know that prepayments can be quite differently from country to country, but I have used only W1 examples here.

Now, when this is clear, we can continue with examples. First, I will describe purchase prepayment invoice. When we choose to create Prepayment Invoice from Purchase order, system will post document with G/L Account in line (from General Posting Setup) and with following G/L entries:

PPPI

The similar situation is when we create and post sales prepayment invoice. Then, we will get these G/L entries:

PSPI

If we want to post Prepayment Credit Memo, in both cases, we will get the same entries, but with opposite signs.

Posting Groups #10 – Item Returns Posting (Sale & Purchase)

In my earl posts about posting groups, I have showed purchase and sales processes. But both of these processes have its opposite processes.

If our customer wants to return items to us, we can use the Sales Return Order for this. When we finish posting, we will get Return Receipt and Sales Credit Memo as result.

On other side, if we want to return items to our vendor, we can use the Purchase Return Order for this. As result of posting, we will get Return Shipment and Purchase Credit Memo.

I will not prepare flow chart about using posting groups, because we can use the same schemas as we already have in Item Sale Posting and Item Purchase Posting posts.

First, I will describe sales return process. When we post Return Receipt, we will get only these G/L Entries:

##1

But, when we finish posting and post Sales Credit Memo, we will get more G/L Entries:

##2

The similar situation is in purchase return process. When we post Return Shipment, we will get again only these G/L Entries:

##3

But, when we post Purchase Credit Memo for this item, we will get more G/L Entries:

##4

And, on the end when we run Adjust Cost – Item Entries batch job, we will get the following G/L Entries (variance between expected and actual cost):

##5

Posting Groups #9 –Item Sale Posting with Payment Method

I have already showed item sale process posting here in Posting Group #2 post. But, we can have some specific variants of this posting. One of them is when we use Payment Method.

If you choose Payment Method code on sales document header, and this Payment Method has configured Bal. Account Type and Bal. Account No., NAV will automatically create the balancing journal line. This functionality is great when we are being paid in full at the time of sale, but we can use this feature in some other specific process.

You can see how system works with Payment Method on following flow-chart:

SalesPMC

When we finish with this Sales Order posting, we can find following G/L entries navigated to Posted Sales Invoice. You can see standard G/L entries about invoice and the last two of them, connected with Payment:

SI_PyM_GLe

New Cumulative Update 7 for NAV 2015 has been released

Cumulative Update 7 for Microsoft Dynamics NAV 2015 has been released today, one hour ago. It includes the most of application area (Administration, Cash Flow, Client, Finance, Fixed Assets, Inventory, Jobs, Manufacturing, Purchase, Sales, Service and Warehouse) on almost 80 objects and very useful platform hotfixes and regulatory features that have been for Microsoft Dynamics NAV 2015. If you are upgrading to this cumulative update (CU7) from a cumulative update earlier than CU4 (build 39663), you first must convert the database.

It also has a lot application hotfixes for following localizations: Australia, Belgium, Switzerland, Czech Republic, Germany, Spanish, France, Italy, North America, Netherlands, Norway, Russia and Sweden.

You can download Cumulative Update 7 for Microsoft Dynamics NAV 2015 from here. This CU is named as Build 40938.

Posting Groups #8 – Revaluation Posting

In my last post, I have touched Revaluation process, but only for Standard cost changing. We can use Revaluation for other cases, as well.

If we change cost only for items on stock, it will be the same situation as on previous example. But, if we want to change cost for already sold or consumed stock, it will be with some differences. First, when we change the cost, we will get the same entries, as I already show in previous post. But, when we run Adjust Cost – Item Entries batch job, we will get the new G/L entries.

I made three scenarios:

In the first scenario, I have raw material with FIFO cost type. I consume this raw material on production order to produce finish goods, configured as also FIFO cost type. In this case, result of posting in G/L entry will be as following:

RevPOfifo

In the second scenario, everything was the same, but only finish goods was configured as Standard cost type. In this case, result of posting in G/L entry will be a bit different, as following example:

RevPOstd

And, in the third scenario, I change the cost on already sold items. In this scenario, G/L entries will be as following:

RevSO