Direct Cost Applied Account not required

Just have your entries all go into one account.

Why doesn't your client want double entry posting? It's absolutely needed when using landed cost and reconciling A/P to inventory.

It shouldn't matter if the item is purchased in an intercompany environment. You still need double entry to be able to properly reconcile the purchases made for the period.

Alex Chow wrote:

It shouldn't matter if the item is purchased in an intercompany environment. You still need double entry to be able to properly reconcile the purchases made for the period.

when using average, fifo or lifo costing method and running nav's item costing batch job, you need this account. otherwise, you can not reconcile inventory and g/l If wrong purchase returns is done.

for example, in turkish legislation there is one inventory account. but, we need to use different purchase, direct cost applied and inventory accounts in nav.

When you will run the Post cost to G/L the transaction you are avoiding will be posted. If you don't run the batch job your inventory valuation will not reflect in the General Ledger which means Cost and Financial books are not integrated.
If I am a client i will be very sad if so much of money spend gives me disintegrated accounts.

You have both the options i.e per entry , per posting group.

davealfa wrote:

ok thanks...so will use Per posting group, as this would create just 1 transaction in the Direct Cost Applied Account

thanks for your help!

dave

There will be an entry "per posting group" for each posting date.

hi experts,


what is the best method u generally used to update general ledger using per entry or per posting group.


Please let me know .


what is your opnion about Automatic cos t posting .
Do i need to place a check mark always.


If not what is the period to run the batch job , that means daily , weekly....



plesase suggest me.

I'm going to state a difference of opinion. Not to say that other statements are wrong. Just that I have a different opinion and experience.

Turning off "Automatic Cost Posting" is a carryover from the old days when NAV understood nothing about performance tuning and provided no tuning capabilities. Their official solution to performance issues was to start disabling features.

I have been integrating NAV for over 9 years (including many high transaction systems) and have never found a need to turn off "Automatic Cost Posting". (I do have a few were "Expected Cost Posting" is disabled) I've worked with many clients that demand (and expect) real time General Ledger. It is not uncommon to see a department manager, toward the end of the period, running their P&L almost hourly to see where they stand. You don't tell a client like this that their GL will update overnight.

Coming to the question posted by "Lally" I will never advise to turn cost posting to G/L off untill client owns the responsibility (though I will still resist).