What is Inventory Adjustment and Write-Off?

Inventory Adjustment and Write-Off is an ERP workflow guide for Inventory & Warehouse Management. It focuses on Inventory Adjustment.

What should a finance team verify before implementation?

Given on-hand inventory and an adjustment request with reason code; when the request is approved (or auto-approved below threshold); then on-hand qty changes and a GL journal posts atomically debiting the expense account and crediting Inventory at current cost; (negative) when adjustment is attempted in a locked period then 422 PERIOD_LOCKED; (negative) when adjustment value exceeds threshold without approver then 403 APPROVAL_REQUIRED.

Inventory Adjustment and Write-Off

Inventory Adjustment is where ERP discipline either begins or breaks.

Inventory Adjustment and Write-Off looks operational from far away. In a real finance team, it is a chain of assertions: the right actor started the work, the required records existed, the control policy was applied, the state change was preserved, and the outcome can be explained later without rebuilding the transaction from emails and spreadsheets.

The expected business outcome is specific: Every quantity variance has a corresponding GL entry; write-offs properly expensed; shrinkage visible by reason and category for loss-prevention analysis.

The control flow a finance team actually needs.

Workflow map for this ERP process, including exception handling and audit evidence.

Step 1

Adjustment Types: Positive, Negative,...

Step 2

Reason Code Mandatory

Step 3

Approval Workflow For Adjustments Above...

Step 4

GL Journal Posted Atomically With...

Step 5

Costing Method Determines Value

The ERP surface involved.

Module

Inventory Adjustment

Actors

Warehouse Supervisor, Inventory Accountant, Platform API

Tier

Tier 1

Finance area

Inventory & Warehouse Management

Region lens

US and UK finance teams

Publication date

May 3, 2026

Adjustment types: positive (found stock), negative (loss/damage), and write-off (zero residual value); reason code mandatory (configurable list); approval workflow for adjustments above configurable dollar threshold; GL journal posted atomically with quantity change; costing method determines value (FIFO layer pop, weighted avg, or standard cost); adjustment reversal supported within same period; complete audit trail: who, what, when, reason, approver; reporting: adjustments by reason code, item, period, and location; prohibition on adjustments in locked periods.

US and UK teams have different compliance hooks, but the same control problem.

US teams usually care about clean evidence for audit support, vendor records, payment controls, tax reporting, and management review. UK teams usually care about VAT-ready records, approval evidence, digital-record discipline, and traceable postings. The country-specific details differ, but the operating pattern is the same: the ERP needs controlled records, explicit ownership, defensible state changes, and evidence that survives beyond the person who completed the task.

The control matrix.

