Business Central Costing Methods: A No-Nonsense Guide to Choosing the Right One

Pick the wrong costing method in Business Central and you’ll only find out months later — in a balance sheet that doesn’t make sense, a margin report that looks suspiciously good, or an audit finding you can’t explain away. And by then, changing it means writing off your stock, creating a new item, and re-entering everything. Ask me how I know.

This article covers all five costing methods available in Business Central — FIFO, Average, Standard, Specific, and LIFO — with real scenarios, honest pros and cons, and a decision framework you can actually use. No accounting textbook fluff. Just the stuff that matters when you’re setting up items and someone asks “which one do we pick?”

---

First: Why This Decision Matters More Than You Think

In Business Central, the costing method is set per item — and once that item has ledger entries, you can’t change it. Not through a toggle switch. Not through a configuration change. The only way is a workaround: write off the stock, create a new item, copy everything over, and block the old one. That’s a production database operation, not an admin tweak.

The costing method determines:

• How COGS is calculated when you sell or consume an item
• How your inventory is valued on the balance sheet
• How margins appear in your P&L reports
• Whether you even see purchase price variances or they get buried
• How much the cost adjustment batch job runs — and how long it takes

There’s also a technical angle: Business Central uses a two-step costing process. When you post a transaction, it first records the cost using the unit cost on the item card. Then, a separate adjustment process — the Adjust Cost – Item Entries batch — recalculates and posts corrective entries to align with your chosen method. If your method generates a lot of layers (FIFO, LIFO, Specific), that batch job runs heavier. If you use Average over a long period, it runs lighter but recalculates retroactively every time a new purchase is posted within that period.

So this isn’t just an accounting decision. It’s a system performance and operational decision too.

---

What Are the Actual Costs of Getting It Wrong?

Nobody publishes numbers on this, so here’s what we’ve seen:

Mistake	Real-World Cost
Wrong method, discovered late	2–5 days of consulting time to restructure items + manual data correction
FIFO where Average was needed	Balance sheet overstatement during rising prices, tax implications
Standard costing without the discipline to maintain it	Accumulated variances in GL that nobody monitors, distorted margin reports
LIFO in an IFRS jurisdiction	Audit qualification — can’t close the books until fixed
Average over too long a period	30-minute cost adjustment jobs during month-end, blocking users

A 2-hour conversation during implementation to get this right costs a fraction of the fix.

---

The Five Methods at a Glance

Method	What It Does	Layer-Based?	IFRS OK?	Typical Users
FIFO	Oldest cost goes out first	Yes — tracks cost layers per receipt	✅	Retail, food, pharma, any perishable-goods business
Average	Weighted average of all receipts in a period	No — one blended cost	✅	Wholesale, distribution, chemicals, commodities
Standard	Fixed predetermined cost; variances go to dedicated GL accounts	No — uses standard cost, not actual	✅ (with proper variance accounting)	Manufacturing, production, cost-control environments
Specific	Each unit tracked by serial/lot with its exact cost	Yes — fixed application per unit	✅	High-value items, regulated industries, serial-tracked equipment
LIFO	Newest cost goes out first	Yes — reverse of FIFO	❌ (disallowed under IFRS)	Limited jurisdictions; declining use globally

---

FIFO — First In, First Out

How It Works

FIFO assumes the oldest items you bought are the first ones you sell. When you post a sales shipment, Business Central looks at your inventory layers — sorted by posting date — and applies the cost from the earliest receipt that still has quantity remaining.

If you bought 10 units at €100 in January and 10 units at €120 in March, then sell 15 units in April: the first 10 units go out at €100, the next 5 go out at €120. Your remaining inventory (5 units) is valued at €120 each.

Business Scenario

Consumer packaged goods distributor. You stock products with expiry dates. The pallets that arrived in January need to leave the warehouse before the pallets that arrived in March — not just for accounting, but because they physically expire. FIFO matches the accounting to the physical reality: the shelf picks the oldest stock, and the system values it the same way.

Advantages

