ERPNext FIFO vs moving average valuation

Choosing FIFO or moving average valuation in ERPNext for each item

The valuation method you choose for an item sets how ERPNext calculates the cost of goods sold each time that item leaves stock, so the decision affects gross margin, inventory value on the balance sheet and the cost figures your managers read every month. Distributors and manufacturers usually face this when item costs move with each purchase: a supplier raises prices, freight varies by shipment, or the same product arrives from two sources at different landed costs. Before the first stock entry is posted, decide which method each item will use. FIFO (first in, first out) costs each outgoing unit at the cost of the oldest receipt still on hand, which tends to suit perishable goods, items with traceable lot costs or businesses that want reported cost to follow the physical flow of stock. Moving average blends the cost of all units on hand into one running rate that updates with each receipt, which tends to suit commodity items, bulk materials or stock where individual lot costs are not meaningful.

The choice is made per item, not for the whole company, so a single ERPNext instance can run FIFO for some items and moving average for others. Your finance team should agree the rule for each item group in writing, and your implementation partner should configure the item master so the default is set consistently for new items. Confirm with your accountants whether the method has to follow a documented accounting policy, and check how your auditors expect the policy to be evidenced. Changing the method on an item that already has stock is not a simple setting change. ERPNext's documentation describes a separate change valuation method procedure, and the impact on existing valuation and posted ledger entries should be reviewed before anyone touches live data.

Plan the change as a controlled project. Identify every item affected, freeze or schedule stock movements during the change window, record the stock value before and after, and agree how historical cost of goods sold will be presented in reports. Serial-number-wise valuation is a separate case that ERPNext documents in its own guide, so check whether any affected items track serial numbers before you start. Ask your partner to deliver a written scope, a test run on a copy of production data and a reconciliation of stock value and general ledger balances, so that the method change can be reviewed and signed off like any other financial control change.

How FIFO and moving average calculate cost of goods sold

Under first in, first out, each receipt creates a cost layer with its own quantity and unit cost. When stock leaves, ERPNext consumes the oldest layers first, so cost of goods sold reflects the purchase prices of the earliest units still on hand. The remaining stock value is made up of the most recent receipts, which means the balance sheet carries current costs while the income statement lags behind them.

Layer consumption: Each issue draws from the earliest open receipt until its quantity is exhausted, then moves to the next layer.
Cost lag: When prices rise, COGS shows older, lower costs and stock value shows newer, higher costs.
Traceability: Each unit can be tied back to the receipt that brought it in, which supports audit trails for purchase cost.
Layer rebuilds: A backdated receipt inserts a new layer in the past, so later issues may consume different costs than were first reported.
Negative stock: Issues that exceed open layers depend on your negative stock settings, so confirm how your configuration treats them.

Before go-live, ask your partner to show how these layers appear in the stock ledger for one of your fast-moving items.

What backdated receipts and invoices do to valuation

A backdated purchase receipt, stock entry or purchase invoice changes the cost of stock that has already been issued, whichever valuation method the item uses. ERPNext does not simply add the new cost to today's balance. It reposts the affected stock ledger entries from the posting date of the backdated document forward, recalculates the cost of each later issue, and then corrects the general ledger entries that carry those costs. Under FIFO, the backdated receipt changes which layer a later delivery consumed, so the cost of goods sold for that delivery moves. Under moving average, the new receipt changes the average rate from its posting date, so every later issue inherits a different rate until the next receipt. The method changes how the error spreads across transactions, but the reader's exposure is the same: closed periods, reports and invoices that were correct when issued can look different after the correction.

The effect differs by method in ways your controller should expect. With FIFO, a correction tends to show up as a shift between specific deliveries, which can be traced batch by batch if you use serial or batch tracking. With moving average, a single late cost can touch many later issues, because each one depends on the running average. Reposting therefore runs through the whole stock ledger after the backdated date, and on a large item history with many warehouses it can take a long time to finish. Until it completes, stock valuation and some reports may not yet reflect the correction. Before you backdate anything in production, confirm with your implementation team how reposting is queued and monitored in your version, and whether it runs in the background or blocks transactions.

Plan for backdating as an exception with a documented approval step, not as a routine correction. The settings that control when and how reposting runs, and how much it can slow day-to-day work, are covered in the stock reposting and closing entries topic, and the related guidance on ERPNext's valuation method change documentation explains what happens to existing valuations when the method itself changes.

Which factors should drive the choice per item

