Inventory accounting case study

Inventory Costing Methodology Change Case Study (Std Cost → FIFO)

A $65M light manufacturer transitioned from standard costing to FIFO with lot tracking, cycle-count discipline, and ASC 250 retrospective application — fixing a 6-year accumulated COGS distortion and unlocking auditor sign-off on inventory for the first time in three years.

Client profile: Composite case study based on a $65M revenue light manufacturer (electronics assembly), 3,400 active SKUs, 2 plants, NetSuite OneWorld with Advanced Manufacturing module, 6-person finance team. Annual external audit; private with sponsor-driven IPO readiness on a 2-year horizon.

Case study breakdown

From std-cost variance accumulation to FIFO with lot discipline

Company context — and why standard costing eventually fails some manufacturers

The client manufactures electronic assemblies at two US plants, with 3,400 active SKUs ranging from $0.20 connectors to $2,400 finished assemblies. Component costs (the largest input) move materially with semiconductor pricing cycles — copper, gold, aluminum prices shift 8–25% annually. The company adopted standard costing 9 years ago when the original CFO believed standard costs were the right answer for any manufacturer. They worked, mostly, until the 2022–2024 commodity volatility produced standard-vs-actual variances of $4.2M annually that nobody could fully explain.

The auditor flagged inventory in three consecutive years. The findings escalated from "control deficiency" to "significant deficiency" because the variance accumulation had grown to material levels and the variance allocation methodology (apportion to COGS) was being applied inconsistently. The audit committee asked whether the methodology was right for the business; that question prompted the engagement.

  • $65M revenue, electronics assembly
  • 3,400 active SKUs across 4 product families
  • 2 plants (East Coast, West Coast) with separate inventory
  • Component cost volatility 8–25% annually
  • $4.2M annual std-vs-actual variance, growing
  • NetSuite OneWorld + Advanced Manufacturing module
  • 3 years of audit findings on inventory
  • Sponsor-driven IPO readiness on 2-year horizon

Why the change — std cost vs. FIFO at this scale

Standard costing is excellent when component costs are stable and volume is high. It produces operationally meaningful variance analysis (purchase price variance, usage variance, overhead absorption variance) that points to specific operational issues. FIFO is excellent when costs are volatile and traceability matters — every dollar of inventory carries its actual purchase cost; gross margin reflects actual material costs at the time of sale.

The decision matrix for this client tipped to FIFO for three reasons. First, commodity volatility had broken the standard-cost variance signal — variances were so large that operational signal was lost in commodity noise. Second, IPO readiness pressure made auditor questions about methodology consistency unwelcome. Third, customer contracts had started referencing actual material costs (cost-plus pricing on key accounts), making FIFO traceability operationally useful, not just accounting-useful.

What Ledger Summit implemented

  • FIFO costing methodology configured in NetSuite Advanced Manufacturing
  • Lot tracking enabled on 1,200 high-velocity SKUs (the rest use FIFO without lot)
  • Cycle-count program redesigned: 100% A-items quarterly, B-items semi-annually, C-items annually
  • Standard cost variances cleared as part of opening balance with documented allocation methodology
  • ASC 250 retrospective application memo prepared and reviewed by auditor
  • Three years of comparative financials restated for the change
  • Inventory valuation safeguards: lower-of-cost-or-NRV testing automated
  • Reserve methodology refresh: excess and obsolete (E&O), slow-moving, expired
  • Margin-by-product-by-customer reporting enabled (impossible under std cost)
  • Per-customer cost-plus billing reconciliation engine

ASC 250 Accounting Changes — what the methodology change required

