Two ingredients on the same truck do not necessarily carry the same freight cost
For Finance controllers, CFOs and accounts teams · Compare approaches
TL;DR — what you’ll learn
- Define which receipt charges are included under the business's approved accounting policy.
- Compare weight, value and volume allocation before choosing a rule for each charge.
- Retain receipt links, calculations and corrections when charges arrive late.
- Keep shared receipt-cost allocation distinct from a product's selling-price decision.
A truck brings a heavy, inexpensive ingredient and a small quantity of a costly extract. Dividing freight by invoice value puts most of the transport cost on the extract. Dividing by weight does the opposite. Neither choice should be hidden inside a spreadsheet formula nobody owns.
How should food businesses allocate freight across ingredients on a shared receipt?
Choose an allocation basis that finance approves for the charge, apply it consistently to the relevant receipt lines and retain the calculation. Weight, value and volume produce different answers. The software should show which basis was used and how later corrections were handled.
- 01Identify the chargesReceipt and commercial basis
- 02Choose the approved driverWeight, value or other basis
- 03Reconcile the allocationComplete amounts and unitsDoes the account reconcile?YesPost and reviewNoResolve missing charges or allocation differences before posting.
- 04Post and reviewRetain the allocation evidence
Illustrative information flow. The article explains the evidence, exceptions and responsible decisions. Diagram: NextEdge Labs.
See the effect before choosing the rule
Suppose an illustrative delivery contains 800 kilograms of ingredient A and 200 kilograms of ingredient B, with ₹5,000 freight to allocate. A weight-based allocation assigns ₹4,000 to A and ₹1,000 to B. A value-based allocation can differ substantially. This example demonstrates the arithmetic; the business's accounting policy and the nature of the charge determine the appropriate treatment.
| Record | Why it matters |
|---|---|
| Charge document and reference | Prevents the same charge being applied twice |
| Eligible receipt lines | Defines which goods share the charge |
| Basis and quantities | Makes the calculation reproducible |
| Approval and correction history | Explains changes after the first receipt |
The freight invoice may arrive after the stock moves
Decide how the ERP handles an estimated charge, a later actual invoice and a correction. Some goods may already have been consumed or sold by then. Test that sequence with finance before automating; a report that updates only today's warehouse balance may leave earlier product analysis inconsistent.
ERPNext's landed-cost documentation shows additional charges associated with inventory receipts. Treat it as an example of a supported mechanism, not evidence that every charge belongs in inventory value or that every ERP recalculates in the same way.
Source: Frappe / ERPNext · Additional charges against receipts. Reference details
Compare two bases using the same receipt
Extend the illustrative 1,000-kilogram delivery with purchase values of ₹40,000 for ingredient A and ₹60,000 for ingredient B. The ₹5,000 freight splits ₹4,000 and ₹1,000 by weight, but ₹2,000 and ₹3,000 by value. The total allocation is unchanged. The resulting ingredient costs differ because the rule answers a different question about how the charge should be distributed.
Do not choose the method simply because it produces the preferred product margin. Finance should approve a basis appropriate to the charge and reporting policy. If a freight invoice identifies a specific surcharge for one line or handling condition, preserve that evidence rather than spreading every charge indiscriminately across the entire delivery.
| Ingredient | Weight share | Value share | Freight by weight / value |
|---|---|---|---|
| A | 80% | 40% | ₹4,000 / ₹2,000 |
| B | 20% | 60% | ₹1,000 / ₹3,000 |
A late charge needs a controlled update
A freight invoice may arrive after some received material has been consumed or sold. The system's handling of that later charge depends on its costing configuration and the organisation's accounting policy. Establish the expected behaviour with finance before the integration updates inventory or production costs.
Retain the original receipt, the later charge, the approved allocation and the posting result. If an estimate was used initially, identify how the final invoice replaces or adjusts it so the charge is not counted twice. The reviewer should see both the amount already included and the proposed difference. A repeated invoice upload must find the existing charge record.
Keep the allocation explainable to operations
Purchasing may see an unchanged supplier price while production sees a higher ingredient cost. A small bridge showing purchase price, allocated charges and later adjustments explains that movement. Without it, teams can spend time investigating a recipe variance that actually came from a freight change.
For a pilot, select receipts containing different weights or values and include one correction after partial consumption. Ask finance to reproduce the result from the source documents. The implementation is ready when the totals reconcile, the accounting treatment is approved and the user can explain why each line received its share. A calculation that balances globally but cannot be traced by receipt is incomplete.
Keep automation accountable to the receipt
An integration can collect freight documents, suggest receipt matches and prepare an allocation for review. Ambiguous multi-drop charges should remain unresolved until an owner establishes the scope. Retain the supplier's original references so an auditor or controller can reconstruct the calculation without relying on the model's explanation.
Evaluate the workflow using a shared load, a late charge and a corrected weight. Measure unmatched charges and the effort needed to explain a product-cost change. Speed is useful when it reduces rework; it is not a reason to make an unexplained allocation permanent.
Summary
Landed-cost allocation is reliable when its scope, basis and timing are explicit. The same freight amount can produce different item costs under different methods. Finance should approve the treatment, and the system should preserve enough evidence to reproduce the allocation and any later correction.
What to do next
- Take one mixed receipt and compare its current allocation with an alternative basis.
- Agree the charge scope and allocation policy with finance.
- Test a late charge and a corrected invoice before automating the receipt-cost update.
Compare this workflow with your current setup
Share the step that takes the most manual work, the systems involved and the exceptions your team handles. That gives us a concrete starting point for comparing approaches.
Sources and further reading
Sources checked 15 October 2026. The worked examples and software evaluation suggestions are NextEdge Labs’ editorial analysis.
- Landed Cost VoucherFrappe / ERPNext · Online product documentation, accessed October 2026
Illustrates additional charges associated with inventory receipts. Applicable accounting policies determine treatment and allocation.
Visual credits
AI-generated illustration created for NextEdge Labs; it does not depict a client facility. Workflow diagram by NextEdge Labs. Icons from Lucide (ISC licence).