• Matches physical goods flow for most businesses that handle physical products
• IFRS and GAAP compliant — accepted everywhere
• Balance sheet accuracy: in rising-price environments, inventory is valued at the most recent (higher) cost, reflecting replacement value
• Intuitive: non-accountants understand “oldest goes out first”
• Traceable: each cost layer links to a specific receipt — easy to audit

Disadvantages

• Higher taxable profit in inflationary periods — COGS is lower (old, cheaper costs), profit is higher, you pay more tax
• Adjustment overhead: the cost adjustment batch processes more entries because it’s matching layers. On high-volume items, this can add minutes to month-end processing
• Sensitive to posting sequence: if you back-date an inventory decrease, existing entries aren’t reapplied — your FIFO flow can go sideways
• More volatile margins: if you bought 100 units cheap and then 100 units expensive, your margin on the next 150 sales looks terrible when the expensive layer kicks in

Best Fit

Retail, food and beverage, pharmaceuticals, electronics, and any business where inventory physically moves in purchase order sequence. Also any business where the balance sheet valuation matters for bank covenants or investor reporting.

---

Average Costing

How It Works

Instead of tracking individual cost layers, Average costing calculates a weighted average of all receipts within a defined period. When you sell, the cost is that period’s average — not any specific purchase order.

Business Central lets you configure the averaging period: Day, Week, Month, Quarter, or Accounting Period. You can also choose the granularity: per item, per item/variant, or per item/variant/location.

The key mechanic: every time you post a new purchase within the same period, the average recalculates. All sales within that period eventually settle at the same average cost. But here’s the gotcha — if you post a purchase dated earlier in the period after you’ve already posted sales, Business Central re-averages everything retroactively. That’s correct accounting but can be surprising when your COGS changes after month-end.

Business Scenario

Wholesale chemicals distributor. You buy solvents by the tanker load. Prices fluctuate weekly. Individual containers from different shipments get mixed in the warehouse — there’s no way to tell which drum came from which delivery. FIFO would be a fiction. Average costing reflects the economic reality: you paid an average price for the stuff in your tanks, and that’s what it costs to sell it.

Advantages

• Smooths out price volatility — no sudden margin swings when a high-cost layer kicks in
• Simple to understand: one blended cost, not layers and layers
• IFRS and GAAP compliant
• Lower adjustment overhead than FIFO — fewer cost layer calculations (but longer periods mean heavier batch runs)
• Works for fungible goods: perfect for items that can’t be distinguished by batch

Disadvantages

• Hides purchase price trends — if your supplier has been raising prices 2% every month for a year, your average cost (and therefore your COGS) lags behind reality
• No physical flow logic: you’re not tracking what actually went out — just a mathematical blend. For non-fungible goods, this can be misleading
• Retroactive recalculations: back-dated purchases within the same period recalculate every affected entry — can be disruptive if discovered late
• Performance at scale: if you set the period to Month and have 50,000 transactions on one item, that batch job crunches a lot of numbers
• Shorter periods = more volatility, longer periods = heavier batch jobs — you’re trading off smoothness for performance

Best Fit

Wholesale and distribution of fungible goods (chemicals, commodities, aggregates, liquids). High-volume businesses where tracking individual cost layers is impractical. Any business where purchase prices fluctuate frequently and you want COGS to reflect an average rather than specific purchase events.

---

Standard Costing

How It Works

You set a predetermined “standard cost” on the item card. Every inventory transaction — purchase, sale, production output, consumption — uses that standard cost. When the actual purchase invoice arrives with a different price, the difference posts to a variance account (typically “Purchase Variance”), not to the item’s cost.

In the GL: inventory goes up by the standard cost. The vendor gets paid the actual cost. The difference goes to variance. If you’re monitoring that variance account, you know whether you’re buying above or below your standard.

Business Scenario

Contract manufacturer of metal components. You negotiate annual contracts with steel suppliers at target prices. Your sales team quotes customers based on standard costs plus margin. You need to know immediately when actual costs deviate — not after month-end when all the layers shake out. Standard costing gives you that variance signal in real time.