A change in inventory costing methodology is a "change in accounting principle" under ASC 250. Specific requirements:

  • Preferability assertion — written justification that FIFO is preferable to std cost for this entity, signed by management. Required before the change.
  • Auditor preferability letter — auditor concurs in writing that the change is preferable.
  • Retrospective application — financial statements for prior periods presented as if FIFO had always been the methodology. Three years of comparatives restated.
  • Cumulative effect — opening retained earnings adjusted for the cumulative effect on prior periods not presented in comparatives.
  • Disclosure — nature of the change, reasons, effect on each line item of the financial statements, effect on per-share amounts (where applicable).
  • Voluntary change rationale — for changes not required by new GAAP, the entity must explain why the change is preferable. Common reasons accepted: better matching, alignment with industry, improved comparability.
  • Internal controls assessment — control implications of the new methodology assessed; changes to ICFR documented.
  • Tax method change consideration — book change may or may not require tax method change; coordinated with tax provider.

Lot tracking — what we enabled and why

FIFO without lot tracking is mathematically clean (oldest cost out first) but operationally weak. Lot tracking marries FIFO accounting to physical lot identification — every receipt creates a lot record with date, quantity, cost, and supplier. Issues consume from the oldest lot first. This is required for some product families and useful for many.

  • 1,200 high-velocity SKUs: Full lot tracking — every lot has a unique ID, date, supplier, cost
  • 900 medium-velocity SKUs: FIFO without explicit lot ID — system tracks cost layers
  • 1,300 low-velocity / consumable SKUs: Average cost — simpler operationally, immaterial
  • Regulated components: Lot tracking required regardless of velocity (RoHS compliance, recall traceability)
  • Customer-specified inventory: Customer-owned material tracked separately — never FIFO'd
  • Consigned inventory: Tracked as memo-only; no GL inventory

Implementation timeline — 16 weeks from preferability assertion to clean year-end

  • Weeks 1–3: Discovery and methodology selection. Reviewed std-cost variance pattern, evaluated FIFO/avg-cost/specific-id alternatives, drafted preferability assertion, obtained auditor preferability letter.
  • Weeks 4–7: System configuration. NetSuite Advanced Manufacturing reconfigured for FIFO; lot tracking enabled on 1,200 SKUs; opening balance methodology designed.
  • Weeks 8–10: Cutover preparation. Cycle counts at both plants for opening balance integrity; lot identification on existing inventory; standard cost variance allocation completed.
  • Week 11: Cutover. Methodology change effective at month-start. Opening inventory valued at FIFO with documented lot identification.
  • Weeks 12–14: Restatement. Three years of comparatives restated for FIFO; ASC 250 disclosure drafted and reviewed.
  • Weeks 15–16: Audit walkthrough. Auditor pre-walkthrough of restatement, opening balance, and ongoing controls. Year-end audit completed without inventory findings for the first time in 3 years.

Measured results