Valuation method is a per-item decision with finance consequences, not a company-wide default. The questions below connect cost behavior, traceability, shelf life, audit needs, warehouse spread and posting discipline, so finance can answer each one before the method is set in ERPNext.

How volatile is purchase cost?

When supplier prices move often, FIFO keeps cost of goods sold tied to the oldest purchase layers, while moving average smooths those swings into a running average. Ask finance which items see large price changes between receipts, and whether management reporting needs margins that reflect recent purchase prices or a blended cost. Pull the last year of purchase receipts for a sample of items to see how far unit costs actually move before deciding.

Does the item need batch or serial traceability?

Serialized and batch-tracked items carry their own identity through the stock ledger, so the valuation question is tied to which specific units left the warehouse. Confirm with operations and quality whether recall or lot tracing already requires specific-lot costing. Serial-number-wise valuation is a separate path in ERPNext, and finance should agree with the warehouse team which items use it before choosing a general method.

Do expiry and shelf life matter?

For perishable or dated goods, the cost of the batch that leaves first often matters as much as its price, and FIFO aligns issue order with receipt order in a way moving average does not. Ask whether stock write-offs for expired goods need to be traced to the purchase cost of the expired batch. Check how the warehouse picks stock today, because the method chosen in accounting should not contradict the physical issue practice.

What does the accounting policy and audit require?

Finance and external auditors will ask how cost of goods sold was determined, whether the method is applied consistently, and how a change of method would be documented and disclosed. Ask your auditors and controller to confirm the written policy for each inventory category and the evidence they expect, such as a method change approval. ERPNext prepares the records, but the policy itself is a decision your organization owns.

How is stock spread across warehouses?

Moving average is calculated per item, so a single item held in several warehouses and receiving at different prices produces one running average, which can hide where cost differences came from. FIFO layers follow each receipt, which can show cost by location but adds complexity when stock moves between branches. Map which items sit in multiple warehouses and whether transfers are frequent enough to change the result meaningfully.

How often do backdated entries occur?

A backdated purchase receipt or stock entry changes valuation for every later issue, and the effect differs by method: FIFO can reassign cost across layers, while moving average recalculates running averages from that date forward. Ask operations how often receipts are posted after the fact and whether stock reposting is scheduled. Frequent backdating raises the operational cost of either method, so it should weigh heavily in the decision.

ERPNext valuation options and when each fits

This table compares FIFO, moving average and serial-number-wise valuation on cost basis, backdated entry effects, traceability and typical use. Read each row against the item's stock pattern, since the method determines which purchase cost reaches cost of goods sold. Confirm each row against the ERPNext documentation for your version before setting a method on items with live stock.

Aspect	FIFO	Moving average	Serial-number-wise
Cost basis	Issues consume the oldest remaining receipt layers first, so cost of goods sold uses earlier purchase rates.	Each receipt updates a running average rate, and issues take the average in effect at that point.	Each issued serial number carries the purchase rate recorded when that unit was received.
Backdated entry effect	A backdated receipt or issue changes which layers are consumed, so later cost of goods sold can shift and stock needs reposting.	A backdated entry changes the running average from that date forward, so later issues and balances move and need reposting.	Only the serial numbers in the backdated entry are affected, but confirm reposting behavior for serialized items in your version.
Traceability fit	Suits batch-level tracking where receipt order matters, such as nearest-expiry stock. Costs are tracked in layers only.	Blends receipts into one average, so the cost of an individual unit or batch is hard to trace.	Strongest fit: each unit's purchase cost stays linked to its serial number through issue and sale.
Typically chosen when	Purchase prices move over time and cost should follow physical receipt order, for example with expiring stock.	Many interchangeable items arrive at varying prices and one smoothed cost per item is preferred.	Items are high value and individually identifiable, such as equipment, devices or vehicles, and each unit's cost must be traceable.
Changing the method later	Changes affect future valuation of the item. Follow the Change Valuation Method guidance and test the accounting impact first.	Same procedure applies: review the Change Valuation Method guidance, then test the accounting impact on a copy of live data.	Depends on serial tracking being in place for the item. Confirm the switching steps and treatment of existing stock in the Change Valuation Method guidance.

Setting the valuation method before the first stock entry

This sequence sets the valuation method at the company default and, where needed, per item before any stock moves, so that cost of goods sold and stock value are right from the first receipt. Each step ends with a check that confirms the setting, the test result or the ledger figure before the next step begins.

Agree the valuation approach with finance
Finance and the implementation lead agree which items use FIFO and which use moving average, and record the reason for each group, such as cost traceability for serialized goods or averaging for bulk commodities. The owner is the finance lead, who signs off the list. Done means a written decision table exists with one row per item group, the expected effect on cost of goods sold, and the accounting policy it follows. Ask your auditors or advisers to confirm the policy fits your reporting basis before you configure anything.
Set the company default valuation method
In the Stock Settings for the site, choose the default valuation method that applies to items without their own setting. The implementation lead makes this change on a non-production site first and records the value. Check that the field shows the agreed default and that the change is logged in the version history. Confirm which setting governs existing items, since the default only applies where an item has no value of its own.
Apply per-item valuation overrides
On each Item record that differs from the default, set the valuation method to match the decision table. The item setting takes precedence over the company default, so an item marked FIFO stays on FIFO even if the default is moving average. The stock analyst completes this and filters the item list to confirm which items carry an override. Done means every item in the decision table matches its agreed method, and no item relies on the default by accident.
Test receipts and issues on a sandbox site
Create a non-production site with the same settings, then post sample purchase receipts at two or more prices, followed by partial and full stock issues. Include one backdated receipt to see how the method reprices earlier movements. The tester compares the cost each issue takes out of stock against a manual calculation done on paper. Done means the sandbox results match the hand calculation for both FIFO and moving average items, and any mismatch is traced to a setting before go-live.
Check cost of goods sold and stock ledger values
After each sandbox test, open the stock ledger and the general ledger entries that the stock movements generated. Confirm that the cost of goods sold account and the stock in hand account show the values the test predicted, and that the stock balance report agrees with the ledger. The accountant performs this check. Done means the stock value in the ledger equals the stock value in the general ledger for every test item, with no unexplained difference.
Document the decision and the settings
Write a short configuration record that lists the company default, each per-item override, the test cases and their results, and the name of the person who approved the decision. Store it with your change records so that a later auditor or new administrator can trace why each item uses its method. Done means the record is approved by finance and linked to the production configuration change. Review it again before any change to the valuation method, because changing it later requires a planned revaluation of existing stock.

What changing the valuation method later involves

Switching an item from FIFO to moving average, or the reverse, after stock has moved is not a simple field edit. It changes how the cost of goods already sold and the remaining stock value were calculated, so it restates past cost. Before anyone touches the item, finance and the inventory owner should agree on a cutoff date from which the new method applies, and confirm that no open transactions straddle it. ERPNext documents a procedure for this in its Change Valuation Method page, which should be read in full against the ERPNext version you run before any change is scheduled.

The change itself is usually followed by a reposting or stock reconciliation plan. Entries dated before the cutoff need to be revalued so the stock ledger and general ledger agree under the new method, and the stock reposting settings in your environment determine how that runs. Confirm with your own test copy how long reposting takes on your data volume, how it interacts with stock closing entries, and whether any serial-number or batch items need separate treatment through the serial-number-wise valuation guide that ERPNext publishes.

Finance should then review the reports and periods affected. Stock valuation, stock ledger, cost of goods sold and gross margin figures for prior periods will move, so any closed period needs a decision on whether to reopen it, post adjusting journals, or record the impact in the current period with a clear note. Ask for a written sign-off from the controller or CFO that lists the items changed, the cutoff date, the reposting evidence and the reconciliation of stock value to the ledger. Treat that sign-off as part of the change record, because auditors will ask for it.

Questions buyers ask before choosing a valuation method

Can we use FIFO for some items and moving average for others in ERPNext?

Yes, the valuation method is chosen per item, so one company can value different item groups in different ways. Before you decide, confirm in the ERPNext documentation how the setting behaves for items that have no explicit method and whether any company-level default applies. Finance should agree which item groups use which method, because the split affects how cost of goods sold is reported across the chart of accounts. Mixed methods also mean two sets of stock reports to read and explain to auditors, so the reason for each split should be written down. A partner will usually start by reviewing your item master and stock ledger to map each item group to a method before any configuration changes are made.

How much effort does changing the valuation method later take?

Effort depends mainly on how much stock history exists, how many items are affected, and how many periods are already closed. Changing the method does not only alter future costs. It can also change the valuation of past issues and the stock balances that feed into closed accounting periods, so the work includes a review of the effect on reported figures. Open purchase receipts, unposted stock entries and items with serial or batch tracking add further steps. The ERPNext documentation has a Change Valuation Method page that describes the procedure, and it is the natural starting point for your own estimate. Ask any partner to show how they will size each of these drivers before quoting.

Can our own team change the valuation method without a partner?