Production managers get measured on beating the standard. If the standard cost for a unit is €50 (materials + labor + overhead) and the plant manager consistently produces it for €47, that €3 variance is documented and attributable. If it costs €54, same thing — the variance flags the problem.

Advantages

• Predictable margins: sales quotes based on known costs, not fluctuating purchase prices
• Performance measurement: variances tell you exactly who’s beating their targets and who isn’t
• Simplified costing for repetitive manufacturing: no need to track actual costs per unit through complex routings
• Variance analysis built in: purchase variance, material variance, capacity variance — all visible in the GL
• Works with manufacturing: standard cost worksheets roll up material, labor, and overhead into finished good standard costs

Disadvantages

• Requires ongoing maintenance: standard costs must be reviewed and updated periodically. If nobody does it, your standards diverge from reality and your variances become meaningless
• Need accounting discipline: someone has to monitor variance accounts, investigate anomalies, and close out variances properly at period-end
• Not for volatile environments without frequent standard updates — if copper prices double overnight, your “standard” is useless
• Setup complexity: requires configuring general posting setup for variance accounts, standard cost worksheets, and (for manufacturing) capacity and overhead calculations
• Ending inventory is at standard, not actual: you need to track whether your total variance is material enough to require inventory revaluation

Best Fit

Manufacturing and production environments with repetitive processes. Companies where cost control is a strategic function — not just an accounting exercise. Any business where the discipline to maintain standards already exists or will be built as part of the implementation.

---

Specific Costing

How It Works

Each unit is tracked by serial number or lot number, and the cost of that specific unit follows it all the way through inventory to the sale. When you sell serial number S-0042, the cost is exactly what you paid for that specific unit — not the average, not the oldest, not a standard.

In Business Central, this requires item tracking — serial numbers or lot numbers — on all transactions, inbound and outbound. The application between receipt and shipment is fixed: the system won’t reallocate it during cost adjustment.

Business Scenario

Heavy equipment dealer. You buy and sell individually identifiable machines — each with its own serial number, purchase price, condition, and often custom modifications. A 2024 Komatsu PC210 isn’t the same cost as a 2023 Komatsu PC210 with 4,000 more hours. Specific costing maps the exact purchase cost to the exact sale, giving you true per-unit margin.

Also: pharmaceutical distributor under serialization regulations. You need full traceability from manufacturer lot through warehouse to patient. The cost needs to trace with the serial number — partly for accounting, partly for regulatory compliance.

Advantages

• True per-unit margin: you know exactly what you made on every single unit
• Regulatory compliance: required for serialized pharmaceuticals, medical devices, defense equipment
• High-value accuracy: for items where a single unit costs thousands, approximations (average, FIFO) don’t cut it
• Fixed applications: no surprises during cost adjustment — the link between receipt and shipment is final
• Audit trail: serial number links purchase invoice to sales invoice — auditors love this

Disadvantages

• Operational overhead: serial number tracking on every transaction — receiving, picking, shipping, returns. Your warehouse team needs to scan every serial number, every time
• No automation without serial assignment: if a serial number is missed, the transaction can’t complete
• Not for bulk or low-value items: tracking serial numbers on boxes of screws is a waste of everyone’s time
• ERP-specific constraint: in Business Central, the physical application must match the cost application — you can’t track serials for traceability but price them at average

Best Fit

High-unit-value items (machinery, vehicles, equipment, aircraft parts). Regulated industries where serial/lot traceability is mandated. Custom-manufactured or one-off products where each unit has a unique cost.

---

LIFO — Last In, First Out

How It Works

The mirror image of FIFO: the newest (most recent) purchase cost is applied to sales first. Old inventory layers sit on the balance sheet at their original (lower) cost while current sales reflect current (higher) purchase prices.

In Business Central, it’s technically supported and works identically to FIFO in mechanics: two-step posting with cost layer matching.

The Reality

LIFO exists in Business Central. It works. But in most of the world, it’s not a real option — it’s disallowed under IFRS and increasingly restricted in local GAAPs. The US still permits it, but even there, the trend is away from LIFO.

