Landed Cost in D365: Voyages, Apportionment, and Inventory Valuation

A question I get from finance and operations alike is some version of "what does this item actually cost us once it is sitting on our shelf?" For domestically sourced goods the purchase price is close enough. For anything imported it is not, because freight, insurance, customs duty, brokerage and handling can add up to a large fraction of the product price, sometimes rivalling it. Carrying inventory at the bare purchase price quietly overstates your margin and distorts every decision downstream. Today I want to walk through landed cost in Dynamics 365: the dedicated Landed Cost module that captures these charges against a shipment, and, just as important, how that cost actually lands in your inventory valuation depending on the costing method you run. The first part is configuration; the second is where finance either trusts the numbers or does not.

WHAT LANDED COST ACTUALLY MEANS

Landed cost is the fully burdened unit cost of getting an item to your location and ready to sell or consume. It is the product price plus every incremental cost incurred along the way: ocean or air freight, inland haulage, marine insurance, import duty, customs brokerage, port handling, demurrage, and agent fees. The goal is simple to state and harder to do well: take all of those charges, attach them to the goods that incurred them, and spread them fairly across the units so that each unit carries its true cost. Once you have that, your inventory value is honest, your margin reporting is real, and your sourcing decisions (make versus buy, this vendor versus that one, near versus far) are made on the right numbers.

THE LANDED COST MODULE: VOYAGES AND JOURNEYS

The dedicated Landed Cost module in D365 is built for import-heavy operations and introduces a vocabulary worth learning. The central object is the voyage, which represents a physical shipment, typically a container or a consolidation of purchase order lines travelling together. A voyage groups the goods that share the same transport and therefore should share the same transport costs. A journey template describes the route and the legs that voyage travels (for example origin port, ocean leg, destination port, inland leg), and it carries the structure that drives which costs apply and when milestones are expected. You set up the templates once to mirror how your goods actually move, then create voyages against them as shipments happen, attaching the relevant purchase order lines.

The reason this structure exists, rather than just dumping a freight charge on a purchase order, is that real import costs are incurred at the shipment level and must be apportioned down to many order lines and items. A single container might hold lines from several purchase orders; the ocean freight is one invoice for the whole box, and it needs to be split across everything inside. The voyage is the container for that logic.

COST TYPES AND AUTO CHARGES

Each kind of cost is defined as a cost type: freight, duty, insurance, and so on, each mapped to the ledger accounts it should post to. Costs reach a voyage in two ways. You can enter them manually as they become known, or you can configure auto charges so that D365 applies an estimated cost automatically based on rules you define (a freight rate per container, a duty percentage of value, an insurance percentage, and so on). Auto charges are what let you value goods at receipt before the real invoices have arrived, which is almost always the case with imports where the carrier and customs paperwork lags the physical goods by days or weeks.

The other half of the configuration is apportionment: how a shipment-level charge is divided among the items on the voyage. D365 supports allocation by quantity, by net weight, by volume, by value (amount), or by a fixed percentage. The right basis depends on the charge. Freight on a full container is usually best apportioned by volume or weight, because that is what fills the box and drives the cost. Duty is naturally apportioned by value, since duty is assessed on value. Insurance by value. Getting the apportionment basis right per cost type is the single configuration choice that most affects whether each unit ends up with a sensible cost, and it is the one people most often set thoughtlessly to "by quantity" for everything.

ESTIMATES VERSUS ACTUALS

The heart of landed cost in practice is the gap between what you estimate and what you actually pay. At receipt you rarely have the final freight and duty invoices, so the auto charges post an estimated landed cost and the goods enter inventory valued at purchase price plus that estimate. Later the carrier invoice and the customs entry arrive, you match them to the voyage as actual costs, and D365 reconciles the actual against the estimate. The difference is a variance that has to go somewhere, and where it goes is the part that ties the module to your costing setup.

HOW LANDED COST HITS INVENTORY VALUATION

This is the part finance cares about most, and it behaves differently depending on the inventory model on the item. Under a moving average or FIFO model, the estimated landed cost is added to the running inventory value at receipt, so the on-hand value already reflects freight and duty rather than bare price. When the actual invoices come in, the reconciliation adjusts the inventory value: if the goods are still on hand, the unit cost catches up to the real figure; if some have already been sold or consumed, the portion that can no longer attach to inventory flows to cost of goods sold or to a variance, because you cannot retroactively load cost onto units that have left.

Under a standard cost model the logic is different and people get caught by it. A standard cost item is held at its frozen standard regardless of what you actually pay, so landed charges do not change the live inventory value the way they do under average costing. Instead, the difference between the standard and the actual landed cost surfaces as a purchase price variance. That does not make landed cost irrelevant under standard costing; it makes it upstream. The freight and duty you expect to incur belong in the cost you load when you calculate the standard (often as a costing-sheet surcharge or an explicit landed element), so that the standard itself reflects landed cost and the variances stay small. If you set standards on bare purchase price and only capture freight and duty as actuals, you will book large, recurring purchase price variances every period and finance will rightly ask why. I covered the mechanics of setting and recalculating standard cost in my article on BOM changes and standard cost, and landed cost is one of the inputs that belongs in that calculation.

WHAT GOES WRONG

• Apportioning every charge by quantity. Freight follows volume or weight and duty follows value. Defaulting all cost types to quantity gives a light item the same freight as a heavy one and distorts every unit cost on the voyage.

• No auto charges, so nothing is valued at receipt. Without estimates the goods enter at bare price and the real cost only appears weeks later, leaving a window where every margin report is wrong.

• Estimates never reconciled to actuals. If the actual carrier and customs invoices are not matched back to the voyage, the estimate becomes the permanent cost and your inventory value drifts from reality.

• Standard cost set on bare purchase price. Leave landed charges out of the standard and you generate large purchase price variances every period; build expected freight and duty into the standard instead.

• Voyage scope mismatched to how costs are billed. If a voyage does not match the unit the carrier actually invoices (the container, the consolidation), splitting that invoice across the right lines becomes guesswork.

• Treating landed cost as a finance-only concern. Buyers and planners need landed cost to compare suppliers and to set reorder economics; if it lives only in a month-end journal, the people making sourcing decisions never see it.

TAKEAWAYS

Landed cost is the difference between knowing what your inventory truly costs and guessing at it, and for imported goods that difference is large. Use the Landed Cost module to capture freight, duty, insurance and handling against the voyage that incurred them, model your journey templates on how goods really move, and choose an apportionment basis per cost type that matches what drives each charge rather than defaulting everything to quantity. Lean on auto charges so goods are valued realistically at receipt, then discipline the reconciliation so estimates are always trued up to the actual invoices. Above all, understand how the cost meets your inventory model: under average or FIFO it adjusts the on-hand value as actuals land, while under standard cost the landed charges belong in the standard you calculate so that variances stay small and explainable. Configure it once with these choices made deliberately and landed cost stops being a month-end surprise and becomes a number you can plan and price against.

Next time I will turn to Asset Management in D365: how maintenance assets and functional locations are structured, how work orders plan and capture maintenance work, and where the module connects to inventory, procurement and production.

In this series: related article BOM Changes and Standard Cost in D365: Timing Cost Recalculations Around Revision Cutovers