Define who matches freight evidence to the goods received and who approves its accounting treatment. Keep shipment identifiers available across purchasing, receipt and carrier documents. The connection should flag unmatched or duplicate charges and preserve the allocation basis for review rather than assuming that a carrier invoice belongs entirely to the first purchase order listed.
Understand the decision
A delivery combines several purchase orders and the freight invoice arrives after some material is sold. The buyer, warehouse and accountant see different parts of the shipment. The review should make the matching and allocation decisions explicit before deciding whether configuration or integration is needed.
Work through the requirements
- Link transport evidence to actual receipts
- Approve the allocation basis with finance
- Review unmatched and late-arriving charges
| Record or decision | Why it matters |
|---|---|
| Shipment reference | Joins carrier and receiving evidence |
| Charge allocation | Records the reviewed distribution of cost |
| Unmatched-charge queue | Prevents silent or duplicate posting |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Do not infer an accounting allocation from the order of lines on a freight invoice. Odoo documents landed-cost functionality, but the appropriate configuration and treatment still depend on the business’s valuation method and the transaction being reviewed.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Building materials distribution in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Units of measure ↗Packaging ↗Landed costs ↗