Moving Average Price Jump After Invoice Posting

Finance or plant accounting notices that a material's inventory value looks wrong right after month-end invoice processing, even though nobody changed anything in the material master. A controller reports that the standard cost report or the stock valuation report shows a unit price for a raw material that jumped from, say, 4.20 to 11.80 overnight, with no corresponding physical event. Production planning complains that a component now costs three times what it did last week and the variance is flowing into their work order settlement. Sometimes it goes the other way: the price drops close to zero after a credit memo is posted. Nobody remembers touching MR21 or the material master accounting view, and the finance team assumes the invoice was posted to the wrong material or the wrong GL account.

Pull the material document list for the material across the period bracketing the invoice, showing quantity and value after each movement, and overlay the accounting document from the invoice showing the split between stock account and price difference account postings. If material ledger is active, CKM3 shows the price change per period broken down by receipt, consumption, and invoice variance, which makes the arithmetic behind the jump visible rather than assumed.

If the calculation is mathematically correct given thin or zero stock coverage, this is not a defect; the fix is process, not system: encourage invoice verification closer to goods receipt, before stock is consumed, or move high-volatility materials to standard price control if moving average is causing recurring cost noise, which requires a material master and costing decision, not a transport. If the invoice was matched to the wrong GR line, the data fix is to reverse and reprocess the invoice against the correct PO line, no configuration change needed. If negative stock at invoice time is the trigger, the fix is a data timing correction: post the missing goods movement first, then reprocess, and separately review whether negative stock should be permitted for this plant or storage location, which is a configuration setting requiring transport. If account determination is routing variances to the stock account when it should go to a price difference account for this valuation class, that is a genuine OBYC configuration fix requiring transport through the usual change path, not a one-off correction. A one-off, provably wrong price can be corrected directly with a manual price change transaction, but only after the underlying cause is understood, otherwise the same swing recurs on the next invoice.

The reflex fix is to run a manual price change to force the moving average price back to what people expect it to be. This clears the visible symptom for a day but does nothing about the underlying stock coverage or account determination issue, so the same swing reappears on the next invoice or the next low-stock moment. It also creates its own accounting entry and can mask a genuine matching error that should have been caught and corrected at the source, leaving a paper trail that is harder to reconcile later.

This sits at the boundary between MM inventory accounting and finance. MM owns matching accuracy and stock movement sequencing; finance owns account determination configuration and the decision on price control strategy for volatile materials. The handover note should state the material, the stock quantity at invoice time, the exact value split between stock and price difference accounts, and whether the swing is a one-off matching error or a recurring coverage problem needing a costing decision.