Key takeaway
A return credit cannot tell you where goods went. Account for every received unit and keep outstanding, quarantined and credit-only cases separate.
Return approval is the beginning of a quantity history
A return authorization can remain open after only part of the goods arrive. A refund can also exist without a physical return. Before describing returns as a record of waste, recovery or resale, reconcile quantities across authorization, receipt, inspection decision, inventory posting and credit. Keep the original unit of measure and item identity so a case of ten does not become ten cases.
Microsoft’s Dynamics documentation distinguishes a reason for returning goods from their disposition. Its sales-return process also distinguishes authorizing a physical return from acceptance and credit. These product examples were checked 8 October 2026; your actual system and agreements may differ. Use them to ask what each status means in your archive rather than treating a generic return label as proof of a physical event.
Complete a split-quantity ledger
This hypothetical request R70 authorizes 12 units of item J. Nine arrive. The local reviewer assigns five to restocking, three to scrap and one to quarantine pending a decision. The remaining three authorized units have not arrived. A separate request R71 produces a two-unit credit without requiring a return. Those two credited units belong to a financial event, not R70’s received population.
The completed reconciliation is nine received equals five restocked plus three scrapped plus one still quarantined. Three authorized but unreceived units remain outside that physical equation. Restock and scrap postings are present in the illustration; quarantine has no final disposition. A review that simply sums both requests’ credited quantities would misstate physical throughput. No refund amount, environmental outcome or resale value is inferred from these invented quantities.
| Request / quantity | Completed illustrative evidence | Ledger treatment |
|---|---|---|
| R70: 12 authorized | 9 received; 3 not received | Keep authorization separate from arrivals |
| R70: 5 received | Restock decision and stock posting linked | 5 physically assigned to restocking |
| R70: 3 received | Scrap decision and stock reduction linked | 3 physically assigned to scrap |
| R70: 1 received | Quarantine receipt; decision pending | 1 in quarantine; no final outcome |
| R71: 2 credited | Credit-only request; no physical receipt | Financial count only; excluded from R70 |
Keep the decision and posting references together
The approved disposition explains what should happen; a stock posting explains what the inventory system recorded. Preserve the link between both and the received line. If the archive retains the decision but not its posting, identify the evidence gap. A displayed restock code should not silently become confirmed available stock. Reconciliation may expose a missing posting, an authorized reversal or a workflow that was never completed.
Microsoft describes splitting a return line when quantities receive different disposition codes or only some arrive. It also separates the physical update associated with the packing slip from the invoice update. This is useful evidence vocabulary for a reviewer: identify which event supports a stock movement and which supports a financial credit. A consolidated export may collapse them, so ask for documented source relationships before drawing a quantity conclusion.
Do not infer recovery from a broad disposition label
A scrap instruction does not establish the material’s eventual recycling route. A restock posting does not establish that a unit was sold again. If remanufacturing or material recovery is the proposed subject, identify its separate process records and actual completed quantities. Keep pending work distinct from completed output, and do not extend the return ledger into a circularity or savings claim without that additional evidence.
Check reversals, reopened cases and corrected receipts using their original references. In the illustration, a later decision on the quarantined unit changes its state and adds the corresponding posting; it should not add a tenth arrival. If a restocked unit is subsequently scrapped, the ledger needs the move out of restock as well as the new disposition. A current-state count alone can conceal that history.
Keep the reconciliation’s cut-off date beside its quantity states. The one quarantined R70 unit belongs in the unresolved queue at that cut-off, even if a later export displays its eventual disposition. A current snapshot can answer where the unit is now; the earlier ledger answers what was known during that review. Preserve both when reconstructing a decision, and reconcile the quantity transition rather than retrospectively presenting all nine units as already resolved.
Define a release boundary that preserves the reconciliation
A metadata description can state which quantity events and distinctions are retained without exposing customer return reasons or actual product problems. Inspect free-text complaints, serial numbers, delivery addresses and confidential product findings before any sample. If identity links are narrowed for disclosure, test that the approved representation can still reconcile split lines without accidentally combining different requests. Do not claim that removing customer names settles every disclosure issue.
The next internal review assigns receiving to arrivals, inventory control to postings and finance to credit-only cases. Record unresolved discrepancies and the exact period covered. Inventory helps capture that structure, while readiness identifies missing decisions. An evaluator’s interest in recovery data is a question about a proposed use, not proof of a buyer or a license. VOID’s named introduction stage does not authorize the underlying records to leave the business.