web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics AX (Archived) / Customer aging report ...
Microsoft Dynamics AX (Archived)

Customer aging report as 'in time snap shot'

(0) ShareShare
ReportReport
Posted on by b_radlyjames 3,157

I have a customer who is under the belief that the Customer (or Vendor) aging report should be an 'in time snap shot' of the customer.  Let me give an example:

Aging report run ON Dec. 31 for Dec. 31 (Start date, Balance as of date) and then let's say Customer A has a balance of $50.

They then run that same report with the same parameters on Jan. 15.  If Customer A has paid the $50 then that aging report wouldn't be the same as the previous one.

This seems correct to me based on the code (CustVendAgingCalculation class) and the definition of this report on technet:

The Customer aging report displays the balances that are due from customers, sorted by date interval or aging period.

The customer is expecting it to be the same.  They think if they run it for Dec 31, no matter what day they run it on, it should show the same report every time.  In their mind it should show what WAS due at that time.

Am I right in thinking that this report is NOT an 'in time snap shot'?

UPDATE:

The 'buckets' on the report appear to be the ones that are changing.  The Total is good.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    The Customer aging report is designed to show the state of the customer on the "as of" date.  It will ignore transactions with a transaction date after the "as of" date.  For transactions that occur before, and are shown, it will calculate the amount that was open on the "as of" date by reversing the settlements that occurred afterward.  It will do exactly what you customer expects provided no transactions are backdated between running the two reports.  In other words, if someone inserts new transactions prior to 12/31, the report will consider them valid and not "notice" that they were inserted on a later date.  The transaction date drives everything.

  • b_radlyjames Profile Picture
    b_radlyjames 3,157 on at

    Brandon,

    Thanks for the response!  You make a lot of sense. In one instance I am seeing a 'backdated' transaction that shows up after.  In another instance, I am seeing amounts that are shown on the Original report but then are gone on subsequent reports.  Should that happen?

  • Verified answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    The backdated transaction, if it follows my example where it was posted after 12/31 (say on 1/14) but using a date on or prior to 12/31, should appear on a report run on 1/15 with an "as of" date of 12/31.  By backdating the transaction, it now occurred in the prior year for all intents and purposes, regardless of when it was actually posted.

    There are cases where an amount that is open on 12/31 fails to appear on the Customer aging report with an "as of" date of 12/31.  In one specific case, the "last settled date" on the CustTrans record was wrong (it was 12/22 when it should have been 1/7), and so the report did NOT include the transaction because it determined based entirely on the last settled date that it was already closed as of 12/31, when in fact it was not.  So without specific details as to what you are seeing and the underlying state of your data, I can only suggest possibilities as to why a report run on 12/31 and a report run on 1/15 with an "as of" date of 12/31 might differ.

    But, to answer your original question, the report is designed to present an accurate "as of" picture for the given date by "rolling back" everything that happened afterward, which may not arrive at a perfect picture in some cases but in general works very well.  The Inventory value report does the same things, but for inventory.

  • Suggested answer
    Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    If you can trace down one of your issues to a problem in the data, you might be able to repair the data.  I also have SQL queries that detect these kinds of data corruption, i.e. where the last settled date does not jive with the maximum date on the CustSettlement table, and so on.  It's unfortunate, but it happens.

  • b_radlyjames Profile Picture
    b_radlyjames 3,157 on at

    Brandon,

    Ok.  Thanks for all the help.  One thing I should have mentioned is that the 'Balance as of (date)' is always correct for the day you select.  It's the 'Buckets' (Future, Today, 1-60, 61-90, etc...) that seem to be jumping around.

  • Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    I prefer to never use aging buckets.  Just set it to backward and specify 30 days, or whatever.  I think that just works a whole lot better.

    Please mark as answered if you found this helpful and think it will help others.

  • b_radlyjames Profile Picture
    b_radlyjames 3,157 on at

    Buckets is what we use.  Nothing I can do about that.  I will have to look into the buckets.

  • Brandon Wiese Profile Picture
    Brandon Wiese 17,788 on at

    If you can reproduce the problem reliably and simply, I might be able to debug on my end and figure out what's wrong.

  • Suggested answer
    b_radlyjames Profile Picture
    b_radlyjames 3,157 on at

    Brandon,

    Thanks!  I think I have found the issue here.  The 'buckets' all come from CustTrans.  At some point, CustTrans must be changing (adding new transactions) which is causing the buckets to change.

    We are going to restore a backup of our database on the day the report would be run (So Dec. 31 FOR Dec. 31) and then take a look at CustTrans.  This should give us a good lead to figure it out.  Thanks!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Alexey Lekanov Profile Picture

Alexey Lekanov 2

#2
Henrik Nordlöf Profile Picture

Henrik Nordlöf 2 User Group Leader

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans