Landed cost should explain the true cost of inventory - not hide it in a general expense

The business problem begins after the supplier price

Imported or transported goods can attract freight, customs duty, insurance, brokerage, handling, port charges, and other expenses before they become available for sale or production. If those amounts are posted only to a general expense account, product cost and gross margin may be understated. If every charge is assigned manually, allocation becomes slow and inconsistent.

Landed cost asks two separate questions: which receipt or shipment does the charge belong to, and how should it be distributed across the included products? Quantity may be appropriate for identical cartons, weight for freight, value for insurance, and volume for space-based charges. A single basis is not defensible for every cost type.

How Simor ERP connects the workflow

Simor ERP Landed Costs attaches additional costs to a Purchase Receipt and distributes them across the received items. The resulting allocation can contribute to inventory valuation and later product profitability instead of remaining disconnected from the stock it helped acquire.

Configuration can define cost categories, allocation bases, rounding behaviour, eligible receipt lines, accounts, permissions, approval thresholds, and reports. Estimated costs and actual invoices should remain distinguishable so finance can explain what changed when a carrier or customs invoice arrives later.

Problems teams commonly search for

• Freight is recorded but product margin still looks too high.
• One invoice covers several receipts, products, or suppliers.
• Heavy low-value items receive too little freight under value allocation.
• Actual charges differ from the estimate after stock was sold.
• Partial receipts create unclear quantities for allocation.
• Rounding leaves an unexplained balance.

These exceptions need controlled adjustment, not deletion and re-entry. The original receipt, estimated allocation, actual charge, variance, user, and journal impact should remain traceable.

Example: allocating one freight invoice

A receipt contains three products with different quantities, weights, and values. Freight is allocated by weight, insurance by product value, and brokerage evenly by line. The allocation preview should show every basis, rate, amount, rounding difference, and revised unit cost before posting.

If only part of the order arrived, the system should use received quantity rather than ordered quantity unless policy states otherwise. When the final carrier invoice differs from the estimate, finance needs a variance route that updates the appropriate inventory or cost accounts without rewriting the first posting.

Implementation checks and useful measures

Test zero-cost lines, returns, over- and under-receipts, foreign currency, charges added after sale, duplicate invoices, and a closed fiscal period. Confirm that unauthorized users cannot alter the allocation basis after approval and that product valuation reconciles with the associated ledger accounts.

Useful measures include landed cost per unit, freight as a percentage of purchase value, estimate-to-actual variance, charges awaiting invoices, and margin before and after allocation. The purpose is better purchasing and pricing decisions, not merely more accounting detail.

Background reading: Microsoft’s landed cost overview and landed cost reporting guidance.

Continue the costing review

Compare the result with inventory valuation, Simor ERP costing and profitability, and the live ERP environment.

Allocation evidence and responsibility

Reliable landed-cost allocation depends on a defined record and named responsibility. Its minimum evidence includes receipt line, cost category, provider invoice, allocation basis, currency, estimate, actual amount, variance, and posting reference. Information for landed-cost allocation should originate in the business transaction where possible instead of being reconstructed at month-end.

Responsibility for landed-cost allocation crosses purchasing, logistics, inventory accounting, and finance. Workshops for landed-cost allocation should identify who creates, reviews, approves, corrects, and closes each record, then establish materiality, tolerance, timing, retention, and escalation rules. Simor ERP can enforce an agreed landed-cost allocation policy, but software cannot resolve a policy the organization has not defined.

Decisions to document

• select quantity, weight, volume, or value as the basis
• separate estimated charges from actual invoices
• assign shared charges across more than one receipt
• handle cost received after inventory was consumed
• approve a variance beyond tolerance
• correct an allocation posted to the wrong items

Every landed-cost allocation decision affects another module or report, so downstream consequences belong in the approved design. Acceptance criteria for customized landed-cost allocation should identify its source, permission, balance or operational effect, and retained evidence.

Receipts and charges that challenge the model

A happy path proves little about landed-cost allocation. Build test data covering mixed weights and values, partial and final receipts, foreign-currency freight, returned merchandise, zero-value samples, closed-period variance. For every landed-cost allocation scenario, record expected status, balance, operational or journal impact, authorized role, correction route, and report result.

Test landed-cost allocation with realistic volume and multiple users. Check concurrency, duplicate prevention, date and period control, precision, and integration retry behaviour. Reverse or correct selected landed-cost allocation records and verify that their original history remains available.

Measures worth reviewing

• unallocated inbound charges
• estimate-to-actual variance
• landed cost per unit
• freight percentage by supplier
• receipts awaiting cost invoices
• margin change after allocation

Each landed-cost allocation measure needs an owner, formula, source, refresh expectation, and action threshold. Its dashboard should drill into underlying transactions so managers can explain change. Measurement of landed-cost allocation should guide correction and improvement rather than encourage convenient status choices.

What happens when cost arrives after the goods

landed-cost allocation does not end when one screen shows Complete. The team receiving landed-cost allocation needs a trusted status, stable identifiers, dates, quantities or amounts, and a route back to the source. Interfaces should exchange business references that people can investigate, not only technical keys.

Define what happens when landed-cost allocation fails after an earlier step succeeded. A retry of landed-cost allocation must not create a duplicate; its timeout must not be interpreted automatically as failure; and its correction must not erase the first attempt. Queued, rejected, partially completed, reversed, and closed landed-cost allocation states need meanings shared by users and integrations.

Reporting cut-off also matters for landed-cost allocation. Operational work related to landed-cost allocation may continue while finance prepares a period result, so posting date, event date, approval time, and effective date should not be treated as interchangeable. Late activity needs a controlled destination and an explanation visible in later review.

Documentation for landed-cost allocation should include the normal flow, exception ownership, permissions, field definitions, integration dependencies, reports, and recovery steps. Training for landed-cost allocation should use the same realistic exceptions tested before launch, because users rarely need help only when every input is perfect.