Your team can do it if an administrator understands both stock and accounts, follows the ERPNext documentation step by step, and tests the change on a copy of production data first. The harder part is usually judgment rather than clicks. Someone must decide how past periods are treated, confirm that the stock ledger and general ledger still agree afterward, and document the change for auditors. Teams that lack this experience often find the reconciliation takes longer than the configuration. A common middle path is to keep the work in-house and bring in an outside reviewer for the reconciliation and the sign-off steps.

What do finance and operations need to provide for a valuation change?

The change needs decisions from finance and clean data from operations. Finance should provide:

A written accounting policy that names the new method and the effective date
Agreement on how closed periods are treated and who approves any restatement
A review of the cost of goods sold impact for a sample of items and periods

Operations should provide accurate stock counts, a clear view of receiving and issue practices, and confirmation of how serial and batch items are received and moved. Both teams need a named owner for testing and a short window in which no stock transactions are posted during the cutover. Without these inputs, the technical change can be correct while the reported numbers are still disputed.

How do backdated stock entries affect FIFO and moving average valuation?

Backdated entries matter for both methods because each one changes the order or the average that later transactions depend on. Under FIFO, a backdated receipt can shift which cost layer is consumed by earlier issues, so a later reposting may change cost of goods sold in periods that looked settled. Under moving average, a backdated receipt or issue changes the running average, and every subsequent valuation after that date is recalculated. The practical effect is that a single late entry can ripple through many transactions. Confirm in the ERPNext documentation how stock reposting is triggered and whether closing entries limit what can be reposted. Agree on a rule for backdating before go-live, because the rule decides how much rework a late entry creates.

Does serial number or batch tracking change the valuation choice?

It can. ERPNext documents a serial-number-wise valuation approach, which assigns cost to each specific unit as it is issued. This suits high-value or individually identified goods, where the cost of each unit is known and must be traced. For items that are interchangeable, a single valuation method is usually simpler to run and explain. Batch tracking sits between these cases, since costs may vary by batch while stock is still counted together. Before you choose, check which items need unit-level cost, how often receipts carry different unit costs, and whether your reporting requires traceability. Make the decision item group by item group, and read the serial-number-wise valuation page in the ERPNext documentation before setting it up.

What should a partner quote include for a valuation method change?

A quote should follow from a written scope, since DeployOpen agrees scope, deliverables and timelines in writing before work starts and does not publish a price list. Ask the partner to itemize the work: an assessment of the stock ledger and item master, the item groups in scope, a test plan on a copy of production, the reposting and reconciliation plan, the cutover steps, documentation of the change, knowledge transfer to your team, and the sign-off criteria. Confirm which items are one-time work and which support or review steps recur. Also ask what the quote excludes, such as restatement of closed periods, custom reports or changes to tax treatment, so you can compare proposals on the same basis.

Controls and operational checks for valuation changes

A valuation method change or a backdated entry touches stock value, cost of goods sold and the general ledger at the same time. The controls below help finance and IT agree who may change valuation settings, how changes are recorded, and how stock and ledger balances are proven to match after each change.

Role permissions for valuation settings

Decide which users can edit the valuation method on an item, change company-level stock settings and submit stock reposting. In ERPNext these rights come from roles and permissions, so a small group of finance and inventory leads should hold them and day-to-day warehouse users should not. Check that the same person does not both request a repost and approve its effect on the ledger. Confirm the exact role names and permission levels in your own environment before go-live.

Audit trail of method changes

Record why each valuation method change was made, who approved it and when it took effect. ERPNext keeps document versions and comments, but a formal change log with a reference to the approval is still your responsibility to maintain. Ask your implementation partner to show which events are captured by default in your version and which need a custom report or a process step. Keep the log outside the system so it survives a rollback.

Reconciling stock ledger to general ledger

After any method change or reposting, compare the stock value in the stock ledger with the balance of your stock-in-hand accounts for each company and warehouse. Differences usually come from entries posted without a matching accounting entry, or from warehouses mapped to the wrong account. Run this check at each period close, not only after a change. Confirm the reconciliation report your version offers and agree who signs it off.

Monitoring reposting jobs

Stock reposting after a backdated entry runs as a background job, and a large one can take time or fail partway. Check the job status and error log after each run, and confirm that no new stock transactions are posted while a repost is pending if your process requires a freeze. Read the repost settings for your version and test the timing on a copy of production data before scheduling it on live stock.

Testing a method change first

Before changing a live item's valuation method, run the change on a copy of the site with a representative set of receipts, issues and backdated entries. Compare the resulting cost of goods sold and closing stock value against the expected figures. Keep the test results with the change request. This step gives finance a documented baseline and lets IT confirm that scripts or custom reports still work after the change.

