Approve an inventory adjustment only after establishing the physical quantity error, the appropriate transaction type, and the expected value effect. A quantity that looks correct after saving can still carry the wrong cost, location, lot detail, or posting period.
The review should answer why the source transaction cannot be corrected through its supported process, what quantity will change, how costing will respond, and who will verify the result. Inventory adjustments are useful controls when supported by evidence; unexplained adjustments make later reconciliation harder.
Start with the cause. A missing purchase receipt, duplicate fulfillment, wrong transfer destination, or incorrect unit conversion may require correction of the original process. An adjustment should not conceal an outstanding purchase or sales document.
For a genuine count difference, damage, loss, or approved opening correction, document the evidence. Identify item, subsidiary, location, quantity and unit, bin, lot or serial, and status. The scope needs to match the physical finding.
Separate quantity correction from cost-only questions. A business seeking to change an inventory valuation should not create artificial quantities simply because the adjustment form is familiar. The accountant should choose the supported method for the item and costing configuration.
An inventory adjustment records a change to quantity and its resulting value. An inventory worksheet establishes a specified quantity or value at its effective point, with behavior that can override the effect of earlier-dated stock totals.
The worksheet does not support lot-numbered or serialized items. It also averages FIFO or LIFO costing history rather than preserving those layers. An ordinary inventory adjustment preserves that costing history. These differences make the two forms unsuitable as interchangeable shortcuts.
Confirm the item's costing method and supported transaction type before preparing a file or form. Standard costing and other account-specific configurations require their own reviewed treatment. Do not infer the correct accounting method from the most convenient screen.
For every proposed line, show current quantity, proposed quantity change, expected ending quantity, relevant current value, proposed or system-derived cost treatment, adjustment account, date, and posting period. Include the evidence and approval reference.
Check positive and negative lines separately. For average-cost additions, the estimated unit cost can be changed. For a negative Adjust Qty By amount, NetSuite calculates the removed inventory cost and does not allow entry in the Est. Unit Cost column. Do not assume one entered rate works symmetrically for both directions.
Normalize units before valuing the quantity. If the adjustment is in cases but the reviewed cost is per individual unit, the expected value can be wrong by the pack size. Keep the conversion visible in the review packet.
A verified count identifies ten additional units of an average-cost item. Before the adjustment, the simplified balance is 100 units valued at $2,000. The accountant approves a $24 unit cost for the ten-unit increase in this illustrative example.
The expected increase is $240, giving 110 units and $2,240 of value before any other transactions. The resulting simple average is approximately $20.36 per unit. The reviewer should expect both quantity and value to change, not merely the stock count.
If the operator enters $240 as the unit cost instead of the total increase, the proposed addition becomes $2,400. The ending quantity would still look correct, but value would be materially wrong. A line-level expected-value check catches the error before posting.
This example deliberately excludes other transactions, costing recalculation, landed costs, and rounding details. Actual posting and valuation must be checked in the account. It is an approval calculation, not a substitute for the system's complete costing engine.
Backdated adjustments can trigger costing recalculations. A backdated worksheet can have broader recalculation scope than an ordinary adjustment. Historical edits can affect subsequent transactions, so the oldest effective date and affected item population belong in the approval request.
Inspect report warnings and cost-accounting processing status before relying on a final value. A saved transaction does not guarantee that every related report has completed its costing update. Retain before-and-after evidence once processing is complete.
Closed-period changes require accountant-owned review. Do not reopen periods, change dates, or alter accounting preferences simply to make an adjustment easier. The legitimate event date, reporting consequences, and company close policy should drive the decision.
An item-location total is not enough for numbered or binned stock. Confirm the exact lot, serial, bin, and status affected. A reduction from the wrong lot can distort traceability even if the item total and GL amount appear reasonable.
Check whether the stock is owned, vendor consigned, or held under another arrangement. Dedicated consigned-inventory processes can have different consumption and accounting consequences. Do not use an ordinary adjustment assumption for every ownership category.
For assemblies, understand whether the proposed transaction changes only finished inventory or also represents component activity. An adjustment is not automatically a build or unbuild. Finance and manufacturing should approve the intended operational meaning before posting.
Use both value and quantity criteria, with special review for controlled items, repeated adjustments, historical dates, and unusual accounts. A low-value adjustment can still damage lot traceability or release held material if inventory detail is wrong.
The preparer should not be the only person deciding that the evidence is sufficient. Match approval and verification responsibilities to the organization's policy and available workflow. Do not claim an approval is automatically enforced unless the actual role and workflow design has been tested.
Record a meaningful reason. “Count variance after documented recount” is more useful than “inventory fix.” Include the count or incident reference so a future reviewer can reconstruct the decision without locating the original employee.
For a CSV import, verify external identifiers, line matching, units, subsidiary, location, adjustment account, and inventory detail. Test a small representative set in a sandbox using the intended mapping and role.
Include one positive line, one negative line, numbered stock if in scope, and an intentionally invalid row. Confirm whether an import update changes an existing adjustment or creates a new one. A second upload after an uncertain result must begin with checking what already exists.
Reconcile imported line count, quantities, and values to the approved file. A successful import status is insufficient when a mapping converted units incorrectly or omitted inventory detail.
After processing and costing completion, compare the transaction, item-location quantity, inventory detail, valuation report, and GL impact with the approved expectations. Investigate differences instead of replacing the expected result with whatever posted.
Check open operational documents too. If a purchase order still expects a receipt that the adjustment was meant to replace, the next receipt could duplicate stock. Resolve that dependency through the proper process.
Track recurring adjustments by reason and source. A recurring integration timing error needs a process fix, not a permanent monthly adjustment. CuriousRubik's NetSuite support services can be approached with the evidence packet and expected accounting result for a controlled review.
No. An adjustment changes quantity and value, while a worksheet establishes a specified balance with different historical and costing behavior. Item type and costing method determine which supported route is appropriate.
The inventory worksheet does not support lot-numbered or serialized items. Use a supported process that preserves the required inventory detail, with the responsible accountant reviewing any value correction.
It averages costing history rather than preserving the existing layers. Use the supported adjustment route when preserving FIFO or LIFO history is required, and validate the expected accounting result before posting.
Only if it is actually a per-unit amount in the relevant unit. Distinguish unit cost from total value change and show the multiplication in the approval packet. Confusing the two can create a large valuation error.
After the approved quantity, inventory detail, valuation, and GL result are verified and relevant costing processing is complete. Also resolve dependent source documents and the root cause so a later transaction does not recreate the error.