Inventory reporting: metrics, reports, and checks

Inventory reporting should show what stock you hold, how it changed, what it is worth, and which exceptions need action. Begin with a quantity reconciliation by SKU and site, then add value and aging views that use the same cutoff. A report becomes useful when each exception has an owner and a decision attached.

Set the scope before collecting files

Write the cutoff, locations, stock statuses, unit of measure, ownership scope, and currency at the top of the reporting pack. A warehouse count, an available-to-promise quantity, and the balance sheet inventory account describe different things. Label them separately.

Ask operations for opening and closing stock snapshots and the period's movement export. Ask finance for the valuation export and the relevant ledger control balance. Ask purchasing for open purchase orders only if the review includes future receipts. Preserve document IDs so an unusual total can be traced to its source.

Ownership needs particular care. The IRS inventory guidance includes purchased merchandise when title has passed, even if it is in transit, and emphasizes consistent inventory practices. That is tax guidance; for the management pack, have finance define the accounting scope instead of assuming everything physically present belongs to the business.

Build a small set of connected reports

Keep the family connected by shared SKU and site keys. A value report grouped by product description will not join reliably to a movement export grouped by item number. Use the stable code and retain descriptions as labels.

Turnover belongs in a periodic efficiency view rather than replacing these reports. The detailed inventory turnover guide owns its formula. For a workbook devoted to building the movement schedule, use the Excel stock movement tutorial.

Reconcile a worked stock export

A US distributor reviews movements from October 1 through October 23, 2026. Every quantity below is measured in individual units. Adjustments are signed; a negative adjustment reduces stock. The unit costs are the valuation export's approved costs at the closing date, not selling prices.

Place this source table in A1:I4. Column I contains days since the last issue at the cutoff, supplied by the operational report.

In J2, calculate expected closing stock. In K2, calculate reported less expected stock. Fill both through row 4:

=C2+D2-E2+F2
=G2-J2

In L2, calculate closing value. In M2, flag the value with no issue for at least 180 days:

=G2*H2
=IF(I2>=180,L2,0)

The quantity control is 220 opening units + 160 receipts - 220 issues - 2 adjustments = 158 closing units. It checks the export as a whole; replenishment still needs the individual SKU and site rows. Never allow offsetting differences to disappear inside a zero total.

Turn reconciled rows into a decision summary

For the East site's closing value, sum L where B equals East. Microsoft documents SUMIFS as adding values that meet multiple criteria, so SKU and status conditions can be added when needed:

=SUMIFS(L2:L4,B2:B4,"East")

That returns $4,660: $1,160 plus $3,500. West holds $600, and the site values reconcile to $5,260. The dormant share of closing value is:

=SUM(M2:M4)/SUM(L2:L4)

The result is 3,500 / 5,260 = 66.5%, rounded to one decimal place. Keep unrounded values in the calculation. This high share directs the review toward B at East; it does not establish that its $3,500 carrying value is unrecoverable.

Define aging carefully. Days since last issue is a dormancy measure: a small recent issue can make old remaining units appear active. Receipt-lot aging measures something else. The inventory aging definition and aging by site example explain the distinction and the underlying rows.

Tie the valuation total to the finance export, then reconcile that export to its ledger control using documented exclusions. Quantity rollforwards do not prove inventory value when costs change. Keep reserves, write-downs, owned goods in transit, and other scope differences visible rather than forcing them into unexplained adjustments.

Covirage is not affiliated with Microsoft.

Assign an action to every material exception

Operations owns unexplained quantity movements and physical-count follow-up. Purchasing owns replenishment decisions after checking demand and confirmed receipts. Finance owns valuation policy and the ledger bridge. Commercial teams can help decide whether dormant stock needs transfer, promotion, or a revised assortment.

Record the exception, source document, responsible person, proposed action, and next review date. A repeated discrepancy should remain visible until its cause is resolved. A fresh export does not itself close last period's issue. Present the largest cash exposures separately from urgent service exceptions so one ranking does not hide the other.

Where it goes wrong

• Mixing cutoffs. A receipt included in movements but absent from the closing snapshot creates a false discrepancy.
• Double counting transfers. A transfer has an issue at one site and a receipt at another. Keep both legs and consistent timing.
• Using blanks as zero. Missing costs and missing last-issue dates need an exception label, not invented certainty.
• Netting differences across keys. Equal and opposite errors can make the total reconcile while both sites remain wrong.
• Reading dormant value as a write-down. Age starts a review; an approved accounting conclusion requires additional evidence.

Run inventory reporting on your own file in Covirage

Bring stock snapshots, movement rows, and a valuation file with consistent SKU and site identifiers. Covirage maps the columns, and its tools compute and check the figures; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for supply chain teams for the wider business context.