Landed Cost Management

Key Features

Voyage/Shipment Cost document that groups freight, duty, insurance, handling and demurrage for a single inbound consignment across multiple receipts and POs

Allocation engine distributing charges by value, net/gross weight, quantity or volume — configurable per charge type and overridable per line

Estimated vs. actual landed cost reconciliation: capture booking estimates, match incoming vendor invoices, post the variance to inventory or a cost-difference G/L account

Duty and customs charge capture with HS-code / tariff reference fields and per-charge tax handling

Multi-currency cost handling with document-level or charge-specific exchange rates, recording landed cost in local currency

Implemented in AL as table and page extensions on Purchase Receipt, Item Charge and Value Entry — upgrade-safe, no base-app code modification

Event subscribers on item-charge assignment and inventory adjustment so allocated cost flows into the standard Average/FIFO/Standard cost engine

Custom API pages (OData v4 / REST) exposing voyage headers and allocation lines for Power BI, Power Automate and Dataverse integration

Job queue entry to flag unreconciled or partially-invoiced voyages and optionally import forwarder rate sheets

Dedicated permission sets separating landed-cost entry, allocation posting and reconciliation approval

Landed-cost analysis pages and account-schedule-ready entries showing the cost build-up per item, per shipment and per voyage

Posted reconciliation audit trail linking each estimate, vendor invoice and variance posting for finance review

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Dynamics 365 Business Central.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Business Central's native item charges let you assign a single freight or duty amount to a posted receipt, but they fall short the moment you import in volume: no shipment-level grouping, no estimated-vs-actual reconciliation, weak multi-currency handling, and allocation limited to equal/value/weight/amount on one document at a time. Landed Cost Management closes that gap.

This is a build-to-order extension, not an instant AppSource download. ECOSIRE designs, develops, installs and supports it on your Business Central environment (cloud/SaaS or on-prem) as a per-tenant AL extension, so it fits your chart of accounts, item categories, currencies and posting rules rather than forcing a generic schema on you.

The app introduces a Voyage/Shipment Cost document that groups every cost line for an inbound consignment — ocean/air freight, customs duty, insurance, terminal handling, demurrage — and allocates them across the receipt lines by value, weight, quantity or volume. It captures estimated charges at booking and reconciles them against actual vendor invoices, posting the variance to inventory or a cost-difference account. Multi-currency charges are handled with the document or a charge-specific exchange rate so cost is always recorded in your local currency.

Built with AL using table/page extensions and event subscribers on the warehouse receipt and item-charge posting routines, it stays upgrade-safe across Microsoft's monthly releases. Charge headers and lines are exposed through custom API pages (OData v4) for Power BI, Power Automate and Dataverse, and a job queue entry can pull freight-forwarder rates or flag unreconciled voyages. Dedicated permission sets keep landed-cost posting controlled.

ECOSIRE delivers source, a signed per-tenant build, a sandbox validation pass, and post-go-live support.

What you get

Per-tenant AL extension (.app) built for your Business Central version, code-signed and installed on your sandbox then production environment

Full AL source code and the compiled artifact handed to you, with a documented object-ID range registered to avoid collisions

Configuration of charge types, allocation methods and the cost-difference / variance G/L accounts to match your chart of accounts

Custom permission sets imported and assigned to the relevant user groups

Sandbox validation pass: posting a sample voyage through receipt, allocation and reconciliation against your data

Admin and end-user runbook plus a short recorded handover walkthrough, and a defined post-go-live support window

Who this is for

Import / Procurement Manager

Books inbound shipments and needs estimated landed cost at PO time, then a clear variance when the freight and duty invoices actually land — without rekeying figures into spreadsheets.

Inventory & Costing Accountant

Owns item cost accuracy. Wants freight, duty and insurance baked into unit cost on receipt so margins, COGS and inventory valuation are true rather than understated.

Finance Controller / CFO

Needs auditable cost build-up per shipment, reconciled estimates vs. actuals, and Power BI visibility into landed cost trends across voyages and suppliers.

How Landed Cost Management Compares

Criterion	ECOSIRE	Custom Build	Competitor
Shipment/voyage-level grouping of charges across multiple receipts	Included	Partial support	Partial support
Estimated vs. actual landed cost reconciliation with variance posting	Included	Partial support	Partial support
Allocation by value, weight, quantity AND volume	Included	Partial support	Partial support
Multi-currency charge handling with per-charge exchange rates	Included	Partial support	Partial support
Built to your chart of accounts, currencies and posting rules	Included	Included	Not included
Upgrade-safe per-tenant AL extension (no base-app modification)	Included	Partial support	Included
OData/REST API pages for Power BI & Dataverse integration	Included	Partial support	Partial support
Full source code ownership handed to you	Included	Included	Not included
Installed, validated and supported on your environment by the vendor	Included	Partial support	Not included

Frequently Asked Questions about Landed Cost Management

How long does delivery take, since this is built to order?

Typical lead time is 2–4 weeks from requirements sign-off, depending on how many charge types, allocation rules and integrations you need. The flow is: discovery and spec, AL development, install on your sandbox for a validation pass with your own data, then a scheduled production deployment. You get a firm timeline in writing before work starts — there is no instant AppSource download; we build, install and validate it on your environment.

How are support and updates handled after go-live?

Every build includes a post-go-live support window for fixes and questions. Because it ships as a per-tenant extension using table/page extensions and event subscribers (never base-app code edits), it is upgrade-safe across Microsoft's monthly Business Central releases. We re-validate it against major version updates on request, and you hold the full source, so you are never locked in. Ongoing support and enhancement retainers are available.

Does this work on Business Central cloud (SaaS) and on-premises?

Yes. It is delivered as a per-tenant AL extension and installs on Business Central online (SaaS) via the admin centre, or on an on-premises / private-cloud deployment. We confirm your version (and any country localisation) during discovery and build the .app to match so it installs cleanly on your sandbox first.

How is this different from Business Central's built-in item charges?

Native item charges let you assign one charge to a posted document and allocate by equal/amount/weight/value on that document alone. There is no shipment/voyage grouping across multiple receipts, no estimated-vs-actual reconciliation, and limited multi-currency control. This extension adds voyage-level grouping, an estimate-then-reconcile workflow with variance posting, volume-based allocation, and duty/customs capture — while still feeding the standard BC cost engine.

Can the landed cost data feed Power BI and our other systems?

Yes. Voyage headers and allocation lines are exposed through custom API pages (OData v4 / REST), so you can pull them into Power BI, trigger Power Automate flows, or sync to Dataverse and the Power Platform. A job queue entry can also flag unreconciled voyages or import forwarder rate sheets on a schedule.