News and Announcements icon

Dynamics 365 CommunityForums Microsoft Dynamics SL (Archived) SL2015 AR - IN and CM ...

Microsoft Dynamics SL (Archived)

SL2015 AR - IN and CM hanging on Aging- posted to future period

(0) Share

Report

Report

Posted on by NorK

290

Hello,

We have an invoice and Credit memo hanging on the current Period Sensitive AR Aging. The entries net to $0.

We are looking to have them no longer appear on the aging. The issue is related to postings to year 2099

Both are applied as follows:

Invoice - posted 02-2099

--Payment Applied – posted 03-2009 (Actual Period)

CM - posted 02-2099

--Invoice Applied - posted 02-2009 (Correct Period)

Is there a way to remove these from the aging so we no longer see the Debit and Credit?

Thanks!

*This post is locked for comments

All responses Img

All responses (2)

Answers Img

Answers (1)

NorK 290 on at

Like (0)

Report

RE: SL2015 AR - IN and CM hanging on Aging- posted to future period

Thanks! Editing PerClosed removed the documents from the aging.
Verified answer

Community Member Microsoft Employee on at

Like (1)

Report

RE: SL2015 AR - IN and CM hanging on Aging- posted to future period

You actually have more than just an AR aging issue here. Both that invoice and that credit memo that were posted to 02-2099 have yet to be reflected on the GL side and will not be until period 2 of 2099. You may have already addressed this with some sort of JE entries.

The reason that the AR aging still shows these is due to the incorrect posting period (as you surmised). The logic in the aging report view considers these items as future period items so they appear as open documents in both the period sensitive aging and the regular aging until AR reaches 02-2099.

If you have access to SQL Server Management Studio and are comfortable with running a couple of SQL update statements you could do the following:

update ardoc set PerClosed = 200903 where refnbr = 'nnnnnn' (where nnnnnn is the reference number of the invoice)

update ardoc set PerClosed = 200902 where refnbr = 'nnnnnn' (where nnnnnn is the reference number of the credit memo)

The above does not correct the incorrect posting period on those 2 documents but will cause the aging to treat these as closed documents (in a period prior to your current period).

Helpful resources

Quick Links

Leaderboard

#1

André Arnaud de Cal... 291,280 Super User 2024 Season 2

#2

Martin Dráb 230,214 Most Valuable Professional

#3

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans