Inventory aging report: reconcile the stock still on hand

Build an inventory aging report from the stock remaining at a defined cutoff, attributed to dated receipt records under a declared issue-allocation rule. Group those remaining quantities into nonoverlapping age buckets, retain missing dates as unknown, and reconcile the result to owned on-hand stock and its selected inventory value. That establishes how much of the balance has each reported age.

A recent warehouse movement can make an old component appear young if the report uses the latest transaction date. Before acting on an aging total, inspect which date starts the clock, how consumption reduced the receipt quantity, and whether transfers or returns changed that date. The same item total can support different age distributions when those rules differ.

Establish the date rule and the stock population

Record the legal entity, locations, stock statuses, base unit, time zone, and cutoff. Decide whether the population includes owned stock in transit, quarantined material, and goods held elsewhere. Keep ownership separate from availability: stock awaiting inspection can still belong in the owned inventory total even while it is unavailable for production.

Receipt age, inactivity, and expiry answer different questions. Receipt age measures elapsed time from the selected receipt date; inactivity measures time since a defined qualifying event, such as the last customer issue. Expiry compares the cutoff with an assigned expiration date. A transfer may change a movement timestamp while leaving both original receipt age and expiry unchanged.

Microsoft’s Business Central report 5808 documentation, updated April 1, 2026, describes aging on-hand quantities and values using remaining open inbound item ledger entries. Those entries can arise from purchases, production output, or positive adjustments, and their posting dates determine the buckets. Its configurable equal-length periods are not identical to the custom buckets used in the example below.

State whether your report uses that native posting-date logic or an analytical date retained from another source. A production-output date ages finished goods from that event; it does not establish the age of every component consumed. A count adjustment dated today may establish a recorded balance without establishing when the goods originally entered the business.

Allocate issues before aging the remaining quantity

A receipt register alone overstates stock when some of its quantity has been consumed or sold. Retain each receipt’s original quantity, linked issues, corrections, and remaining quantity at the cutoff. Where physical lot or application links exist, use them under the approved method. Where they do not, label the allocation convention and avoid presenting it as observed physical consumption.

Microsoft’s Dynamics 365 Supply Chain Management aging logic, updated July 1, 2026, summarizes receipts into periods and deducts issues using first in, first out (FIFO), regardless of the item’s inventory model. It calculates bucket amounts using average unit cost at the financial inventory dimension. Warehouse rows can repeat site-level financial values, so reconcile at the dimension’s grain before summing. That report allocation does not establish a company’s financial FIFO policy or prove which physical unit shipped.

Reconcile the underlying balance before interpreting age. The inventory reconciliation process aligns movements, units, locations, and cutoffs. Keep negative remaining quantities and unallocated issues in an exception view; spreading them across old buckets to reach a total hides the unresolved allocation.

Reconcile explicit age buckets to quantity and value

Consider a hypothetical component held across two owned warehouses as of November 3, 2026, at 23:59:59 America/Chicago. Use calendar-date differences (in the stated time zone), with receipt day counted as age zero. The nonoverlapping buckets are 0-30 days: October 4 through November 3; 31-60 days: September 4 through October 3; 61+ days: September 3 or earlier. The boundary dates refer to 2026; the oldest bucket also includes earlier years.

Assume R1 received 200 units on September 1, R2 received 100 on September 19, and R3 received 80 on October 24. Source-linked issue records are assumed to assign 150 units to R1 and none to R2 or R3. Another separately identified opening lot contains ten unissued units with no supported receipt date. There are no other receipts, issues, returns, or adjustments affecting the balance.

For this example, finance selects a uniform management-report value of $10 per remaining unit in US dollars. This is an assumed valuation input, not a financial accounting recommendation or a claim about actual receipt-layer costs. All quantities use individual units, and the same $10 basis applies to both the bucket values and the comparison inventory total.

The movement balance is 10 opening + 200 + 100 + 80 receipts - 150 issues = 240 units. The aging check is 80 + 100 + 50 dated units + 10 unknown = 240. Values reconcile as $800 + $1,000 + $500 + $100 = $2,400, matching 240 × $10. Only 50 units remain from the oldest receipt; assigning all 200 to the oldest bucket would ignore the assumed linked issues.

Keep transfers and returns distinct from new purchases

Now assume ten of R1’s remaining units transferred between the owned warehouses on November 1. Under this example’s declared company-wide original-receipt rule, they remain 63 days old on November 3. Their location changed two days earlier, but the transfer does not add another ten units to the company’s inventory or reset the retained September 1 receipt date.

Native report behavior can differ. Microsoft’s Supply Chain Management example shows that adding warehouse detail changes the age distribution: a same-site transfer ignored at site level appears in the warehouse-level buckets. Preserve the selected grouping and transfer treatment with every saved report, so a changed layout is not mistaken for stock becoming younger.

A supplier return reduces the stock in scope. A customer return increases stock but needs an approved date rule: retain supported original history or keep the age unresolved while that history is investigated. The lot traceability process explains how receipt and movement links support that investigation. Similar descriptions and matching quantities cannot establish the returned lot’s identity on their own.

Assign stock actions after checking demand and condition

Give the inventory owner the oldest supported quantities and the unknown-age exceptions, with source references. Review open demand, approved substitute uses, physical condition, and storage constraints before selecting an action. A service part held for a known maintenance need and a discontinued component can share an age bucket while requiring different decisions.

Use the inventory turnover ratio to assess movement relative to average inventory over a period. It complements the cutoff aging balance. A single new issue can change inactivity while leaving substantial old stock, so retain receipt-age and demand evidence alongside movement measures.

Quality owns release and condition decisions; purchasing can investigate supplier-return options; finance owns valuation and any loss treatment. An age threshold alone does not authorize disposal, a markdown, or a write-down. Keep the selected action, approver, and unresolved assumptions with the report rather than converting every old row into the same recommendation.

Where Permute fits in an aging review

Permute sells connected business data, custom applications, and AI grounded in business records. We support permitted source connections, uploaded files, and reusable transformations. A scoped aging report can combine supplied inventory balances and movement records while retaining the receipt and issue references behind each remaining quantity.

We can apply your declared cutoff, date rule, issue allocation, and selected value basis. Item mappings, units, and warehouse identities need resolution before those rules produce comparable totals. Missing receipt history remains a visible unknown; a new report cannot reconstruct an original date without supporting evidence.

An inventory lead could inspect an old balance, identify the receipts and issues behind it, and see whether a transfer affected the reported age. The proposed output depends on available history and source fields. Verify those inputs and refresh behavior before relying on a recurring review, especially when earlier snapshots exist only in exports.

Keep valuation and disposal under the existing policy

We read supplied or connected records for this reporting workflow. It does not change inventory, post a write-down, or dispose of stock. Finance and operations retain their accounting and approval policies. Reconcile amounts to the selected inventory value before comparing periods; Microsoft’s aging report documentation notes that inventory closing can update its cost values.

An inventory aging report should explain the remaining stock through dated quantities and a separate unknown balance. Keep the cutoff, issue allocation, transfer treatment, and value basis attached to the result. Reconcile both quantities and amounts before interpreting a change in old stock. Use the resulting evidence to assign a review owner, with stock actions approved under the existing policy.

Questions about receipt-age reporting