Recurring Journal - Balance Method

nverma

[u]The Manual says: [/u]
There are three fields on the Recurring Journal that are populated from the account card and that determine posting for the journal line:
• Gen. Posting Type
• Gen. Bus. Posting Group
• Gen. Prod. Posting Group

Therefore, when I pick a G/L Account on the Recurring Journal Line, it will bring in those fields from the G/L Account card to Recurring Journal Line.

In the Allocation window, when I select a G/L Account to distribute the cost too, it will also bring in those fields from the G/L Account card.

[u]The manual says[/u]
The posting group fields can be filled in on either the recurring journal line or on the allocation line, but not on both. These fields are as follows: Gen.
Posting Type, Gen. Bus. Posting Group, Gen. Prod. Posting Group, VAT Bus. Posting Group, and VAT Prod. Posting Group.

Therefore, system throws me an error. But I don't get it. Is it because, the G/L Accounts that we pick in the allocation window does not need Gen. posting type, gen. bus. posting group, etc defined on the G/L Account card, since we are not going to be calculating (posting) TAX?

nverma

Nevermind. I think I get it.

Since the accounts mentioned in the allocation window act as balancing account for the line amount in recurring journal, we don't need to specify tax on it since its already specified on the Recurring Journal Line. Is that the reason?

jglathe

Hi,

nverma wrote:

Is it because, the G/L Accounts that we pick in the allocation window does not need Gen. posting type, gen. bus. posting group, etc defined on the G/L Account card, since we are not going to be calculating (posting) TAX?

The limitation has been deliberately done in T221 Gen. Jnl. Allocation. I tried it out to disable the CheckVAT() function, and it works nicely with VAT posting on account and allocations. I would see no problem to do this, since there should be no rounding issues whatsoever. And it would be the logical extension of what you can already do in the Gen.Jnl.Line. Does anybody know why this limitation is in place?

I've tested on NAV2009R2 W1 (SITC), btw. But it's the same in NAV2013 (R2).

with best regards

Jens

nverma

I am curious to know why is this limitation put in place?? What is the reason for it?