Aged Account Receivable - aging by document date

Fairul_78

Hi all,

Can anyone help me to solve my problem on the aged account receivable report - aging by document date? It seems that that the report is only filtering on the Posting Date rather than taking it from the document date eventhough the aging By is set to Document Date.

I have 4 customer ledger entries. Only one of those having different posting date and document date. The rest are having the same date in customer ledger entry. However, if i try to view the aging by document date, Navision will skip the one entry that has a different posting date and document date.

Does anyone face any problem on the report. I'm running 4.0 SP1 AP version.

Please help.
Regards,
Fairul

ara3n

what are the posting dates and what are the document dates, as of what date are you aging it?

obviously you are aging it as of date that is latter than the document date.

Alex_Chow

Yes, by default, Navision aging report uses the Posting Date as the basis of filtering for the date. Then it categorizes them based on how you age the report.

So if you have an entry that has a posting date of 1/1/07 and a document date of 12/20/06, you will not be able to see this when you run the aging as of 12/31/06.

This makes sense since you're reflecting this entry on 1/1/07 on your G/L.

Fairul_78

Hi,

These are the posting dates and document dates:(based on dd/mm/yy)

Posting Dates Document Dates
18/09/06 18/09/06
11/10/06 11/10/06
12/10/06 12/10/06
14/11/06 01/11/06

Now i also understand that Navision takes Posting Date as the base of filtering aging information. But quite a number of customers in Malaysia are reflecting the aging by document date. Hence, looking at the sample above, if i were to put 01/11/06 as ending date for rep 120, i will not see the fourth line showing in my aging. Only if i specify 14/11/06 as ending date that i would be able to see the last transaction is reflected into my aging report.

Is there any way that i can make use of the document date basis filtering rather than posting date? If so, that would require a customization, i guess. Will it reflect the report only or can it also extend to the cust. ledger entry table level (customization extension).

sajidhanifkhan

Hi,

In standard report 120 you have to define the period length (e.g 2M) for 2 months or so. and the you can also click a check mark on Print details on the Options Tab.You will have the choice of Aging by Posting date or document date or Due date followed by Age as of date.

I hope you are defining all criterias properly and sure it will give the right result without skiping any single transaction.

regards

Sajid

Alex_Chow

Fairul_78 wrote:

Hi,

These are the posting dates and document dates:(based on dd/mm/yy)

Posting Dates Document Dates
18/09/06 18/09/06
11/10/06 11/10/06
12/10/06 12/10/06
14/11/06 01/11/06

Now i also understand that Navision takes Posting Date as the base of filtering aging information. But quite a number of customers in Malaysia are reflecting the aging by document date. Hence, looking at the sample above, if i were to put 01/11/06 as ending date for rep 120, i will not see the fourth line showing in my aging. Only if i specify 14/11/06 as ending date that i would be able to see the last transaction is reflected into my aging report.

Is there any way that i can make use of the document date basis filtering rather than posting date? If so, that would require a customization, i guess. Will it reflect the report only or can it also extend to the cust. ledger entry table level (customization extension).

It is pretty simple to modify the report to use the document dates instead of posting dates. But you run the risk of not being able to tie to the G/L, since the G/L uses the posting date.

This is not a customization, but more of a "tweak".