Inventory Aging Report Shows Different Age Between Single and All Locations

Inventory Aging Report Shows Different Age Between Single and All Locations

Q: When I run the Inventory Aging Report for a single location, the age of the same inventory is more recent than if I run it for all locations.  How could that happen?

A: When you run an Inventory Aging Report for "All" locations, we use the "last receive date" (i.e., the date received from the PO or IM modules) for aging purposes.  When you use single location, we use either "last receive date" or "last transfer receiving date."  In this case, you probably have some recent transfers to this location, which causes the system to consider that as the age date and distort the aging calculation.

Why do we use two different standards between single and multiple locations?  This is because in a single location scenario, it is quite possible that there are no receiving transactions for that location.  Therefore, to limit aging calculation to receiving transactions only may cause a problem for a single location aging calculation. On the other hand, if we calculate aging for all locations, it would be reasonable to expect that the receiving takes place for at least one of the locations. Using that receiving transactions for aging would be accurate.

So when you run an Aging Report for a single location and multiple locations, the aging value may not match.  The bottom line is that it is not possible for us to give you accurate aging information for a single location if there are transfer transactions.  The aging report for all locations will always show the true aging information for your organization regardless of whether you use transfer transactions or not.

Please also refer to the following similar knowledge base article on this issue:






    • Related Articles

    • Limitations for Inventory Aging Report

      Release Date: 08/15/2018 The Inventory Aging Report is a very valuable tool. It is primarily used to determine the aging of the inventory for all locations for the current date, but you could use it for a specific location or use it to determine the ...

    • Inventory Aging Report by Location Sequence Produces Different Result Than by Other Sequence

      Q - When I run I/M -> Reports -> Inventory Aging Report, if I choose to run by "location" sequence, the aging result is different than if I run by another sequence (e.g., by item). See sample screen below. Why is that? A - There's an inherent design ...

    • ARAGEMNU Accounts Receivable Aging Reports

      Reports Aging Reports Application Overview The Aging Reports are reports that can tell you a great deal about the state of a customer's account. It will tell you how much the customer owes you, and how old these owed amounts are. In A/R Setup, you ...

    • ARAGEBAL Accounts Receivable Age Customer Accounts

      Age Customer Accounts Application Overview In the Customer file there are four fields that store the age amounts for period‑1, period‑2, period‑3, and period‑4 for each customer as of the last age date. The primary use of these fields is for display ...

    • Aging Shows Differently After Database Rebuild

      Q - After the database rebuild on A/R Open Item File (AROPNFIL.BTR), the A/R aging shows differently than before. For some reason, the payments are showing before the invoices. Also, they are not in any logical order that we can see. Here are the ...