Control area	Requirement	Acceptance proof
Control 1	Adjustment types: positive (found stock), negative (loss/damage), and write-off (zero residual value	Given on-hand inventory and an adjustment request with reason code
Control 2	reason code mandatory (configurable list	when the request is approved (or auto-approved below threshold
Control 3	approval workflow for adjustments above configurable dollar threshold	then on-hand qty changes and a GL journal posts atomically debiting the expense account and crediting Inventory at current cost
Control 4	GL journal posted atomically with quantity change	negative) when adjustment is attempted in a locked period then 422 PERIOD_LOCKED
Control 5	costing method determines value (FIFO layer pop, weighted avg, or standard cost	negative) when adjustment value exceeds threshold without approver then 403 APPROVAL_REQUIRED.
Control 6	adjustment reversal supported within same period	Every quantity variance has a corresponding GL entry; write-offs properly expensed; shrinkage visible by reason and category for loss-prevention analysis.

Audit evidence is a chain, not a folder.

Evidence layer	What should be preserved
Business event	A warehouse supervisor identifies a damaged or missing item and initiates an inventory adjustment request, specifying item, location, quantity change, reason code (damage, theft, spoilage, write-off), and supporting notes. The request routes to the inventory accountant for approval if the value exceeds a threshold. On approval, the system decrements on-hand quantity and posts a GL journal debiting the appropriate expense account (e.g., Inventory Write-Off) and crediting the Inventory asset account at the item's current cost. A reference document number is stored for audit.
Control rules	Adjustment types: positive (found stock), negative (loss/damage), and write-off (zero residual value); reason code mandatory (configurable list); approval workflow for adjustments above configurable dollar threshold; GL journal posted atomically with quantity change; costing method determines value (FIFO layer pop, weighted avg, or standard cost); adjustment reversal supported within same period; complete audit trail: who, what, when, reason, approver; reporting: adjustments by reason code, item, period, and location; prohibition on adjustments in locked periods.
Acceptance proof	Given on-hand inventory and an adjustment request with reason code; when the request is approved (or auto-approved below threshold); then on-hand qty changes and a GL journal posts atomically debiting the expense account and crediting Inventory at current cost; (negative) when adjustment is attempted in a locked period then 422 PERIOD_LOCKED; (negative) when adjustment value exceeds threshold without approver then 403 APPROVAL_REQUIRED.
Data record	`inventory_adjustment { id: string, external_id: string, entity_id: string, item_id: string, location_id: string, adjustment_qty: int, adjustment_type: enum(POSITIVE,NEGATIVE,WRITE_OFF), reason_code: string, notes: string, cost_minor: int64, currency_code: char(3), gl_journal_id: string, approved_by: string, status: enum(PENDING,APPROVED,POSTED,REVERSED) }; (reference, product may differ).`
System event	`POST /v1/inventory-adjustments { item_id, location_id, adjustment_qty, adjustment_type, reason_code, notes, external_id } -> 201 { id, status, requires_approval: bool }; POST /v1/inventory-adjustments/{id}/approve -> 200 { gl_journal_id }; POST /v1/inventory-adjustments/{id}/reverse -> 200; GET /v1/inventory-adjustments { filters: reason_code, item_id, period }; emits inventory.adjustment_posted event; idempotent via external_id.`
Lifecycle state	`PENDING -> APPROVED -> POSTED; terminal REVERSED; guard: POSTED blocked in locked period; reversal allowed within same period only; write-off sets residual value to zero.`

The useful version of this workflow is not only fast. It is inspectable. A controller, auditor, or operator should be able to move from source event to system record to state transition to final business outcome without guessing.

Implementation contracts.

Reference data model

`inventory_adjustment` { id: string, external_id: string, entity_id: string, item_id: string, location_id: string, adjustment_qty: int, adjustment_type: enum(POSITIVE,NEGATIVE,WRITE_OFF), reason_code: string, notes: string, cost_minor: int64, currency_code: char(3), gl_journal_id: string, approved_by: string, status: enum(PENDING,APPROVED,POSTED,REVERSED) }; (reference, product may differ).

API and events

`POST /v1/inventory-adjustments` { item_id, location_id, adjustment_qty, adjustment_type, reason_code, notes, external_id } -> 201 { id, status, requires_approval: bool }; `POST /v1/inventory-adjustments/{id}/approve` -> 200 { gl_journal_id }; `POST /v1/inventory-adjustments/{id}/reverse` -> 200; `GET /v1/inventory-adjustments` { filters: reason_code, item_id, period }; emits `inventory.adjustment_posted` event; idempotent via `external_id`.

State transitions

`PENDING -> APPROVED -> POSTED`; terminal `REVERSED`; guard: POSTED blocked in locked period; reversal allowed within same period only; write-off sets residual value to zero.

Common implementation traps.

Treating the workflow as data entry

If the ERP only stores the final record, the team loses the decision trail that explains how the record became valid.

Hiding exception logic

Exceptions need owners, reason codes, and time stamps. A vague pending state is not a control.

Posting without recovery design

Retries, duplicate submissions, and partial failures must be explicit so the system does not create inconsistent records.

Skipping evidence design

A workflow that cannot produce evidence on demand will eventually push finance teams back into manual screenshots and spreadsheets.

Where Rivane fits.

Rivane is built for finance workflows where automation must stay tied to source documents, approvals, state transitions, ledger impact, reporting, and audit evidence. Use this guide as a checklist for evaluating whether an ERP workflow is merely digitized or actually controlled.

References and source basis.

These sources provide the standards, regulatory, or government context around the flow. They are included so the guide is useful to finance operators, auditors, and implementation teams, not only buyers reading software copy.

Back to ERP use cases