Landed Cost Variance Analysis: Plan vs Actual
Ananya Ploesu · · 2 min read
The short answer
Landed cost variance analysis compares an approved cost scenario with actual shipment and invoice records, then attributes the difference to defined components such as price, currency, freight, duty, insurance or handling. It is useful only when both versions use the same product, quantity, route, currency policy and cost definitions.
What decision should landed cost variance analysis support
The analysis should tell purchasing and finance which assumption changed, whether the change was expected and who should update the next sourcing decision.
Landed Cost Variance Analysis: Landed cost variance analysis compares an approved cost scenario with actual shipment and invoice records, then attributes the difference to defined components such as price, currency, freight, duty, insurance or handling. It is useful only when both versions use the same product, quantity, route, currency policy and cost definitions.
A useful scope starts with the action a named owner will take. It does not start with the largest possible list of fields, sources or features. This keeps the work testable and prevents a technically complete output that nobody can use.
Which inputs and definitions are needed
The input list should be written before implementation. Each input needs an owner, an agreed meaning and a rule for missing or conflicting values.
- Versioned pre-purchase cost scenario
- Purchase order and supplier invoice
- Shipment, freight and insurance records
- Customs duty and broker records
- Currency-rate policy and actual conversion
The items above are scoping categories, not a claim that every project uses every source. Actual inputs depend on the approved use case, access and legal basis.
What does a reviewable method look like
A reviewable method separates collection or calculation from validation and business approval. That separation makes it possible to find where a result changed and who accepted it.
- Align product, quantity, route and currency basis
- Reconcile planned and actual cost components
- Attribute each difference to an agreed variance category
- Review unexplained and repeated differences
- Update assumptions only after owner approval
See how this connects to total import cost monitor.
How should quality and exceptions be reviewed
Quality is not one universal percentage. The right checks depend on the decision and the harm caused by a wrong, late or unexplained result. Agree the definitions before reporting any measure.
| Review area | Question to answer |
|---|---|
| Reconciliation | Do actual records tie to the shipment and order? |
| Attribution | Is each difference assigned once? |
| Materiality | Which variances require action under the agreed rule? |
| Repeatability | Does the same cause recur across shipments? |
Ambiguous cases should be visible rather than forced through the normal path. The reviewer needs the original input, the proposed result and the reason it was flagged.
Which limits and buying questions should be made explicit
A credible plan states what remains with the client and where human judgement is required. It also distinguishes a managed outcome from software access or temporary project support.
- A variance is not automatically an error or recoverable amount
- Missing actual records can create false explanations
- Currency and timing policies must be consistent
- The model should not overwrite historical scenarios after the fact
Ask a provider to show how scope changes, exceptions, quality definitions and ownership will be handled. Ask an internal team the same questions. The better option is the one that can own the full operating method at an acceptable level of effort and risk.
Key takeaways
- Start with a named decision and owner, not a broad technology requirement
- Define inputs, meanings and exception rules before implementation
- Keep collection or calculation separate from review and approval
- Treat quality measures as project-specific definitions, not universal claims
- Document limits and retained client responsibilities before comparing options
Questions buyers ask
What is the first step in landed cost variance analysis?
Name the business decision, its owner and the minimum evidence needed to act. Then define the records, fields, review rules and delivery format around that decision.
Which quality measures should be used?
Use measures tied to the failure modes of the specific workflow, such as coverage, completeness, freshness, unresolved exceptions, reviewer agreement or reconciliation status. Define each measure and its owner before setting a target.
When is human review required?
Human review is appropriate for ambiguous matches, missing evidence, conflicting records, policy-sensitive cases and decisions where the consequence of an error is material. The scope should identify those cases before launch.
Can this start with one category or workflow?
Yes. A narrow first scope makes definitions, exceptions and ownership easier to test. Expansion should follow only when the first output is accepted and the operating method is clear.
How should buyers compare a managed service with software or an internal team?
Compare responsibility for collection, maintenance, matching, quality review, exception handling, delivery and change management. A lower tool price can still require significant internal ownership, while a managed service should make its responsibilities explicit.
One-page checklist
Landed Cost Variance Analysis review checklist
Use this before approving a scope, provider or internal implementation.
Data & AI Lead, DataplexLabs
Works with operations, finance and machine learning teams on data collection, margin analysis and model-ready datasets.
Related reading
Find out where your margin is actually going
Bring one question about pricing, rebates, landed cost or a manual process. We come back with a focused view of what the data can prove.
One business-day response · NDA on request · No newsletter spam.