Posting Groups #18 – FA Sales Posting

If we want to sale our fixed assets, it is a similar process as FA purchasing, but in opposite direction. In this situation, system uses customer posting group, VAT and general posting groups and FA posting groups.

You can see this process concept on following flowchart. One of specifics is how system determines VAT Production Posting Group. You can use it on one of following ways:

  • Manually choosing VAT Production Posting Group;
  • Inheriting from manually choosing/changing General Production Posting Group (Def. VAT Prod. Posting Group);
  • Inheriting from VAT Production Posting Group, configuring on Acq. Cost Acc. On Disposal on FA Posting Group;
  • Inheriting from General Production Posting Group (Def. VAT Prod. Posting Group), configuring on Acq. Cost Acc. On Disposal on FA Posting Group.

FA_Sale_FwC

Other specific in FA sales process is that system uses different configuration from FA Posting Group, depending of FA sales price (higher or lower price in comparison with Book Value).

In my first example, you will see what G/L entries you will get when we sale FA with higher price:

FA_Sale_G

In this example, you will see result of FA sales posting with lower price:

FA_Sale_L

On both of these examples, you will see that we have the last additional G/L entry. This entry will exist as Residual caused by rounding of Additional-Currency, but only if you use Additional Currency configured on General Ledger Setup. This entry will be usually a zero amount.

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

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

Posting Groups #7 – Change Standard Cost

If you use Standard cost type for your Items and you want to change it, you need to use Standard Cost Worksheet. When you run Implement Standard Cost Changes command, all changes will be moved to Revaluation Journal.

When you post Revaluation Journal, you will get following G/L entries, if you have cost increasing:

std_rev_1

If you have cost decreasing, you will get the same Accounts, but the different values, as following:

std_rev_2

Posting Groups #6 – Manufacturing Posting (Std. Cost Type)

In my previous post, I describe all G/L posting results when we do with production, but using FIFO costing method. It this new example, I will describe results of posting when we have finish goods with Costing Method configured as Standard.

In this case, we use the same flow chart for posting groups, as I have described in my previous post.

In this example, when we post consumption and output, we will get following entries in G/L Ledger. In this case, we will get entries from cost of Item consumption and cost of Work Centers using, and value for output Item based on Standard Cost:

C&OJPstd

When we change status of Production Order to Finished, we will get additional G/L Entries. These are correction of standard cost on output Item and variance from standard to actual cost. You can find these entries in next table:

POsFstd

Posting Groups #5 – Manufacturing Posting

When we post manufacturing processes, we have Production Order as the base document. Then, we can use Production Journal (for posting in one step), or Consumption and Output Journals (for posting in two steps). Never mind, what you variant use, result in G/L Entries is the same.

In any case, we have some rules about using posting groups. Some posting groups are used from items, and other from work centers. In following chart, you can see how system uses posting groups in manufacturing posting.

Production Diagram

Difference in G/L Entries can be based on Costing Method you use for output items. It is not the same when you use Standard or some other costing methods. In this example, I will describe non-standard method (in this case I have used FIFO). I will describe using of standard method in next post.

In this example, when we post consumption and output, we will get following entries in G/L Ledger. These are only cost of Item consumption and cost of Work Centers using:

C&OJPfifo

When we change status of Production Order to Finished, we will get additional G/L Entries. These are cost of output Item, calculated from consumption Items and Work Centers usage. You can find these entries in next table:

POsFfifo

Posting Groups #4 – Adjust Cost – Item Entries Posting

When we run Adjust Cost – Item Entries batch job, system forwards any cost changes from inbound entries, to the related outbound entries. In our small example, we will see what we will get after post Item Charges to already sold items. Currently, we will use very simple example; we have only purchased and sold item.

In this example, automatic cost adjustment is not configured. We can use example with additional costs using Item Charge or using higher cost on Invoice in comparison with Receipt.

When we run this batch job, we will get G/L Entries as result. You can find completely description of them in next table:

ACIE-1

System will post only the difference between the higher and lower costs. System will use Inventory Posting Setup from Inventory Posting Group and Location on source document. On the same way, system will use General Posting Setup from the same source document, but from General Business and Production Posting Groups from document header and line.

In some other examples, it can be more complex posting, but I will process this examples in another articles.