In an inflationary environment, LIFO reduces taxable income (COGS is higher) and understates inventory on the balance sheet. That’s exactly why regulators don’t like it — it can be used to manage earnings. If you’re operating in Romania, the EU, the UK, or the Gulf, LIFO is not available to you for financial reporting.

I’m including it here because it exists in the system and someone might ask — but for our client base, the answer is almost always “no.”

---

The Decision Matrix

Answer these five questions and the method usually picks itself:

Question	If Yes →
Do your items have expiry dates or a physical FIFO flow?	FIFO
Are your items fungible — can’t distinguish one batch from another?	Average
Do you manufacture, and need to measure production efficiency?	Standard
Are your items high-value, individually identifiable, and serial-tracked?	Specific
Are you in a jurisdiction that permits LIFO and want tax deferral?	LIFO (but really, talk to your accountant)

Most businesses land on FIFO or Average. Manufacturing adds Standard to the mix. High-value or regulated items get Specific. And LIFO is a niche that’s shrinking every year.

The hybrid reality: You don’t have to use one method across your entire item master. A typical manufacturer might use Standard for finished goods and raw materials, FIFO for MRO supplies, and Average for packaging materials. The costing method is set per item — use that flexibility.

---

What Nobody Tells You About Business Central Costing

1. The Adjust Cost batch job is your new month-end ritual. For FIFO, LIFO, and Specific items, this batch — run from the Adjust Cost – Item Entries page — recalibrates every cost layer. You run it after posting all purchase invoices and before closing the period. Skip it for three months and your COGS numbers are wrong. Run it on a Monday morning with users in the system and you’ll get locking errors. Run it during month-end closing and you’ll wonder why your margin report changed between 4pm and 5pm. Tip: schedule it, don’t manually trigger it.

2. Average costing and posting dates are tightly coupled. If you’re using Average by Month and someone posts a purchase invoice dated July 15th on August 3rd, Business Central retroactively recalculates the July average — and every July sale gets a cost adjustment entry. Your closed July COGS changes. That’s correct accounting, but it surprises finance teams who thought July was done.

3. The item card unit cost is just a starting point. For FIFO, LIFO, Average, and Specific, the Unit Cost field on the item card shows (invoiced costs + expected costs) ÷ quantity on hand. It’s a snapshot, not the final cost. The final cost is determined during adjustment. Don’t run reports off the item card expecting accurate COGS — wait for the adjustment batch to finish.

4. Changing costing method after go-live is a project, not a setting. The workaround — write off stock, copy item, rename, re-enter — works, but it requires planning. You need to coordinate with the warehouse (no physical stock during the switch), finance (expect a GL spike from the write-off), and operations (the old item gets blocked, the new one picks up). Budget 2–5 consulting days depending on item count and transaction volume.

5. Average cost period length is a performance decision as much as an accounting one. Average by Day gives you the most responsive cost — every purchase updates the average immediately. But it also means the adjustment batch has less work to do per run (only recalculates within a day). Average by Month gives smoother margins but the month-end batch run is heavier. There’s no single right answer — it depends on your transaction volume and month-end closing window.

---

How This Connects to Your Implementation

Choosing costing methods is part of the solution design phase of any Business Central implementation. It’s a decision you make once — at setup — and live with for years. Getting it right means understanding your industry, your accounting requirements, your operational capacity for processes like serial tracking, and your appetite for maintenance (Standard costing).

We walk through this decision item by item during the requirements and design phases of an implementation. If you’re mid-implementation and second-guessing a choice, or planning a migration from a legacy system where the costing logic is different — let’s talk before you set up items.

---

Vanguard 360 Solutions is a Microsoft Dynamics 365 Business Central partner and LS Retail Gold Partner. We’ve configured costing methods across 50+ implementations in manufacturing, distribution, retail, and services — from simple FIFO setups to multi-method manufacturing environments with standard costing, variance tracking, and serial-specific valuation.