MetricBefore (std cost)After (FIFO with lot)Delta
Annual std-vs-actual variance$4.2M unexplained$0 (concept doesn't apply)
Audit findings — inventory3 (significant deficiency)0−3
Cumulative variance carried in inventory$2.1M (mis-stated)$0Cleaned
Margin-by-product reportingNot availableReal-time dashboard
Cost-plus billing reconciliationManual, 8 hours / monthAutomated, 30 min / month−94%
Cycle-count accuracy (A-items)~92%~99.5%+7.5 pp
Inventory days on hand (visibility)Aggregate onlyPer-SKU, per-lot
E&O reserve methodologyAged inventory %Lot-aged with usage forecast
Year-end audit fieldwork (inventory)5 days2 days−3 days
IPO-readiness inventory workMaterial remediation neededAudit-clean

Cycle-count discipline — A/B/C classification

FIFO accuracy depends on physical inventory accuracy. Cycle counting replaces annual physical inventory with continuous counting on a velocity-based cadence.

ClassDefinitionCount cadenceAccuracy target
A-itemsTop 80% of dollar volume — typically 15–25% of SKUsQuarterly≥99% accuracy
B-itemsNext 15% of dollar volume — typically 30–40% of SKUsSemi-annually≥97% accuracy
C-itemsLast 5% of dollar volume — typically 40–55% of SKUsAnnually≥95% accuracy
Strategic / regulatedRoHS, ITAR, controlled components regardless of valueQuarterly minimum100% accuracy required

When a costing methodology change makes sense

  • Material commodity-cost volatility breaking std-cost variance signal
  • IPO readiness or sponsor diligence requiring audit-clean inventory
  • Cost-plus customer pricing requiring traceable component costs
  • Product mix shift (more SKUs, more variability) outgrowing std-cost methodology
  • Auditor findings or significant deficiencies on inventory
  • Industry/regulatory traceability requirements (lot tracking)
  • M&A integration where target uses different methodology

When NOT to change methodology

  • Stable component costs. If commodity inputs are stable, std cost is operationally superior.
  • High-volume, low-mix manufacturing. Std cost shines here; variance analysis is the operational tool.
  • Methodology change driven by short-term P&L management. Auditors and audit committees push back hard on changes that look income-management-driven.
  • Insufficient data history for retrospective application. Three years of restated comparatives need three years of clean source data; some companies don't have it.
  • Tax method change implications not assessed. Book and tax don't have to align but require coordination.

Alternatives considered — methodology selection

MethodologyProsConsVerdict
Standard cost (current)Operational variance signalVariance signal lost in commodity noiseReject — broken at this commodity volatility
Weighted-average costSimpler than FIFO; absorbs volatilityLess traceability; cost-plus reconciliation harderReject — cost-plus contracts need lot trace
FIFO without lot trackingCleaner than std cost; no lot complexityNo physical traceability; recall riskReject — RoHS/recall requires lot
FIFO with lot tracking (selected)Audit-clean; lot traceability; operationally usefulImplementation complexityAdopt — fits all 3 driving needs
Specific identificationMost preciseOperationally impractical at 3,400 SKUsReject — too granular
LIFOTax benefit in inflationary periodsIFRS prohibits; IPO-incompatibleReject — IPO horizon

Frequently asked questions

Did you have to restate prior periods?

Yes — ASC 250 requires retrospective application for accounting principle changes. We restated three years of comparatives plus opening retained earnings adjustment for the cumulative effect of earlier periods.

How did the auditor react?

Positive. The preferability letter was straightforward; the restatement was supported by clean source data; the new control framework cleared up the prior years' findings. First clean inventory audit in three years.

What about tax method change?

Book change doesn't automatically require tax method change. We coordinated with the tax provider; the company elected to keep tax on std cost (allowed under specific IRS regs) for the first year, with planned alignment to FIFO in Year 2. Form 3115 (Application for Change in Accounting Method) filed for the tax change.

How long does a methodology change typically take?

12–20 weeks for mid-market manufacturers. Discovery and preferability: 3 weeks. System configuration: 4 weeks. Cutover prep including cycle counts: 3 weeks. Cutover: 1 week. Restatement: 3 weeks. Audit walkthrough: 2 weeks.

What if our auditor doesn't agree the change is preferable?

The auditor preferability letter is the gating item. If the auditor doesn't concur, we revisit the preferability assertion or evaluate alternative methodologies. In practice, methodology changes that align with industry norms and address audit findings get auditor support.

What about WIP inventory during cutover?

WIP at cutover is valued using standard cost rolled forward to FIFO based on component receipt date for components and labor/overhead application date for value-added. Documented methodology required and reviewed by auditor.

Can you handle this without NetSuite Advanced Manufacturing?

Yes — we've done methodology changes on Sage Intacct, Oracle EBS, and SAP. The mechanics are similar; the configuration steps differ per ERP.

How does lower-of-cost-or-NRV apply under FIFO?

Tested per SKU at lot or layer level (FIFO inventory has identifiable cost layers). NRV testing automated quarterly; reserve adjustments documented.

What about customer-owned (consigned) inventory?

Tracked as memo-only — never on the balance sheet, never FIFO'd. Documented separately for audit support.

Is this a SOX-relevant change?

Yes. Methodology changes affect ICFR design. We documented the new control environment, performed walkthrough testing, and updated the SOX matrix. For the IPO-readiness horizon, this is a meaningful uplift.

Inventory accounting holding back the audit?

A 30-minute call walks your costing methodology and tells you whether a change is the right answer.

Book a free call