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:
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:
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:
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:
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:
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.
I have to share with you one feedback about my Posting Groups series. I have got this mail yesterday from one guy I really appreciate:
“I really appreciate your blog posts about the posting setups. I even took printout of them and posted in our Dynamics Team room wall (Hope you ok with it). It will be really good reading material for our new team members.”
I am really happy if my posts help to someone in his daily work :).
One of features in Microsoft Dynamics NAV is using of payment discount. You can configure conditions of using this functionality on General Ledger Setup. With this configuration, I mean on Appln. Rounding Precision and Payment Tolerance and types of Payment Accounts from Customer Posting Groups. More about this configuration, you can find using Help for these fields.
We can use payment tolerances and discounts in few different situations. You can see how it generally works on following flowchart:
In my first example, I have configured only payment tolerance without discounts. When we post payment some less from original amount on invoice (e.g. 2.395 instead 2.400), we will get following G/L entries:
If our payment is greater than Invoice Amount reduced by discount, we will get following entries. System will post full payment as original invoice amount plus tolerance and discount, as well:
If payment is less than Invoice Amount reduced by discount, we will get following entries. System will post full payment as original invoice amount, discount and tolerance:
When we have overdue sales invoices, we usually can use Reminders and/or Finance Charge Memos. Both of these documents increases debits of our customers. We don’t post these documents, but we issue them. But, these issued documents also can make G/L entries.
On the first flowchart, you can see how system uses posting groups on Finance Charge Memos.
Results of this issued document in G/L entries are as following:
Now, on the second flowchart, you can see how system uses posting groups on Reminder. It uses very similar as on Finance Charge Memos, but fees on Finance Charge Memos lines are based only on Terms, while fees on Reminders can be based on Terms and Levels.
Results of Issued Reminders in G/L entries are as following:
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.
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:
If we use non-local currency in payment process, after running Adjust Exchange Rate batch job, we will get the following G/L entries:
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:
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:
All postings, based on difference currency code, use posting groups and accounts as on following flow chart:
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:
The similar situation is when we create and post sales prepayment invoice. Then, we will get these G/L entries:
If we want to post Prepayment Credit Memo, in both cases, we will get the same entries, but with opposite signs.
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:
But, when we finish posting and post Sales Credit Memo, we will get more G/L Entries:
The similar situation is in purchase return process. When we post Return Shipment, we will get again only these G/L Entries:
But, when we post Purchase Credit Memo for this item, we will get more G/L Entries:
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):
Totovic Dynamics 365 Blog 