How we corrected a compromised average-costing engine — without restating tax-filed periods — by triggering NetSuite's own cost recalculation engine through a deliberate inventory zero-out at the cutoff date.
ERP
NetSuite
Costing Method
Average Costing
Cutoff Date
1 January 2025
This case study is part of a larger engagement covered in The $2.3M Recovery: Rebuilding a US Manufacturer's Accounting & EDI from Scratch. The client is a US-based consumer goods manufacturer running NetSuite with multi-tier in-house assemblies, imports from overseas, and four distinct shipping configurations sold under one product line. Acgile took over a NetSuite environment in which inventory valuation, landed cost, and COGS had become unreliable. This page focuses on the inventory and COGS rebuild.
The compounding effect of broken landed cost, mismatched receipts and bills, and unreconciled inventory adjustments was that NetSuite's inventory valuation was wrong. Because the client uses average costing, every incorrect receipt cost was averaged into the item's running cost, which then flowed into COGS on every subsequent sale. By the time the engagement began, average item values were no longer reflective of any real economic cost, and COGS on the income statement was unreliable for every period.
The technical challenge is that NetSuite does not retroactively recalculate COGS when historical costs are corrected. Fixing a bill from a year ago does not flow through to the COGS that was posted on a sale six months ago. This is a well-known constraint of the platform, and it is what causes most cleanup engagements to either accept a distorted historical COGS or attempt a line-by-line recalculation that never converges.
Investigate landed cost components, vendor bills, item receipts, and BOM hierarchies. Validate that corrected unit costs are defensible.
On the cutoff date, all on-hand inventory in NetSuite is zeroed out. This is the critical move.
Re-enter the opening inventory at corrected average cost. This deliberately triggers NetSuite's inventory cost recalculation engine.
NetSuite recalculates COGS retrospectively across affected periods within scope, and prospectively for all future activity. The result is a clean restart of the inventory cost layer.
1 January 2025
The cutoff was set at 1 January 2025 because that was the boundary of the client's filed 2024 tax returns. Bills, expenses, and historical transactional activity before that line were not modified. Everything from that date forward was the engagement's responsibility.
For inventory and COGS specifically, the cutoff date was the trigger point: zeroing out inventory and re-entering it at corrected cost on 1 January 2025 made NetSuite recalculate the cost layer from that date forward, including correcting the COGS posted in periods within the engagement's scope. It is a feature of NetSuite's average-costing engine that makes the rebuild method viable.
Most NetSuite cleanup engagements either accept a distorted historical COGS or attempt a line-by-line recalculation that never converges. Both approaches fail in different ways. Accepting distortion means handing leadership a financial statement that does not reflect economic reality. Line-by-line recalculation means spending months on a problem that NetSuite is structurally unable to solve.
The cutoff-and-rebuild technique is a faster, more defensible path to a correct inventory cost layer when average costing has been compromised. It uses the platform's own recalculation engine instead of fighting it. It is bounded by a deliberate date that aligns with tax-filed periods. And it produces an inventory and COGS position that is verifiable and audit-ready from the cutoff date forward.
The Key Insight
NetSuite's cost recalculation engine fires when you zero out inventory and re-enter it. Use the platform's behavior, instead of fighting it.
The cutoff-and-rebuild corrects inventory valuation in the books. To confirm the corrected book inventory matches physical reality, Acgile coordinates a year-end physical inventory count and reconciles it to NetSuite. Where physical and book quantities differ, inventory is adjusted to the actual count with documented reasons. This is the discipline that turns a one-time book correction into a verified, audit-ready inventory position; it is now a standing year-end procedure on the close calendar.
The inventory and COGS rebuild ran alongside three other workstreams that fed into the same clean cost layer.
— Item receipts matched to warehouse records and bills corrected, eliminating a multi-year imbalance on the balance sheet.
— Weekly application of freight, customs, duties, brokerage, and insurance against the right inventory pools, with monthly reconciliation.
— $1.09M of open AP investigated across 80+ vendors; balances current, in active follow-up, or queued for write-off decision.
Acgile runs cleanup engagements and ongoing managed accounting for US manufacturers, distributors, and SMBs on NetSuite and QuickBooks. If your books, your EDI, or your dispute defense aren't where they should be, the first conversation is on us.