Executive Summary
A write-off inventory journal entry eliminates inventory from the balance sheet completely. If the inventory is gone, it has no recoverable value: the carrying value, at standard cost or actual cost, leaves the inventory account and is recorded as a loss.
An inventory write-down lowers the carrying value to net realizable value. The inventory still exists and has some value, but less than the ERP currently carries. An inventory adjustment is the wider term for any change to on-hand quantity or value in the ERP, including write-offs, write-downs, cycle count corrections, and quantity adjustments.
Inventory Write-Off vs Write-Down vs Adjustment: The Difference
Each has its own trigger, and the trigger decides which entry posts.
The damaged goods with no resale value, obsolete inventory that cannot be sold or reworked, expired lot-tracked inventory in food, pharmaceutical and cannabis operations, and theft or shrinkage confirmed as permanent loss.
Slow-moving inventory still saleable at a discount, or cosmetic damage that reduces but does not eliminate value, and raw materials that can be substituted only at a lower grade.
A cycle count correction where the system on-hand does not match the physical count, a receiving quantity correction, or a transfer posting error.
Inventory Write-Off Journal Entry in Manufacturing ERP
The inventory write-off journal entry removes the carrying value of the written-off inventory from the balance sheet and records the loss on the income statement. In a perpetual inventory system, which all manufacturing ERPs use, the entry posts when the write-off is approved, not at period end.
Standard cost write-off
Under standard costing, the write-off always posts at standard cost, not the actual cost of producing those specific units. Any gap between standard and actual cost is already in the manufacturing variance account from when the units were produced.
Example: 500 units of Item X are written off due to damage. Standard cost is $8.40 per unit.
| Account | Debit | Credit |
|---|---|---|
| Inventory Write-Off Loss (or Inventory Adjustment Expense) | $4,200.00 | — |
| Finished Goods Inventory | — | $4,200.00 |
The same entry structure applies to a write-off journal entry for obsolete inventory or damaged goods. Only the reason code and the inventory account (raw materials, WIP, or finished goods) change.
Lot-actual cost write-off
In food, pharmaceutical, and cannabis operations using FEFO lot-costed inventory, the write-off posts at the specific lot's actual cost, not standard cost. Different lots of the same item code produce different entries: a lot produced at $9.10 per unit and a lot produced at $8.60 per unit are written off at different values. This is why lot traceability matters at the accounting level.
Example: 200 units are written off from a lot costed at $9.10 per unit.
| Account | Debit | Credit |
|---|---|---|
| Inventory Write-Off Loss | $1,820.00 | — |
| Finished Goods Inventory | — | $1,820.00 |
Write-down journal entry
When inventory is not fully removed but its value drops to net realizable value, the entry records only the reduction.
Example: 1,000 units carried at $8.40 per unit have a net realizable value of $6.00 per unit. The reduction is $2,400.
| Account | Debit | Credit |
|---|---|---|
| Inventory Write-Down Loss | $2,400.00 | — |
| Inventory Reserve (or Inventory directly) | — | $2,400.00 |
The inventory stays on hand in the ERP at the reduced value. When it is eventually sold, COGS posts at the written-down value.
Adjustments Posting Straight to the GL?
20 minutes. Tell us which ERP you run and whether your adjustment workflow requires controller approval before posting. We will tell you what the gap looks like from an auditor's side.
Inventory Shrinkage Accounting: Journal Entry and ERP Handling
Inventory shrinkage is the difference between ERP on-hand quantity and the actual physical quantity, caused by theft, receiving errors, picking errors, or undocumented consumption. In a perpetual inventory ERP, shrinkage is recorded when a cycle count or physical inventory confirms the discrepancy.
In accounting terms, shrinkage is an inventory loss that reduces on-hand inventory below the recorded balance without a corresponding sale or consumption transaction. It is recorded as an inventory adjustment expense on the income statement and reduces the inventory asset on the balance sheet.
Example: a cycle count finds 30 units of Item Y missing. Standard cost is $6.25 per unit.
| Account | Debit | Credit |
|---|---|---|
| Inventory Shrinkage Expense (or Inventory Adjustment Expense) | $187.50 | — |
| Raw Materials Inventory | — | $187.50 |
Once the discrepancy is verified and approved, the entry is posted. A manufacturing ERP handles this as follows:
- The cycle count generates a count variance between the system on-hand and the physical quantity.
- The ERP carries the variance in a pending adjustment state until the controller approves.
- On approval, the journal entry posts automatically, recording who approved it, the count date, and the quantity and value adjusted.
- For lot-tracked inventory, the specific lot must be identified. The system cannot reduce inventory from an unnamed lot, which creates an audit trail linking the shrinkage to a lot record.
Shrinkage is usually discovered through cycle counting and inventory accuracy processes.
Tax note
The write-off journal entry and shrinkage losses are generally deductible in the period the inventory is confirmed as lost or worthless. The specific timing and method depend on the manufacturer's accounting method and tax jurisdiction. Consult your tax advisor before treating a write-off or shrinkage loss as a current-period deduction.
Inventory Adjustment Approval Workflow: Before the GL Posts
In a properly configured manufacturing ERP, an inventory adjustment does not post to the GL the moment an operator enters it. An approval workflow sits between the request and the posting, requiring controller review before the write-off affects financial statements. Without it, a warehouse operator can reduce inventory and affect COGS or write-off expense with no financial oversight.
Adjustment request
A warehouse operator or inventory analyst identifies the discrepancy (physical count, damaged goods, expired lot) and enters the item, quantity, reason code (damaged, obsolete, shrinkage, cycle count correction), and supporting documentation such as a damage report, expiry date, or count sheet.
Controller review queue
The adjustment enters a pending queue. On-hand may be flagged as pending, but no financial impact is recorded yet.
Approval or rejection
The controller checks the request against the reason code, quantity, and documentation. Adjustments above a dollar threshold may need a second approval level. Rejections go back to the requestor with a comment.
GL posting
On approval, the ERP posts the entry automatically (debit Adjustment Expense, credit Inventory), recording the approver, the timestamp, and the inventory transaction that triggered it.
Skipping this workflow is an audit control error. Any user with inventory access can reduce on-hand and move the asset balance and write-off expense unchecked. It is a common finding in manufacturing ERP audits, where the system allows adjustments but does not enforce a pre-posting approval chain.
GrayCyan's AI layer, part of our manufacturing AI solutions, monitors the adjustment queue in real time. It flags requests that deviate from historical patterns, such as quantities far larger than the item's typical cycle count variance, multiple adjustments on one lot in a short period, or submissions from users who do not normally handle that item category.
The controller does not get a raw list but a pre-screened queue with anomalies flagged. Approved adjustments then feed into inventory reconciliation at period close.
Frequently Asked Questions: Inventory Write-Offs and Adjustments
Inventory Adjustments Posting Without Controller Approval?
Tell us which ERP you use, whether your adjustment workflow needs controller approval before GL posting, and whether shrinkage or write-offs are surfacing as audit findings. GrayCyan will help you understand what a properly configured approval workflow looks like, and how AI anomaly detection flags adjustment patterns before they reach the auditor.
See inventory reconciliation across ERP and WMS or ERP inventory management.
