ERPNext values inventory with actual costing (FIFO or moving average), not classic standard costing with posted variance accounts. It does have a "standard cost" in the sense of the planned cost from a BOM, but stock is always valued at what you actually paid or produced. If you expect SAP-style standard cost and variance accounting, ERPNext works differently, and knowing how avoids a lot of confusion.
"Standard costing" means different things to different people, which is why it trips up finance teams evaluating ERPNext. To a cost accountant it often means a fixed standard cost per item with automatic variance postings. To a manufacturer it often means "the planned cost from my BOM". ERPNext supports the second well and the first only partly, so here is exactly what it does.
ERPNext is an actual-costing system. It gives you a planned standard cost from the BOM and values real stock at FIFO or moving average, but it doesn't post formal standard-cost variances the way a standard-costing system does. I lead ERPNext and Frappe implementations at MithTech, a team of Frappe specialists in Bengaluru.
Does ERPNext support standard costing?
ERPNext supports standard costing only in a limited sense: it provides a planned "standard" cost from the BOM and lets you compare it against actual production cost, but it values inventory using actual costing and does not post standard-cost variances automatically. If your definition of standard costing is a fixed cost per item with variance accounts updated at each transaction, ERPNext does not do that natively.
What ERPNext does give you is the standard cost as a reference (the BOM total for a manufactured item) while valuing real stock at FIFO or moving average. You can see the difference between planned and actual, which is the useful part of standard costing, without the overhead of maintaining and reconciling formal standard-cost variance accounts. For many businesses that is enough.
Skimmable summary: ERPNext offers a planned standard cost from the BOM and lets you compare it to actual, but values stock with actual costing and posts no standard-cost variances automatically. Classic SAP-style standard costing with variance accounts is not native.
How does ERPNext value inventory: FIFO or moving average?
ERPNext values inventory with FIFO (first in, first out) or moving average; LIFO is also in the list. The default is set in Stock Settings and can be overridden per item. FIFO values stock issues at the cost of the oldest units on hand; moving average recalculates a blended average cost each time you receive stock. Both are actual-costing methods: stock value reflects what you really paid. Indian accounting standards (AS 2 and Ind AS 2) allow FIFO or weighted average for inventory, so check with your CA before using LIFO.
| Method | How it values | Best when |
|---|---|---|
| FIFO | Oldest units' cost first | Prices change over time and you want cost to follow purchase order |
| Moving Average | Blended average, updated on each receipt | You want a smooth, single running cost per item |
You set the default valuation method in Stock Settings and override it on the Item where needed. Neither is "standard costing": both track real cost. Manufactured items get their valuation from the Work Order at actual production cost, which then follows the chosen method in stock.
Skimmable summary: ERPNext values inventory with FIFO or moving average, with a default in Stock Settings and an override per item. Both are actual costing: stock value reflects real cost, not a fixed standard.
What is the difference between standard cost and actual cost in ERPNext?
In ERPNext, standard cost is the planned cost of a manufactured item from its BOM, while actual cost is what a specific Work Order really consumed in material and operations. Standard cost is used for quoting, planning, and setting expectations; actual cost is what stock is valued at and what hits your accounts. The gap between them is the variance: visible as information, not as an automatic posting.
This is the practical, useful half of standard costing. You quote and plan against the BOM standard, then review actual Work Order costs to see whether production ran to plan. A widening gap flags inefficiency, price rises, or waste. The mechanics of that comparison live in my finished-goods costing guide and the BOM-cost-on-item guide.
Skimmable summary: Standard cost is the BOM's planned cost for quoting and planning; actual cost is what a Work Order consumed and what stock is valued at. The variance between them is visible as information for spotting inefficiency, not posted automatically to variance accounts.
Should an SME use standard costing or actual costing in ERPNext?
Many SMEs are better served by ERPNext's actual costing (FIFO or moving average) than by forcing formal standard costing, because actual costing is simpler and needs no variance reconciliation. Formal standard costing suits manufacturers with stable products and cost accountants who want variance analysis in the ledger, which is a different way of working.
What I suggest to clients: use moving average for a smooth running cost or FIFO where purchase-order costing matters, plan against BOM standard cost, and review BOM-versus-actual as your variance signal. That gives you the insight of standard costing without the maintenance burden. If group reporting or a parent company requires posted standard-cost variances, that is custom development, not a checkbox; confirm it before you commit.
Skimmable summary: many SMEs do well with ERPNext's actual costing plus a BOM-against-actual review, with no variance reconciliation. Formal posted standard costing means custom development in ERPNext.
Frequently asked questions
+Does ERPNext support standard costing with variances?
Not in the classic sense. ERPNext provides a planned standard cost from the BOM and values stock using actual costing (FIFO or moving average), but it does not automatically post standard-cost variances to the ledger. You can compare BOM standard cost against actual Work Order cost to see variance as information. True posted standard-cost variance accounting requires custom development in ERPNext.
+What valuation methods does ERPNext support?
ERPNext supports FIFO (first in, first out) and moving average valuation, and also lists LIFO. The default is set in Stock Settings and can be overridden per item. FIFO values issues at the cost of the oldest units on hand; moving average keeps a blended running cost updated on each receipt. Indian accounting standards allow FIFO or weighted average, so ask your CA before choosing LIFO.
+Is moving average or FIFO better in ERPNext?
Neither is better in every case; it depends on your goal. Moving average gives a single smooth running cost per item, which is easy to reason about; FIFO makes cost follow the order of purchases, which suits businesses where prices move and you want issues costed against specific receipts. Moving average is the simpler of the two to explain. The method can be set per item, so you can mix them where it makes sense, but ERPNext can block a change of method once stock transactions exist, so decide early.
+Can I set a fixed standard cost per item in ERPNext?
You can record a planned cost through the BOM and use it for quoting and planning, but ERPNext will still value actual stock at FIFO or moving average rather than holding a fixed standard on the ledger. There is no native mode that freezes a standard cost and posts variances against it. If you need that behaviour for group reporting, it is a custom-development scope.
+How do I see cost variance in ERPNext?
Compare the BOM (standard) cost of an item against the actual cost recorded on its Work Orders. The BOM total is the planned cost; the Work Order shows the real material and operation cost of a run. Reviewing the two side by side reveals whether production is costing more than planned. ERPNext surfaces this as information for analysis rather than posting an automatic variance entry.
Comments & ratings
No comments yet. Start a new discussion.
Manoj · Published on 11 July 2026
Worked with us? Leave a Google review