Limits to confirm in your environment

Valuation method behavior in ERPNext depends on the version you run, the item types you hold and the size of your stock history. The cards below are questions to settle with a test site before you choose a method for each item group.

Version and documented behavior

Confirm which ERPNext version your site runs and read the valuation documentation for that exact release. Ask whether FIFO and moving average behave as described for backdated receipts, returns and stock reconciliation in your version. Run a short scripted scenario on a copy of production data and compare the resulting cost of goods sold with your hand calculation.

Support by item type

Check whether your chosen method applies to every item you stock, including serialized and batch-tracked items. Ask how serial-number-wise valuation interacts with FIFO or moving average, and whether any item group needs a separate treatment. Document the exception list so that purchasing and finance apply the same rule.

Multi-company reporting

If several companies share items or warehouses, confirm how valuation is set per company and how inter-company transfers carry cost. Ask finance to reconcile stock value in each company's ledger against the balance sheet account for stock in hand. Agree which reports the group consolidates and in which currency.

Backdated entry impact

Identify how often receipts or invoices are posted after the period they belong to, because each backdated entry can reprice later issues under either method. Ask whether your team will run stock reposting after such entries and who approves it. Test one backdated receipt on a copy of the site and record which issue entries change.

Performance on large ledgers

Measure how long reposting and valuation recalculation take on your largest item and warehouse combinations. Ask whether stock closing entries are needed for faster reports and what your backup window allows during a reposting run. Schedule the test against realistic volume before the cutover date is fixed.

Change request and cutover

Ask what a later change of valuation method involves in your version, including whether existing stock must be revalued and how the change is recorded for audit. Agree in writing who signs off the change and when it takes effect, so that no period is mixed under two methods.

Where to read the official valuation guidance

Before you fix a valuation method for any item group, read ERPNext's own guidance on the subject. The first stop is the ERPNext Change Valuation Method page, which covers how the setting is changed on an item and what the system expects from the stock ledger when that happens. Read it with your finance lead, because the change touches stock value and the accounting entries that follow from it, not only the item record. Confirm in that page which steps apply to your ERPNext version, since the documentation describes the procedure for the release you run, and your version determines which screens and checks you see.

The second read is the guide on serial-number-wise valuation. If any of your items are serialized, this is where the rules for valuing individual units are set out, and it matters for how cost of goods sold is traced to specific receipts. Use it to check whether serialized items can follow the same valuation logic as the rest of your catalog or need separate handling. Write down the questions the guide leaves open for your business, such as how returns of serialized units are valued, and take them to your implementation partner or to the ERPNext community before any item master is loaded.

Treat both pages as the baseline for your design decisions, not as a substitute for testing. Build a short test set with a few representative items, one backdated purchase receipt and one sales return, and compare the stock ledger and general ledger results under each method in a non-production site. Keep the outputs as evidence for your controllers and auditors. The documentation explains what the software does, but whether a method suits your costing policy, tax position and reporting needs is a decision your finance team must own and record.

How DeployOpen scopes valuation decisions for ERPNext

DeployOpen plans, implements, tests, documents and supports self-hosted open-source platforms inside your own infrastructure, including ERPNext. For FIFO versus moving average valuation, we start from the items, warehouses and accounts that drive your cost of goods sold, then write the valuation decision down before any configuration begins.

How we scope

Written scope lists which items, item groups and warehouses each valuation method will cover, agreed before work starts.
We inventory backdated entry patterns, returns and landed cost use so the method choice reflects how your stock really moves.
Fixed-scope engagements set out deliverables and timelines in writing, and a quote follows from that scope.

How we build

We configure the valuation method per item in a test site and record the stock and accounting effects for each case.
Test scenarios cover backdated receipts, partial deliveries and returns, with expected cost of goods sold worked out in advance.
Where a method change is in scope, we build the reposting and reconciliation steps and rehearse them on a copy of your data.

How we hand over

Documentation covers the valuation rule for each item group, the approval needed before a method change, and who runs reposting.
Your team receives test evidence showing stock ledger and general ledger agreement for the agreed scenarios.
A walkthrough with your finance and stock owners confirms they can run the monthly checks without us.

How we support

Ongoing support, upgrades and continuous testing are available as a retainer after handover.
Retainer work can cover re-checking valuation after ERPNext version upgrades and new item onboarding.
Confirm with us which accounting, audit or tax obligations apply to your valuation policy before relying on this setup.